View Relay "clarke"

Fingerprint: `76DA37526C3DA20A5616FE9E4E1565865FCDF90F` | Operator: c3w.at v3 (32 relays) ✓ Validated | Family: 1 relay | Chaos Computer Club Wien (C3W)... | AS208323 | Austria | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Fast, Stable, Guard (6)
BW Verified: 5/7 BW Auths Measured 736 Mbit/s Median
Stability: Not Overloaded | UP 2d 27m 34s ago | UP 99% (1M)

Reachability: IPv4: 9/9 | v6: 8/8(Directory Auths)
First Seen: 1y 4mo 2d ago
BW Weight: 0.05% of Network | 506 Mbit/s Observed By Relay
Version: 0.4.9.15 Recommended

Issues Detected:

HSDir: uptime below 96 hours : Only 0/9 authorities voted HSDir, though this relay has Fast, Stable and V2Dir
Suggestion: HSDir needs 96 hours of uptime as each authority sees it (MinUptimeHidServDirectoryV2): the time since your relay restarted, or since that authority last failed to reach it if that is shorter. Keep the relay running and reachable.
High consensus weight deviation : Large variation in Consensus Weight values across authorities (see 'Cons Wt' column in Per-Authority Details below)
Suggestion: Consensus weight measurements vary significantly between authorities. This can affect traffic distribution. Ensure stable network connection and consistent bandwidth availability.

Connectivity and Location

Addresses

OR Address: cern.relays.tor.c3w.at
109.70.100.246:80
[2a03:e600:100:c3::10]:80

Reachability (Directory Authorities)

IPv4: 9/9
IPv6: 8/8 (1 don't test)

Location

Country: Austria
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS208323
AS Name: Foundation for Applied Privacy (BGP.tools)
AS Rarity: Rare (score: 2/5, 3.01% consensus weight, 2 operators)

Flags and Eligibility

Current Flags (6): Running, Valid, V2Dir, Fast, Stable, Guard

Eligibility Flag Vote Details

Flag	Metric	Status	Relay Value	Threshold Required
Running	IPv4 Reachability	Meets (9/9 DA)	9/9 authorities reached relay	≥5/9 DA ORPort reachable
Running	IPv6 Reachability	Meets (8/8 DA)	8/8 tested authorities reached relay	≥5/8 tested (majority) (≥5/8 DA)
Valid	Descriptor	Meets (9/9 DA)	9/9 authorities assigned Valid	Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir	DirPort Available	Meets (9/9 DA)	Tunnelled: Yes (no DirPort) (R)	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast	Speed	Meets (9/9 DA)	376.0 Mbit/s – 1.0 Gbit/s (5 DA measured) 80.0 Mbit/s (4 DA relay-reported)	≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
Stable	MTBF	Partial (8/9 DA)	Median: 19.4d (8/9 DA above threshold) Min/Max: 5.0d / 5284.6d (9/9 DA, Voting / Total Eligible)	≥2.4d - 9.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥7616.8d
Stable	Uptime	Below (0/9 DA)	2.0d (R)	≥5.2d - 5.5d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (9/9 DA)	9/9 DA assigned Fast 376.0 Mbit/s – 1.0 Gbit/s (5 DA measured) 80.0 Mbit/s (4 DA relay-reported)	≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Meets (9/9 DA)	9/9 DA assigned Stable	≥2.4d - 9.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥7616.8d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	Uptime	Below (0/9 DA)	2.0d (R)	≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known
Guard	Prereq: Fast	Meets (9/9 DA)	9/9 DA assigned Fast 376.0 Mbit/s – 1.0 Gbit/s (5 DA measured) 80.0 Mbit/s (4 DA relay-reported)	≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Meets (9/9 DA)	9/9 DA assigned Stable	≥2.4d - 9.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥7616.8d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Meets (9/9 DA)	Median: 99.8% (9/9 DA above threshold) Min/Max: 99.2% / 99.9% (9/9 DA, Voting / Total Eligible)	≥98%; dizum: ≥97.86% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 34.8d (9/9 DA above threshold) Min/Max: 9.7d / 38.1d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	376.0 Mbit/s – 1.0 Gbit/s (5 DA measured) 80.0 Mbit/s (4 DA relay-reported)	≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-272.0 Mbit/s) (≥5/9 DA)
Exit	Exit Policy	Below (0/9 DA)	Port 80: No \| Port 443: No (R)	Allows ≥1 /8 on ports 80 AND 443 (≥5/9 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-11-04 17:15:06).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 506.04 Mbit/s
Advertised Bandwidth: 506.04 Mbit/s
Rate Limit: 8.59 Gbit/s
Burst Limit: 8.59 Gbit/s
Total Data: 1.5 PB (5 years)
1mo: 110 TB | 6mo: 718 TB | 1y: 1.3 PB | 5y: 1.5 PB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-04 17:15:06

