Tor Relays :: rathergonaked

View Relay "rathergonaked"

Fingerprint: `B34836F2027C14E4040478768986BFEA827B4628` | Family: 1 relay | AS3320 | Germany | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Fast, Stable, HSDir (6)
BW Verified: 5/6 BW Auths Measured 2000 bit/s Median
Stability: Overloaded | UP 1w 3d 19h ago | UP 58% (1M)

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 7y 1mo 1w ago
BW Weight: 0.00% of Network | 4 Mbit/s Observed By Relay
Version: 0.4.8.16 Not Recommended

Issues Detected:

Guard: bandwidth below threshold : Observed bandwidth 0.6 MB/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM.
Guard: WFU below threshold : Weighted Fractional Uptime 78.2% 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.
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.16 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.
General Overload Active : Relay reported general overload at 2026-03-29 01: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.
Read Bandwidth Limit Hit : Read rate limit (7 Mbit/s) was hit 26 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=7 Mbit/s, Burst=9 Mbit/s. Limits hit: Write=0, Read=26.

Connectivity and Location

Addresses

OR Address: pd955a941.dip0.t-ipconnect.de
217.85.169.65:9002

Reachability (Directory Authorities)

IPv4: 9/9

Location

Country: Germany
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS3320
AS Name: Deutsche Telekom AG (BGP.tools)
AS Rarity: Rare (score: 2/5, 0.21% consensus weight, 56 operators)

Flags and Eligibility

Current Flags (6): Running, Valid, V2Dir, Fast, Stable, HSDir

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)	4.7 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: 13.4d (1/9 DA above threshold) Min/Max: 12.6d / 1930.5d (9/9 DA, Voting / Total Eligible)	≥17.9d - 58.7d (varies) (≥5/9 DA) [Stricter] moria1: ≥293.7d
Stable	Uptime	Meets (9/9 DA)	10.8d (R)	≥3.3d - 3.4d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (6/9 DA)	6/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	≥17.9d - 58.7d (varies) (≥5/9 DA) [Stricter] moria1: ≥293.7d
	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: 78.2% (0/9 DA above threshold) Min/Max: 76.0% / 80.5% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (8/9 DA)	Median: 18.6d (9/9 DA above threshold) Min/Max: 9.7d / 19.1d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.9d
Guard	Prereq: Fast	Meets (6/9 DA)	6/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	≥17.9d - 58.7d (varies) (≥5/9 DA) [Stricter] moria1: ≥293.7d
	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: 78.2% (0/9 DA above threshold) Min/Max: 76.0% / 80.5% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 18.6d (9/9 DA above threshold) Min/Max: 9.7d / 19.1d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Below (0/9 DA)	4.7 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 12:45:07).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 4.70 Mbit/s
Advertised Bandwidth: 4.70 Mbit/s
Rate Limit: 4.92 Mbit/s
Burst Limit: 6.55 Mbit/s
Total Data: 28 TB (5 years)
1mo: 262 GB | 6mo: 2.0 TB | 1y: 4.0 TB | 5y: 28 TB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-29 12:45:07

