View Relay "EsperpentoEspantoso"
Fingerprint: D54ED56BF843C6EF788F762CD5CAB2CD583AFC40 |
Family: 1 relay
|
AS57269
|
Spain
|
Linux
- Consensus
- In Consensus (7/7 Directory Auths)
- BW Verified
- 5/6 BW Auths Measured 42 Kbit/s Median
- Stability
- Overloaded | UP 2h 31m 46s ago | UP 77% (1M)
- Reachability
- IPv4: 7/7 (Directory Auths)
- BW Weight
- 0.00% of Network | 36 Mbit/s Observed By Relay
- Version
- 0.4.9.6 Recommended
-
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 58.1% 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 58.1% 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-19 21: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.
Addresses
- OR Address
- 79.112.2.136:9003
Reachability (Directory Authorities)
- IPv4
- 7/7
Location
- Country
-
Spain
- Interactive Map
- View in RouteFluxMap
Eligibility Flag Vote Details
| Flag | Metric | Status | Relay Value | Threshold Required |
|---|---|---|---|---|
| Running | IPv4 Reachability | Meets (7/7 DA) | 7/7 authorities reached relay | ≥4/7 DA ORPort reachable |
| Valid | Descriptor | Meets (7/7 DA) | 7/7 authorities assigned Valid | Not blacklisted + valid descriptor (≥4/7 DA) |
| V2Dir | DirPort Available | Meets (7/7 DA) | Tunnelled: Yes (no DirPort) (R) | Tunnelled directory via ORPort or DirPort (≥4/7 DA) |
| Fast | Speed | Meets (7/7 DA) | 36.6 Mbit/s (R) | ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Stable | MTBF | Below (1/7 DA) | Median: 1.4d (1/7 DA above threshold) Min/Max: 1.0d / 15697.4d (7/7 DA, Voting / Total Eligible) |
≥8.2d - 14.9d (varies) (≥4/7 DA) [Stricter] moria1: ≥9062.0d |
| Uptime | Below (0/7 DA) | 0.1d (R) | ≥8.4d - 8.6d (varies) (≥4/7 DA) | |
| HSDir | Prereq: Fast | Meets (6/7 DA) | 6/7 DA assigned Fast | ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (1/7 DA) | 1/7 DA assigned Stable | ≥8.2d - 14.9d (varies) (≥4/7 DA) [Stricter] moria1: ≥9062.0d |
|
| Prereq: V2Dir | Meets (7/7 DA) | 7/7 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥4/7 DA) | |
| WFU | Below (0/7 DA) | Median: 57.6% (0/7 DA above threshold) Min/Max: 55.9% / 59.9% (7/7 DA, Voting / Total Eligible) |
≥98.0% (≥4/7 DA) | |
| Time Known | Meets (6/7 DA) | Median: 11.9d (7/7 DA above threshold) Min/Max: 9.6d / 12.1d (7/7 DA, Voting / Total Eligible) |
≥1.0d (most) (≥4/7 DA) [Stricter] moria1: ≥9.7d |
|
| Guard | Prereq: Fast | Meets (6/7 DA) | 6/7 DA assigned Fast | ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (1/7 DA) | 1/7 DA assigned Stable | ≥8.2d - 14.9d (varies) (≥4/7 DA) [Stricter] moria1: ≥9062.0d |
|
| Prereq: V2Dir | Meets (7/7 DA) | 7/7 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥4/7 DA) | |
| WFU | Below (0/7 DA) | Median: 57.6% (0/7 DA above threshold) Min/Max: 55.9% / 59.9% (7/7 DA, Voting / Total Eligible) |
≥98% (≥4/7 DA) | |
| Time Known | Meets (7/7 DA) | Median: 11.9d (7/7 DA above threshold) Min/Max: 9.6d / 12.1d (7/7 DA, Voting / Total Eligible) |
≥8 days (≥4/7 DA) | |
| Bandwidth | Meets (7/7 DA) | 36.6 Mbit/s (R) | ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-280.0 Mbit/s (≥4/7 DA) | |
| Exit | Exit Policy | Below (0/7 DA) | Port 80: No | Port 443: No (R) | Allows ≥1 /8 on ports 80 AND 443 (≥4/7 DA) |
(DA) = Dir. Auth. Measured |
(R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-07-20 00:00:25).
Capacity (Relay Reported)
- Observed Bandwidth
- 36.65 Mbit/s
- Advertised Bandwidth
- 36.65 Mbit/s
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
-
165 TB
(1 year)
1mo: 24 TB | 6mo: 155 TB | 1y: 165 TB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-07-20 00:00:25
- Measured By
-
5/6
Bandwidth Authorities
Not measured by: bastet - Median Measurement
- 42.4 Kbit/s
- Min / Max
- 568 bit/s / 65.6 Kbit/s
- Deviation
- 65.0 Kbit/s [Warning] High variation
Uptime Metrics
- Current Status
- UP 2h 31m 46s ago
- Overall Uptime (1M/6M/1Y/5Y)
- 77.8%/91.0%/81.5%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- 74.7%/90.5%/80.5%/—
- Hibernating
- No
Timestamps
- First Seen
- 10mo 1d 12h ago (2025-09-21 12:00:00)
- Last Seen
- 2h 2m 31s ago (2026-07-19 22:00:00)
- Last Restarted
- 2h 31m 46s ago (2026-07-19 21:30:45)
- Last Changed Address
- 2026-07-18 10:00:00
General Overload (from /details)
- Status
- Reported
- When
- 2026-07-19 21:00 UTC (3 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
MaxMemInQueuesin torrc
Operator Identity
Source: AROI Validation API — 2026-07-19 16:00 UTC
Family Configuration
- Family Support
- None — No family membership configured
- Effective Members: 0
- none
- Effective Member: 1
D54ED56BF843C6EF788F762CD5CAB2CD583AFC40 (this relay)
- Alleged Members: 0
- none
- Indirect Members: 0
- none
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Mon, 20 Jul 2026 00:02:22 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-07-20 00:00:25).
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 | 36.6 Mbit/s | 816.0 Kbit/s | 36.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 58.1% | 98% | 12.1d | 8d | 1.4d | 21.1d | 0.1d | 8.4d | 58.1% | 98.0% | 12.1d | 1.0d | 2026-07-19 21:50:46 | 36.6 Kbit/s |
| dannenberg (DE) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Fast | 36.6 Mbit/s | 816.0 Kbit/s | 36.6 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s | 57.0% | 98% | 12.0d | 8d | 1.0d | 8.2d | 0.1d | 8.6d | 57.0% | 98.0% | 12.0d | 1.0d | 2026-07-19 21:50:46 | 48.8 Kbit/s |
| dizum (NL) | Yes | Yes | No | — | N | Yes | Running, Valid, V2Dir, Fast | 36.6 Mbit/s | 816.0 Kbit/s | 36.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 58.3% | 98% | 11.5d | 8d | 1.4d | 13.2d | 0.1d | 8.6d | 58.3% | 98.0% | 11.5d | 1.0d | 2026-07-19 21:50:46 | 36.6 Kbit/s |
| faravahar (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Fast | 36.6 Mbit/s | 816.0 Kbit/s | 36.6 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s | 55.9% | 98% | 11.9d | 8d | 1.2d | 14.4d | 0.1d | 8.6d | 55.9% | 98.0% | 11.9d | 1.0d | 2026-07-19 21:50:46 | 65.6 Kbit/s |
| maatuska (SE) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Fast | 36.6 Mbit/s | 816.0 Kbit/s | 36.6 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s | 57.3% | 98% | 11.8d | 8d | 1.4d | 14.9d | 0.1d | 8.6d | 57.3% | 98.0% | 11.8d | 1.0d | 2026-07-19 21:50:46 | 42.4 Kbit/s |
| moria1 (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Stable | 36.6 Mbit/s | 8.4 Mbit/s | 36.6 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s | 59.9% | 98% | 9.6d | 8d | 15697.4d | 9062.0d | 0.1d | 8.6d | 59.9% | 98.0% | 9.6d | 9.7d | 2026-07-19 21:50:46 | 568 bit/s |
| tor26 (AT) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Fast | 36.6 Mbit/s | 816.0 Kbit/s | 36.6 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s | 57.6% | 98% | 11.9d | 8d | 1.4d | 21.0d | 0.1d | 8.6d | 57.6% | 98.0% | 11.9d | 1.0d | 2026-07-19 21:50:46 | 60.8 Kbit/s |
— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known
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.
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.