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
5/7 BW Auths Measured 120 Kbit/s Median
Stability
Overloaded | UP 3d 2h 57m ago | UP 96% (1M)
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen
2y 10mo 1w ago
BW Weight
0.01% of Network | 165 Mbit/s Observed By Relay
Version
0.4.9.16 Recommended
Issues Detected:
  • Guard: WFU below threshold : Weighted Fractional Uptime 96.0% 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.
  • 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
  • HSDir: WFU below threshold : WFU 96.0% 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.
  • Write Bandwidth Limit Hit : Write rate limit (157 Mbit/s) was hit 140 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 161 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=140, Read=161.

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 Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS197540
AS Name
netcup GmbH (BGP.tools)
AS Rarity
Common (score: 0/5, 4.25% consensus weight, 186 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, Fast, Stable
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 9/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 0/9
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
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.6 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 (6/9 DA) Median: 11.8d (5/9 DA above threshold)
Min/Max: 5.3d / 6496.3d (9/9 DA, Voting / Total Eligible)		 ≥3.2d - 11.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥6577.2d
Uptime Below (0/9 DA) 3.1d (R) ≥3.3d - 3.3d (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 ≥3.2d - 11.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥6577.2d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 97.5% (0/9 DA above threshold)
Min/Max: 94.7% / 97.6% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 21.0d (9/9 DA above threshold)
Min/Max: 9.8d / 22.0d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
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 ≥3.2d - 11.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥6577.2d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 97.5% (0/9 DA above threshold)
Min/Max: 94.7% / 97.6% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 21.0d (9/9 DA above threshold)
Min/Max: 9.8d / 22.0d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 165.6 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-280.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-11-08 08:01:41).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
165.55 Mbit/s
Advertised Bandwidth
125.83 Mbit/s
Rate Limit
125.83 Mbit/s
Burst Limit
314.57 Mbit/s
Total Data
3.6 PB (5 years)
1mo: 69 TB | 6mo: 415 TB | 1y: 767 TB | 5y: 3.6 PB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-08 08:01:41

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Median Measurement
120.0 Kbit/s
Min / Max
80.0 Kbit/s / 248.0 Kbit/s
Deviation
168.0 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0130% of network (71th pctl) | Guard: N/A | Middle: 0.0386% (90th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 3d 2h 57m ago
Overall Uptime (1M/6M/1Y/5Y)
97.0%/96.3%/98.1%/98.6%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (97.0%/96.3%/98.1%/98.6%)
Hibernating
No
Timestamps
First Seen
2y 10mo 1w ago (2024-01-01 00:00:00)
Last Seen
2h 6m 56s ago (2026-11-08 06:00:00)
Last Restarted
3d 2h 57m ago (2026-11-05 05:09:25)
Last Changed Address
2026-04-06 23:00:00
[Warning] OVERLOADED — Rate limits hit W:140 R:161 (limit: 157 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
157.29 Mbit/s
Burst Limit
39 MB
Write Limit Hit
140 times
Read Limit Hit
161 times
Last Reported
18 hours ago
Recommendations
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-11-07 23: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.16 on Linux
Version
0.4.9.16 — 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
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Sun, 08 Nov 2026 08:06:52 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-11-08 08:01:41).

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 — Y Yes Yes Running, Valid, Fast, Stable 165.6 Mbit/s | 816.0 Kbit/s 165.6 Mbit/s | 184.0 Mbit/s OR 16.0 Mbit/s 96.0% | 98% 16.4d | 8d 8.9d | 9.7d 3.1d | 5.7d 96.0% | 98.0% 16.4d | 1.0d 2026-11-05 23:09:30 120.0 Kbit/s
dannenberg (DE) Yes Yes No — Y Yes Yes Running, Valid, Fast, Stable 165.6 Mbit/s | 816.0 Kbit/s 165.6 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 97.5% | 98% 20.7d | 8d 11.8d | 11.2d 3.1d | 3.4d 97.5% | 98.0% 20.7d | 1.0d 2026-11-07 15:09:27 248.0 Kbit/s
dizum (NL) Yes Yes No — N Yes Yes Running, Valid, Fast, Stable 165.6 Mbit/s | 816.0 Kbit/s 165.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 96.1% | 98% 18.3d | 8d 5.3d | 8.6d 3.1d | 3.4d 96.1% | 98.0% 18.3d | 1.0d 2026-11-07 15:09:27 80.0 Kbit/s
faravahar (US) Yes Yes No — Y Yes Yes Running, Valid, Fast, Stable 165.6 Mbit/s | 816.0 Kbit/s 165.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 97.6% | 98% 21.3d | 8d 11.2d | 8.0d 3.1d | 3.3d 97.6% | 98.0% 21.3d | 1.0d 2026-11-07 15:09:27 80.0 Kbit/s
gabelmoo (DE) Yes Yes No — Y Yes Yes Running, Valid, Fast, Stable 165.6 Mbit/s | 816.0 Kbit/s 165.6 Mbit/s | 264.0 Mbit/s OR 16.0 Mbit/s 97.6% | 98% 22.0d | 8d 14.7d | 12.9d 3.1d | 3.3d 97.6% | 98.0% 22.0d | 1.0d 2026-11-07 15:09:27 200.0 Kbit/s
longclaw (US) Yes Yes No — Y Yes — Running, Valid, Fast, Stable 165.6 Mbit/s | 816.0 Kbit/s 165.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 97.6% | 98% 21.3d | 8d 14.5d | 13.2d 3.1d | 3.3d 97.6% | 98.0% 21.3d | 1.0d 2026-11-07 15:09:27 80.0 Kbit/s
maatuska (SE) Yes Yes No — N Yes Yes Running, Valid, Fast, Stable 165.6 Mbit/s | 816.0 Kbit/s 165.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 97.1% | 98% 21.0d | 8d 7.5d | 3.2d 3.1d | 3.3d 97.1% | 98.0% 21.0d | 1.0d 2026-11-07 15:09:27 80.0 Kbit/s
moria1 (US) Yes Yes No — Y Yes Yes Running, Valid, Fast, Stable 165.6 Mbit/s | 8.4 Mbit/s 165.6 Mbit/s | 184.0 Mbit/s OR 16.0 Mbit/s 94.7% | 98% 9.8d | 8d 6496.3d | 6577.2d 3.1d | 3.3d 94.7% | 98.0% 9.8d | 9.9d 2026-11-07 15:09:27 176.0 Kbit/s
tor26 (AT) Yes Yes No — Y Yes Yes Running, Valid, Fast, Stable 165.6 Mbit/s | 816.0 Kbit/s 165.6 Mbit/s | 256.0 Mbit/s OR 16.0 Mbit/s 97.6% | 98% 21.3d | 8d 14.5d | 13.0d 3.1d | 3.4d 97.6% | 98.0% 21.3d | 1.0d 2026-11-07 15:09:27 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.