View Relay "TheMadHacker5Plaza"

Family: 8 relays | TheMadHacker <TheMadHacker AT... | AS44382 | United States of America | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Exit, Fast, Running, V2Dir, Valid (5)
BW Verified
5/6 BW Auths Measured 33 Kbit/s Median
Stability
Not Overloaded | UP 3h 15m 38s ago | UP 95% (1M)
Reachability
IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen
1w 2d 17h ago
BW Weight
0.00% of Network | 33 Mbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • Guard: WFU below threshold : Weighted Fractional Uptime 92.3% 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: Time Known below threshold : Time Known 6.6 days is below 8 days requirement (1.4 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).
  • 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 92.3% 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
216.9.225.157:9001
[2602:fa5d:1::69]:9001
Exit Address
216.9.225.157
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
AS44382
AS Name
Fiba Cloud Operation Company, LLC (BGP.tools)

Flags and Eligibility

Current Flags (5): Exit, Fast, Running, V2Dir, Valid
Eligible Flags (4): Guard: 0/9 | Stable: 1/9 | Fast: 9/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 92.3% (DA) ≥98% (all authorities)
Time Known Below (need 1.4 more days) 6.6 days (DA) ≥8 days (all authorities)
Bandwidth Meets (≥2 MB/s) 33.3 Mbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s
Stable MTBF Below 7 days (DA) ≥26.6d - 45.4d (varies)
Uptime Below 0.1d (R) ≥19.1d - 19.7d (varies)
Fast Speed Meets (≥100 KB/s) 33.3 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
HSDir WFU Below 92.3% (DA) ≥98.0%
Time Known Below 6.6 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
TheMadHacker5Plaza
Fingerprint
08062152A807CAEFDCCE6A020F36FFC0656717EC
AROI (?)
none
Contact
TheMadHacker <TheMadHacker AT TheMadHacker dot net>
IPv4 Exit Policy Summary 
reject: 
  25
  119
  135-139
  445
  563
  1214
  4661-4666
  6346-6429
  6699
  6881-6999
IPv6 Exit Policy Summary 
reject: 
  25
  119
  135-139
  445
  563
  1214
  4661-4666
  6346-6429
  6699
  6881-6999
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 216.9.225.157:*
reject *:25
reject *:119
reject *:135-139
reject *:445
reject *:563
reject *:1214
reject *:4661-4666
reject *:6346-6429
reject *:6699
reject *:6881-6999
accept *:*
Effective Family Members: 8 (View) 
08062152A807CAEFDCCE6A020F36FFC0656717EC
32A33AC6A45E440B3D0E7C0BA6BFC762ADCFFE82
41C5E3A4A29E841DC3ED96B859B51077197AEA67
4A3DC8611757021A0B667CD2B2F110302AF1AE36
4CDF5E6E92D48F02A369043A36F164E95970B5FB
5DCE5EE23D39EF54A97116DD1587E05DBF31E4E7
959C5935AA3BBC56E174B2DC30D6ABEA0A9914D4
98A2762D6C8E73E068A6DE1AB9EA9C4CFF405B4B
Alleged Family Members: 0 
none
Indirect Family Members: 2 
88A71709C141569FCE4EDFFBE99800E0D6E60D13
AC5463A1D4356369D7F6F52D644B16A4A1E4D400
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
33.35 Mbit/s | 33.35 Mbit/s| 8.59 Gbit/s| 8.59 Gbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | N/A | 0.01%
OR Address
216.9.225.157:9001, [2602:fa5d:1::69]:9001
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)
AS44382 | Fiba Cloud Operation Company, LLC (BGP.tools)
Flags: 5
Exit Exit Fast Fast Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
Match Overall Uptime (95.8%/0.0%/0.0%/0.0%)
Uptime (1M/6M/1Y/5Y)
95.8%/0.0%/0.0%/0.0%
Uptime / Downtime
UP 3h 15m 38s ago
Seen (First | Last)
1w 2d 17h ago (2025-12-31 11:00:00) | 1h 54m 57s ago (2026-01-10 03:00:00)
Last Restarted
3h 23m 7s ago (2026-01-10 01:31:50)
Last Changed Address or Port
2025-12-31 11: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: 0/9 | Stable: 1/9 | Fast: 9/9 | HSDir: 0/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: 33.3 Kbit/s | Min: 8 bit/s | Max: 208.0 Kbit/s [Warning] High deviation
  • Identified Issues:
    • Guard: WFU below threshold: Weighted Fractional Uptime 92.3% 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: Time Known below threshold: Time Known 6.6 days is below 8 days requirement (1.4 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).
    • 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 92.3% 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.) 33.3 Kbit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 92.3% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 6.6 days ≥8 days (all authorities) BELOW - need 1.4 more days
