View Relay "wurzelIO"

Family: 1 relay | Lennart Hostettler... | AS60404 | Netherlands | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Exit, Fast, Running, Valid (4)
BW Verified
5/6 BW Auths Measured 96 Kbit/s Median
Stability
Not Overloaded | UP 2d 5h 47m ago | UP 93% (1M)
Reachability
IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen
1y 11mo 3w ago
BW Weight
0.01% of Network | 109 Mbit/s Observed By Relay
Version
0.4.8.10 Not Recommended
Issues Detected:
  • Guard: WFU below threshold : Weighted Fractional Uptime 93.5% 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 93.5% 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.
  • Tor version not recommended : Running Tor version 0.4.8.10 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.

Connectivity and Location

Addresses
OR Address
tor-exit-01.wurzel.io
5.255.100.26:9001
[2a04:52c0:105:d7eb::1]:9001
Exit Address
5.255.100.26
Reachability (Directory Authorities)
IPv4
9/9
IPv6
7/7 (2 don't test)
Location
Country
Netherlands Netherlands
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS60404
AS Name
The Infrastructure Group B.V. (BGP.tools)

Flags and Eligibility

Current Flags (4): Exit, Fast, Running, 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 93.5% (DA) ≥98% (all authorities)
Time Known Meets 11.9 days (DA) ≥8 days (all authorities)
Bandwidth Meets (≥2 MB/s) 109.4 Mbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s
Stable MTBF Below 12 days (DA) ≥26.6d - 45.4d (varies)
Uptime Below 2.2d (R) ≥19.1d - 19.7d (varies)
Fast Speed Meets (≥100 KB/s) 109.4 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
HSDir WFU Below 93.5% (DA) ≥98.0%
Time Known Meets 11.9 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
wurzelIO
Fingerprint
74693D7675AD548D341D15A8182AE31D7BDB6E36
AROI (?)
none
Contact
Lennart Hostettler <lennart.hostettler // wurzel.io>
IPv4 Exit Policy Summary 
reject: 
  22
  25
  119
  135-139
  445
  465
  563
  587
  1214
  4661-4666
  6346-6429
  6699
  6881-6999
IPv6 Exit Policy Summary 
none
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 5.255.100.26:*
reject *:22
reject *:25
reject *:465
reject *:587
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 Member: 1 
74693D7675AD548D341D15A8182AE31D7BDB6E36
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
109.36 Mbit/s | 109.36 Mbit/s| 8.59 Gbit/s| 8.59 Gbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.01% | N/A | N/A | 0.03%
OR Address
tor-exit-01.wurzel.io | 5.255.100.26:9001, [2a04:52c0:105:d7eb::1]:9001
Exit Address
none
Dir Address
none
Country
Netherlands Netherlands
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS60404 | The Infrastructure Group B.V. (BGP.tools)
Flags: 4
Exit Exit Fast Fast Running Running Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
Match Overall Uptime (93.9%/66.4%/57.9%/66.7%)
Uptime (1M/6M/1Y/5Y)
93.9%/66.4%/57.9%/66.7%
Uptime / Downtime
UP 2d 5h 47m ago
Seen (First | Last)
1y 11mo 3w ago (2024-01-22 12:00:00) | 1h 54m 46s ago (2026-01-10 03:00:00)
Last Restarted
2d 5h 54m ago (2026-01-07 22:59:59)
Last Changed Address or Port
2024-05-08 15:00:00
Hibernating
No
Platform (Short | Long)
Linux | Tor 0.4.8.10 on Linux
Version (Running | Recommended | Status)
0.4.8.10 | No | obsolete

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: 96.0 Kbit/s | Min: 80.0 Kbit/s | Max: 232.0 Kbit/s [Warning] High deviation
  • Identified Issues:
    • Guard: WFU below threshold: Weighted Fractional Uptime 93.5% 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 93.5% 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.
    • Tor version not recommended: Running Tor version 0.4.8.10 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.

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.) 96.0 Kbit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 93.5% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 11.9 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 109.4 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported) 2.2d ≥19.1d - 19.7d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 12 days ≥26.6d - 45.4d (typical)
[Stricter] moria1: ≥376.2d 		BELOW - 1/9
Fast Speed (Relay Reported) 109.4 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) 93.5% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 11.9 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, Valid 109.4 Mbit/s | 816.0 Kbit/s 109.4 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 93.5% | 98% 11.9d | 8d 2.0d | 47.0d 2.2d | 19.7d 93.5% | 98.0% 11.9d | 1.0d 2026-01-09 11:24:22 104.0 Kbit/s
dannenberg (DE) Yes Yes N Yes Yes Exit, Fast, Running, Valid 109.4 Mbit/s | 816.0 Kbit/s 109.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 93.2% | 98% 11.8d | 8d 1.9d | 35.7d 2.2d | 20.2d 93.2% | 98.0% 11.8d | 1.0d 2026-01-09 11:24:22 80.0 Kbit/s
dizum (NL) Yes Yes N Yes — Exit, Fast, Running, Valid 109.4 Mbit/s | 816.0 Kbit/s 109.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 93.0% | 98% 12.0d | 8d 1.9d | 26.6d 2.2d | 20.4d 93.0% | 98.0% 12.0d | 1.0d 2026-01-09 11:24:22 80.0 Kbit/s
faravahar (US) Yes Yes N Yes Yes Exit, Fast, Running, Valid 109.4 Mbit/s | 816.0 Kbit/s 109.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 94.3% | 98% 13.3d | 8d 2.6d | 41.9d 2.2d | 19.1d 94.3% | 98.0% 13.3d | 1.0d 2026-01-09 11:24:22 80.0 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Yes Exit, Fast, Running, Valid 109.4 Mbit/s | 816.0 Kbit/s 109.4 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 93.4% | 98% 12.1d | 8d 2.3d | 45.4d 2.2d | 19.6d 93.4% | 98.0% 12.1d | 1.0d 2026-01-09 11:24:22 160.0 Kbit/s
longclaw (US) Yes Yes Y Yes — Exit, Fast, Running, Valid 109.4 Mbit/s | 816.0 Kbit/s 109.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 93.2% | 98% 11.7d | 8d 1.9d | 48.7d 2.2d | 19.5d 93.2% | 98.0% 11.7d | 1.0d 2026-01-09 11:24:22 80.0 Kbit/s
maatuska (SE) Yes Yes Y Yes Yes Exit, Fast, Running, Valid 109.4 Mbit/s | 816.0 Kbit/s 109.4 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 93.0% | 98% 12.0d | 8d 2.0d | 42.3d 2.2d | 19.4d 93.0% | 98.0% 12.0d | 1.0d 2026-01-09 11:24:22 232.0 Kbit/s
moria1 (US) Yes Yes Y Yes Yes Exit, Fast, Running, Stable, Valid 109.4 Mbit/s | 8.4 Mbit/s 109.4 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 91.7% | 98% 9.8d | 8d 16893.8d | 376.2d 2.2d | 20.4d 91.7% | 98.0% 9.8d | 9.9d 2026-01-09 11:24:22 96.0 Kbit/s
tor26 (AT) Yes Yes Y Yes Yes Exit, Fast, Running, Valid 109.4 Mbit/s | 816.0 Kbit/s 109.4 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 93.6% | 98% 12.0d | 8d 2.3d | 51.8d 2.2d | 19.7d 93.6% | 98.0% 12.0d | 1.0d 2026-01-09 11:24:22 208.0 Kbit/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.