View Relay "zrts45lopp00"

Fingerprint: `FC4FF6A5C62F2F313579FF704C0BB9F710BB92A1` | Family: 1 relay | AS28753 | Germany | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Fast (4)
BW Verified: 4/7 BW Auths Measured 41 Kbit/s Median
Stability: Overloaded | DOWN 1d 2h 16m ago | UP 28% (1M)

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 3w 5d 1h ago
BW Weight: 0.00% of Network | 42 Mbit/s Observed By Relay
Version: 0.4.8.10 Not Recommended

Issues Detected:

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: WFU below threshold : Weighted Fractional Uptime 27.7% 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.
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: requires Stable flag : HSDir 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). Avoid restarts.
HSDir: WFU below threshold : WFU 27.7% 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.
Read Bandwidth Limit Hit : Read rate limit (42 Mbit/s) was hit 2 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=42 Mbit/s, Burst=5.2 MB. Limits hit: Write=0, Read=2.

Connectivity and Location

Addresses

OR Address: 37.1.197.16:443

Reachability (Directory Authorities)

IPv4: 9/9

Location

Country: Germany
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS28753
AS Name: Leaseweb Deutschland GmbH (BGP.tools)
AS Rarity: Epic (score: 3/5, 0.21% consensus weight, 9 operators)

Flags and Eligibility

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

Eligibility Flag Vote Details

Flag	Metric	Status	Relay Value	Threshold Required
Running	IPv4 Reachability	Meets (9/9 DA)	9/9 authorities reached relay	≥5/9 DA ORPort reachable
Valid	Descriptor	Meets (9/9 DA)	9/9 authorities assigned Valid	Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir	DirPort Available	Meets (9/9 DA)	Tunnelled: Yes (no DirPort) (R)	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast	Speed	Meets (9/9 DA)	42.1 Mbit/s (R)	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
Stable	MTBF	Below (1/9 DA)	Median: 0.0d (1/9 DA above threshold) Min/Max: 0.0d / 20290.2d (9/9 DA, Voting / Total Eligible)	≥9.9d - 12.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥8501.8d
Stable	Uptime	Below (0/9 DA)	0.1d (R)	≥5.3d - 5.5d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (8/9 DA)	8/9 DA assigned Fast	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Below (1/9 DA)	1/9 DA assigned Stable	≥9.9d - 12.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥8501.8d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (0/9 DA)	Median: 27.7% (0/9 DA above threshold) Min/Max: 26.2% / 30.7% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (8/9 DA)	Median: 10.0d (9/9 DA above threshold) Min/Max: 8.2d / 10.2d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Meets (8/9 DA)	8/9 DA assigned Fast	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Below (1/9 DA)	1/9 DA assigned Stable	≥9.9d - 12.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥8501.8d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (0/9 DA)	Median: 27.7% (0/9 DA above threshold) Min/Max: 26.2% / 30.7% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 10.0d (9/9 DA above threshold) Min/Max: 8.2d / 10.2d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	42.1 Mbit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.0 Mbit/s (≥5/9 DA)
Exit	Exit Policy	Below (0/9 DA)	Port 80: No \| Port 443: No (R)	Allows ≥1 /8 on ports 80 AND 443 (≥5/9 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-08-06 05:15:06).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 42.06 Mbit/s
Advertised Bandwidth: 41.94 Mbit/s
Rate Limit: 41.94 Mbit/s
Burst Limit: 41.94 Mbit/s
Total Data: 237 GB (6 months)
1mo: 237 GB | 6mo: 237 GB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-08-06 05:15:06

Measured By: 4/7 Bandwidth Authorities
Not measured by: faravahar, longclaw, maatuska
Median Measurement: 41.9 Kbit/s
Min / Max: 33.6 Kbit/s / 67.2 Kbit/s
Deviation: 33.6 Kbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0032% of network (43th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: DOWN 1d 2h 16m ago
Overall Uptime (1M/6M/1Y/5Y): 28.7%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): 28.3%/—/—/—
Hibernating: No

Timestamps

First Seen: 3w 5d 1h ago (2026-07-11 04:00:00)
Last Seen: 1d 2h 16m ago (2026-08-05 03:00:00)
Last Restarted: 2h 35m 15s ago (2026-08-06 02:41:27)
Last Changed Address: 2026-07-11 04:00:00

[Warning] OVERLOADED — Rate limits hit W:0 R:2 (limit: 42 Mbit/s)

