View Relay "EsperpentoEspantoso"
Fingerprint: D54ED56BF843C6EF788F762CD5CAB2CD583AFC40 |
Family: 1 relay
|
AS57269
|
Spain
|
Linux
- Consensus
- In Consensus (has Running flag)
- BW Verified
- Measured
- Stability
- Overloaded | DOWN 1d 21h 15m ago | UP 93% (1M)
- Reachability
- N/A
- BW Weight
- 0.00% of Network | 60 Mbit/s Observed By Relay
- Version
- 0.4.9.15 Recommended
-
General Overload Active
: Relay reported general overload at 2026-11-01 17:00 UTC. Reported timestamps use hour precision, so the displayed minute is not an exact incident time. The flag does not identify which trigger fired. Investigation paths are Tor's internal OOM handling, dropped ntor onionskins, and TCP port exhaustion.
Suggestion: Inspect CPU and memory with htop, Tor service logs, host or container memory headroom, and the effective MaxMemInQueues. When the process was killed or restarted, check kernel OOM logs separately. A kernel OOM kill is a different mechanism from Tor freeing memory itself. MetricsPort: tor_relay_load_oom_bytes_total. Broken down by subsys. An increase measures bytes freed by Tor’s internal OOM handling. It is not an invocation count and it is not proof of a kernel OOM kill. Review Tor’s onionskin and drop messages, and whether the CPU is saturated or contended. The general-overload flag does not say this trigger fired. MetricsPort: tor_relay_load_onionskins_total{type="ntor",action="dropped"} and {type="ntor_v3",action="dropped"}. Compare each with the matching action="processed" series. Inspect both supported handshake types. Review Tor logs, socket usage, and the host’s ephemeral-port allocation. On Linux, ss -s and reading net.ipv4.ip_local_port_range are useful starting checks. MetricsPort: tor_relay_load_tcp_exhaustion_total. An increase records additional exhaustion events. See the Tor overload troubleshooting guide.
Addresses
- OR Address
-
79.112.21.117:9003
[2a0c:5a86:f505:4300:7a7b:8aff:feb8:c532]:9003
Reachability (Directory Authorities)
- Status
- Reachability data unavailable
Location
- Country
-
Spain
- Interactive Map
- View in RouteFluxMap
Capacity (Relay Reported)
- Observed Bandwidth
- 60.58 Mbit/s
- Advertised Bandwidth
- 60.58 Mbit/s
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
-
227 TB
(5 years)
1mo: 19 TB | 6mo: 141 TB | 1y: 225 TB | 5y: 227 TB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-04 08:15:15
- Measured By
- Yes (≥3 authorities)
History
Uptime Metrics
- Current Status
- DOWN 1d 21h 15m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 93.8%/85.6%/87.7%/83.8%
- Flag Uptime (1M/6M/1Y/5Y)
- —/85.1%/87.3%/82.8%
- Hibernating
- No
Timestamps
- First Seen
- 1y 1mo 1w ago (2025-09-21 12:00:00)
- Last Seen
- 1d 21h 15m ago (2026-11-02 12:00:00)
- Last Restarted
- 2d 15h 36m ago (2026-11-01 17:39:07)
- Last Changed Address
- 2026-10-29 07:00:00
Evaluated 2026-11-04 09:15 UTC. /details snapshot 2026-11-04 08:00:00 UTC (cached 11s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 1h 30m ago).
Reported timestamps use hour precision, so the displayed minute is not an exact incident time.
General Overload (from /details)
- Status
- Reported
- When
- 2026-11-01 17:00 UTC (2 days ago)
The general-overload flag does not say which trigger fired. Possible paths are Tor’s internal memory handling, dropped ntor handshakes, and TCP port exhaustion. Allium treats a valid report as eligible for 72 hours; that cutoff is not proof the relay recovered then.
File Descriptor Exhaustion (from /bandwidth)
- Status
- No file-descriptor exhaustion report in available data
Rate Limits (from /bandwidth)
- Status
- No rate-limit report in available data
- Rate Limit
- —
- Burst Limit
- —
- Write counter
- —
- Read counter
- —
What to check
-
Tor internal memory pressure
Inspect CPU and memory with htop, Tor service logs, host or container memory headroom, and the effective MaxMemInQueues. When the process was killed or restarted, check kernel OOM logs separately. A kernel OOM kill is a different mechanism from Tor freeing memory itself.MetricsPort:
tor_relay_load_oom_bytes_total— Broken down by subsys. An increase measures bytes freed by Tor’s internal OOM handling. It is not an invocation count and it is not proof of a kernel OOM kill. -
ntor handshake pressure
Review Tor’s onionskin and drop messages, and whether the CPU is saturated or contended. The general-overload flag does not say this trigger fired.MetricsPort:
tor_relay_load_onionskins_total{type="ntor",action="dropped"} and {type="ntor_v3",action="dropped"}— Compare each with the matching action="processed" series. Inspect both supported handshake types. -
TCP port exhaustion
Review Tor logs, socket usage, and the host’s ephemeral-port allocation. On Linux, ss -s and reading net.ipv4.ip_local_port_range are useful starting checks.MetricsPort:
tor_relay_load_tcp_exhaustion_total— An increase records additional exhaustion events.
About these reports and MetricsPort
Allium’s eligibility windows are applied to the reported timestamps: 72 hours for general overload and file-descriptor exhaustion, 24 hours for a rate-limit hit. A report at the cutoff is historical. An older report can remain visible after Onionoo or Allium’s cache still has it. The cutoff does not prove the relay recovered at that moment. Allium caches the bandwidth document for 12 hours by default. The snapshot time is when Onionoo published that document. It is not the relay’s event time, and it is not necessarily the extra-info publication time. Cache age is how old Allium’s copy is.
MetricsPort counters are cumulative. Compare samples, and account for process restarts. A nonzero total alone does not show ongoing activity. Gauges describe current values. An unavailable metric is unknown, not zero. Allium does not have this relay’s MetricsPort readings and does not invent them.
The port below is an example for an endpoint you have already configured. MetricsPort must be enabled with restricted access and must not be exposed publicly. Setup stays in the Tor overload troubleshooting guide.
curl http://127.0.0.1:9035/metrics
History
Operator Identity
Source: AROI Validation API — 2026-11-04 00: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 Wed, 04 Nov 2026 09:15:43 GMT.