Measured By: 5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight: 736.0 Mbit/s (median of 5 measurements)
Measured Min / Max: 376.0 Mbit/s / 1.0 Gbit/s
Deviation: 664.0 Mbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0475% of network (97th pctl) | Guard: 0.1046% (96th pctl) | Middle: 0.0343% (88th pctl) | Exit: N/A

History

Throughput and write/read, last 6 months

Uptime and Stability

Uptime Metrics

Current Status: UP 2d 27m 34s ago
Overall Uptime (1M/6M/1Y/5Y): 99.7%/99.8%/99.8%/99.0%
Flag Uptime (1M/6M/1Y/5Y): —/86.6%/87.8%/82.5%
Hibernating: No

Timestamps

First Seen: 1y 4mo 2d ago (2025-07-05 18:00:00)
Last Seen: 1h 15m 22s ago (2026-11-04 17:00:00)
Last Restarted: 2d 27m 34s ago (2026-11-02 17:47:48)
Last Changed Address: 2026-04-15 03:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-04 18:15 UTC. /details snapshot 2026-11-04 17:00:00 UTC (cached 19s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 10h 30m ago).

General Overload (from /details)

Status: No general overload report in available data

File Descriptor Exhaustion (from /bandwidth)

Status: No file-descriptor exhaustion report in available data

Rate Limits (from /bandwidth)

Status: No rate-limit report in available data
Rate Limit: —
Burst Limit: —
Write counter: —
Read counter: —

About these reports and MetricsPort

Allium’s eligibility windows are applied to the reported timestamps: 72 hours for general overload and file-descriptor exhaustion, 24 hours for a rate-limit hit. A report at the cutoff is historical. An older report can remain visible after Onionoo or Allium’s cache still has it. The cutoff does not prove the relay recovered at that moment. Allium caches the bandwidth document for 12 hours by default. The snapshot time is when Onionoo published that document. It is not the relay’s event time, and it is not necessarily the extra-info publication time. Cache age is how old Allium’s copy is.

MetricsPort counters are cumulative. Compare samples, and account for process restarts. A nonzero total alone does not show ongoing activity. Gauges describe current values. An unavailable metric is unknown, not zero. Allium does not have this relay’s MetricsPort readings and does not invent them.

The port below is an example for an endpoint you have already configured. MetricsPort must be enabled with restricted access and must not be exposed publicly. Setup stays in the Tor overload troubleshooting guide.

curl http://127.0.0.1:9035/metrics

History

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-11-04 08:00 UTC

AROI Domain (?): c3w.at
Operator Validation: Validated (32/32 relays)
This Relay: Validated (uri-familyid-ed25519)
Contact: Chaos Computer Club Wien (C3W) email:anonymity[]c3w.at url:https://c3w.at proof:uri-familyid-ed25519 abuse:abuse[]c3w.at mastodon:https://chaos.social/@C3Wien offlinemasterkey:y signingkeylifetime:90 sandbox:y os:debian aesni:y autoupdate:y confmgmt:ansible ciissversion:3

Family Configuration

Family Support: Happy Families (32) — Has family-cert in server descriptor (guide)

Happy Families (family-cert)

Effective Members: 32