Guard BW (Relay Reported) 33.3 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported) 0.1d ≥19.1d - 19.7d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 7 days ≥26.6d - 45.4d (typical)
[Stricter] moria1: ≥376.2d 		BELOW - 1/9
Fast Speed (Relay Reported) 33.3 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) 92.3% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 6.6 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d 		BELOW - 0/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 Exit, Fast, Running, V2Dir, Valid 33.3 Mbit/s | 816.0 Kbit/s 33.3 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 92.3% | 98% 6.6d | 8d 0.8d | 47.0d 0.1d | 19.7d 92.3% | 98.0% 6.6d | 1.0d 2026-01-10 03:32:30 184.0 Kbit/s
dannenberg (DE) Yes Yes N Yes Yes Exit, Fast, Running, V2Dir, Valid 33.3 Mbit/s | 816.0 Kbit/s 33.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 91.8% | 98% 6.4d | 8d 0.6d | 35.7d 0.1d | 20.2d 91.8% | 98.0% 6.4d | 1.0d 2026-01-10 03:32:30 33.3 Kbit/s
dizum (NL) Yes Yes N Yes — Exit, Fast, Running, V2Dir, Valid 33.3 Mbit/s | 816.0 Kbit/s 33.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 89.4% | 98% 6.4d | 8d 0.5d | 26.6d 0.1d | 20.4d 89.4% | 98.0% 6.4d | 1.0d 2026-01-10 03:32:30 33.3 Kbit/s
faravahar (US) Yes Yes N Yes Yes Exit, Fast, Running, V2Dir, Valid 33.3 Mbit/s | 816.0 Kbit/s 33.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 89.1% | 98% 6.4d | 8d 0.5d | 41.9d 0.1d | 19.1d 89.1% | 98.0% 6.4d | 1.0d 2026-01-10 03:32:30 33.3 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Yes Exit, Fast, Running, V2Dir, Valid 33.3 Mbit/s | 816.0 Kbit/s 33.3 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 91.2% | 98% 6.6d | 8d 0.6d | 45.4d 0.1d | 19.6d 91.2% | 98.0% 6.6d | 1.0d 2026-01-10 03:32:30 44.8 Kbit/s
longclaw (US) Yes Yes Y Yes — Exit, Fast, Running, V2Dir, Valid 33.3 Mbit/s | 816.0 Kbit/s 33.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 96.2% | 98% 6.9d | 8d 2.0d | 48.7d 0.1d | 19.5d 96.2% | 98.0% 6.9d | 1.0d 2026-01-10 03:32:30 33.3 Kbit/s
maatuska (SE) Yes Yes Y Yes Yes Exit, Fast, Running, V2Dir, Valid 33.3 Mbit/s | 816.0 Kbit/s 33.3 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 92.2% | 98% 6.6d | 8d 0.8d | 42.3d 0.1d | 19.4d 92.2% | 98.0% 6.6d | 1.0d 2026-01-10 03:32:30 9.6 Kbit/s
moria1 (US) Yes Yes Y Yes Yes Exit, Fast, Running, Stable, V2Dir, Valid 33.3 Mbit/s | 8.4 Mbit/s 33.3 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 93.0% | 98% 6.2d | 8d 17897.9d | 376.2d 0.1d | 20.4d 93.0% | 98.0% 6.2d | 9.9d 2026-01-10 03:32:30 208.0 Kbit/s
tor26 (AT) Yes Yes Y Yes Yes Exit, Running, V2Dir, Valid 33.3 Mbit/s | 816.0 Kbit/s 33.3 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 93.0% | 98% 6.5d | 8d 0.9d | 51.8d 0.1d | 19.7d 93.0% | 98.0% 6.5d | 1.0d 2026-01-10 03:32:30 8 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.