View Relay "rocket"

Family: 16 relays | [email protected] | AS206134 | Germany | Linux

Consensus
In Consensus (9/9 Directory Auths)
Flags
Fast, Running, V2Dir, Valid (4)
BW Verified
5/6 BW Auths Measured 73 Kbit/s Median
Stability
Not Overloaded | UP 2h 2m 23s ago | UP 100% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
5d 14h 47m ago
BW Weight
0.00% of Network | 73 Mbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • Guard: WFU below threshold : Weighted Fractional Uptime 97.1% 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 4.5 days is below 8 days requirement (3.5 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 97.1% 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.

Addresses
OR Address
vm51267.it-garage.network
144.31.98.204:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Germany Germany
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS206134
AS Name
NEKOBYTE INTERNATIONAL LIMITED (BGP.tools)

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 7/9 | Stable: 1/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 Meets (≥100 KB/s) 73.6 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below Median: 1.3d (1/9 DA above threshold)
Min/Max: 0.9d / 12816.0d (9/9 DA, Voting / Total Eligible)
≥22.3d - 53.9d (varies)
[Stricter] moria1: ≥403.9d
Uptime Below 0.1d (R) ≥10.0d - 10.8d (varies)
HSDir Prereq: Stable Below 1/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: Fast Meets 7/9 authorities assigned Fast flag ≥5/9 authorities
WFU Below Median: 97.9% (4/9 DA above threshold)
Min/Max: 96.9% / 99.0% (9/9 DA, Voting / Total Eligible)
≥98.0%
Time Known Below Median: 4.7d (0/9 DA above threshold)
Min/Max: 4.2d / 4.9d (9/9 DA, Voting / Total Eligible)
≥1.0d (most)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Meets 7/9 authorities assigned Fast flag ≥5/9 authorities
Prereq: Stable Below 1/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: V2Dir Meets 9/9 authorities assigned V2Dir flag ≥5/9 authorities
WFU Below Median: 97.9% (4/9 DA above threshold)
Min/Max: 96.9% / 99.0% (9/9 DA, Voting / Total Eligible)
≥98% (all authorities)
Time Known Below (need 3.3 more days) Median: 4.7d (0/9 DA above threshold)
Min/Max: 4.2d / 4.9d (9/9 DA, Voting / Total Eligible)
≥8 days (all authorities)
Bandwidth Meets (≥2 MB/s) 73.6 Mbit/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 11:45:07).

Last fetch was at Thu, 29 Jan 2026 12:45:34 GMT.

73.58 Mbit/s | 73.58 Mbit/s| 8.59 Gbit/s| 8.59 Gbit/s  Measured
0.00% | N/A | 0.01% | N/A
vm51267.it-garage.network | 144.31.98.204:9001
none
none
Germany Germany
View on Interactive Map
AS206134 | NEKOBYTE INTERNATIONAL LIMITED (BGP.tools)
Fast Fast Running Running V2Dir V2Dir Valid Valid
Match Overall Uptime (100.0%/0.0%/0.0%/0.0%)
100.0%/0.0%/0.0%/0.0%
UP 2h 2m 23s ago
5d 14h 47m ago (2026-01-23 22:00:00) | 1h 47m 1s ago (2026-01-29 11:00:00)
2h 3m 49s ago (2026-01-29 10:43:12)
2026-01-23 22:00:00
No
Linux | Tor 0.4.8.21 on Linux
0.4.8.21 | Yes | recommended