1C8C4A0889F248334A9C486BA68770D62E21047E
309C5E8057781B748B79E4CB6F33E5F7D7CF577D
38B0226F4318EEB45D4D6777E18A17B50615F3A5
3EF7794702439CF6610B70FF48EF868458F5D351
4FDCEB0A10F599BE355D465754DD544EB05086A7
5044A5DD5540358D78759CD7E1211F46B11ACCDB
53508DECD9A503C50CA5A41D500367C98C1391F7
6A1B3493EC9D60437C52D32D173023FD21A9A23D
724F4622EA76583AF64614979DB847DD39EEA61B
76DA37526C3DA20A5616FE9E4E1565865FCDF90F (this relay)
7DB78CA3414FD3E938487E83CDEF6C49C57F8943
843BB7CFFD51A4A5DA4A3296F1A1C49ECCEFC45D
89E552CFB28EF96D6E3A8B27037BD897FDD4A700
930A9F95EDD55695CACDC5B245230EA63368450D
9AA56B3478DE9C8350F544DFBCA182CC20E5A733
9E03B94B16FF39EA2019CE7BF5C6C8BBF84CD675
A0EC0C1A78324AB641B7900FD1019A73C4312B0C
A1C47AD5B30D1943D7B62907B448043F1A9DCCC5
A41DCADBD817F6D488F1C763DEFA6BC050C4A27E
A7280CC3C80F69C10C6F971DED2D780EA31F2C4C
B7214D02707DC541AEF1213755E31E691E6A4162
B9B1EDF634226DE80AB753AF5ECFB4EF02936F33
BCB49A51CAB8CF95B37B40370F64E7BFCD512C91
C99B344D0FFFCD1A51657387771F812E250269B5
D12FBEA6247B25C0FCD09D5E123DD59BF943D7BB
D3E106AEE8AF14AE45DCE8E620079D2BAE137B84
D6643771AED9DDAAB31E4F553819757B2E2C76D9
DFA0B9DE5CB1D8E100D552761F1DDD7D1D0E72FD
DFB5CE34FE6F5D9C56377F38E86B3E55FFFA1830
E3BF6104564D424282D1D46B1C34DC94CE212E86
E5A4F065BA4E4CB193E50FFD310BA09788A27856
E8CCA1C61EBA1614BAB6B5CA792BDC687F397B4F

MyFamily (legacy declarations) — none

Software and Version

Platform: Linux — Tor 0.4.9.15 on Linux
Version: 0.4.9.15 — Recommended
Version Status: Recommended

Exit Health & Policy

DNS Health

Not an exit relay — DNS health testing does not apply.

IPv4 Exit Policy Summary

reject: 
  1-65535

IPv6 Exit Policy Summary

None

Full Exit Policy

reject *:*

Last fetch was at Wed, 04 Nov 2026 18:15:22 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-11-04 17:15:06).

Per-Authority Details

Each cell shows: your measured value | authority threshold. Green = meets, red = below. Flags: green = all authorities agree, yellow = partial.