General Overload (from /details)

Status: Not Reported

OOM killer, onionskin queue saturation, or TCP port exhaustion. Flag remains 72h after last event (Tor spec 328).

File Descriptor Exhaustion (from /bandwidth)

Status: Not Reported

Rate Limits (from /bandwidth)

Rate Limit: 41.94 Mbit/s
Burst Limit: 5.2 MB
Write Limit Hit: 0 times
Read Limit Hit: 2 times
Last Reported: 1 days ago

Recommendations

Consider increasing RelayBandwidthRate
Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-08-05 22:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: none

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

FC4FF6A5C62F2F313579FF704C0BB9F710BB92A1 (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.8.10 on Linux
Version: 0.4.8.10 — Not Recommended
Version Status: Obsolete — Update urgently. See torproject.org/download

Exit Health & Policy

DNS Health

Not an exit relay — DNS health testing does not apply.

IPv4 Exit Policy Summary

reject: 
  1-65535

Full Exit Policy

reject *:*

Last fetch was at Thu, 06 Aug 2026 05:16:41 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-08-06 05:15:06).

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	Exit	MiddleOnly	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	No	—	N	Yes	Running, Valid, V2Dir, Fast	42.1 Mbit/s \| 816.0 Kbit/s	42.1 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	27.7% \| 98%	10.1d \| 8d	0.0d \| 12.2d	0.1d \| 5.5d	27.7% \| 98.0%	10.1d \| 1.0d	2026-08-06 02:43:31	41.9 Kbit/s
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	42.1 Mbit/s \| 816.0 Kbit/s	42.1 Mbit/s \| 328.0 Mbit/s OR 16.0 Mbit/s	26.9% \| 98%	10.1d \| 8d	0.0d \| 10.6d	0.1d \| 5.6d	26.9% \| 98.0%	10.1d \| 1.0d	2026-08-06 02:43:31	33.6 Kbit/s
dizum (NL)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast	42.1 Mbit/s \| 816.0 Kbit/s	42.1 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	27.1% \| 98%	10.1d \| 8d	0.0d \| 9.9d	0.1d \| 5.3d	27.1% \| 98.0%	10.1d \| 1.0d	2026-08-06 02:43:31	41.9 Kbit/s
faravahar (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	42.1 Mbit/s \| 816.0 Kbit/s	42.1 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	30.7% \| 98%	10.0d \| 8d	0.1d \| 10.1d	0.1d \| 5.4d	30.7% \| 98.0%	10.0d \| 1.0d	2026-08-06 02:43:31	41.9 Kbit/s
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	42.1 Mbit/s \| 816.0 Kbit/s	42.1 Mbit/s \| 312.0 Mbit/s OR 16.0 Mbit/s	28.4% \| 98%	8.2d \| 8d	0.0d \| 13.4d	0.1d \| 5.5d	28.4% \| 98.0%	8.2d \| 1.0d	2026-08-06 02:43:31	67.2 Kbit/s
longclaw (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	42.1 Mbit/s \| 816.0 Kbit/s	42.1 Mbit/s \| 248.0 Mbit/s OR 16.0 Mbit/s	26.2% \| 98%	9.2d \| 8d	0.0d \| 17.3d	0.1d \| 5.5d	26.2% \| 98.0%	9.2d \| 1.0d	2026-08-06 02:43:31	41.9 Kbit/s
maatuska (SE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir	42.1 Mbit/s \| 816.0 Kbit/s	42.1 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	28.4% \| 98%	10.2d \| 8d	0.1d \| 10.8d	0.1d \| 5.5d	28.4% \| 98.0%	10.2d \| 1.0d	2026-08-06 02:43:31	41.9 Kbit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable	42.1 Mbit/s \| 8.4 Mbit/s	42.1 Mbit/s \| 216.0 Mbit/s OR 16.0 Mbit/s	28.5% \| 98%	9.8d \| 8d	20290.2d \| 8501.8d	0.1d \| 5.4d	28.5% \| 98.0%	9.81d \| 9.85d	2026-08-06 02:43:31	35.2 Kbit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	42.1 Mbit/s \| 816.0 Kbit/s	42.1 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	27.1% \| 98%	9.8d \| 8d	0.0d \| 12.6d	0.1d \| 5.4d	27.1% \| 98.0%	9.8d \| 1.0d	2026-08-06 02:43:31	64.8 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). Self-reported uptime from 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.