Tor Relays :: tortzshukistan

View Relay "tortzshukistan"

Fingerprint: `4A4E7E5524F14809EFB928E484F1881ED7BE3EE0` | Family: 1 relay | tortzshukistan /at/ proton /dot/ me | AS15943 | Germany | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Fast, Stable, HSDir, Guard (7)
BW Verified: 3/7 BW Auths Measured 80 Kbit/s Median
Stability: Overloaded | DOWN 5d 5h 11m ago | UP 99% (1M)

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 4mo 1w 2d ago
BW Weight: 0.01% of Network | 86 Mbit/s Observed By Relay
Version: 0.4.9.8 Recommended

Issues Detected:

General Overload Active : Relay reported general overload at 2026-07-02 19: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.

Notes:

Bandwidth authority measurements below majority: 3/7 bandwidth authorities measured this relay (majority is 4).

Connectivity and Location

Addresses

OR Address: 84.46.78.85.static-pppoe.dt.ipv4.wtnet.de
84.46.78.85:8443

Reachability (Directory Authorities)

IPv4: 9/9

Location

Country: Germany
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS15943
AS Name: wilhelm.tel GmbH (BGP.tools)
AS Rarity: Epic (score: 3/5, 0.08% consensus weight, 8 operators)

Flags and Eligibility

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

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)	86.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 (2/9 DA)	Median: 11.0d (1/9 DA above threshold) Min/Max: 8.4d / 20631.7d (9/9 DA, Voting / Total Eligible)	≥10.1d - 48.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥1364.1d
Stable	Uptime	Below (0/9 DA)	3.8d (R)	≥4.3d - 5.2d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (7/9 DA)	7/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	≥10.1d - 48.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥1364.1d
	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: 82.9% (0/9 DA above threshold) Min/Max: 57.8% / 94.2% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (8/9 DA)	Median: 30.9d (9/9 DA above threshold) Min/Max: 9.8d / 37.5d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Meets (7/9 DA)	7/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	≥10.1d - 48.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥1364.1d
	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: 82.9% (0/9 DA above threshold) Min/Max: 57.8% / 94.2% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 30.9d (9/9 DA above threshold) Min/Max: 9.8d / 37.5d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	86.7 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-07-03 03:02:32).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 86.70 Mbit/s
Advertised Bandwidth: 83.89 Mbit/s
Rate Limit: 83.89 Mbit/s
Burst Limit: 167.77 Mbit/s
Total Data: 94 TB (6 months)
1mo: 19 TB | 6mo: 94 TB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-07-03 03:02:32

Measured By: 3/7 Bandwidth Authorities
Not measured by: bastet, dannenberg, longclaw, maatuska
Median Measurement: 80.0 Kbit/s
Min / Max: 80.0 Kbit/s / 120.0 Kbit/s

Network Participation: Consensus Weight: 0.0058% of network (52th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: DOWN 5d 5h 11m ago
Overall Uptime (1M/6M/1Y/5Y): 99.2%/99.7%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): —/36.6%/—/—
Hibernating: No

Timestamps

First Seen: 4mo 1w 2d ago (2026-02-23 19:00:00)
Last Seen: 5d 5h 11m ago (2026-06-27 22:00:00)
Last Restarted: 3d 19h 49m ago (2026-06-29 07:21:35)
Last Changed Address: 2026-04-06 23:00:00

[Warning] OVERLOADED — General overload at 2026-07-02 19:00 UTC

General Overload (from /details)

Status: Reported
When: 2026-07-02 19:00 UTC (8 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)

No rate limit data from /bandwidth endpoint.

Recommendations

Check CPU/memory: htop
Review MaxMemInQueues in torrc

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-07-02 19:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: tortzshukistan /at/ proton /dot/ me

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

4A4E7E5524F14809EFB928E484F1881ED7BE3EE0 (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.8 on Linux
Version: 0.4.9.8 — 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 Fri, 03 Jul 2026 03:11:23 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-07-03 03:02:32).

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, Stable	86.7 Mbit/s \| 816.0 Kbit/s	86.7 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	82.9% \| 98%	31.3d \| 8d	11.4d \| 48.4d	3.8d \| 5.1d	82.9% \| 98.0%	31.3d \| 1.0d	2026-07-03 00:26:16	80.0 Kbit/s
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Valid, V2Dir, Fast, Stable	86.7 Mbit/s \| 816.0 Kbit/s	86.7 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	86.2% \| 98%	30.9d \| 8d	11.4d \| 10.1d	3.8d \| 5.2d	86.2% \| 98.0%	30.9d \| 1.0d	2026-07-03 00:26:16	80.0 Kbit/s
dizum (NL)	Yes	Yes	No	—	N	Yes	Valid, V2Dir, Fast, Stable	86.7 Mbit/s \| 816.0 Kbit/s	86.7 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	82.1% \| 98%	29.9d \| 8d	10.6d \| 25.9d	3.8d \| 5.2d	82.1% \| 98.0%	29.9d \| 1.0d	2026-07-03 00:26:16	80.0 Kbit/s
faravahar (US)	Yes	Yes	No	—	N	Yes	Valid, V2Dir, Fast, Stable	86.7 Mbit/s \| 816.0 Kbit/s	86.7 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	82.9% \| 98%	31.3d \| 8d	10.9d \| 28.4d	3.8d \| 5.2d	82.9% \| 98.0%	31.3d \| 1.0d	2026-07-03 00:26:16	80.0 Kbit/s
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Valid, V2Dir, Fast, Stable	86.7 Mbit/s \| 816.0 Kbit/s	86.7 Mbit/s \| 312.0 Mbit/s OR 16.0 Mbit/s	94.2% \| 98%	37.5d \| 8d	11.2d \| 60.1d	3.8d \| 4.3d	94.2% \| 98.0%	37.5d \| 1.0d	2026-06-29 20:58:24	120.0 Kbit/s
longclaw (US)	Yes	Yes	No	—	Y	Yes	Valid, V2Dir, Stable	86.7 Mbit/s \| 816.0 Kbit/s	86.7 Mbit/s \| 240.0 Mbit/s OR 16.0 Mbit/s	82.7% \| 98%	30.8d \| 8d	10.7d \| 57.2d	3.8d \| 5.4d	82.7% \| 98.0%	30.8d \| 1.0d	2026-07-03 00:26:16	80.0 Kbit/s
maatuska (SE)	Yes	Yes	No	—	Y	Yes	Valid, V2Dir, Stable	86.7 Mbit/s \| 816.0 Kbit/s	86.7 Mbit/s \| 304.0 Mbit/s OR 16.0 Mbit/s	82.8% \| 98%	31.0d \| 8d	11.0d \| 30.6d	3.8d \| 5.3d	82.8% \| 98.0%	31.0d \| 1.0d	2026-07-03 00:26:16	80.0 Kbit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Valid, V2Dir, Fast, Stable	86.7 Mbit/s \| 8.4 Mbit/s	86.7 Mbit/s \| 248.0 Mbit/s OR 16.0 Mbit/s	57.8% \| 98%	9.8d \| 8d	20631.7d \| 1364.1d	3.8d \| 5.4d	57.8% \| 98.0%	9.80d \| 9.83d	2026-07-03 00:26:16	88.0 Kbit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Valid, V2Dir, Fast, Stable	86.7 Mbit/s \| 816.0 Kbit/s	86.7 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	84.0% \| 98%	30.7d \| 8d	8.4d \| 53.1d	3.8d \| 5.4d	84.0% \| 98.0%	30.7d \| 1.0d	2026-07-03 00:26:16	104.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.