Tor Relays :: EsperpentoEspantoso

View Relay "EsperpentoEspantoso"

Fingerprint: `D54ED56BF843C6EF788F762CD5CAB2CD583AFC40` | Family: 1 relay | AS57269 | Spain | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Fast (4)
BW Verified: 5/7 BW Auths Measured 208 Kbit/s Median
Stability: Overloaded | UP 11h 7m 51s ago | UP 80% (1M)

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 9mo 2w 15h ago
BW Weight: 0.02% of Network | 216 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 88.5% 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 88.5% 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.
General Overload Active : Relay reported general overload at 2026-07-02 16: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: 79.112.131.125:9003
Unreachable Addresses: [Warning] Declared but unreachable:
[2a0c:5a86:f40a:ec00:7a7b:8aff:feb8:c532]:9003

Reachability (Directory Authorities)

IPv4: 9/9

Location

Country: Spain
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS57269
AS Name: DIGI SPAIN TELECOM S.A (BGP.tools)
AS Rarity: Epic (score: 3/5, 0.08% consensus weight, 6 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Fast

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 (3/3 DA)	3/3 tested authorities reached relay	≥2/3 tested (majority) (≥2/3 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)	216.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 (1/9 DA)	Median: 3.8d (1/9 DA above threshold) Min/Max: 0.8d / 14143.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)	0.5d (R)	≥4.3d - 5.2d (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	≥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: 88.1% (0/9 DA above threshold) Min/Max: 81.1% / 88.5% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 13.6d (9/9 DA above threshold) Min/Max: 9.8d / 14.2d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d
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	≥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: 88.1% (0/9 DA above threshold) Min/Max: 81.1% / 88.5% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 13.6d (9/9 DA above threshold) Min/Max: 9.8d / 14.2d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	216.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	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: 216.60 Mbit/s
Advertised Bandwidth: 216.60 Mbit/s
Rate Limit: 8.59 Gbit/s
Burst Limit: 8.59 Gbit/s
Total Data: 159 TB (1 year)
1mo: 39 TB | 6mo: 152 TB | 1y: 159 TB

Measurement (Directory Authority Verified)

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

Measured By: 5/7 Bandwidth Authorities
Not measured by: bastet, dannenberg
Median Measurement: 208.0 Kbit/s
Min / Max: 80.0 Kbit/s / 376.0 Kbit/s
Deviation: 296.0 Kbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0158% of network (76th pctl) | Guard: N/A | Middle: 0.0460% (94th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: UP 11h 7m 51s ago
Overall Uptime (1M/6M/1Y/5Y): 80.0%/93.8%/82.7%/0.0%
Flag Uptime (1M/6M/1Y/5Y): —/93.5%/82.0%/—
Hibernating: No

Timestamps

First Seen: 9mo 2w 15h ago (2025-09-21 12:00:00)
Last Seen: 2h 11m 25s ago (2026-07-03 01:00:00)
Last Restarted: 11h 7m 51s ago (2026-07-02 16:03:34)
Last Changed Address: 2026-07-02 14:00:00

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

General Overload (from /details)

Status: Reported
When: 2026-07-02 16: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)

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: none

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

D54ED56BF843C6EF788F762CD5CAB2CD583AFC40 (this relay)

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, 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	Running, Valid, V2Dir, Fast	216.6 Mbit/s \| 816.0 Kbit/s	216.6 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	88.5% \| 98%	13.6d \| 8d	3.8d \| 48.4d	0.5d \| 5.1d	88.5% \| 98.0%	13.6d \| 1.0d	2026-07-02 13:26:34	80.0 Kbit/s
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	216.6 Mbit/s \| 816.0 Kbit/s	216.6 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	84.7% \| 98%	12.9d \| 8d	0.8d \| 10.1d	0.5d \| 5.2d	84.7% \| 98.0%	12.9d \| 1.0d	2026-07-02 16:19:25	80.0 Kbit/s
dizum (NL)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast	216.6 Mbit/s \| 816.0 Kbit/s	216.6 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	88.3% \| 98%	13.3d \| 8d	3.7d \| 25.9d	0.5d \| 5.2d	88.3% \| 98.0%	13.3d \| 1.0d	2026-07-02 13:26:34	80.0 Kbit/s
faravahar (US)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast	216.6 Mbit/s \| 816.0 Kbit/s	216.6 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	81.1% \| 98%	13.8d \| 8d	3.6d \| 28.4d	0.5d \| 5.2d	81.1% \| 98.0%	13.8d \| 1.0d	2026-07-02 16:19:25	80.0 Kbit/s
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	216.6 Mbit/s \| 816.0 Kbit/s	216.6 Mbit/s \| 312.0 Mbit/s OR 16.0 Mbit/s	85.8% \| 98%	14.2d \| 8d	4.6d \| 60.1d	0.5d \| 4.3d	85.8% \| 98.0%	14.2d \| 1.0d	2026-06-29 16:05:55	376.0 Kbit/s
longclaw (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	216.6 Mbit/s \| 816.0 Kbit/s	216.6 Mbit/s \| 240.0 Mbit/s OR 16.0 Mbit/s	88.1% \| 98%	13.7d \| 8d	3.8d \| 57.2d	0.5d \| 5.4d	88.1% \| 98.0%	13.7d \| 1.0d	2026-07-02 13:26:34	208.0 Kbit/s
maatuska (SE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	216.6 Mbit/s \| 816.0 Kbit/s	216.6 Mbit/s \| 304.0 Mbit/s OR 16.0 Mbit/s	88.5% \| 98%	13.6d \| 8d	3.8d \| 30.6d	0.5d \| 5.3d	88.5% \| 98.0%	13.6d \| 1.0d	2026-07-02 13:26:34	232.0 Kbit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable	216.6 Mbit/s \| 8.4 Mbit/s	216.6 Mbit/s \| 248.0 Mbit/s OR 16.0 Mbit/s	87.9% \| 98%	9.8d \| 8d	14143.7d \| 1364.1d	0.5d \| 5.4d	87.9% \| 98.0%	9.84d \| 9.83d	2026-07-02 13:26:34	304.0 Kbit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	216.6 Mbit/s \| 816.0 Kbit/s	216.6 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	88.2% \| 98%	13.8d \| 8d	3.8d \| 53.1d	0.5d \| 5.4d	88.2% \| 98.0%	13.8d \| 1.0d	2026-07-02 13:26:34	304.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.