View Relay "NetWorkXXIV"

Fingerprint: B5168D25AE4EB439A7C1B80367B890400ACE0A7F | Family: 2 relays | Thiesi... | AS197540 | Germany | NetBSD

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast (4)
BW Verified
5/7 BW Auths Measured 31 Kbit/s Median
Stability
Overloaded | DOWN 4h 6m 17s ago | UP 63% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
4y 9mo 2w ago
BW Weight
0.00% of Network | 36 Mbit/s Observed By Relay
Version
0.4.9.11 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 54.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.
  • 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 54.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.
  • Tor version not recommended : Running Tor version 0.4.9.11 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.
  • File Descriptor Exhaustion : Relay ran out of file descriptors at 2026-10-17 18:00 UTC. This severely impacts connections and performance.
    Suggestion: Increase file descriptor limits: For systemd: add "LimitNOFILE=65535" to [Service] section. For shell: ulimit -n 65535. Persistent: edit /etc/security/limits.conf.

Connectivity and Location

Addresses
OR Address
networkxxiv.tor-relay.org
89.58.26.150:443
[2a03:4000:62:f06:7777:7777:7777:7777]:443
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS197540
AS Name
netcup GmbH (BGP.tools)
AS Rarity
Emerging (score: 1/5, 3.49% consensus weight, 174 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 1/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
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) 36.5 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.1d (1/9 DA above threshold)
Min/Max: 0.1d / 20736.2d (9/9 DA, Voting / Total Eligible)		 ≥6.1d - 9.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10198.2d
Uptime Meets (9/9 DA) 22.5d (R) ≥5.7d - 5.7d (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 Below (1/9 DA) 1/9 DA assigned Stable ≥6.1d - 9.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10198.2d
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: 56.5% (0/9 DA above threshold)
Min/Max: 52.1% / 58.9% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 10.8d (9/9 DA above threshold)
Min/Max: 9.6d / 11.1d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.7d
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 Below (1/9 DA) 1/9 DA assigned Stable ≥6.1d - 9.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10198.2d
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: 56.5% (0/9 DA above threshold)
Min/Max: 52.1% / 58.9% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 10.8d (9/9 DA above threshold)
Min/Max: 9.6d / 11.1d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 36.5 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.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-10-17 23:00:36).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
36.50 Mbit/s
Advertised Bandwidth
36.50 Mbit/s
Rate Limit
2.52 Gbit/s
Burst Limit
2.60 Gbit/s
Total Data
462 TB (5 years)
1mo: 4.4 TB | 6mo: 10 TB | 1y: 10 TB | 5y: 462 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-17 23:00:36

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Median Measurement
31.2 Kbit/s
Min / Max
12.0 Kbit/s / 36.5 Kbit/s
Deviation
24.5 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0017% of network (22th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
DOWN 4h 6m 17s ago
Overall Uptime (1M/6M/1Y/5Y)
63.6%/24.9%/12.3%/61.5%
Flag Uptime (1M/6M/1Y/5Y)
—/24.4%/12.0%/61.2%
Hibernating
No
Timestamps
First Seen
4y 9mo 2w ago (2022-01-03 00:00:00)
Last Seen
4h 6m 17s ago (2026-10-17 20:00:00)
Last Restarted
3w 1d 12h ago (2026-09-25 11:34:03)
Last Changed Address
2026-08-21 20:00:00
[Warning] OVERLOADED — FD exhaustion (last: 2026-10-17)
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
Reported — 2026-10-17 18:00 UTC (6 hours ago)
Rate Limits (from /bandwidth)

No rate limit data from /bandwidth endpoint.

Recommendations
  • Increase FD limit: ulimit -n 65535
  • systemd: LimitNOFILE=65535 in [Service]

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-10-17 16:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
Thiesi <1thiesi2+3tor4@5gmail6.7com8> (strip all numbers from the email address)
Family Configuration
Family Support
MyFamily Only (2) — Legacy only. Consider migrating to Happy Families. | View Full Family (2)
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Members: 2 
752BC361622E9BC2DBF395235431A2BEFBE79135
B5168D25AE4EB439A7C1B80367B890400ACE0A7F (this relay)
Alleged Member: 1
(they don't list you back) 
CC403519DD172434B9DBE88BCD8FE65EF312CE22
Indirect Members: 0
none

Software and Version

Platform
NetBSD — Tor 0.4.9.11 on NetBSD
Version
0.4.9.11 — 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
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Sun, 18 Oct 2026 00:06:03 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-10-17 23:00:36).

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 — Y Yes Valid, V2Dir, Fast 36.5 Mbit/s | 816.0 Kbit/s 36.5 Mbit/s | 184.0 Mbit/s OR 16.0 Mbit/s 54.0% | 98% 11.0d | 8d 0.1d | 9.0d 22.5d | 5.7d 54.0% | 98.0% 11.0d | 1.0d 2026-10-17 18:47:12 28.8 Kbit/s
dannenberg (DE) Yes Yes No — Y Yes Valid, V2Dir, Fast 36.5 Mbit/s | 816.0 Kbit/s 36.5 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 53.3% | 98% 10.3d | 8d 0.1d | 6.1d 22.5d | 5.8d 53.3% | 98.0% 10.3d | 1.0d 2026-10-17 18:47:12 31.2 Kbit/s
dizum (NL) Yes Yes No — N Yes Valid, V2Dir, Fast 36.5 Mbit/s | 816.0 Kbit/s 36.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 57.2% | 98% 11.1d | 8d 0.1d | 9.0d 22.5d | 5.7d 57.2% | 98.0% 11.1d | 1.0d 2026-10-17 18:47:12 36.5 Kbit/s
faravahar (US) Yes Yes No — Y Yes Valid, V2Dir, Fast 36.5 Mbit/s | 816.0 Kbit/s 36.5 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 53.6% | 98% 10.8d | 8d 0.1d | 9.5d 22.5d | 6.3d 53.6% | 98.0% 10.8d | 1.0d 2026-10-17 18:47:12 36.5 Kbit/s
gabelmoo (DE) Yes Yes No — Y Yes Valid, V2Dir, Fast 36.5 Mbit/s | 816.0 Kbit/s 36.5 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 56.8% | 98% 11.1d | 8d 0.1d | 9.0d 22.5d | 5.7d 56.8% | 98.0% 11.1d | 1.0d 2026-10-17 18:47:12 12.0 Kbit/s
longclaw (US) Yes Yes No — Y Yes Valid, V2Dir, Fast 36.5 Mbit/s | 816.0 Kbit/s 36.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 56.5% | 98% 10.8d | 8d 0.1d | 9.2d 22.5d | 5.7d 56.5% | 98.0% 10.8d | 1.0d 2026-10-17 18:47:12 36.5 Kbit/s
maatuska (SE) Yes Yes No — N Yes Valid, V2Dir, Fast 36.5 Mbit/s | 816.0 Kbit/s 36.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 58.9% | 98% 10.6d | 8d 0.1d | 8.8d 22.5d | 5.7d 58.9% | 98.0% 10.6d | 1.0d 2026-10-17 18:47:12 36.5 Kbit/s
moria1 (US) Yes Yes No — Y Yes Valid, V2Dir, Fast, Stable 36.5 Mbit/s | 8.4 Mbit/s 36.5 Mbit/s | 192.0 Mbit/s OR 16.0 Mbit/s 52.1% | 98% 9.6d | 8d 20736.2d | 10198.2d 22.5d | 5.7d 52.1% | 98.0% 9.6d | 9.7d 2026-10-17 18:47:12 20.8 Kbit/s
tor26 (AT) Yes Yes No — Y Yes Valid, V2Dir, Fast 36.5 Mbit/s | 816.0 Kbit/s 36.5 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 57.2% | 98% 10.8d | 8d 0.1d | 9.3d 22.5d | 5.7d 57.2% | 98.0% 10.8d | 1.0d 2026-10-17 18:47:12 28.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.