View Relay "NerdreichRelay1"

Fingerprint: `BE2B68B8B88BFC353302360D58ACF9BD9BA98024` | Family: 1 relay | email:tormaster[]nerdreich.de... | AS197540 | Germany | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, Fast, Stable (4)
BW Verified: 6/7 BW Auths Measured 200 Kbit/s Median
Stability: Overloaded | UP 5d 8h 16m ago | UP 89% (1M)

Reachability: IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen: 2y 7mo 1w ago
BW Weight: 0.01% of Network | 165 Mbit/s Observed By Relay
Version: 0.4.9.11 Recommended

Issues Detected:

HSDir: requires V2Dir (tunnelled-dir-server) : HSDir requires the relay to support tunnelled directory requests (V2Dir flag). This relay is missing V2Dir — the descriptor likely does not include tunnelled-dir-server, usually because DirCache 0 is set in torrc.
Suggestion: Remove DirCache 0 from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includes tunnelled-dir-server. You can check with: grep tunnelled-dir-server /var/lib/tor/cached-descriptors
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.
General Overload Active : Relay reported general overload at 2026-08-06 04:00 UTC. This indicates OOM killer invocation, onionskin queue saturation, or TCP port exhaustion.
Suggestion: Check CPU/memory with htop. Review logs for "out of memory" or "onionskins" warnings. Consider increasing MaxMemInQueues in torrc. Verify TCP ports available.
Write Bandwidth Limit Hit : Write rate limit (157 Mbit/s) was hit 2,918 times. Relay is throttling outbound traffic.
Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more upload capacity.
Read Bandwidth Limit Hit : Read rate limit (157 Mbit/s) was hit 10,972 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=157 Mbit/s, Burst=39 MB. Limits hit: Write=2,918, Read=10,972.

Connectivity and Location

Addresses

OR Address: nio.lkspr.net
89.58.3.114:443
[2a03:4000:5d:e6a:d8cc:e3ff:fea6:f015]:443

Reachability (Directory Authorities)

