View Relay "Lungutor"

Fingerprint: E17F1B9520FA402BFC01F26AD364B05586B207DD | Family: 1 relay | hi AT lungustefan DOT com | AS205941 | United States of America | Linux

Health Status

Consensus
In Consensus (10/10 Directory Auths)
Flags
Running, Valid, V2Dir, Fast, Exit (5)
DNS Health
Healthy (8.6s, 3rd percentile) (via exitdnshealth.1aeo.com)
BW Verified
4/8 BW Auths Measured 36 Mbit/s Median
Stability
Overloaded | UP 6d 2h 12m ago | UP 70% (1M)
Reachability
IPv4: 10/10 | v6: 9/9(Directory Auths)
First Seen
6mo 1w 1d ago
BW Weight
0.00% of Network | 54 Mbit/s Observed By Relay
Version
0.4.9.14 Not Recommended
Issues Detected:
  • Guard: requires Stable flag : Guard flag requires having the Stable flag first
    Suggestion: Get Stable flag by maintaining consistent uptime. Stable requires uptime and MTBF at or above network median (typically 2-3 weeks of stable running).
  • Guard: WFU below threshold : 2/10 authorities meet guard-wfu (≥98%; maatuska: ≥97.051%; 6 needed). dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 measured 78.2%–83.8%.
    Suggestion: WFU measures recent uptime (recent downtime weighs more heavily). To improve: 1) Minimize restarts, 2) Use systemd with Restart=always, 3) Monitor for OOM kills, 4) Schedule updates during low-traffic periods.
  • Not eligible for Stable flag : 2/10 authorities meet Stable (uptime or MTBF at or above their own median; 6 needed). 5947BB57, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska and tor26 do not.
    Suggestion: Stable flag requires uptime/MTBF at or above network median. Keep your relay running continuously for 2-3 weeks. Avoid restarts. Use reliable hardware and network connection.
  • HSDir: requires Stable flag : HSDir flag requires having the Stable flag first
    Suggestion: Get Stable flag by maintaining consistent uptime. Stable requires uptime and MTBF at or above network median (typically 2-3 weeks of stable running). Avoid restarts.
  • 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.
  • StaleDesc flag assigned : Relay descriptor is older than 18 hours
    Suggestion: Your relay is not publishing fresh descriptors. Check: 1) Tor process is running, 2) Network connectivity, 3) Clock is synchronized (NTP). Restart Tor if needed.
  • Tor version not recommended : Running Tor version 0.4.9.14 which is not on the recommended list.
    Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.
  • General Overload Active : Relay reported general overload at 2026-11-14 21: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:
  • Bandwidth authority measurements below majority: 4/8 bandwidth authorities measured this relay (majority is 5).
    Suggestion: Some bandwidth authorities cannot measure your relay. This may be temporary or due to geographic routing. Monitor over 24-48 hours. If persistent, check firewall rules and ensure ORPort is accessible from various locations.

Connectivity and Location

