View Relay "RacknerdRelay"

Family: 1 relay | AS36352 | United States of America | Linux

Consensus
In Consensus (9/9 Directory Auths)
Flags
Fast, HSDir, Running, Stable, V2Dir, Valid (6)
BW Verified
5/6 BW Auths Measured 6160 bit/s Median
Stability
Overloaded | UP 4mo 1w 6d ago | UP 100% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
4mo 1w 6d ago
BW Weight
0.00% of Network | 8 Mbit/s Observed By Relay
Version
0.4.8.17 Not Recommended
Issues Detected:
  • Guard: bandwidth below threshold : Observed bandwidth 1.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.
  • 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.
  • Tor version not recommended : Running Tor version 0.4.8.17 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.
  • Write Bandwidth Limit Hit : Write rate limit (8 Mbit/s) was hit 652 times. Relay is throttling outbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more upload capacity.
  • Read Bandwidth Limit Hit : Read rate limit (8 Mbit/s) was hit 2,537 times. Relay is throttling inbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more download capacity.
Notes:
  • Rate Limit Configuration: Configured limits: Rate=8 Mbit/s, Burst=16 Mbit/s. Limits hit: Write=652, Read=2,537.

Addresses
OR Address
96-8-120-57-host.colocrossing.com
96.8.120.57:9001
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
AS36352
AS Name
HostPapa (BGP.tools)

Current Flags (6): Stable, Fast, HSDir, Running, V2Dir, Valid
Eligible Flags (6): Guard: 0/9 | Stable: 8/9 | Fast: 9/9 | HSDir: 8/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 Meets 100.0% (DA) ≥98% (all authorities)
Time Known Meets 133.2 days (DA) ≥8 days (all authorities)
Bandwidth Below 8.8 Mbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s
Stable MTBF Partial (8/9) 133 days (DA) ≥26.6d - 45.4d (varies)
Uptime Meets 133.2d (R) ≥19.1d - 19.7d (varies)
Fast Speed Meets (≥100 KB/s) 8.8 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
HSDir WFU Meets 100.0% (DA) ≥98.0%
Time Known Meets 133.2 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.

RacknerdRelay
D9814ECF6AA508FA11FBDE5FA9874CF0C79E0D3F
none
none
reject: 
  1-65535
