View Relay "nlson01"

Fingerprint: D509F18AF017D7FADF8114FAA93AB7B4FAD3F140 | Family: 5 relays | ops@freedomstack.de | AS215365 | Germany | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast (4)
BW Verified
6/6 BW Auths Measured 104 Kbit/s Median
Stability
Overloaded | UP 3d 5h 7m ago | UP 80% (1M)
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen
3w 3d 12h ago
BW Weight
0.01% of Network | 87 Mbit/s Observed By Relay
Version
0.4.9.6 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 71.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 71.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 (84 Mbit/s) was hit 7 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 (84 Mbit/s) was hit 6 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=84 Mbit/s, Burst=168 Mbit/s. Limits hit: Write=7, Read=6.

Connectivity and Location

Addresses
OR Address
threatoff.eu
77.90.63.15:443
[2a14:7c0:1002:1216::]: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
AS215365
AS Name
Tom Gewiese (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 2 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
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 Meets (9/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 87.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.2d (1/9 DA above threshold)
Min/Max: 0.1d / 20063.9d (9/9 DA, Voting / Total Eligible)		 ≥17.9d - 58.6d (varies) (≥5/9 DA)
Uptime Below (0/9 DA) 3.2d (R) ≥3.3d - 3.4d (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 ≥17.9d - 58.6d (varies) (≥5/9 DA)
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: 71.0% (0/9 DA above threshold)
Min/Max: 67.5% / 75.1% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 9.1d (9/9 DA above threshold)
Min/Max: 8.5d / 9.3d (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 Below (1/9 DA) 1/9 DA assigned Stable ≥17.9d - 58.6d (varies) (≥5/9 DA)
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: 71.0% (0/9 DA above threshold)
Min/Max: 67.5% / 75.1% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 9.1d (9/9 DA above threshold)
Min/Max: 8.5d / 9.3d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 87.1 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-296.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-03-29 09:45:08).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
87.10 Mbit/s
Advertised Bandwidth
83.89 Mbit/s
Rate Limit
83.89 Mbit/s
Burst Limit
167.77 Mbit/s
Total Data
6.1 TB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-29 09:45:08

Measured By
6/6 Bandwidth Authorities
Median Measurement
104.0 Kbit/s
Min / Max
80.0 Kbit/s / 176.0 Kbit/s
Deviation
96.0 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0097% of network (64th pctl) | Guard: N/A | Middle: 0.0291% (88th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 3d 5h 7m ago
Overall Uptime (1M/6M/1Y/5Y)
80.8%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
73.3%/—/—/—
Hibernating
No
Timestamps
First Seen
3w 3d 12h ago (2026-03-04 22:00:00)
Last Seen
2h 46m 39s ago (2026-03-29 08:00:00)
Last Restarted
3d 5h 7m ago (2026-03-26 05:39:29)
Last Changed Address
2026-03-04 22:00:00
[Warning] OVERLOADED — Rate limits hit W:7 R:6 (limit: 84 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
83.89 Mbit/s
Burst Limit
167.77 Mbit/s
Write Limit Hit
7 times
Read Limit Hit
6 times
Last Reported
12 hours ago
Recommendations
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-03-29 02:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
ops@freedomstack.de
Family Configuration
Family Support
Happy Families (5) — Has family-cert in server descriptor (guide) | View Full Family (5)
MyFamily (legacy declarations) — none

Software and Version

Platform
Linux — Tor 0.4.9.6 on Linux
Version
0.4.9.6 — 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, 29 Mar 2026 10:46:38 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-29 09:45:08).

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, V2Dir, Fast 87.1 Mbit/s | 816.0 Kbit/s 87.1 Mbit/s | 200.0 Mbit/s OR 16.0 Mbit/s 71.0% | 98% 9.2d | 8d 0.1d | 63.4d 3.2d | 3.3d 71.0% | 98.0% 9.2d | 1.0d 2026-03-29 04:07:48 96.0 Kbit/s
dannenberg (DE) Yes Yes No — N Yes Yes Running, Valid, V2Dir, Fast 87.1 Mbit/s | 816.0 Kbit/s 87.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 73.6% | 98% 9.1d | 8d 0.2d | 17.9d 3.2d | 3.3d 73.6% | 98.0% 9.1d | 1.0d 2026-03-29 04:07:48 80.0 Kbit/s
dizum (NL) Yes Yes No — N Yes Yes Running, Valid, V2Dir, Fast 87.1 Mbit/s | 816.0 Kbit/s 87.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 73.3% | 98% 8.5d | 8d 0.2d | 42.9d 3.2d | 3.4d 73.3% | 98.0% 8.5d | 1.0d 2026-03-29 04:07:48 80.0 Kbit/s
faravahar (US) Yes Yes No — N Yes Yes Running, Valid, V2Dir, Fast 87.1 Mbit/s | 816.0 Kbit/s 87.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 70.8% | 98% 9.1d | 8d 0.2d | 56.4d 3.2d | 3.4d 70.8% | 98.0% 9.1d | 1.0d 2026-03-29 04:07:48 80.0 Kbit/s
gabelmoo (DE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast 87.1 Mbit/s | 816.0 Kbit/s 87.1 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 70.2% | 98% 9.3d | 8d 0.1d | 62.1d 3.2d | 3.4d 70.2% | 98.0% 9.3d | 1.0d 2026-03-29 04:07:48 176.0 Kbit/s
longclaw (US) Yes Yes No — Y Yes — Running, Valid, V2Dir, Fast 87.1 Mbit/s | 816.0 Kbit/s 87.1 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 75.1% | 98% 8.8d | 8d 0.2d | 62.6d 3.2d | 3.3d 75.1% | 98.0% 8.8d | 1.0d 2026-03-29 04:07:48 136.0 Kbit/s
maatuska (SE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast 87.1 Mbit/s | 816.0 Kbit/s 87.1 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 67.5% | 98% 9.3d | 8d 0.1d | 50.7d 3.2d | 3.3d 67.5% | 98.0% 9.3d | 1.0d 2026-03-29 04:07:48 144.0 Kbit/s
moria1 (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable 87.1 Mbit/s | 8.4 Mbit/s 87.1 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 69.5% | 98% 9.2d | 8d 20063.9d | 291.4d 3.2d | 4.1d 69.5% | 98.0% 9.2d | 9.9d 2026-03-29 04:07:48 104.0 Kbit/s
tor26 (AT) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast 87.1 Mbit/s | 816.0 Kbit/s 87.1 Mbit/s | 264.0 Mbit/s OR 16.0 Mbit/s 73.9% | 98% 9.0d | 8d 0.2d | 58.6d 3.2d | 3.9d 73.9% | 98.0% 9.0d | 1.0d 2026-03-29 04:07:48 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). 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.