View Relay "SaL"

Family: 1 relay | [email protected] | AS5650 | United States of America | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, V2Dir, Valid (3)
BW Verified
1/6 BW Auths Measured 472 bit/s Median
Stability
Not Overloaded | UP 18h 46m 55s ago | UP 49% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
2mo 1w 20h ago
BW Weight
0.00% of Network | 475 Kbit/s Observed By Relay
Version
0.4.8.10 Not Recommended
Issues Detected:
  • Guard: bandwidth below threshold : Observed bandwidth 0.1 MB/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
    Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM.
  • Guard: WFU below threshold : Weighted Fractional Uptime 37.7% 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).
  • Guard: requires Fast flag : Guard flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • 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 37.7% 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.
  • Low bandwidth authority measurements : Only 1/6 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
    Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.
  • Tor version not recommended : Running Tor version 0.4.8.10 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.

Connectivity and Location

Addresses
OR Address
50-121-19-248.fdr02.ftwy.in.ip.frontiernet.net
50.121.19.248:58653
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
United States of America United States of America
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS5650
AS Name
Frontier Communications of America, Inc. (BGP.tools)

Flags and Eligibility

Current Flags (3): Running, V2Dir, Valid
Eligible Flags (3): Guard: 0/9 | Stable: 1/9 | Fast: 0/9 | HSDir: 0/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 37.7% (DA) ≥98% (all authorities)
Time Known Meets 9.7 days (DA) ≥8 days (all authorities)
Bandwidth Below 475.1 Kbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s
Stable MTBF Below 10 days (DA) ≥26.6d - 45.4d (varies)
Uptime Below 0.8d (R) ≥19.1d - 19.7d (varies)
Fast Speed Below 475.1 Kbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
HSDir WFU Below 37.7% (DA) ≥98.0%
Time Known Below 9.7 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
SaL
Fingerprint
2717FEA1732A7162EEB80BDF801B59808292208E
AROI (?)
none
Contact
[email protected]
IPv4 Exit Policy Summary 
reject: 
  1-65535