IPv4: 9/9
IPv6: 8/8 (1 don't test)

Location

Country: Germany
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS197540
AS Name: netcup GmbH (BGP.tools)
AS Rarity: Emerging (score: 1/5, 3.56% consensus weight, 181 operators)

Flags and Eligibility

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

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
Running	IPv6 Reachability	Meets (8/8 DA)	8/8 tested authorities reached relay	≥5/8 tested (majority) (≥5/8 DA)
Valid	Descriptor	Meets (9/9 DA)	9/9 authorities assigned Valid	Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir	DirPort Available	Below (0/9 DA)	No DirPort, no tunnelled-dir-server (R)	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast	Speed	Meets (9/9 DA)	165.4 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	Partial (8/9 DA)	Median: 44.9d (9/9 DA above threshold) Min/Max: 18.3d / 6095.9d (9/9 DA, Voting / Total Eligible)	≥9.9d - 12.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥8501.8d
Stable	Uptime	Below (1/9 DA)	5.3d (R)	≥5.3d - 5.5d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (9/9 DA)	9/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	Meets (9/9 DA)	9/9 DA assigned Stable	≥9.9d - 12.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥8501.8d
	Prereq: V2Dir	Below (0/9 DA)	0/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (3/9 DA)	Median: 97.1% (3/9 DA above threshold) Min/Max: 83.0% / 99.0% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 65.6d (9/9 DA above threshold) Min/Max: 9.9d / 183.7d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Meets (9/9 DA)	9/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	Meets (9/9 DA)	9/9 DA assigned Stable	≥9.9d - 12.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥8501.8d
	Prereq: V2Dir	Below (0/9 DA)	0/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (3/9 DA)	Median: 97.1% (3/9 DA above threshold) Min/Max: 83.0% / 99.0% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 65.6d (9/9 DA above threshold) Min/Max: 9.9d / 183.7d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	165.4 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: 165.44 Mbit/s
Advertised Bandwidth: 125.83 Mbit/s
Rate Limit: 125.83 Mbit/s
Burst Limit: 314.57 Mbit/s
Total Data: 3.4 PB (5 years)
1mo: 70 TB | 6mo: 386 TB | 1y: 739 TB | 5y: 3.4 PB

Measurement (Directory Authority Verified)

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

Measured By: 6/7 Bandwidth Authorities
Not measured by: faravahar
Median Measurement: 200.0 Kbit/s
Min / Max: 80.0 Kbit/s / 312.0 Kbit/s
Deviation: 232.0 Kbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0141% of network (74th pctl) | Guard: N/A | Middle: 0.0424% (93th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: UP 5d 8h 16m ago
Overall Uptime (1M/6M/1Y/5Y): 89.4%/98.2%/99.1%/98.9%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (89.4%/98.2%/99.1%/98.9%)
Hibernating: No

Timestamps

First Seen: 2y 7mo 1w ago (2024-01-01 00:00:00)
Last Seen: 1h 16m 6s ago (2026-08-06 05:00:00)
Last Restarted: 5d 8h 16m ago (2026-07-31 21:59:59)
Last Changed Address: 2026-04-06 23:00:00

[Warning] OVERLOADED — General overload at 2026-08-06 04:00 UTC; Rate limits hit W:2918 R:10972 (limit: 157 Mbit/s)

General Overload (from /details)

Status: Reported
When: 2026-08-06 04:00 UTC (2 hours ago)

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: 157.29 Mbit/s
Burst Limit: 39 MB
Write Limit Hit: 2,918 times
Read Limit Hit: 10,972 times
Last Reported: 21 hours ago

Recommendations

Check CPU/memory: htop
Review MaxMemInQueues in torrc
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: email:tormaster[]nerdreich.de btc:1Ma9whLg6U5HDBUPDmH82W5rbpakNkmiJX xmr:891ef7Fp1e8j8T57cy3cQmdGyLHXmwvJC8L47V2d8tzoVj4RQ9Pg2Y5SeQ6WEnrhLoaff6EkrWqPQ7CSLGmdSnNvSb2jXiz eth:0xd1a9fd16aedabc09cbac360fed2031dd8272776a ciissversion:2

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

BE2B68B8B88BFC353302360D58ACF9BD9BA98024 (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.11 on Linux
Version: 0.4.9.11 — Recommended
Version Status: Recommended

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 06:16:05 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	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	No	—	N	Yes	Yes	Running, Valid, Fast, Stable	165.4 Mbit/s \| 816.0 Kbit/s	165.4 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	99.0% \| 98%	183.5d \| 8d	128.0d \| 12.2d	5.3d \| 5.5d	99.0% \| 98.0%	183.5d \| 1.0d	2026-08-05 10:00:13	80.0 Kbit/s
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, Fast, Stable	165.4 Mbit/s \| 816.0 Kbit/s	165.4 Mbit/s \| 328.0 Mbit/s OR 16.0 Mbit/s	97.1% \| 98%	65.6d \| 8d	44.9d \| 10.6d	5.3d \| 5.6d	97.1% \| 98.0%	65.6d \| 1.0d	2026-08-05 10:00:13	264.0 Kbit/s
dizum (NL)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, Fast, Stable	165.4 Mbit/s \| 816.0 Kbit/s	165.4 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	95.0% \| 98%	39.7d \| 8d	26.6d \| 9.9d	5.3d \| 5.3d	95.0% \| 98.0%	39.7d \| 1.0d	2026-08-05 10:00:13	80.0 Kbit/s
faravahar (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, Fast, Stable	165.4 Mbit/s \| 816.0 Kbit/s	165.4 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	93.2% \| 98%	28.3d \| 8d	18.3d \| 10.1d	5.3d \| 5.4d	93.2% \| 98.0%	28.3d \| 1.0d	2026-08-05 10:00:13	80.0 Kbit/s
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, Fast, Stable	165.4 Mbit/s \| 816.0 Kbit/s	165.4 Mbit/s \| 312.0 Mbit/s OR 16.0 Mbit/s	97.5% \| 98%	80.6d \| 8d	36.0d \| 13.4d	5.3d \| 5.5d	97.5% \| 98.0%	80.6d \| 1.0d	2026-08-05 10:00:13	200.0 Kbit/s
longclaw (US)	Yes	Yes	No	—	Y	Yes	—	Running, Valid, Fast, Stable	165.4 Mbit/s \| 816.0 Kbit/s	165.4 Mbit/s \| 248.0 Mbit/s OR 16.0 Mbit/s	98.9% \| 98%	176.9d \| 8d	123.4d \| 17.3d	5.3d \| 5.5d	98.9% \| 98.0%	176.9d \| 1.0d	2026-08-05 10:00:13	312.0 Kbit/s
maatuska (SE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, Fast, Stable	165.4 Mbit/s \| 816.0 Kbit/s	165.4 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	95.9% \| 98%	48.5d \| 8d	32.8d \| 10.8d	5.3d \| 5.5d	95.9% \| 98.0%	48.5d \| 1.0d	2026-08-05 10:00:13	232.0 Kbit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, Fast, Stable	165.4 Mbit/s \| 8.4 Mbit/s	165.4 Mbit/s \| 216.0 Mbit/s OR 16.0 Mbit/s	83.0% \| 98%	9.9d \| 8d	6095.9d \| 8501.8d	5.3d \| 5.4d	83.0% \| 98.0%	9.9d \| 9.8d	2026-08-05 10:00:13	144.0 Kbit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, Fast, Stable	165.4 Mbit/s \| 816.0 Kbit/s	165.4 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	99.0% \| 98%	183.7d \| 8d	128.2d \| 12.6d	5.3d \| 5.4d	99.0% \| 98.0%	183.7d \| 1.0d	2026-08-05 10:00:13	240.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). 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.