Measured By: 5/6 Bandwidth Authorities
Not measured by: bastet
Median Measurement: 2000 bit/s
Min / Max: 712 bit/s / 4696 bit/s
Deviation: 3984 bit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0001% of network (6th pctl) | Guard: N/A | Middle: 0.0002% (5th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: UP 1w 3d 19h ago
Overall Uptime (1M/6M/1Y/5Y): 58.1%/71.3%/64.4%/71.6%
Flag Uptime (1M/6M/1Y/5Y): 56.7%/70.1%/62.8%/70.0%
Hibernating: No

Timestamps

First Seen: 7y 1mo 1w ago (2019-02-18 00:00:00)
Last Seen: 2h 45m 55s ago (2026-03-29 10:00:00)
Last Restarted: 1w 3d 19h ago (2026-03-18 16:48:40)
Last Changed Address: 2026-03-18 18:00:00

[Warning] OVERLOADED — General overload at 2026-03-29 01:00 UTC; Rate limits hit W:0 R:26 (limit: 7 Mbit/s)

General Overload (from /details)

Status: Reported
When: 2026-03-29 01:00 UTC (11 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: 7.37 Mbit/s
Burst Limit: 9.01 Mbit/s
Write Limit Hit: 0 times
Read Limit Hit: 26 times
Last Reported: 6 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-03-29 05: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

B34836F2027C14E4040478768986BFEA827B4628 (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.8.16 on Linux
Version: 0.4.8.16 — 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 Sun, 29 Mar 2026 12:45:53 GMT.

Consensus Evaluation

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

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	Running, Valid, V2Dir, Fast, Stable, HSDir	4.7 Mbit/s \| 816.0 Kbit/s	4.7 Mbit/s \| 200.0 Mbit/s OR 16.0 Mbit/s	78.2% \| 98%	19.0d \| 8d	13.5d \| 63.5d	10.8d \| 3.3d	78.2% \| 98.0%	19.0d \| 1.0d	2026-03-29 07:34:30	4696 bit/s
dannenberg (DE)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir	4.7 Mbit/s \| 816.0 Kbit/s	4.7 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	77.5% \| 98%	18.4d \| 8d	12.9d \| 17.9d	10.8d \| 3.4d	77.5% \| 98.0%	18.4d \| 1.0d	2026-03-29 07:34:30	4696 bit/s
dizum (NL)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir	4.7 Mbit/s \| 816.0 Kbit/s	4.7 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	77.1% \| 98%	18.1d \| 8d	12.6d \| 42.9d	10.8d \| 3.4d	77.1% \| 98.0%	18.1d \| 1.0d	2026-03-29 07:34:30	4696 bit/s
faravahar (US)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir	4.7 Mbit/s \| 816.0 Kbit/s	4.7 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	78.3% \| 98%	19.1d \| 8d	13.5d \| 56.6d	10.8d \| 3.4d	78.3% \| 98.0%	19.1d \| 1.0d	2026-03-29 07:34:30	4696 bit/s
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Stable	4.7 Mbit/s \| 816.0 Kbit/s	4.7 Mbit/s \| 280.0 Mbit/s OR 16.0 Mbit/s	78.3% \| 98%	19.1d \| 8d	13.5d \| 62.1d	10.8d \| 3.4d	78.3% \| 98.0%	19.1d \| 1.0d	2026-03-29 07:34:30	720 bit/s
longclaw (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir	4.7 Mbit/s \| 816.0 Kbit/s	4.7 Mbit/s \| 232.0 Mbit/s OR 16.0 Mbit/s	80.5% \| 98%	18.3d \| 8d	13.4d \| 62.6d	10.8d \| 3.4d	80.5% \| 98.0%	18.3d \| 1.0d	2026-03-29 07:34:30	1680 bit/s
maatuska (SE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir	4.7 Mbit/s \| 816.0 Kbit/s	4.7 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	78.9% \| 98%	18.6d \| 8d	13.4d \| 50.7d	10.8d \| 3.4d	78.9% \| 98.0%	18.6d \| 1.0d	2026-03-29 07:34:30	960 bit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Stable	4.7 Mbit/s \| 8.4 Mbit/s	4.7 Mbit/s \| 216.0 Mbit/s OR 16.0 Mbit/s	76.0% \| 98%	9.7d \| 8d	1930.5d \| 293.7d	10.8d \| 4.1d	76.0% \| 98.0%	9.7d \| 9.9d	2026-03-29 07:34:30	2000 bit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Stable	4.7 Mbit/s \| 816.0 Kbit/s	4.7 Mbit/s \| 264.0 Mbit/s OR 16.0 Mbit/s	78.0% \| 98%	18.9d \| 8d	13.4d \| 58.7d	10.8d \| 3.8d	78.0% \| 98.0%	18.9d \| 1.0d	2026-03-29 07:34:30	712 bit/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.