Tor Relays :: 17aeea434ea95807c5d

View Relay "17aeea434ea95807c5d"

Fingerprint: `2275A1D3816926C139D5BD0001AF7D45C27E3341` | Family: 4 relays | tor@funil.de | AS29551 | Germany | Linux

Health Status

Consensus: In Consensus (8/8 Directory Auths)
Flags: Running, Valid, V2Dir, Fast, Stable, HSDir, Guard (7)
BW Verified: 5/5 BW Auths Measured 184 Kbit/s Median
Stability: Overloaded | UP 3w 3d 1h ago | UP 100% (1M)

Reachability: IPv4: 8/9 (Directory Auths)
First Seen: 3w 3d 6h ago
BW Weight: 0.01% of Network | 154 Mbit/s Observed By Relay
Version: 0.4.9.6 Recommended

Issues Detected:

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

Notes:

Partial IPv4 reachability: 8/9 authorities can reach this relay

Connectivity and Location

Addresses

OR Address: 82.149.227.236:9004

Reachability (Directory Authorities)

IPv4: 8/9

Location

Country: Germany
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS29551
AS Name: Aixit GmbH (BGP.tools)
AS Rarity: Epic (score: 3/5, 0.06% consensus weight, 2 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 (8/8 DA)	8/8 authorities reached relay	≥5/8 DA ORPort reachable
Valid	Descriptor	Meets (8/8 DA)	8/8 authorities assigned Valid	Not blacklisted + valid descriptor (≥5/8 DA)
V2Dir	DirPort Available	Meets (8/8 DA)	Tunnelled: Yes (no DirPort) (R)	Tunnelled directory via ORPort or DirPort (≥5/8 DA)
Fast	Speed	Meets (8/8 DA)	154.6 Mbit/s (R)	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA) [Stricter] moria1: ≥8.4 Mbit/s
Stable	MTBF	Below (1/8 DA)	Median: 48.2d (1/8 DA above threshold) Min/Max: 13.8d / 227.3d (8/8 DA, Voting / Total Eligible)	≥16.6d - 56.4d (varies) (≥5/8 DA) [Stricter] moria1: ≥312.0d
Stable	Uptime	Meets (8/8 DA)	24.1d (R)	≥8.9d - 8.9d (varies) (≥5/8 DA)
HSDir	Prereq: Fast	Meets (8/8 DA)	8/8 DA assigned Fast	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Meets (8/8 DA)	8/8 DA assigned Stable	≥16.6d - 56.4d (varies) (≥5/8 DA) [Stricter] moria1: ≥312.0d
	Prereq: V2Dir	Meets (8/8 DA)	8/8 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/8 DA)
	WFU	Meets (8/8 DA)	Median: 100.0% (8/8 DA above threshold) Min/Max: 98.3% / 100.0% (8/8 DA, Voting / Total Eligible)	≥98.0% (≥5/8 DA)
	Time Known	Meets (7/8 DA)	Median: 47.3d (8/8 DA above threshold) Min/Max: 9.7d / 49.2d (8/8 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/8 DA) [Stricter] moria1: ≥9.9d
Guard	Prereq: Fast	Meets (8/8 DA)	8/8 DA assigned Fast	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Meets (8/8 DA)	8/8 DA assigned Stable	≥16.6d - 56.4d (varies) (≥5/8 DA) [Stricter] moria1: ≥312.0d
	Prereq: V2Dir	Meets (8/8 DA)	8/8 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/8 DA)
	WFU	Meets (8/8 DA)	Median: 100.0% (8/8 DA above threshold) Min/Max: 98.3% / 100.0% (8/8 DA, Voting / Total Eligible)	≥98% (≥5/8 DA)
	Time Known	Meets (8/8 DA)	Median: 47.3d (8/8 DA above threshold) Min/Max: 9.7d / 49.2d (8/8 DA, Voting / Total Eligible)	≥8 days (≥5/8 DA)
	Bandwidth	Meets (8/8 DA)	154.6 Mbit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.0 Mbit/s (≥5/8 DA)
Exit	Exit Policy	Below (0/8 DA)	Port 80: No \| Port 443: No (R)	Allows ≥1 /8 on ports 80 AND 443 (≥5/8 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-05-01 05:45:08).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 154.57 Mbit/s
Advertised Bandwidth: 154.57 Mbit/s
Rate Limit: 8.59 Gbit/s
Burst Limit: 8.59 Gbit/s
Total Data: 473 TB (5 years)
1mo: 43 TB | 6mo: 245 TB | 1y: 472 TB | 5y: 473 TB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-05-01 05:45:08