none
reject *:*
D9814ECF6AA508FA11FBDE5FA9874CF0C79E0D3F
none
none
8.81 Mbit/s | 8.19 Mbit/s| 8.19 Mbit/s| 16.38 Mbit/s  Measured
0.00% | N/A | 0.00% | N/A
96-8-120-57-host.colocrossing.com | 96.8.120.57:9001
none
none
United States of America United States of America
View on Interactive Map
AS36352 | HostPapa (BGP.tools)
Fast Fast HSDir HSDir Running Running Stable Stable V2Dir V2Dir Valid Valid
Match Overall Uptime (100.0%/100.0%/0.0%/0.0%)
100.0%/100.0%/0.0%/0.0%
UP 4mo 1w 6d ago
4mo 1w 6d ago (2025-08-30 00:00:00) | 1h 55m 2s ago (2026-01-10 03:00:00)
4mo 1w 6d ago (2025-08-29 22:52:55)
2025-08-30 00:00:00
No
Linux | Tor 0.4.8.17 on Linux
0.4.8.17 | No | obsolete

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: 8/9 | Fast: 9/9 | HSDir: 8/9 | Running: 9/9 | Valid: 9/9 | V2Dir: 9/9
  • Reachability: IPv4: 9/9
  • Consensus Weight (Dir. Auth.): Median: 6160 bit/s | Min: 1920 bit/s | Max: 8.2 Kbit/s [Warning] High deviation
  • Identified Issues:
    • Guard: bandwidth below threshold: Observed bandwidth 1.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.
    • 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.
    • Tor version not recommended: Running Tor version 0.4.8.17 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.
    • Write Bandwidth Limit Hit: Write rate limit (8 Mbit/s) was hit 652 times. Relay is throttling outbound traffic.
      • Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more upload capacity.
    • Read Bandwidth Limit Hit: Read rate limit (8 Mbit/s) was hit 2,537 times. Relay is throttling inbound traffic.
      • Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more download capacity.
  • Notes:
    • Rate Limit Configuration: Configured limits: Rate=8 Mbit/s, Burst=16 Mbit/s. Limits hit: Write=652, Read=2,537.

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.) 6160 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) 133.2 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 8.8 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported) 133.2d ≥19.1d - 19.7d (typical) MEETS - all authorities
Stable MTBF (Dir. Auth., mtbf) 133 days ≥26.6d - 45.4d (typical)
[Stricter] moria1: ≥376.2d
PARTIAL - 8/9
Fast Speed (Relay Reported) 8.8 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) 100.0% ≥98.0% (from all auths) PARTIAL - 8/9
HSDir TK (Dir. Auth., tk) 133.2 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d
PARTIAL - 8/9

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, HSDir, Running, Stable, V2Dir, Valid 8.8 Mbit/s | 816.0 Kbit/s 8.8 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 133.2d | 8d 133.2d | 47.0d 133.2d | 19.7d 100.0% | 98.0% 133.2d | 1.0d 2026-01-09 22:54:42 6160 bit/s
dannenberg (DE) Yes Yes N Yes Fast, HSDir, Running, Stable, V2Dir, Valid 8.8 Mbit/s | 816.0 Kbit/s 8.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 132.4d | 8d 132.4d | 35.7d 133.2d | 20.2d 100.0% | 98.0% 132.4d | 1.0d 2026-01-09 22:54:42 8.2 Kbit/s
dizum (NL) Yes Yes N Yes Fast, HSDir, Running, Stable, V2Dir, Valid 8.8 Mbit/s | 816.0 Kbit/s 8.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 33.5d | 8d 31.6d | 26.6d 133.2d | 20.4d 100.0% | 98.0% 33.5d | 1.0d 2026-01-09 22:54:42 8.2 Kbit/s
faravahar (US) Yes Yes N Yes Fast, HSDir, Running, Stable, V2Dir, Valid 8.8 Mbit/s | 816.0 Kbit/s 8.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 132.7d | 8d 132.7d | 41.9d 133.2d | 19.1d 100.0% | 98.0% 132.7d | 1.0d 2026-01-09 22:54:42 8.2 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Fast, HSDir, Running, Stable, V2Dir, Valid 8.8 Mbit/s | 816.0 Kbit/s 8.8 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 133.2d | 8d 133.2d | 45.4d 133.2d | 19.6d 100.0% | 98.0% 133.2d | 1.0d 2026-01-09 22:54:42 2080 bit/s
longclaw (US) Yes Yes Y Yes Fast, HSDir, Running, Stable, V2Dir, Valid 8.8 Mbit/s | 816.0 Kbit/s 8.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 132.3d | 8d 132.3d | 48.7d 133.2d | 19.5d 100.0% | 98.0% 132.3d | 1.0d 2026-01-09 22:54:42 8.2 Kbit/s
maatuska (SE) Yes Yes Y Yes Fast, HSDir, Running, Stable, V2Dir, Valid 8.8 Mbit/s | 816.0 Kbit/s 8.8 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 74.2d | 8d 74.2d | 42.3d 133.2d | 19.4d 100.0% | 98.0% 74.2d | 1.0d 2026-01-09 22:54:42 2560 bit/s
moria1 (US) Yes Yes Y Yes Running, Stable, V2Dir, Valid 8.8 Mbit/s | 8.4 Mbit/s 8.8 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 9.7d | 8d 133.2d | 376.2d 133.2d | 20.4d 100.0% | 98.0% 9.7d | 9.9d 2026-01-09 22:54:42 5440 bit/s
tor26 (AT) Yes Yes Y Yes Fast, HSDir, Running, Stable, V2Dir, Valid 8.8 Mbit/s | 816.0 Kbit/s 8.8 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 133.2d | 8d 133.2d | 51.8d 133.2d | 19.7d 100.0% | 98.0% 133.2d | 1.0d 2026-01-09 22:54:42 1920 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.