Authority	Running	Valid	Exit	MiddleOnly	BW Scan (Authority)	v4	v6	Flags	Fast (BW\|T)	Guard BW (BW\|Threshold)	Guard WFU (M\|T)	Guard TK (M\|T)	Stable MTBF (M\|T)	Stable Uptime (Relay\|T)	Desc Published	Cons Wt (Authority)
bastet (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	496.0 Mbit/s (M) \| 816.0 Kbit/s	496.0 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	99.8% \| 98%	30.9d \| 8d	19.0d \| 8.4d	2.0d \| 5.2d	2026-11-04 05:47:54	496.0 Mbit/s (M)
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Yes	Valid, V2Dir, Fast, Stable, Guard	736.0 Mbit/s (M) \| 816.0 Kbit/s	736.0 Mbit/s (M) \| 272.0 Mbit/s OR 16.8 Mbit/s	99.8% \| 98%	23.7d \| 8d	15.9d \| 9.4d	2.0d \| 5.5d	2026-11-04 05:47:54	736.0 Mbit/s (M)
dizum (NL)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	80.0 Mbit/s (R) \| 816.0 Kbit/s	80.0 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	99.2% \| 98%	35.3d \| 8d	19.4d \| 6.8d	2.0d \| 5.5d	2026-11-04 05:47:54	80.0 Mbit/s (R)
faravahar (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	80.0 Mbit/s (R) \| 816.0 Kbit/s	80.0 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	99.9% \| 98%	34.8d \| 8d	17.9d \| 6.5d	2.0d \| 5.5d	2026-11-04 05:47:54	80.0 Mbit/s (R)
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	880.0 Mbit/s (M) \| 816.0 Kbit/s	880.0 Mbit/s (M) \| 248.0 Mbit/s OR 16.8 Mbit/s	99.9% \| 98%	37.0d \| 8d	27.6d \| 10.8d	2.0d \| 5.5d	2026-11-04 05:47:54	880.0 Mbit/s (M)
longclaw (US)	Yes	Yes	No	—	Y	Yes	N/T	Running, Valid, V2Dir, Fast, Stable, Guard	80.0 Mbit/s (R) \| 816.0 Kbit/s	80.0 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	99.9% \| 98%	38.1d \| 8d	28.0d \| 10.9d	2.0d \| 5.3d	2026-11-04 05:47:54	80.0 Mbit/s (R)
maatuska (SE)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	80.0 Mbit/s (R) \| 816.0 Kbit/s	80.0 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	99.3% \| 98%	30.7d \| 8d	5.0d \| 2.4d	2.0d \| 5.5d	2026-11-04 05:47:54	80.0 Mbit/s (R)
moria1 (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	376.0 Mbit/s (M) \| 8.4 Mbit/s	376.0 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	99.6% \| 98%	9.7d \| 8d	5284.6d \| 7616.8d	2.0d \| 5.5d	2026-11-04 05:47:54	376.0 Mbit/s (M)
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	1.0 Gbit/s (M) \| 816.0 Kbit/s	1.0 Gbit/s (M) \| 256.0 Mbit/s OR 16.8 Mbit/s	99.9% \| 98%	37.0d \| 8d	27.5d \| 10.7d	2.0d \| 5.5d	2026-11-04 05:47:54	1.0 Gbit/s (M)

N/T = this authority does not test IPv6 • — = not in this vote • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known • Bandwidth source: (M) bandwidth-scanner measurement, (R) relay-reported, (U) unmeasured, counted as 0

Bandwidth Values Explained:
Measured (M) = An authority's bandwidth-scanner measurement of your relay (Measured= in its vote). An authority that has one uses it for the Fast and Guard flags, and the consensus weight is the median of these measurements when 3 or more authorities have one.
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (Bandwidth= in every vote). An authority without a measurement uses it for flags, unless it has measurements for enough other relays (ignoring-advertised-bws=1); then your relay counts as 0 (U). It sets the consensus weight only when fewer than 3 authorities measured the relay, capped at 20 KB/s (maxunmeasuredbw) while 3 or more authorities publish measurements.
Not published = The authority has no measurement of your relay in its vote and ignores relay-reported bandwidth, yet it voted Fast or its vote has no measurements at all: it judges your relay by a measurement kept from an earlier bandwidth file (0 if none), which its vote doesn't show.
Why different? A low measurement means the bandwidth scanners see your relay underperforming compared with other relays that report a similar speed. Votes list both values in kilobytes per second. Rules: Assigning flags in a vote, Computing a consensus.

Stable Uptime (Two Data Sources):
Relay Uptime = From Onionoo API (last_restarted field). Self-reported uptime from descriptor. Same value for all authorities.
Authority Threshold = From CollecTor vote files (flag-thresholds stable-uptime). Each authority may have different thresholds.
Why two sources? Vote files contain authority thresholds but not per-relay uptime values. Onionoo aggregates relay descriptors which include uptime.

View Relay "clarke"

Fingerprint: 76DA37526C3DA20A5616FE9E4E1565865FCDF90F | Operator: c3w.at v3 (32 relays) ✓ Validated | Family: 1 relay | Chaos Computer Club Wien (C3W)... | AS208323 | Austria | Linux

Addresses

Reachability (Directory Authorities)

Location

Autonomous System

Eligibility Flag Vote Details

Capacity (Relay Reported)

Measurement (Directory Authority Verified)

History

Uptime Metrics

Timestamps

General Overload (from /details)

File Descriptor Exhaustion (from /bandwidth)

Rate Limits (from /bandwidth)

History

Operator Identity

Family Configuration

Full Exit Policy

Fingerprint: `76DA37526C3DA20A5616FE9E4E1565865FCDF90F` | Operator: c3w.at v3 (32 relays) ✓ Validated | Family: 1 relay | Chaos Computer Club Wien (C3W)... | AS208323 | Austria | Linux