Tor Relays :: PresidentXi

View Relay "PresidentXi"

Family: 3 relays | IchAntworteNicht@proton.me | AS208208 | Germany | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Fast, Running, V2Dir, Valid (4)
BW Verified: 5/6 BW Auths Measured 80 Kbit/s Median
Stability: Not Overloaded | UP 1d 4h 13m ago | UP 65% (1M)

Reachability: IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen: 3w 15h 47m ago
BW Weight: 0.01% of Network | 0 Kbit/s Observed By Relay
Version: 0.4.8.21 Recommended

Issues Detected:

Guard: WFU below threshold : Weighted Fractional Uptime 50.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 50.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: 185.230.161.105:443
[2a09:6301:0:4b5:2eab:ba2e:fa96:1a3f]:443

Reachability (Directory Authorities)

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

Location

Country: Germany
Interactive Map: View on Interactive Map

Autonomous System

AS Number: AS208208
AS Name: Marco Lingl trading as Cyberse GmbH & Co. KG (BGP.tools)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Fast

Eligibility Flag Vote Details

Flag	Metric	Status	Relay Value	Threshold Required
Fast	Speed	Below	80.0 Kbit/s (R)	≥800.0 Kbit/s (guarantee) OR top 7/8 [Stricter] moria1: ≥8.4 Mbit/s
Stable	MTBF	Below	Median: 4.6d (1/9 DA above threshold) Min/Max: 3.1d / 6037.3d (9/9 DA, Voting / Total Eligible)	≥22.0d - 54.0d (varies) [Stricter] moria1: ≥405.5d
Stable	Uptime	Below	1.2d (R)	≥9.7d - 10.1d (varies)
HSDir	Prereq: Stable	Below	1/9 authorities assigned Stable flag	≥5/9 authorities
	Prereq: Fast	Meets	5/9 authorities assigned Fast flag	≥5/9 authorities
	WFU	Below	Median: 48.7% (0/9 DA above threshold) Min/Max: 42.4% / 50.8% (9/9 DA, Voting / Total Eligible)	≥98.0%
	Time Known	Meets	Median: 13.1d (9/9 DA above threshold) Min/Max: 8.8d / 13.4d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) [Stricter] moria1: ≥9.9d
Guard	Prereq: Fast	Meets	5/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: 48.7% (0/9 DA above threshold) Min/Max: 42.4% / 50.8% (9/9 DA, Voting / Total Eligible)	≥98% (all authorities)
	Time Known	Meets	Median: 13.1d (9/9 DA above threshold) Min/Max: 8.8d / 13.4d (9/9 DA, Voting / Total Eligible)	≥8 days (all authorities)
	Bandwidth	Below	80.0 Kbit/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 14:45:07).

Last fetch was at Thu, 29 Jan 2026 14:45:42 GMT.

Nickname

PresidentXi

Fingerprint

E3AFB6136FCE6B651785818A99E2E51972036225

AROI (?)

none

Contact

IchAntworteNicht@proton.me

IPv4 Exit Policy Summary

reject: 
  1-65535

IPv6 Exit Policy Summary

none

Exit Policy

reject *:*

Effective Family Members: 3 (View)

2F16FAC5EE676C08743B467835B6C562A1808DEA
4113E50AE4232C006ED799B8FA76FF1FFB4A59F9
E3AFB6136FCE6B651785818A99E2E51972036225

Alleged Family Members: 0

none

Indirect Family Members: 0