IPv6 Exit Policy Summary 
none
Exit Policy 
reject *:*
Effective Family Member: 1 
2717FEA1732A7162EEB80BDF801B59808292208E
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
475.14 Kbit/s | 475.14 Kbit/s| 8.39 Mbit/s| 134.22 Mbit/s  Not Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | 0.00% | N/A
OR Address
50-121-19-248.fdr02.ftwy.in.ip.frontiernet.net | 50.121.19.248:58653
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)
AS5650 | Frontier Communications of America, Inc. (BGP.tools)
Flags: 3
Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
Match Overall Uptime (49.4%/49.0%/0.0%/0.0%)
Uptime (1M/6M/1Y/5Y)
49.4%/49.0%/0.0%/0.0%
Uptime / Downtime
UP 18h 46m 55s ago
Seen (First | Last)
2mo 1w 20h ago (2025-11-03 08:00:00) | 1h 55m 4s ago (2026-01-10 03:00:00)
Last Restarted
18h 54m 30s ago (2026-01-09 10:00:34)
Last Changed Address or Port
2025-11-03 08:00:00
Hibernating
No
Platform (Short | Long)
Linux | Tor 0.4.8.10 on Linux
Version (Running | Recommended | Status)
0.4.8.10 | No | obsolete

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: 0/9 | Stable: 1/9 | Fast: 0/9 | HSDir: 0/9 | Running: 9/9 | Valid: 9/9 | V2Dir: 9/9
  • Reachability: IPv4: 9/9
  • Consensus Weight (Dir. Auth.): Median: 472 bit/s | Min: 184 bit/s | Max: 472 bit/s [Warning] High deviation
  • Identified Issues:
    • Guard: bandwidth below threshold: Observed bandwidth 0.1 MB/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
      • Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM.
    • Guard: WFU below threshold: Weighted Fractional Uptime 37.7% 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).
    • Guard: requires Fast flag: Guard flag requires having the Fast flag first
      • Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
    • 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 37.7% 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.
    • Low bandwidth authority measurements: Only 1/6 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
      • Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.
    • Tor version not recommended: Running Tor version 0.4.8.10 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.

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.) 472 bit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 37.7% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 9.7 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 475.1 Kbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported) 0.8d ≥19.1d - 19.7d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 10 days ≥26.6d - 45.4d (typical)
[Stricter] moria1: ≥376.2d 		BELOW - 1/9
Fast Speed (Relay Reported) 475.1 Kbit/s ≥800.0 Kbit/s (guarantee) OR ≥816.0 Kbit/s (typical)
[Stricter] moria1: ≥8.4 Mbit/s 		BELOW - need ≥100 KB/s
HSDir WFU (Dir. Auth., wfu) 37.7% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 9.7 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d 		BELOW - 0/9

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 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 Running, V2Dir, Valid 475.1 Kbit/s | 816.0 Kbit/s 475.1 Kbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 37.7% | 98% 9.7d | 8d 0.1d | 47.0d 0.8d | 19.7d 37.7% | 98.0% 9.7d | 1.0d 2026-01-10 00:35:03 472 bit/s
dannenberg (DE) Yes Yes N Yes V2Dir, Valid 475.1 Kbit/s | 816.0 Kbit/s 475.1 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 26.2% | 98% 9.6d | 8d 0.0d | 35.7d 0.8d | 20.2d 26.2% | 98.0% 9.6d | 1.0d 2026-01-10 00:35:03 472 bit/s
dizum (NL) Yes Yes N Yes V2Dir, Valid 475.1 Kbit/s | 816.0 Kbit/s 475.1 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 36.8% | 98% 9.8d | 8d 0.1d | 26.6d 0.8d | 20.4d 36.8% | 98.0% 9.8d | 1.0d 2026-01-10 00:35:03 472 bit/s
faravahar (US) Yes Yes N Yes Running, V2Dir, Valid 475.1 Kbit/s | 816.0 Kbit/s 475.1 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 36.3% | 98% 9.6d | 8d 0.1d | 41.9d 0.8d | 19.1d 36.3% | 98.0% 9.6d | 1.0d 2026-01-10 00:35:03 472 bit/s
gabelmoo (DE) Yes Yes Y Yes Running, V2Dir, Valid 475.1 Kbit/s | 816.0 Kbit/s 475.1 Kbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 46.1% | 98% 9.8d | 8d 0.1d | 45.4d 0.8d | 19.6d 46.1% | 98.0% 9.8d | 1.0d 2026-01-10 00:35:03 472 bit/s
longclaw (US) Yes Yes Y Yes V2Dir, Valid 475.1 Kbit/s | 816.0 Kbit/s 475.1 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 42.7% | 98% 9.6d | 8d 0.1d | 48.7d 0.8d | 19.5d 42.7% | 98.0% 9.6d | 1.0d 2026-01-10 00:35:03 472 bit/s
maatuska (SE) Yes Yes Y Yes Running, V2Dir, Valid 475.1 Kbit/s | 816.0 Kbit/s 475.1 Kbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 43.9% | 98% 9.9d | 8d 0.1d | 42.3d 0.8d | 19.4d 43.9% | 98.0% 9.9d | 1.0d 2026-01-10 00:35:03 184 bit/s
moria1 (US) Yes Yes Y Yes Running, Stable, V2Dir, Valid 475.1 Kbit/s | 8.4 Mbit/s 475.1 Kbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 54.1% | 98% 9.8d | 8d 20145.2d | 376.2d 0.8d | 20.4d 54.1% | 98.0% 9.8d | 9.9d 2026-01-10 00:35:03 472 bit/s
tor26 (AT) Yes Yes Y Yes Running, V2Dir, Valid 475.1 Kbit/s | 816.0 Kbit/s 475.1 Kbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 42.2% | 98% 9.6d | 8d 0.1d | 51.8d 0.8d | 19.7d 42.2% | 98.0% 9.6d | 1.0d 2026-01-10 00:35:03 472 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.