View Relay "Zurich"
Fingerprint: 0DBDDF93345A9D1368FA64BDFA495562D0505DC5 |
Operator: alpenwall.codeberg.page v3
(65 relays)
✓ Validated
⚠ this relay: Misconfigured|
Family: 34 relays
|
Alpenwall email:alpenwall[]proton.me... |
AS29222
|
Switzerland
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- BW Verified
- 5/7 BW Auths Measured 464 Mbit/s Median
- Stability
- Overloaded | UP 3d 4h 58m ago | UP 99% (1M)
- Reachability
- IPv4: 9/9 | v6: 8/8(Directory Auths)
- BW Weight
- 0.03% of Network | 278 Mbit/s Observed By Relay
- Version
- 0.4.9.15 Recommended
Issues Detected:
-
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. -
General Overload Active
: Relay reported general overload at 2026-11-01 14:00 UTC. Reported timestamps use hour precision, so the displayed minute is not an exact incident time. The flag does not identify which trigger fired. Investigation paths are Tor's internal OOM handling, dropped ntor onionskins, and TCP port exhaustion.
Suggestion: Inspect CPU and memory with htop, Tor service logs, host or container memory headroom, and the effective MaxMemInQueues. When the process was killed or restarted, check kernel OOM logs separately. A kernel OOM kill is a different mechanism from Tor freeing memory itself. MetricsPort: tor_relay_load_oom_bytes_total. Broken down by subsys. An increase measures bytes freed by Tor’s internal OOM handling. It is not an invocation count and it is not proof of a kernel OOM kill. Review Tor’s onionskin and drop messages, and whether the CPU is saturated or contended. The general-overload flag does not say this trigger fired. MetricsPort: tor_relay_load_onionskins_total{type="ntor",action="dropped"} and {type="ntor_v3",action="dropped"}. Compare each with the matching action="processed" series. Inspect both supported handshake types. Review Tor logs, socket usage, and the host’s ephemeral-port allocation. On Linux, ss -s and reading net.ipv4.ip_local_port_range are useful starting checks. MetricsPort: tor_relay_load_tcp_exhaustion_total. An increase records additional exhaustion events. See the Tor overload troubleshooting guide.
Notes:
- Guard: WFU near threshold: Weighted Fractional Uptime is just above the Guard bar at dizum (98.0%, need ≥97.84099999999999%) and maatuska (98.2%, need ≥98%). Recent downtime weighs more than older downtime. Avoid restarts while it is this close; a short outage can drop the Guard flag.
Suggestion: Recent downtime weighs more than older downtime. Minimize restarts, use systemd Restart=always, and watch for OOM kills until each authority has more room above its own guard-wfu.
Addresses
- OR Address
-
ov-1ff802.infomaniak.ch
83.228.196.41:443
[2001:1600:13:101::5db]:443
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- 8/8 (1 don't test)
Location
- Country
-
Switzerland
- Interactive Map
- View in RouteFluxMap
Eligible Flags (7):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 8/9 | HSDir: 8/9 | Guard: 8/9 | Exit: 0/9
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 |
| 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) | 296.0 Mbit/s – 576.0 Mbit/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 | Below (2/9 DA) | Median: 7.8d (4/9 DA above threshold) Min/Max: 1.8d / 7530.4d (9/9 DA, Voting / Total Eligible) |
≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
| Uptime | Below (0/9 DA) | 3.2d (R) | ≥5.2d - 5.3d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 296.0 Mbit/s – 576.0 Mbit/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 (8/9 DA) | 8/9 DA assigned Stable | ≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Partial (8/9 DA) | 3.2d (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 296.0 Mbit/s – 576.0 Mbit/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 (8/9 DA) | 8/9 DA assigned Stable | ≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
|
| 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.5% (9/9 DA above threshold) Min/Max: 98.0% / 99.7% (9/9 DA, Voting / Total Eligible) |
≥98%; dizum: ≥97.84099999999999% (≥5/9 DA) | |
| Time Known | Meets (9/9 DA) | Median: 14.3d (9/9 DA above threshold) Min/Max: 9.9d / 17.5d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Meets (9/9 DA) | 296.0 Mbit/s – 576.0 Mbit/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 12:45:10).
Capacity (Relay Reported)
- Observed Bandwidth
- 278.40 Mbit/s
- Advertised Bandwidth
- 278.40 Mbit/s
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
-
627 TB
(1 year)
1mo: 130 TB | 6mo: 613 TB | 1y: 627 TB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-04 12:45:10
- Measured By
-
5/7
Bandwidth Authorities
Not measured by: faravahar, longclaw - Consensus Weight
- 464.0 Mbit/s (median of 5 measurements)
- Measured Min / Max
- 296.0 Mbit/s / 576.0 Mbit/s
- Deviation
- 280.0 Mbit/s [Warning] High variation
Network Participation:
Consensus Weight:
0.0293% of network
(91th pctl)
|
Guard:
0.0615% (86th pctl) |
Middle:
0.0231% (82th pctl) |
Exit:
N/A
History
Uptime Metrics
- Current Status
- UP 3d 4h 58m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 99.3%/99.7%/97.4%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- —/97.3%/87.0%/—
- Hibernating
- No
Timestamps
- First Seen
- 6mo 3w 6d ago (2026-04-11 00:00:00)
- Last Seen
- 2h 45m 39s ago (2026-11-04 11:00:00)
- Last Restarted
- 3d 4h 58m ago (2026-11-01 08:47:25)
- Last Changed Address
- 2026-04-11 00:00:00
[Warning] OVERLOADED
— General overload at 2026-11-01 14:00 UTC
Evaluated 2026-11-04 13:45 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 42s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 6h ago).
Reported timestamps use hour precision, so the displayed minute is not an exact incident time.
General Overload (from /details)
- Status
- Reported
- When
- 2026-11-01 14:00 UTC (2 days ago)
The general-overload flag does not say which trigger fired. Possible paths are Tor’s internal memory handling, dropped ntor handshakes, and TCP port exhaustion. Allium treats a valid report as eligible for 72 hours; that cutoff is not proof the relay recovered then.
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
- —
What to check
-
Tor internal memory pressure
Inspect CPU and memory with htop, Tor service logs, host or container memory headroom, and the effective MaxMemInQueues. When the process was killed or restarted, check kernel OOM logs separately. A kernel OOM kill is a different mechanism from Tor freeing memory itself.MetricsPort:
tor_relay_load_oom_bytes_total— Broken down by subsys. An increase measures bytes freed by Tor’s internal OOM handling. It is not an invocation count and it is not proof of a kernel OOM kill. -
ntor handshake pressure
Review Tor’s onionskin and drop messages, and whether the CPU is saturated or contended. The general-overload flag does not say this trigger fired.MetricsPort:
tor_relay_load_onionskins_total{type="ntor",action="dropped"} and {type="ntor_v3",action="dropped"}— Compare each with the matching action="processed" series. Inspect both supported handshake types. -
TCP port exhaustion
Review Tor logs, socket usage, and the host’s ephemeral-port allocation. On Linux, ss -s and reading net.ipv4.ip_local_port_range are useful starting checks.MetricsPort:
tor_relay_load_tcp_exhaustion_total— An increase records additional exhaustion events.
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 Identity
Source: AROI Validation API — 2026-11-04 04:00 UTC
- AROI Domain (?)
- alpenwall.codeberg.page
- Operator Validation
- Validated (49/65 relays)
- This Relay
-
Unvalidated
Error: URI-FamilyID: HTTP error connection timed out after 5s for URL: https://alpenwall.codeberg.page/.well-known/tor-relay/ed25519-family-id.txt - Contact
- Alpenwall email:alpenwall[]proton.me pgp:11F9B9631297C6E8A6ABAEB20F35FDA0683553A3 url:alpenwall.codeberg.page proof:uri-familyid-ed25519 hoster:www.infomaniak.com cost:3.19EUR uplinkbw:500 trafficacct:unmetered memory:2048 offlinemasterkey:n os:debian autoupdate:y confmgmt:manual ciissversion:3
Family Configuration
- Family Support
- Both — Happy Families (65 / 100%) and MyFamily (0 / 0%) | View Full Family (34)
Happy Families (family-cert)
- Effective Members: 65
00588E8ED6B571AE3D4F002300793406DD7A62B6 006D9484FB7ABCB2423DC4F7557893C452119347 0530443B234BECD95A0610D4F6221601949C5019 06F3E28948A3C6E2BA8B0C7D109C7BFC12D69DC5 079D0984072F7E288CDF42CA30143BC6C1CD8AB8 0D3D4CBD1AED41A771DBEA209A6412BEB6C403F9 0DBDDF93345A9D1368FA64BDFA495562D0505DC5 (this relay) 173A78C6DC204029362F9C555EC1F36467F01989 182F4078EC6DFF341ABA5B7301C3E7AFF3159BF4 1E5DEC04CD9ADEE0000C14107B3745C800FB1AA6 2102D92A37EC6EE58E59CACC58DC76130697AE6A 21CE56BE0FEBB7D26CA6085C48CF37F2D778D195 245875388F7334CE4A8A9B976B3658E1905D4B1B 2501A5C7F00A7C8877BE81F97504036173667417 251E8F651B19D4B88A90E192C876EA165EF0C984 2A1DE3F65F28AA9785FFDC229D8605DC7A70AD73 2A5AF3CAFA5C7904ADCF7B209EB85D6E8BE256F3 2B6FBBA678C38EF7DF374BD44B76C26B55A8641B 2E3F15298298A8E262472CD3D55D5D5453AAD289 34AFA4DF32394385C182D9B3BEBD4967F33B43C8 42CCF0C07564FC3AF7245C66318CD5347C16706F 43967C8930CDFDA53901D7A3653266FF907403D8 43F78AD981890ABAB79280D930C8D580641CA547 477A080784134FEC0D242047ABB39459F852F44D 48296B5E1A1A341ED43A80BABC936D03438094BB 4A12055C4C8936FD10DC4D9BCD169B5FC7CBCFD2 4DEB0CF64A573E2BA017A74B0BAAD7AB75D30504 54CC34EE7EE45EC335C7E24CC3EBC5547B7D5229 5D8C96BEEFA8D1D2BD43E23B311B69864AC3DD83 68225F5A4EC2EC64E5C4F198581FBDBB01217620 6B90BDCF9C5896048FCE8C968A72E795816B8475 6D6D462B5EC0EF7F1205151ACCD9058E5C1AE8DC 7285BCE8034736BB4AF56F44DFAEAB286FF782F6 7A011DE06AEDB840ECB01F6E5653B214342325FF 7ADC512212B7C99856D5AA98BB9142169C238533 7C2D734D485609B9B6874BEDCDB9E4942C4C9A8C 7EA759ABE1D95C60D96B8A4F141A5BD4AF1815CB 806FE0598CE367C7E9EE740808AC855DA152B1C2 87AB127305A87C406A0CCA40DB769436BA051B22 8B23688C0ED86684CCABB58AAFEC505014548194 8FB99E409E74ABD13DE3E1D2A0C6F2C4C26BB23B 911F66D113ACE0D892100B266A104FE2BE869231 A1D0A2B517B8078CE9840875D9E7455F991FAB3E A8348F0A0EFD3D5400DFA6CB1EA906CE2E959DA2 A9083DE18D737BBC8DA4FC621457400BC5A53831 B2DF2DB3FE071F54508090A0D21B8835B4C38AF6 B3217A2C58F325F451CA4C3255F815C35F7B9CA7 BA2AD0818B8D764F645A4116343BB71406D9C931 BD727135E1453E16053A0382BF3CA0C3313B82FC BFE3996727ED30E4B7444F144304A2515617E1DA C390DBDBCDA2F9EE2A7FBC3FC8EE30C140415764 C3E5373ECB6DF586313A6D5F2ECC78B650B83B50 CF2C63AF47595B96CCF5CFC23C8C95826F9B9B53 D19182132D4BB4A35FB619278301976EBFE88F76 D29BE60D0F2EBFBD435719D1E1AFD4D488E24AC6 D3639E6F2E188229E9ED91020C0043D4DB267A0F E2354C0B366C6D4262EAA1EB509AECF5AF4ED130 EA71DBFA346E000640658E762EC627C1A69D3A23 F0B3F6F3063B7FE1BE95F45587FCCF0E2CA42F84 F25E5739789E65FE488F5CE78B4686BFF8A9AF84 F4893B5389FEDFB8116F367AD1E15AA469730028 F88373683DF18A8CA0229B80CD927FF8091E9568 F92D58C1F7422A31F694221385569054535FF108 FA01576E6B5CB77DF2330DEC999A7259BA3A48A3 FB6D60C8B414A3FAE729D7EB34DC3BFC09020069
MyFamily (legacy declarations)
- Effective Members: 0
- none
- Alleged Members: 13
-
(they don't list you back)
0C1384BD0ABBC06E25B3CAADA4D31EB6D6256532 (not in the network) 149266A3EC0986A43BC2C0C5EC50F91622270E66 (not in the network) 1721F504E4581C4A218173562EDEBC38BF48774B (not in the network) 25DCFDAF83FC42292CA3CCEFD5B11A9DEED0C987 (not in the network) A6F3B90879F95EF4C8D51438AB88802D9475C366 (not in the network) BCF5A4572230296086FC2036E3B8D15F92044CB4 (not in the network) BCFD389EB6D6E01C581BB221BA7F597D9BD16FAF (not in the network) D01049AC9178252D23EADF2323BB44CE2647774A (not in the network) D3639E6F2E188229E9ED91020C0043D4DB267A0F D5D28B5AC08022E0E760DFBFE341C83FC3FABE80 (not in the network) E339970C7021BB066F033083DC7F402FC95CFCFC (not in the network) E85A2E8BF9A35A6FC5F31F9E208B0462AFAF151E (not in the network) FC7373EC8E1AFAA56F53A9A1A68F1063DCBC42F9 (not in the network)
- Indirect Members: 18
-
(they list you, you don't list them)
006D9484FB7ABCB2423DC4F7557893C452119347 21CE56BE0FEBB7D26CA6085C48CF37F2D778D195 245875388F7334CE4A8A9B976B3658E1905D4B1B 2501A5C7F00A7C8877BE81F97504036173667417 251E8F651B19D4B88A90E192C876EA165EF0C984 2A5AF3CAFA5C7904ADCF7B209EB85D6E8BE256F3 42CCF0C07564FC3AF7245C66318CD5347C16706F 48296B5E1A1A341ED43A80BABC936D03438094BB 4A12055C4C8936FD10DC4D9BCD169B5FC7CBCFD2 5D8C96BEEFA8D1D2BD43E23B311B69864AC3DD83 806FE0598CE367C7E9EE740808AC855DA152B1C2 BFE3996727ED30E4B7444F144304A2515617E1DA D19182132D4BB4A35FB619278301976EBFE88F76 E2354C0B366C6D4262EAA1EB509AECF5AF4ED130 F0B3F6F3063B7FE1BE95F45587FCCF0E2CA42F84 F25E5739789E65FE488F5CE78B4686BFF8A9AF84 F92D58C1F7422A31F694221385569054535FF108 FA01576E6B5CB77DF2330DEC999A7259BA3A48A3
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Wed, 04 Nov 2026 13:45:39 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-04 12:45:10).
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, HSDir, Guard | 296.0 Mbit/s (M) | 816.0 Kbit/s | 296.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 99.3% | 98% | 14.2d | 8d | 5.9d | 8.4d | 3.2d | 5.2d | 2026-11-04 08:47:41 | 296.0 Mbit/s (M) |
| dannenberg (DE) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Guard | 464.0 Mbit/s (M) | 816.0 Kbit/s | 464.0 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s | 99.7% | 98% | 17.4d | 8d | 9.4d | 9.3d | 3.2d | 5.3d | 2026-11-04 08:47:41 | 464.0 Mbit/s (M) |
| dizum (NL) | Yes | Yes | No | — | N | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Guard | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 98.0% | 98% | 14.9d | 8d | 7.1d | 6.7d | 3.2d | 5.3d | 2026-11-04 08:47:41 | 80.0 Mbit/s (R) |
| faravahar (US) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, 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.6% | 98% | 13.9d | 8d | 5.8d | 6.5d | 3.2d | 5.3d | 2026-11-04 08:47:41 | 80.0 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Guard | 576.0 Mbit/s (M) | 816.0 Kbit/s | 576.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s | 99.5% | 98% | 14.3d | 8d | 7.8d | 10.8d | 3.2d | 5.3d | 2026-11-04 08:47:41 | 576.0 Mbit/s (M) |
| longclaw (US) | Yes | Yes | No | — | Y | Yes | N/T | Running, Valid, V2Dir, Fast, Stable, HSDir, 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.6% | 98% | 15.4d | 8d | 9.4d | 10.9d | 3.2d | 5.3d | 2026-11-04 08:47:41 | 80.0 Mbit/s (R) |
| maatuska (SE) | Yes | Yes | No | — | N | Yes | Yes | Running, Valid, V2Dir, Fast | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 98.2% | 98% | 12.0d | 8d | 1.8d | 2.4d | 3.2d | 5.3d | 2026-11-04 08:47:41 | 80.0 Mbit/s (R) |
| moria1 (US) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Guard | 312.0 Mbit/s (M) | 8.4 Mbit/s | 312.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 99.5% | 98% | 9.9d | 8d | 7530.4d | 7607.5d | 3.2d | 5.3d | 2026-11-04 08:47:41 | 312.0 Mbit/s (M) |
| tor26 (AT) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Guard | 464.0 Mbit/s (M) | 816.0 Kbit/s | 464.0 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s | 99.7% | 98% | 17.5d | 8d | 9.8d | 10.6d | 3.2d | 5.3d | 2026-11-04 08:47:41 | 464.0 Mbit/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 (
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (
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.
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.
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.