View Relay "nanotor5"

Family: 8 relays | [email protected] | AS63949 | United States of America | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Fast, Running, V2Dir, Valid (4)
BW Verified
5/6 BW Auths Measured 30 Kbit/s Median
Stability
Not Overloaded | UP 2w 20h 50m ago | UP 94% (1M)
Reachability
IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen
3mo 1w 3d ago
BW Weight
0.00% of Network | 30 Mbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • Guard: WFU below threshold : Weighted Fractional Uptime 97.8% is below 98% requirement
    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.
  • 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).
  • Not eligible for Stable flag : Uptime or MTBF below network median for most authorities
    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: WFU below threshold : WFU 97.8% below 98% required for HSDir
    Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.
  • 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
172-236-228-103.ip.linodeusercontent.com
172.236.228.103:443
[2a01:7e03::2000:dff:fee4:799a]:443
Reachability (Directory Authorities)
IPv4
9/9
IPv6
7/7 (2 don't test)
Location
Country
United States of America United States of America
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS63949
AS Name
Akamai Technologies, Inc. (BGP.tools)

Flags and Eligibility

Current Flags (4): Fast, Running, V2Dir, Valid
Eligible Flags (4): Guard: 2/9 | Stable: 1/9 | Fast: 9/9 | HSDir: 2/9 | Running: 9/9 | V2Dir: 9/9 | Valid: 9/9 (need ≥5/9 for flag)
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Guard WFU Below 97.8% (DA) ≥98% (all authorities)
Time Known Meets 25.0 days (DA) ≥8 days (all authorities)
Bandwidth Meets (≥2 MB/s) 30.2 Mbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s
Stable MTBF Below 25 days (DA) ≥26.6d - 45.4d (varies)
Uptime Below 14.9d (R) ≥19.1d - 19.7d (varies)
Fast Speed Meets (≥100 KB/s) 30.2 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
HSDir WFU Below 97.8% (DA) ≥98.0%
Time Known Meets 25.0 days (DA) ≥1.0d (most) / 9.9d (max)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-01-10 04:46:16).

Last fetch was at Sat, 10 Jan 2026 04:47:26 GMT.

Nickname
nanotor5
Fingerprint
70BE051A3006B18C93B48D516AF18DD45FEC6EDB
AROI (?)
none
Contact
[email protected]
IPv4 Exit Policy Summary 
reject: 
  1-65535
IPv6 Exit Policy Summary 
none
Exit Policy 
reject *:*
Effective Family Members: 8 (View) 
430A5639D3DB4CC0D40E78C4D960773CF63ECD9F
57F82230A3325BAB25184C8F20C7838D7D856FFE
7073D39EA428DEC487C9D008C5F9437FE57FA61D
70BE051A3006B18C93B48D516AF18DD45FEC6EDB
92BA1B71122F3C8891CCC1196C8087DAC674195B
A1FD18B914FB0EF8A4CF699181E58AC549F353C1
BC1643C7377EB45FCAE5BA78194CA1629AAA6C45
C0B1F3442BA7B51F58005743A2397D113F19D1B5
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
30.18 Mbit/s | 30.18 Mbit/s| 8.59 Gbit/s| 8.59 Gbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | 0.00% | N/A
OR Address
172-236-228-103.ip.linodeusercontent.com | 172.236.228.103:443, [2a01:7e03::2000:dff:fee4:799a]:443
Exit Address
none
Dir Address
none
Country
United States of America United States of America
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS63949 | Akamai Technologies, Inc. (BGP.tools)
Flags: 4
Fast Fast Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
—/96.7%/—/—
Uptime (1M/6M/1Y/5Y)
94.4%/98.3%/0.0%/0.0%
Uptime / Downtime
UP 2w 20h 50m ago
Seen (First | Last)
3mo 1w 3d ago (2025-10-01 05:00:00) | 1h 54m 58s ago (2026-01-10 03:00:00)
Last Restarted
2w 20h 57m ago (2025-12-26 07:57:04)
Last Changed Address or Port
2025-10-01 05:00:00
Hibernating
No
Platform (Short | Long)
Linux | Tor 0.4.8.21 on Linux
Version (Running | Recommended | Status)
0.4.8.21 | Yes | recommended

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-01-10 04:46:16).

  • Consensus Status (need ≥5/9): In Consensus — 9/9 authorities voted.
  • Flag Eligibility (need ≥5/9 for flag): Guard: 2/9 | Stable: 1/9 | Fast: 9/9 | HSDir: 2/9 | Running: 9/9 | Valid: 9/9 | V2Dir: 9/9
  • Reachability: IPv4: 9/9 | IPv6: 7/7 (2 don't test)
  • Consensus Weight (Dir. Auth.): Median: 30.2 Kbit/s | Min: 6080 bit/s | Max: 53.6 Kbit/s [Warning] High deviation
  • Identified Issues:
    • Guard: WFU below threshold: Weighted Fractional Uptime 97.8% is below 98% requirement
      • 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.
    • 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).
    • Not eligible for Stable flag: Uptime or MTBF below network median for most authorities
      • 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: WFU below threshold: WFU 97.8% below 98% required for HSDir
      • Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.
    • 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.

Summary: Your Relay vs Consensus

Green = meets threshold, Red = below threshold, Yellow = partial.