Addresses
OR Address
tor1.ams.as205941.org
142.249.174.14:9090
[2a13:c8c4:5a4::1]:9090
Exit Address
142.249.174.14
Reachability (Directory Authorities)
IPv4
10/10
IPv6
9/9 (1 don't test)
Location
Country
United States of America United States of America
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS205941
AS Name
Lungu Stefan Gabriel (BGP.tools)
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (5): Running: 10/10 | Valid: 10/10 | V2Dir: 10/10 | Fast: 9/10 | Stable: 1/10 | HSDir: 0/10 | Guard: 0/10 | Exit: 10/10
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (10/10 DA) 10/10 authorities reached relay ≥6/10 DA ORPort reachable
IPv6 Reachability Meets (9/9 DA) 9/9 tested authorities reached relay ≥5/9 tested (majority) (≥5/9 DA)
Valid Descriptor Meets (10/10 DA) 10/10 authorities assigned Valid Not blacklisted + valid descriptor (≥6/10 DA)
V2Dir DirPort Available Meets (10/10 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥6/10 DA)
Fast Speed Partial (9/10 DA) 13.6 Mbit/s – 120.0 Mbit/s (4 DA measured)
47.8 Mbit/s – 54.3 Mbit/s (5 DA relay-reported)
0 bit/s (1 DA unmeasured, counted as 0)		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥6/10 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (2/10 DA) Median: 0.3d (1/10 DA above threshold)
Min/Max: 0.0d / 19996.2d (10/10 DA, Voting / Total Eligible)		 ≥0.0d - 8.7d (varies) (≥6/10 DA)
[Stricter] moria1: ≥10768.2d
Uptime Meets (10/10 DA) 6.1d (R) ≥2.0d - 2.4d (varies) (≥6/10 DA)
[Stricter] 5947BB57: ≥5.9d
HSDir Prereq: Fast Meets (9/10 DA) 9/10 DA assigned Fast
13.6 Mbit/s – 120.0 Mbit/s (4 DA measured)
47.8 Mbit/s – 54.3 Mbit/s (5 DA relay-reported)
0 bit/s (1 DA unmeasured, counted as 0)		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥6/10 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/10 DA) 1/10 DA assigned Stable ≥0.0d - 8.7d (varies) (≥6/10 DA)
[Stricter] moria1: ≥10768.2d
Prereq: V2Dir Meets (10/10 DA) 10/10 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥6/10 DA)
Uptime Partial (8/10 DA) 6.1d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥6/10 DA)
[Stricter] moria1: ≥98% WFU and ≥9.7d Time Known
Guard Prereq: Fast Meets (9/10 DA) 9/10 DA assigned Fast
13.6 Mbit/s – 120.0 Mbit/s (4 DA measured)
47.8 Mbit/s – 54.3 Mbit/s (5 DA relay-reported)
0 bit/s (1 DA unmeasured, counted as 0)		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥6/10 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/10 DA) 1/10 DA assigned Stable ≥0.0d - 8.7d (varies) (≥6/10 DA)
[Stricter] moria1: ≥10768.2d
Prereq: V2Dir Meets (10/10 DA) 10/10 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥6/10 DA)
WFU Below (2/10 DA) Median: 83.3% (2/10 DA above threshold)
Min/Max: 78.2% / 100.0% (10/10 DA, Voting / Total Eligible)		 ≥98%; maatuska: ≥97.051% (≥6/10 DA)
Time Known Meets (10/10 DA) Median: 11.4d (10/10 DA above threshold)
Min/Max: 0.0d / 11.5d (10/10 DA, Voting / Total Eligible)		 ≥8 days; 5947BB57: ≥37 minutes 34 seconds; E30CF7B3: ≥2 days 13 minutes 8 seconds (≥6/10 DA)
Bandwidth Partial (8/10 DA) 13.6 Mbit/s – 120.0 Mbit/s (4 DA measured)
47.8 Mbit/s – 54.3 Mbit/s (5 DA relay-reported)
0 bit/s (1 DA unmeasured, counted as 0)		 ≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-256.0 Mbit/s) (≥6/10 DA)
Exit Exit Policy Meets (10/10 DA) Port 80: Yes | Port 443: Yes (R) Allows ≥1 /8 on ports 80 AND 443 (≥6/10 DA)

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

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
54.32 Mbit/s
Advertised Bandwidth
54.32 Mbit/s
Rate Limit
838.86 Mbit/s
Burst Limit
1.01 Gbit/s
Total Data
192 TB (1 year)
1mo: 1.1 TB | 6mo: 192 TB | 1y: 192 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-14 22:45:06

