Tor Relays :: torexitams05

View Relay "torexitams05"

Fingerprint: `5FD75011744B0C27A1CF5FA26EE9B7B6C5A284D2` | Operator: sabotage.net v2 (32 relays) ✓ Validated | Family: 1 relay | email:usura[]sabotage.org... | AS61125 | Netherlands | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Fast, Exit (5)
DNS Health: Healthy (16.7s, 65th percentile) (via exitdnshealth.1aeo.com)
BW Verified: 5/7 BW Auths Measured 80 Kbit/s Median
Stability: Overloaded | UP 1w 13h 46m ago | UP 98% (1M)

Reachability: IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen: 1w 13h 6m ago
BW Weight: 0.01% of Network | 135 Mbit/s Observed By Relay
Version: 0.4.9.14 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: Time Known below threshold : Time Known 6.7 days is below 8 days requirement (1.3 more days needed)
Suggestion: Time Known tracks how long authorities have observed your relay. This resets if: 1) Identity key changes, 2) Long downtime makes authorities forget you. Just keep running stably.
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.
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-10-16 05: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.

Connectivity and Location

Addresses

OR Address: ams05.torexit.nl
45.66.35.25:1984
[2a09:61c0::25]:1984
Exit Address: 45.66.35.25

Reachability (Directory Authorities)