Data from Tor CollecTor (authority votes, fetched 2026-01-29 11: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: 7/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9
  • Reachability: IPv4: 9/9
  • Consensus Weight (Dir. Auth.): Median: 73.6 Kbit/s | Min: 8 bit/s | Max: 144.0 Kbit/s [Warning] High deviation
  • Identified Issues:
    • Guard: WFU below threshold: Weighted Fractional Uptime 97.1% 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 4.5 days is below 8 days requirement (3.5 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 97.1% 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.

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.) 73.6 Kbit/s (median) N/A (no threshold, used for path selection)
Guard WFU (Dir. Auth., guard-wfu) 97.9% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 4.7 days ≥8 days (all authorities) BELOW - need 3.3 more days
Guard BW (Relay Reported) 73.6 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported) 0.1d ≥10.0d - 10.8d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 1 days ≥22.3d - 53.9d (typical)
[Stricter] moria1: ≥403.9d
BELOW - 1/9
Fast Speed (Relay Reported) 73.6 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) 97.9% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 4.7 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.8d
BELOW - 0/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 Running, Valid, V2Dir, Fast 73.6 Mbit/s | 816.0 Kbit/s 73.6 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 97.1% | 98% 4.5d | 8d 1.0d | 50.5d 0.1d | 11.4d 97.1% | 98.0% 4.5d | 1.0d 2026-01-29 06:54:32 49.6 Kbit/s
dannenberg (DE) Yes Yes N Yes Running, Valid, V2Dir, Fast 73.6 Mbit/s | 816.0 Kbit/s 73.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 97.1% | 98% 4.8d | 8d 0.9d | 22.3d 0.1d | 10.8d 97.1% | 98.0% 4.8d | 1.0d 2026-01-29 10:43:15 73.6 Kbit/s
dizum (NL) Yes Yes N Yes Running, Valid, V2Dir, Fast 73.6 Mbit/s | 816.0 Kbit/s 73.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 97.7% | 98% 4.7d | 8d 1.1d | 34.8d 0.1d | 10.9d 97.7% | 98.0% 4.7d | 1.0d 2026-01-29 10:29:59 73.6 Kbit/s
faravahar (US) Yes Yes N Yes Running, Valid, V2Dir, Fast 73.6 Mbit/s | 816.0 Kbit/s 73.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 98.1% | 98% 4.8d | 8d 1.3d | 47.4d 0.1d | 10.0d 98.1% | 98.0% 4.8d | 1.0d 2026-01-29 10:29:59 73.6 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Running, Valid, V2Dir 73.6 Mbit/s | 816.0 Kbit/s 73.6 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 99.0% | 98% 4.9d | 8d 2.7d | 53.9d 0.1d | 10.9d 99.0% | 98.0% 4.9d | 1.0d 2026-01-29 10:29:59 8 bit/s
longclaw (US) Yes Yes Y Yes Running, Valid, V2Dir, Fast 73.6 Mbit/s | 816.0 Kbit/s 73.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 96.9% | 98% 4.8d | 8d 1.1d | 55.1d 0.1d | 10.2d 96.9% | 98.0% 4.8d | 1.0d 2026-01-29 10:38:11 73.6 Kbit/s
maatuska (SE) Yes Yes Y Yes Running, Valid, V2Dir, Fast 73.6 Mbit/s | 816.0 Kbit/s 73.6 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 99.0% | 98% 4.7d | 8d 1.8d | 55.2d 0.1d | 10.1d 99.0% | 98.0% 4.7d | 1.0d 2026-01-29 10:43:15 144.0 Kbit/s
moria1 (US) Yes Yes Y Yes Running, Valid, V2Dir, Fast, Stable 73.6 Mbit/s | 8.4 Mbit/s 73.6 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 97.9% | 98% 4.2d | 8d 12816.0d | 403.9d 0.1d | 10.6d 97.9% | 98.0% 4.2d | 9.8d 2026-01-29 06:54:32 63.2 Kbit/s
tor26 (AT) Yes Yes Y Yes Running, Valid, V2Dir 73.6 Mbit/s | 816.0 Kbit/s 73.6 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 99.0% | 98% 4.7d | 8d 1.8d | 55.8d 0.1d | 11.9d 99.0% | 98.0% 4.7d | 1.0d 2026-01-29 10:29:59 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.