View Relay "desolate"

Family: 1 relay | 44FBABA6BC5EF8D1B69AB9C054994A18C5974... | AS205759 | United Kingdom of Great Britain and Northern Ireland | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, V2Dir, Valid (3)
BW Verified
0/6 BW Auths Measured
Stability
Not Overloaded | UP 3h 7m 42s ago
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
2h 47m 12s ago
BW Weight
0 Kbit/s Observed By Relay
Version
0.4.8.22 Recommended
Issues Detected:
  • Guard: Time Known below threshold : Time Known 0.1 days is below 8 days requirement (7.9 more days needed)
    Suggestion: Time Known tracks how long authorities have observed your relay. This resets if: 1) Identity key changes, 2) Long downtime makes authorities forget you. Just keep running stably.
  • 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: Time Known below threshold : Time Known 2.2 hours below 25 hours (dir-spec default)
    Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
  • Low bandwidth authority measurements : Only 0/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.

Connectivity and Location

Addresses
OR Address
64.89.161.194:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
United Kingdom of Great Britain and Northern Ireland United Kingdom of Great Britain and Northern Ireland
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS205759
AS Name
Ghosty Networks LLC (BGP.tools)

Flags and Eligibility

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 0/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 (need ≥5/9 for flag)
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Fast Speed Below 0 bit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below Median: 0.1d (0/9 DA above threshold)
Min/Max: 0.1d / 0.1d (9/9 DA, Voting / Total Eligible)		 ≥22.1d - 53.8d (varies)
[Stricter] moria1: ≥406.0d
Uptime Below 0.1d (R) ≥10.5d - 11.3d (varies)
HSDir Prereq: Stable Below 0/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: Fast Below 0/9 authorities assigned Fast flag ≥5/9 authorities
WFU Meets Majority: 100.0% (9/9 DA) ≥98.0%
Time Known Below Median: 0.1d (0/9 DA above threshold)
Min/Max: 0.1d / 0.1d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below 0/9 authorities assigned Fast flag ≥5/9 authorities
Prereq: Stable Below 0/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: V2Dir Meets 9/9 authorities assigned V2Dir flag ≥5/9 authorities
WFU Meets Majority: 100.0% (9/9 DA) ≥98% (all authorities)
Time Known Below (need 7.9 more days) Median: 0.1d (0/9 DA above threshold)
Min/Max: 0.1d / 0.1d (9/9 DA, Voting / Total Eligible)		 ≥8 days (all authorities)
Bandwidth Below 0 bit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-01-29 08:45:07).

Last fetch was at Thu, 29 Jan 2026 08:45:42 GMT.

Nickname
desolate
Fingerprint
2C6E5CAD77F2318F3534840BAA5621F3A313EF96
AROI (?)
none
Contact
44FBABA6BC5EF8D1B69AB9C054994A18C5974B99 Satanist <admin AT 2cb dot network>
IPv4 Exit Policy Summary 
reject: 
  1-65535