IPv4: 9/9
IPv6: 8/8 (1 don't test)

Location

Country: Netherlands
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS61125
AS Name: SABOTAGE LLC (BGP.tools)
AS Rarity: Epic (score: 3/5, 1.26% consensus weight, 1 operator)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Exit

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
Running	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)	135.6 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 (0/9 DA)	Median: 3.6d (1/9 DA above threshold) Min/Max: 3.5d / 9311.8d (9/9 DA, Voting / Total Eligible)	≥6.1d - 9.0d (varies) (≥5/9 DA) [Stricter] moria1: ≥10198.2d
Stable	Uptime	Meets (9/9 DA)	7.6d (R)	≥5.7d - 5.7d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (8/9 DA)	8/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	Meets (9/9 DA)	Median: 98.7% (9/9 DA above threshold) Min/Max: 98.4% / 98.7% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (8/9 DA)	Median: 6.7d (0/9 DA above threshold) Min/Max: 5.1d / 6.7d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.7d
Guard	Prereq: Fast	Meets (8/9 DA)	8/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	Meets (9/9 DA)	Median: 98.7% (9/9 DA above threshold) Min/Max: 98.4% / 98.7% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Below (0/9 DA) (need 1.3 more days)	Median: 6.7d (0/9 DA above threshold) Min/Max: 5.1d / 6.7d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	135.6 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	Meets (9/9 DA)	Port 80: Yes \| Port 443: Yes (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: 135.58 Mbit/s
Advertised Bandwidth: 135.58 Mbit/s
Rate Limit: 8.59 Gbit/s
Burst Limit: 8.59 Gbit/s
Total Data: 2.6 TB (1 month)

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: 80.0 Kbit/s
Min / Max: 77.6 Kbit/s / 336.0 Kbit/s
Deviation: 258.4 Kbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0127% of network (69th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0386% (60th pctl)

Uptime and Stability

Uptime Metrics

Current Status: UP 1w 13h 46m ago
Overall Uptime (1M/6M/1Y/5Y): 98.9%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (98.9%/0.0%/0.0%/0.0%)
Hibernating: No

Timestamps

First Seen: 1w 13h 6m ago (2026-10-10 10:00:00)
Last Seen: 2h 6m 37s ago (2026-10-17 21:00:00)
Last Restarted: 1w 13h 46m ago (2026-10-10 09:19:40)
Last Changed Address: 2026-10-10 10:00:00

[Warning] OVERLOADED — General overload at 2026-10-16 05:00 UTC

General Overload (from /details)

Status: Reported
When: 2026-10-16 05:00 UTC (1 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-10-17 14:00 UTC

AROI Domain (?): sabotage.net
Operator Validation: Validated (32/32 relays)
This Relay: Validated (uri-rsa)
Contact: email:usura[]sabotage.org url:https://sabotage.net proof:uri-rsa abuse:abuse[]sabotage.net twitter:adejoode ciissversion:2

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

5FD75011744B0C27A1CF5FA26EE9B7B6C5A284D2 (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.14 on Linux
Version: 0.4.9.14 — Recommended
Version Status: Recommended

Exit Health & Policy

DNS Health

Status

Healthy (avg. 16.7s, 65th percentile)

Query Domain

95c30dd0ed52448fac95541b517f8550.5fd75011.tor.exit.validator.1aeo.com

DNS Result

Resolved to 64.65.4.1

Cross-Validation

3/3 instances succeeded

First Hop

fedstookover (DE) EAD42BE6847AEC775F718E7BB2F17E99C46065DB

Exit Address Used

45.66.35.25

Per-Instance Results

Cross Validation Attempt 1:	Success, 21.4s	(cv1_w2)
Cross Validation Attempt 2:	Success, 12.2s	(cv3_w2)
Cross Validation Attempt 3:	Success, 16.5s	(cv4_w2)

Tested: 2026-10-17 19:11:11 UTC

Source: exitdnshealth.1aeo.com

IPv4 Exit Policy Summary

accept: 
  20-21
  43
  53
  80-81
  443
  5222-5223
  6667-7000
  8008
  8082
  8332-8333
  8888
  9418
  18080-18081
  50002
  64738

IPv6 Exit Policy Summary

accept: 
  20-21
  43
  53
  80-81
  443
  5222-5223
  6667-7000
  8008
  8082
  8332-8333
  8888
  9418
  18080-18081
  50002
  64738

Full Exit Policy

reject 0.0.0.0/8:*
reject 169.254.0.0/16:*
reject 127.0.0.0/8:*
reject 192.168.0.0/16:*
reject 10.0.0.0/8:*
reject 172.16.0.0/12:*
reject 45.66.32.0/22:*
accept *:20-21
accept *:43
accept *:53
accept *:80-81
accept *:443
accept *:5222-5223
accept *:6667-7000
accept *:8008
accept *:8082
accept *:8332-8333
accept *:8888
accept *:9418
accept *:50002
accept *:64738
accept *:18080-18081
reject *:*

Last fetch was at Sat, 17 Oct 2026 23:06:30 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	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	Yes	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Exit	135.6 Mbit/s \| 816.0 Kbit/s	135.6 Mbit/s \| 184.0 Mbit/s OR 16.0 Mbit/s	98.7% \| 98%	6.7d \| 8d	3.6d \| 9.0d	7.6d \| 5.7d	98.7% \| 98.0%	6.7d \| 1.0d	2026-10-17 17:30:44	88.0 Kbit/s
dannenberg (DE)	Yes	Yes	Yes	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Exit	135.6 Mbit/s \| 816.0 Kbit/s	135.6 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	98.5% \| 98%	6.7d \| 8d	3.5d \| 6.1d	7.6d \| 5.8d	98.5% \| 98.0%	6.7d \| 1.0d	2026-10-17 17:30:44	200.0 Kbit/s
dizum (NL)	Yes	Yes	Yes	—	N	Yes	Yes	Running, Valid, V2Dir, Fast, Exit	135.6 Mbit/s \| 816.0 Kbit/s	135.6 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	98.7% \| 98%	6.7d \| 8d	3.6d \| 9.0d	7.6d \| 5.7d	98.7% \| 98.0%	6.7d \| 1.0d	2026-10-17 17:30:44	80.0 Kbit/s
faravahar (US)	Yes	Yes	Yes	—	Y	Yes	Yes	Running, Valid, V2Dir, Exit	135.6 Mbit/s \| 816.0 Kbit/s	135.6 Mbit/s \| 312.0 Mbit/s OR 16.0 Mbit/s	98.5% \| 98%	6.7d \| 8d	3.5d \| 9.5d	7.6d \| 6.3d	98.5% \| 98.0%	6.7d \| 1.0d	2026-10-17 17:30:44	80.0 Kbit/s
gabelmoo (DE)	Yes	Yes	Yes	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Exit	135.6 Mbit/s \| 816.0 Kbit/s	135.6 Mbit/s \| 272.0 Mbit/s OR 16.0 Mbit/s	98.7% \| 98%	6.7d \| 8d	3.6d \| 9.0d	7.6d \| 5.7d	98.7% \| 98.0%	6.7d \| 1.0d	2026-10-17 17:30:44	304.0 Kbit/s
longclaw (US)	Yes	Yes	Yes	—	Y	Yes	—	Running, Valid, V2Dir, Fast, Exit	135.6 Mbit/s \| 816.0 Kbit/s	135.6 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	98.7% \| 98%	6.7d \| 8d	3.6d \| 9.2d	7.6d \| 5.7d	98.7% \| 98.0%	6.7d \| 1.0d	2026-10-17 17:30:44	80.0 Kbit/s
maatuska (SE)	Yes	Yes	Yes	—	N	Yes	Yes	Running, Valid, V2Dir, Fast, Exit	135.6 Mbit/s \| 816.0 Kbit/s	135.6 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	98.5% \| 98%	6.4d \| 8d	3.5d \| 8.8d	7.6d \| 5.7d	98.5% \| 98.0%	6.4d \| 1.0d	2026-10-17 17:30:44	80.0 Kbit/s
moria1 (US)	Yes	Yes	Yes	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Exit	135.6 Mbit/s \| 8.4 Mbit/s	135.6 Mbit/s \| 192.0 Mbit/s OR 16.0 Mbit/s	98.4% \| 98%	5.1d \| 8d	9311.8d \| 10198.2d	7.6d \| 5.7d	98.4% \| 98.0%	5.1d \| 9.7d	2026-10-17 17:30:44	77.6 Kbit/s
tor26 (AT)	Yes	Yes	Yes	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Exit	135.6 Mbit/s \| 816.0 Kbit/s	135.6 Mbit/s \| 272.0 Mbit/s OR 16.0 Mbit/s	98.7% \| 98%	6.7d \| 8d	3.5d \| 9.3d	7.6d \| 5.7d	98.7% \| 98.0%	6.7d \| 1.0d	2026-10-17 17:30:44	336.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.