View Relay "magiciansRelay"

Family: 1 relay | [email protected] | AS31898 | 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 13 Kbit/s Median
Stability
Not Overloaded | UP 1d 14h 43m ago | UP 47% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
1y 5mo 4w ago
BW Weight
0.00% of Network | 13 Mbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • Guard: bandwidth below threshold : Observed bandwidth 1.7 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 55.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 55.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
129.146.43.72:443
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
AS31898
AS Name
Oracle Corporation (BGP.tools)

Flags and Eligibility

Current Flags (4): 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 55.8% (DA) ≥98% (all authorities)
Time Known Meets 11.0 days (DA) ≥8 days (all authorities)
Bandwidth Below 13.9 Mbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s
Stable MTBF Below 11 days (DA) ≥26.6d - 45.4d (varies)
Uptime Below 1.6d (R) ≥19.1d - 19.7d (varies)
Fast Speed Meets (≥100 KB/s) 13.9 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
HSDir WFU Below 55.8% (DA) ≥98.0%
Time Known Meets 11.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
magiciansRelay
Fingerprint
10CB84C040124EDC58D4707D260D113EBB142BC7
AROI (?)
none
Contact
[email protected]
IPv4 Exit Policy Summary 
reject: 
  1-65535
IPv6 Exit Policy Summary 
none
Exit Policy 
reject *:*
Effective Family Member: 1 
10CB84C040124EDC58D4707D260D113EBB142BC7
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
13.89 Mbit/s | 13.89 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
129.146.43.72: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)
AS31898 | Oracle Corporation (BGP.tools)
Flags: 4
Fast Fast Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
44.9%/76.1%/87.8%/91.8%
Uptime (1M/6M/1Y/5Y)
47.4%/76.5%/88.0%/92.0%
Uptime / Downtime
UP 1d 14h 43m ago
Seen (First | Last)
1y 5mo 4w ago (2024-07-15 04:00:00) | 1h 55m 1s ago (2026-01-10 03:00:00)
Last Restarted
1d 14h 50m ago (2026-01-08 14:04:26)
Last Changed Address or Port
2024-07-15 04: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
  • Consensus Weight (Dir. Auth.): Median: 13.9 Kbit/s | Min: 2000 bit/s | Max: 23.2 Kbit/s [Warning] High deviation
  • Identified Issues:
    • Guard: bandwidth below threshold: Observed bandwidth 1.7 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 55.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 55.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.) 13.9 Kbit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 55.8% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 11.0 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 13.9 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported) 1.6d ≥19.1d - 19.7d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 11 days ≥26.6d - 45.4d (typical)
[Stricter] moria1: ≥376.2d 		BELOW - 1/9
Fast Speed (Relay Reported) 13.9 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) 55.8% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 11.0 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 Fast, Running, V2Dir, Valid 13.9 Mbit/s | 816.0 Kbit/s 13.9 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 55.8% | 98% 11.0d | 8d 0.5d | 47.0d 1.6d | 19.7d 55.8% | 98.0% 11.0d | 1.0d 2026-01-10 02:05:46 23.2 Kbit/s
dannenberg (DE) Yes Yes N Yes Fast, Running, V2Dir, Valid 13.9 Mbit/s | 816.0 Kbit/s 13.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 56.3% | 98% 10.8d | 8d 0.5d | 35.7d 1.6d | 20.2d 56.3% | 98.0% 10.8d | 1.0d 2026-01-10 02:05:46 13.9 Kbit/s
dizum (NL) Yes Yes N Yes Fast, Running, V2Dir, Valid 13.9 Mbit/s | 816.0 Kbit/s 13.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 55.4% | 98% 11.1d | 8d 0.5d | 26.6d 1.6d | 20.4d 55.4% | 98.0% 11.1d | 1.0d 2026-01-10 02:05:46 13.9 Kbit/s
faravahar (US) Yes Yes N Yes Fast, Running, V2Dir, Valid 13.9 Mbit/s | 816.0 Kbit/s 13.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 55.1% | 98% 10.9d | 8d 0.6d | 41.9d 1.6d | 19.1d 55.1% | 98.0% 10.9d | 1.0d 2026-01-10 02:05:46 13.9 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Fast, Running, V2Dir, Valid 13.9 Mbit/s | 816.0 Kbit/s 13.9 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 56.2% | 98% 11.1d | 8d 0.5d | 45.4d 1.6d | 19.6d 56.2% | 98.0% 11.1d | 1.0d 2026-01-10 02:05:46 2000 bit/s
longclaw (US) Yes Yes Y Yes Fast, Running, V2Dir, Valid 13.9 Mbit/s | 816.0 Kbit/s 13.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 56.9% | 98% 10.8d | 8d 0.4d | 48.7d 1.6d | 19.5d 56.9% | 98.0% 10.8d | 1.0d 2026-01-10 02:05:46 13.9 Kbit/s
maatuska (SE) Yes Yes Y Yes Fast, Running, V2Dir, Valid 13.9 Mbit/s | 816.0 Kbit/s 13.9 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 55.6% | 98% 11.0d | 8d 0.5d | 42.3d 1.6d | 19.4d 55.6% | 98.0% 11.0d | 1.0d 2026-01-10 02:05:46 3280 bit/s
moria1 (US) Yes Yes Y Yes Fast, Running, Stable, V2Dir, Valid 13.9 Mbit/s | 8.4 Mbit/s 13.9 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 54.1% | 98% 9.7d | 8d 18894.8d | 376.2d 1.6d | 20.4d 54.1% | 98.0% 9.7d | 9.9d 2026-01-10 02:05:46 9.6 Kbit/s
tor26 (AT) Yes Yes Y Yes Fast, Running, V2Dir, Valid 13.9 Mbit/s | 816.0 Kbit/s 13.9 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 56.1% | 98% 10.9d | 8d 0.5d | 51.8d 1.6d | 19.7d 56.1% | 98.0% 10.9d | 1.0d 2026-01-10 02:05:46 2240 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.