IPv6 Exit Policy Summary 
none
Exit Policy 
reject *:*
Effective Family Member: 1 
2C6E5CAD77F2318F3534840BAA5621F3A313EF96
Alleged Family Members: 13 
2554E8FD30B57BF796CDC2C12496F92A076192AA
518F58F70E8C07F2BC63C20A0A5907A39152FEA3
5D1ACF7998E783EE5AE83A3E2529ECD80A1DBC58
872BE4C147B7071C248D32EFF561D7468AC94A82
90D76DEA5400FF1B6BC3EE3ADD5AC0347F3D4884
92D8015FE3706A3F7C4881F121747181553CDB2B
97F35D21D2A8F51FB70DA35C6C3878C2DA5C3B4E
AB3CBBB2A6284CCDC2780512887D2385C4383CE3
BC67DB594CBE96563AFE2CE165F2C107130FB2F0
C4FEABB1C0F7709312B33345040FBC29682877DE
DACA72CEC131FEA3120B1DBB2187A2365A539F0C
E6EE6BDA956878BC8F17B392568723DC1009DE9A
E8953FFF6D47182B07C6D3F0E092F83D8E45D62F
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
0.00 Kbit/s | unknown| 8.59 Gbit/s| 8.59 Gbit/s  Not Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
N/A | N/A | N/A | N/A
OR Address
64.89.161.194:9001
Exit Address
none
Dir Address
none
Country
United Kingdom of Great Britain and Northern Ireland United Kingdom of Great Britain and Northern Ireland
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS205759 | Ghosty Networks LLC (BGP.tools)
Flags: 3
Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
N/A
Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Uptime / Downtime
UP 3h 7m 42s ago
Seen (First | Last)
2h 47m 12s ago (2026-01-29 06:00:00) | 1h 47m 12s ago (2026-01-29 07:00:00)
Last Restarted
3h 9m 11s ago (2026-01-29 05:38:01)
Last Changed Address or Port
2026-01-29 06:00:00
Hibernating
No
Platform (Short | Long)
Linux | Tor 0.4.8.22 on Linux
Version (Running | Recommended | Status)
0.4.8.22 | Yes | recommended

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-01-29 08:45:07).

  • Consensus Status (need ≥5/9): In Consensus — 9/9 authorities voted.
  • Flag Eligibility (need ≥5/9 for flag): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 0/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9
  • Reachability: IPv4: 9/9
  • Consensus Weight (Dir. Auth.): Median: 0 bit/s | Min: 0 bit/s | Max: 0 bit/s
  • Identified Issues:
    • Guard: Time Known below threshold: Time Known 0.1 days is below 8 days requirement (7.9 more days needed)
      • Suggestion: Time Known tracks how long authorities have observed your relay. This resets if: 1) Identity key changes, 2) Long downtime makes authorities forget you. Just keep running stably.
    • 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: Time Known below threshold: Time Known 2.2 hours below 25 hours (dir-spec default)
      • Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
    • Low bandwidth authority measurements: Only 0/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.

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.) 0 bit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 100.0% ≥98% (all authorities) MEETS
Guard TK (Dir. Auth., tk) 0.1 days ≥8 days (all authorities) BELOW - need 7.9 more days
Guard BW (Relay Reported) 0 bit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported) 0.1d ≥10.5d - 11.3d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 0 days ≥22.1d - 53.8d (typical)
[Stricter] moria1: ≥406.0d 		BELOW - 0/9
Fast Speed (Relay Reported) 0 bit/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) 100.0% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 0.1 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, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 50.2d 0.1d | 12.0d 100.0% | 98.0% 0.1d | 1.0d 2026-01-29 05:38:03 —
dannenberg (DE) Yes Yes N Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 22.1d 0.1d | 11.4d 100.0% | 98.0% 0.1d | 1.0d 2026-01-29 05:38:03 —
dizum (NL) Yes Yes N Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 34.4d 0.1d | 11.3d 100.0% | 98.0% 0.1d | 1.0d 2026-01-29 05:38:03 —
faravahar (US) Yes Yes N Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 47.2d 0.1d | 10.5d 100.0% | 98.0% 0.1d | 1.0d 2026-01-29 05:38:03 —
gabelmoo (DE) Yes Yes Y Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 53.8d 0.1d | 11.4d 100.0% | 98.0% 0.1d | 1.0d 2026-01-29 05:38:03 —
longclaw (US) Yes Yes Y Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 54.5d 0.1d | 10.7d 100.0% | 98.0% 0.1d | 1.0d 2026-01-29 05:38:03 —
maatuska (SE) Yes Yes Y Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 54.6d 0.1d | 10.6d 100.0% | 98.0% 0.1d | 1.0d 2026-01-29 05:38:03 —
moria1 (US) Yes Yes Y Yes Running, Valid, V2Dir 0 bit/s | 8.4 Mbit/s 0 bit/s | 240.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 406.0d 0.1d | 10.8d 100.0% | 98.0% 0.1d | 9.9d 2026-01-29 05:38:03 —
tor26 (AT) Yes Yes Y Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 55.6d 0.1d | 12.0d 100.0% | 98.0% 0.1d | 1.0d 2026-01-29 05:38:03 —

— = 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.