Metric Dir Auth Measured Dir Auth Threshold Status
In Consensus (Dir. Auth.) 9/9 authorities ≥5/9 (majority) IN CONSENSUS
Running (IPv4 Reachable) 9/9 authorities reached this relay ≥5/9 (majority) RUNNING
Valid 9/9 (Running + Valid Descriptor) ≥5/9 (majority) VALID
Consensus Weight (Dir. Auth.) 30.2 Kbit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 97.8% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 25.0 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 30.2 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported) 14.9d ≥19.1d - 19.7d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 25 days ≥26.6d - 45.4d (typical)
[Stricter] moria1: ≥376.2d 		BELOW - 1/9
Fast Speed (Relay Reported) 30.2 Mbit/s ≥800.0 Kbit/s (guarantee) OR ≥816.0 Kbit/s (typical)
[Stricter] moria1: ≥8.4 Mbit/s 		MEETS - ≥100 KB/s guarantee
HSDir WFU (Dir. Auth., wfu) 97.8% ≥98.0% (from all auths) BELOW - 2/9
HSDir TK (Dir. Auth., tk) 25.0 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d 		BELOW - 2/9
IPv6 Reachable (Dir. Auth.) 7/7 tested ≥4/7 (majority) REACHABLE

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 BW Scan (Authority) v4 v6 Flags Fast (Relay|T) Guard BW (Relay|Threshold) Guard WFU (M|T) Guard TK (M|T) Stable MTBF (M|T) Stable Uptime (Relay|T) HSDir WFU (M|T) HSDir TK (M|T) Desc Published Cons Wt (Authority)
bastet (US) Yes Yes Y Yes Yes Fast, Running, V2Dir, Valid 30.2 Mbit/s | 816.0 Kbit/s 30.2 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 97.8% | 98% 25.0d | 8d 4.5d | 47.0d 14.9d | 19.7d 97.8% | 98.0% 25.0d | 1.0d 2026-01-10 00:50:36 53.6 Kbit/s
dannenberg (DE) Yes Yes N Yes Yes Fast, Running, V2Dir, Valid 30.2 Mbit/s | 816.0 Kbit/s 30.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 96.5% | 98% 17.0d | 8d 2.3d | 35.7d 14.9d | 20.2d 96.5% | 98.0% 17.0d | 1.0d 2026-01-10 00:50:36 30.2 Kbit/s
dizum (NL) Yes Yes N Yes — Fast, HSDir, Running, Stable, V2Dir, Valid 30.2 Mbit/s | 816.0 Kbit/s 30.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 97.5% | 98% 17.5d | 8d 6.7d | 26.6d 14.9d | 20.4d 97.5% | 98.0% 17.5d | 1.0d 2026-01-10 00:50:36 30.2 Kbit/s
faravahar (US) Yes Yes N Yes Yes Fast, Guard, Running, Stable, V2Dir, Valid 30.2 Mbit/s | 816.0 Kbit/s 30.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 98.1% | 98% 26.0d | 8d 5.0d | 41.9d 14.9d | 19.1d 98.1% | 98.0% 26.0d | 1.0d 2026-01-10 00:50:36 30.2 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Yes Fast, HSDir, Running, Stable, V2Dir, Valid 30.2 Mbit/s | 816.0 Kbit/s 30.2 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 98.0% | 98% 20.7d | 8d 8.1d | 45.4d 14.9d | 19.6d 98.0% | 98.0% 20.7d | 1.0d 2026-01-10 00:50:36 6080 bit/s
longclaw (US) Yes Yes Y Yes — Fast, Guard, HSDir, Running, Stable, V2Dir, Valid 30.2 Mbit/s | 816.0 Kbit/s 30.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 98.1% | 98% 25.0d | 8d 5.7d | 48.7d 14.9d | 19.5d 98.1% | 98.0% 25.0d | 1.0d 2026-01-10 00:50:36 30.2 Kbit/s
maatuska (SE) Yes Yes Y Yes Yes Fast, Running, V2Dir, Valid 30.2 Mbit/s | 816.0 Kbit/s 30.2 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 97.6% | 98% 21.2d | 8d 3.6d | 42.3d 14.9d | 19.4d 97.6% | 98.0% 21.2d | 1.0d 2026-01-10 00:50:36 10.4 Kbit/s
moria1 (US) Yes Yes Y Yes Yes Fast, Running, Stable, V2Dir, Valid 30.2 Mbit/s | 8.4 Mbit/s 30.2 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 95.7% | 98% 9.9d | 8d 14223.8d | 376.2d 14.9d | 20.4d 95.7% | 98.0% 9.9d | 9.9d 2026-01-10 00:50:36 34.4 Kbit/s
tor26 (AT) Yes Yes Y Yes Yes Fast, Running, V2Dir, Valid 30.2 Mbit/s | 816.0 Kbit/s 30.2 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 98.0% | 98% 24.1d | 8d 4.3d | 51.8d 14.9d | 19.7d 98.0% | 98.0% 24.1d | 1.0d 2026-01-10 00:50:36 7280 bit/s

— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known

Bandwidth Values Explained:
Relay Reported = Your relay's self-reported bandwidth from its descriptor (observed_bandwidth). Used for flag eligibility (Guard, Fast).
Authority Measured = Bandwidth measured by authority's sbws scanner. Used for consensus weight (path selection probability).
Why different? Authorities verify your reported bandwidth independently. 6 of 9 authorities run bandwidth scanners; 3 use relay-reported values directly.
Stable Uptime (Two Data Sources):
Relay Uptime = From Onionoo API (last_restarted field). This is your relay's self-reported uptime from its 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.