Measured By: 5/5 Bandwidth Authorities
Median Measurement: 184.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.0140% of network (73th pctl) | Guard: 0.0236% (77th pctl) | Middle: 0.0184% (79th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: UP 3w 3d 1h ago
Overall Uptime (1M/6M/1Y/5Y): 100.0%/100.0%/100.0%/100.0%
Flag Uptime (1M/6M/1Y/5Y): —/—/—/98.3%
Hibernating: No

Timestamps

First Seen: 3w 3d 6h ago (2026-04-06 23:00:00)
Last Seen: 1h 45m 38s ago (2026-05-01 04:00:00)
Last Restarted: 3w 3d 1h ago (2026-04-07 04:29:09)
Last Changed Address: 2026-04-06 23:00:00

[Warning] OVERLOADED — General overload at 2026-04-29 01:00 UTC

General Overload (from /details)

Status: Reported
When: 2026-04-29 01:00 UTC (2 days 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-04-30 22:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: tor@funil.de

Family Configuration

Family Support: MyFamily Only (4) — Legacy only. Consider migrating to Happy Families. | View Full Family (4)

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Members: 4

2275A1D3816926C139D5BD0001AF7D45C27E3341 (this relay)
35A31A210074D66EBE76C4F3FEB972E8C0B178CE
67E7B7D4BFCB1E0B4DF2CDB33B1FDE4B69C9DD62
B25E02013A30693556480274240B8B392AB04179

Alleged Members: 0

none

Indirect Members: 0

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

Full Exit Policy

reject *:*

Last fetch was at Fri, 01 May 2026 05:45:38 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-05-01 05: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	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)	No	—	—	—	N	No	—	—	—	—	—	—	—	—	—	—	—
dannenberg (DE)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	154.6 Mbit/s \| 816.0 Kbit/s	154.6 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	46.5d \| 8d	45.9d \| 47.5d	24.1d \| 8.9d	100.0% \| 98.0%	46.5d \| 1.0d	2026-05-01 02:31:03	80.0 Kbit/s
dizum (NL)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	154.6 Mbit/s \| 816.0 Kbit/s	154.6 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	43.0d \| 8d	42.5d \| 42.5d	24.1d \| 10.4d	100.0% \| 98.0%	43.0d \| 1.0d	2026-04-28 02:30:48	80.0 Kbit/s
faravahar (US)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	154.6 Mbit/s \| 816.0 Kbit/s	154.6 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	49.1d \| 8d	48.6d \| 56.8d	24.1d \| 8.9d	100.0% \| 98.0%	49.1d \| 1.0d	2026-05-01 02:31:03	80.0 Kbit/s
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	154.6 Mbit/s \| 816.0 Kbit/s	154.6 Mbit/s \| 304.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	49.2d \| 8d	48.7d \| 55.4d	24.1d \| 8.9d	100.0% \| 98.0%	49.2d \| 1.0d	2026-05-01 02:31:03	232.0 Kbit/s
longclaw (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	154.6 Mbit/s \| 816.0 Kbit/s	154.6 Mbit/s \| 248.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	48.2d \| 8d	47.8d \| 63.1d	24.1d \| 8.9d	100.0% \| 98.0%	48.2d \| 1.0d	2026-05-01 02:31:03	248.0 Kbit/s
maatuska (SE)	Yes	Yes	No	—	Y	Yes	Valid, V2Dir, Fast, Stable, HSDir, Guard	154.6 Mbit/s \| 816.0 Kbit/s	154.6 Mbit/s \| 328.0 Mbit/s OR 16.0 Mbit/s	98.3% \| 98%	22.7d \| 8d	13.8d \| 16.6d	24.1d \| 8.9d	98.3% \| 98.0%	22.7d \| 1.0d	2026-05-01 02:31:03	216.0 Kbit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	154.6 Mbit/s \| 8.4 Mbit/s	154.6 Mbit/s \| 224.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	9.7d \| 8d	227.3d \| 312.0d	24.1d \| 9.4d	100.0% \| 98.0%	9.7d \| 9.9d	2026-05-01 02:31:03	240.0 Kbit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	154.6 Mbit/s \| 816.0 Kbit/s	154.6 Mbit/s \| 288.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	49.0d \| 8d	48.6d \| 56.4d	24.1d \| 8.9d	100.0% \| 98.0%	49.0d \| 1.0d	2026-05-01 02:31:03	152.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.