Measured By
4/8 Bandwidth Authorities
Not measured by: 5947BB57, E30CF7B3, faravahar, longclaw
Consensus Weight
36.8 Mbit/s (median of 4 measurements)
Measured Min / Max
13.6 Mbit/s / 120.0 Mbit/s
Deviation
106.4 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0026% of network (31th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0082% (9th pctl)
History
Throughput and write/read, last 6 months Throughput and write/read, last year Throughput and write/read, last 30 days
1M 6M 1Y

Uptime and Stability

Uptime Metrics
Current Status
UP 6d 2h 12m ago
Overall Uptime (1M/6M/1Y/5Y)
70.7%/85.9%/85.9%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (70.7%/85.9%/85.9%/0.0%)
Hibernating
No
Timestamps
First Seen
6mo 1w 1d ago (2026-05-10 20:00:00)
Last Seen
1h 15m 27s ago (2026-11-14 22:00:00)
Last Restarted
6d 2h 12m ago (2026-11-08 21:02:57)
Last Changed Address
2026-11-08 22:00:00
[Warning] OVERLOADED — General overload at 2026-11-14 21:00 UTC

Evaluated 2026-11-14 23:15 UTC. /details snapshot 2026-11-14 22:00:00 UTC (cached 28s ago). /bandwidth snapshot 2026-11-14 20:00:00 UTC (cached 1h 30m 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-14 21:00 UTC (2 hours 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
Uptime, last 6 months Uptime, last year Uptime, last 30 days
1M 6M 1Y

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-11-14 14:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
hi AT lungustefan DOT com
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
E17F1B9520FA402BFC01F26AD364B05586B207DD (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

Platform
Linux — Tor 0.4.9.14 on Linux
Version
0.4.9.14 — Not Recommended
Version Status
Obsolete — Update urgently. See torproject.org/download

Exit Health & Policy

DNS Health
Status
Healthy (avg. 8.6s, 3rd percentile)
Query Domain
ded9b99674b948e7b121cd078413a254.e17f1b95.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Upstream Resolver
Cloudflare (public resolver)
Cloudflare 100% (~55 estimated queries)
Cross-Validation
2/2 instances succeeded
First Hop
bludicapra (IT) 4FCA270A887D2BB0666A05EF45B393C7A6B13214
Exit Address Used
142.249.174.14
Per-Instance Results
Cross Validation Attempt 1: Success, 8.1s (cv3_w4)
Cross Validation Attempt 2: Success, 9.0s (cv4_w4)
Tested: 2026-11-14 20:23:53 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  20-23
  43
  53
  79-81
  88
  110
  143
  194
  220
  389
  443
  464-465
  531
  543-544
  554
  563
  587
  636
  706
  749
  853
  873
  902-904
  981
  989-995
  1194
  1220
  1293
  1500
  1533
  1677
  1723
  1755
  1863
  2082-2083
  2086-2087
  2095-2096
  2102-2104
  3128
  3389
  3690
  4321
  4643
  5050
  5190
  5222-5223
  5228
  5900
  6660-6669
  6679
  6697
  8000
  8008
  8074
  8080
  8082
  8087-8088
  8232-8233
  8332-8333
  8443
  8888
  9418
  9999-10000
  11371
  19294
  19638
  50002
  64738
IPv6 Exit Policy Summary
accept: 
  20-23
  43
  53
  79-81
  88
  110
  143
  194
  220
  389
  443
  464-465
  531
  543-544
  554
  563
  587
  636
  706
  749
  853
  873
  902-904
  981
  989-995
  1194
  1220
  1293
  1500
  1533
  1677
  1723
  1755
  1863
  2082-2083
  2086-2087
  2095-2096
  2102-2104
  3128
  3389
  3690
  4321
  4643
  5050
  5190
  5222-5223
  5228
  5900
  6660-6669
  6679
  6697
  8000
  8008
  8074
  8080
  8082
  8087-8088
  8232-8233
  8332-8333
  8443
  8888
  9418
  9999-10000
  11371
  19294
  19638
  50002
  64738
Full Exit Policy
reject 0.0.0.0/8:*
reject 169.254.0.0/16:*
reject 127.0.0.0/8:*
reject 192.168.0.0/16:*
reject 10.0.0.0/8:*
reject 172.16.0.0/12:*
reject 142.249.174.14:*
accept *:20-21
accept *:22
accept *:23
accept *:43
accept *:53
accept *:79
accept *:80-81
accept *:88
accept *:110
accept *:143
accept *:194
accept *:220
accept *:389
accept *:443
accept *:464
accept *:465
accept *:531
accept *:543-544
accept *:554
accept *:563
accept *:587
accept *:636
accept *:706
accept *:749
accept *:853
accept *:873
accept *:902-904
accept *:981
accept *:989-990
accept *:991
accept *:992
accept *:993
accept *:994
accept *:995
accept *:1194
accept *:1220
accept *:1293
accept *:1500
accept *:1533
accept *:1677
accept *:1723
accept *:1755
accept *:1863
accept *:2082
accept *:2083
accept *:2086-2087
accept *:2095-2096
accept *:2102-2104
accept *:3128
accept *:3389
accept *:3690
accept *:4321
accept *:4643
accept *:5050
accept *:5190
accept *:5222-5223
accept *:5228
accept *:5900
accept *:6660-6669
accept *:6679
accept *:6697
accept *:8000
accept *:8008
accept *:8074
accept *:8080
accept *:8082
accept *:8087-8088
accept *:8232-8233
accept *:8332-8333
accept *:8443
accept *:8888
accept *:9418
accept *:9999
accept *:10000
accept *:11371
accept *:19294
accept *:19638
accept *:50002
accept *:64738
reject *:*

Last fetch was at Sat, 14 Nov 2026 23:15:27 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-11-14 22:45: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)
5947BB57 Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 47.8 Mbit/s (R) | 816.0 Kbit/s 47.8 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.0d | 0d 0.0d | 0.0d 6.1d | 5.9d 2026-11-12 15:05:42 47.8 Mbit/s (R)
E30CF7B3 Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 184.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 2.1d | 2d 2.1d | 2.1d 6.1d | 2.5d 2026-11-14 21:07:55 54.3 Mbit/s (R)
dannenberg (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 120.0 Mbit/s (M) | 816.0 Kbit/s 120.0 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 81.9% | 98% 11.4d | 8d 0.3d | 8.7d 6.1d | 2.2d 2026-11-14 21:07:55 120.0 Mbit/s (M)
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 54.3 Mbit/s (R) | 816.0 Kbit/s 54.3 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 83.4% | 98% 11.5d | 8d 0.4d | 6.7d 6.1d | 3.1d 2026-11-14 21:07:55 54.3 Mbit/s (R)
faravahar (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 54.3 Mbit/s (R) | 816.0 Kbit/s 54.3 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 83.2% | 98% 11.4d | 8d 0.3d | 6.8d 6.1d | 2.3d 2026-11-14 03:07:15 54.3 Mbit/s (R)
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 96.0 Mbit/s (M) | 816.0 Kbit/s 96.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 83.5% | 98% 11.5d | 8d 0.4d | 8.9d 6.1d | 2.2d 2026-11-14 21:07:55 96.0 Mbit/s (M)
longclaw (US) Yes Yes Yes — Y Yes N/T Valid, V2Dir, Fast, Exit, StaleDesc 54.3 Mbit/s (R) | 816.0 Kbit/s 54.3 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 81.3% | 98% 11.4d | 8d 0.3d | 9.5d 6.1d | 2.4d 2026-11-14 03:07:15 [Stale] 54.3 Mbit/s (R)
maatuska (SE) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 54.3 Mbit/s (R) | 816.0 Kbit/s 54.3 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 78.2% | 97% 10.6d | 8d 0.2d | 1.6d 6.1d | 2.3d 2026-11-14 21:07:55 54.3 Mbit/s (R)
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, Exit 36.8 Mbit/s (M) | 8.4 Mbit/s 36.8 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 79.3% | 98% 9.5d | 8d 19996.2d | 10768.2d 6.1d | 2.0d 2026-11-14 21:07:55 36.8 Mbit/s (M)
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 13.6 Mbit/s (M) | 816.0 Kbit/s 13.6 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 83.8% | 98% 11.5d | 8d 0.4d | 8.8d 6.1d | 2.4d 2026-11-14 21:07:55 13.6 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 (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.