none

Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit): 0.00 Kbit/s | unknown| 73.40 Mbit/s| 209.72 Mbit/s Measured
Network Participation (Consensus Weight | Guard | Middle | Exit): 0.01% | N/A | 0.03% | N/A
OR Address: 185.230.161.105:443, [2a09:6301:0:4b5:2eab:ba2e:fa96:1a3f]:443
Exit Address: none
Dir Address: none
Country: Germany
Interactive Map: View on Interactive Map
Autonomous System (AS Number | AS Name): AS208208 | Marco Lingl trading as Cyberse GmbH & Co. KG (BGP.tools)
Flags: 4: Fast Running V2Dir Valid
Flag Uptime (1M/6M/1Y/5Y): 57.0%/—/—/—
Uptime (1M/6M/1Y/5Y): 65.2%/0.0%/0.0%/0.0%
Uptime / Downtime: UP 1d 4h 13m ago
Seen (First | Last): 3w 15h 47m ago (2026-01-07 23:00:00) | 1h 47m 13s ago (2026-01-29 13:00:00)
Last Restarted: 1d 4h 15m ago (2026-01-28 10:32:13)
Last Changed Address or Port: 2026-01-07 23: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-29 14: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: 5/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9
Reachability: IPv4: 9/9 | IPv6: 7/7 (2 don't test)
Consensus Weight (Dir. Auth.): Median: 80.0 Kbit/s | Min: 0 bit/s | Max: 168.0 Kbit/s [Warning] High deviation
Identified Issues:
- Guard: WFU below threshold: Weighted Fractional Uptime 50.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 50.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.)	80.0 Kbit/s (median)	N/A (no threshold, used for path selection)	—
Guard WFU (Dir. Auth., guard-wfu)	48.7%	≥98% (all authorities)	BELOW - cannot get Guard
Guard TK (Dir. Auth., tk)	13.1 days	≥8 days (all authorities)	MEETS
Guard BW (Relay Reported)	80.0 Kbit/s	≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s	BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported)	1.2d	≥9.7d - 10.1d (typical)	BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf)	5 days	≥22.0d - 54.0d (typical) [Stricter] moria1: ≥405.5d	BELOW - 1/9
Fast Speed (Relay Reported)	80.0 Kbit/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)	48.7%	≥98.0% (from all auths)	BELOW - 0/9
HSDir TK (Dir. Auth., tk)	13.1 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	Running, Valid, V2Dir, Fast	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 232.0 Mbit/s OR 16.0 Mbit/s	50.8% \| 98%	12.4d \| 8d	4.5d \| 49.8d	1.2d \| 10.6d	50.8% \| 98.0%	12.4d \| 1.0d	2026-01-29 04:32:21	80.0 Kbit/s
dannenberg (DE)	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	43.5% \| 98%	11.5d \| 8d	3.1d \| 22.0d	1.2d \| 10.1d	43.5% \| 98.0%	11.5d \| 1.0d	2026-01-29 04:32:21	—
dizum (NL)	Yes	Yes	N	Yes	—	Running, Valid, V2Dir	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	42.4% \| 98%	11.9d \| 8d	3.1d \| 34.6d	1.2d \| 10.1d	42.4% \| 98.0%	11.9d \| 1.0d	2026-01-29 04:32: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	48.7% \| 98%	13.4d \| 8d	4.6d \| 47.5d	1.2d \| 9.7d	48.7% \| 98.0%	13.4d \| 1.0d	2026-01-29 04:32:21	—
gabelmoo (DE)	Yes	Yes	Y	Yes	Yes	Running, Valid, V2Dir, Fast	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 304.0 Mbit/s OR 16.0 Mbit/s	47.8% \| 98%	13.1d \| 8d	4.5d \| 54.0d	1.2d \| 10.1d	47.8% \| 98.0%	13.1d \| 1.0d	2026-01-29 04:32:21	160.0 Kbit/s
longclaw (US)	Yes	Yes	Y	Yes	—	Running, Valid, V2Dir	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	48.9% \| 98%	13.4d \| 8d	4.6d \| 54.8d	1.2d \| 9.9d	48.9% \| 98.0%	13.4d \| 1.0d	2026-01-29 04:32:21	—
maatuska (SE)	Yes	Yes	Y	Yes	Yes	Running, Valid, V2Dir, Fast	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 312.0 Mbit/s OR 16.0 Mbit/s	48.9% \| 98%	13.4d \| 8d	4.6d \| 54.4d	1.2d \| 9.8d	48.9% \| 98.0%	13.4d \| 1.0d	2026-01-29 04:32:21	160.0 Kbit/s
moria1 (US)	Yes	Yes	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable	0 bit/s \| 8.4 Mbit/s	0 bit/s \| 240.0 Mbit/s OR 16.0 Mbit/s	46.7% \| 98%	8.8d \| 8d	6037.3d \| 405.5d	1.2d \| 10.1d	46.7% \| 98.0%	8.8d \| 9.9d	2026-01-29 04:32:21	104.0 Kbit/s
tor26 (AT)	Yes	Yes	Y	Yes	Yes	Running, Valid, V2Dir, Fast	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 288.0 Mbit/s OR 16.0 Mbit/s	48.9% \| 98%	13.4d \| 8d	4.6d \| 55.9d	1.2d \| 11.1d	48.9% \| 98.0%	13.4d \| 1.0d	2026-01-29 04:32:21	168.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.