Tor Relays :: ohWi7sie4ahlizahg8a

View Relay "ohWi7sie4ahlizahg8a"

Family: 6 relays | tor@wurzelmann.at | AS8560 | United Kingdom of Great Britain and Northern Ireland | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, V2Dir, Valid (3)
BW Verified: 5/6 BW Auths Measured 8 bit/s Median
Stability: Not Overloaded | UP 14h 38m 26s ago

Reachability: IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen: 13h 47m 20s ago
BW Weight: 0.00% of Network | 0 Kbit/s Observed By Relay
Version: 0.4.8.22 Recommended

Issues Detected:

Guard: Time Known below threshold : Time Known 0.5 days is below 8 days requirement (7.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).
Guard: requires Fast flag : Guard flag requires having the Fast flag first
Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
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: Time Known below threshold : Time Known 12.7 hours below 25 hours (dir-spec default)
Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
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: angharad.wurzelmann.at
87.106.110.34:443
[2a00:da00:f468:bf00::1]:443

Reachability (Directory Authorities)

IPv4: 9/9
IPv6: 7/7 (2 don't test)

Location

Country: United Kingdom of Great Britain and Northern Ireland
Interactive Map: View on Interactive Map

Autonomous System

AS Number: AS8560
AS Name: IONOS SE (BGP.tools)
AS Rarity: Emerging (score: 1/5, 2.98% consensus weight, 167 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, V2Dir

Eligibility Flag Vote Details

Flag	Metric	Status	Relay Value	Threshold Required
Fast	Speed	Below	8 bit/s (R)	≥800.0 Kbit/s (guarantee) OR top 7/8 [Stricter] moria1: ≥8.4 Mbit/s
Stable	MTBF	Below	Median: 0.5d (0/9 DA above threshold) Min/Max: 0.2d / 0.5d (9/9 DA, Voting / Total Eligible)	≥22.3d - 52.0d (varies) [Stricter] moria1: ≥442.5d
Stable	Uptime	Below	0.6d (R)	≥6.4d - 7.6d (varies)
HSDir	Prereq: Stable	Below	0/9 authorities assigned Stable flag	≥5/9 authorities
	Prereq: Fast	Below	0/9 authorities assigned Fast flag	≥5/9 authorities
	WFU	Meets	Majority: 100.0% (9/9 DA)	≥98.0%
	Time Known	Below	Median: 0.5d (0/9 DA above threshold) Min/Max: 0.2d / 0.5d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Below	0/9 authorities assigned Fast flag	≥5/9 authorities
	Prereq: Stable	Below	0/9 authorities assigned Stable flag	≥5/9 authorities
	Prereq: V2Dir	Meets	9/9 authorities assigned V2Dir flag	≥5/9 authorities
	WFU	Meets	Majority: 100.0% (9/9 DA)	≥98% (all authorities)
	Time Known	Below (need 7.5 more days)	Median: 0.5d (0/9 DA above threshold) Min/Max: 0.2d / 0.5d (9/9 DA, Voting / Total Eligible)	≥8 days (all authorities)
	Bandwidth	Below	8 bit/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-02-11 22:45:07).

Last fetch was at Wed, 11 Feb 2026 23:45:42 GMT.

Nickname

ohWi7sie4ahlizahg8a

Fingerprint

131B0A31E487197D3C38A2778C0B6334953DE1CF

AROI (?)

none

Contact

tor@wurzelmann.at

IPv4 Exit Policy Summary

reject: 
  1-65535

IPv6 Exit Policy Summary

none

Exit Policy

reject *:*

Effective Family Members: 6 (View)

131B0A31E487197D3C38A2778C0B6334953DE1CF
9721548CB554B5E6A1CAC823AAD29800785A77B5
B3E9AF81BA20C80C14C4739E9DCCD055923BB35F
D8264158CADD79C871E051E447FED01924065982
DBDEB20419CCA33037E7C92601DEA597D5187E73
F9583CFAAC972193A6DDA21920937C2D5B6FA6F8

Alleged Family Member: 1

0DB4B9654E02A4159A838915F5D3CB13EA6AD134

Indirect Family Member: 1

0DB4B9654E02A4159A838915F5D3CB13EA6AD134

Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit): 0.00 Kbit/s | unknown| 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: angharad.wurzelmann.at | 87.106.110.34:443, [2a00:da00:f468:bf00::1]:443
Exit Address: none
Dir Address: none
Country: United Kingdom of Great Britain and Northern Ireland
Interactive Map: View on Interactive Map
Autonomous System (AS Number | AS Name): AS8560 | IONOS SE (BGP.tools)
Flags: 3: Running V2Dir Valid
Flag Uptime (1M/6M/1Y/5Y): Match Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Uptime (1M/6M/1Y/5Y): 0.0%/0.0%/0.0%/0.0%
Uptime / Downtime: UP 14h 38m 26s ago
Seen (First | Last): 13h 47m 20s ago (2026-02-11 10:00:00) | 1h 47m 20s ago (2026-02-11 22:00:00)
Last Restarted: 14h 40m 2s ago (2026-02-11 09:07:18)
Last Changed Address or Port: 2026-02-11 10:00:00
Hibernating: No
Platform (Short | Long): Linux | Tor 0.4.8.22 on Linux
Version (Running | Recommended | Status): 0.4.8.22 | Yes | recommended

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-02-11 22: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: 0/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9
Reachability: IPv4: 9/9 | IPv6: 7/7 (2 don't test)
Consensus Weight (Dir. Auth.): Median: 8 bit/s | Min: 0 bit/s | Max: 8 bit/s [Warning] High deviation
Identified Issues:
- Guard: Time Known below threshold: Time Known 0.5 days is below 8 days requirement (7.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).
- Guard: requires Fast flag: Guard flag requires having the Fast flag first
  - Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
- 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: Time Known below threshold: Time Known 12.7 hours below 25 hours (dir-spec default)
  - Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
- 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.)	8 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)	0.5 days	≥8 days (all authorities)	BELOW - need 7.5 more days
Guard BW (Relay Reported)	8 bit/s	≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s	BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported)	0.6d	≥6.4d - 7.6d (typical)	BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf)	1 days	≥22.3d - 52.0d (typical) [Stricter] moria1: ≥442.5d	BELOW - 0/9
Fast Speed (Relay Reported)	8 bit/s	≥800.0 Kbit/s (guarantee) OR ≥816.0 Kbit/s (typical) [Stricter] moria1: ≥8.4 Mbit/s	BELOW - need ≥100 KB/s
HSDir WFU (Dir. Auth., wfu)	100.0%	≥98.0% (from all auths)	BELOW - 0/9
HSDir TK (Dir. Auth., tk)	0.5 days	≥1.0d (8/9 auths) [Stricter] moria1: ≥9.8d	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	Running, Valid, V2Dir	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 224.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.5d \| 8d	0.5d \| 52.0d	0.6d \| 7.6d	100.0% \| 98.0%	0.5d \| 1.0d	2026-02-11 09:07:21	8 bit/s
dannenberg (DE)	Yes	Yes	N	Yes	Yes	Running, Valid, V2Dir	0 bit/s \| 712.0 Kbit/s	0 bit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.5d \| 6d	0.5d \| 22.3d	0.6d \| 6.4d	100.0% \| 98.0%	0.5d \| 1.0d	2026-02-11 09:07:21	—
dizum (NL)	Yes	Yes	N	Yes	—	Running, Valid, V2Dir	0 bit/s \| 704.0 Kbit/s	0 bit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.5d \| 6d	0.5d \| 27.8d	0.6d \| 6.4d	100.0% \| 98.0%	0.5d \| 1.0d	2026-02-11 09:07:21	—
faravahar (US)	Yes	Yes	N	Yes	Yes	Running, Valid, V2Dir	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.5d \| 8d	0.5d \| 48.0d	0.6d \| 7.6d	100.0% \| 98.0%	0.5d \| 1.0d	2026-02-11 09:07:21	—
gabelmoo (DE)	Yes	Yes	Y	Yes	Yes	Running, Valid, V2Dir	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 312.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.5d \| 8d	0.5d \| 60.5d	0.6d \| 7.6d	100.0% \| 98.0%	0.5d \| 1.0d	2026-02-11 09:07:21	8 bit/s
longclaw (US)	Yes	Yes	Y	Yes	—	Valid, V2Dir	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.2d \| 8d	0.2d \| 62.0d	0.6d \| 7.6d	100.0% \| 98.0%	0.2d \| 1.0d	2026-02-11 09:07:21	—
maatuska (SE)	Yes	Yes	Y	Yes	Yes	Running, Valid, V2Dir	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 304.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.5d \| 8d	0.5d \| 41.9d	0.6d \| 7.6d	100.0% \| 98.0%	0.5d \| 1.0d	2026-02-11 09:07:21	8 bit/s
moria1 (US)	Yes	Yes	Y	Yes	Yes	Running, Valid, V2Dir	0 bit/s \| 8.4 Mbit/s	0 bit/s \| 224.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.5d \| 8d	0.5d \| 442.5d	0.6d \| 7.6d	100.0% \| 98.0%	0.5d \| 9.8d	2026-02-11 09:07:21	8 bit/s
tor26 (AT)	Yes	Yes	Y	Yes	Yes	Running, Valid, V2Dir	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.5d \| 8d	0.5d \| 57.7d	0.6d \| 7.6d	100.0% \| 98.0%	0.5d \| 1.0d	2026-02-11 09:07:21	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.