View Relay "pewpew"

Fingerprint: 580E3BD5AA99ECF6A4624E0A71AC42FEEB65F7A1 | Family: 2 relays | tor@aaronb.cc | AS24940 | Germany | Linux

Health Status

Consensus
In Consensus (has Running flag)
Flags
Fast, Running, V2Dir, Valid (4)
BW Verified
Measured
Stability
Not Overloaded | DOWN 4d 18h 15m ago | UP 84% (1M)
Reachability
N/A
First Seen
1y 7mo 3d ago
BW Weight
0.01% of Network | 119 Mbit/s Observed By Relay
Version
0.4.9.11 Not Recommended
Notes:
  • Recent Overload Reported: Relay reported general overload 6 days ago, outside the 72-hour eligibility window. The report can remain available after that window; the cutoff is not proof the relay recovered then.
    Suggestion: Monitor for a new report. Check system resources if it recurs.

Connectivity and Location

Addresses
OR Address
static.234.203.245.188.clients.your-server.de
188.245.203.234:9001
Reachability (Directory Authorities)
Status
Reachability data unavailable
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS24940
AS Name
Hetzner Online GmbH (BGP.tools)
AS Rarity
Common (score: 0/5, 7.97% consensus weight, 240 operators)

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
119.17 Mbit/s
Advertised Bandwidth
104.86 Mbit/s
Rate Limit
104.86 Mbit/s
Burst Limit
157.29 Mbit/s
Total Data
800 TB (5 years)
1mo: 45 TB | 6mo: 251 TB | 1y: 503 TB | 5y: 800 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-04 12:45:10

Measured By
Yes (≥3 authorities)
Network Participation: Consensus Weight: 0.0069% of network (58th pctl) | Guard: N/A | Middle: N/A | Exit: N/A
History
Throughput and write/read, last 6 months Throughput and write/read, last year Throughput and write/read, last 5 years Throughput and write/read, last 30 days
1M 6M 1Y 5Y

Uptime and Stability

Uptime Metrics
Current Status
DOWN 4d 18h 15m ago
Overall Uptime (1M/6M/1Y/5Y)
84.0%/97.1%/99.0%/98.4%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (84.0%/97.1%/99.0%/98.4%)
Hibernating
No
Timestamps
First Seen
1y 7mo 3d ago (2025-04-05 02:00:00)
Last Seen
4d 18h 15m ago (2026-10-30 19:00:00)
Last Restarted
2w 6h 47m ago (2026-10-21 06:28:34)
Last Changed Address
2026-04-06 23:00:00
Overload Status: Not Overloaded. Last general overload: 6 days ago

Evaluated 2026-11-04 13:15 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 19s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 5h 30m ago).

Reported timestamps use hour precision, so the displayed minute is not an exact incident time.

General Overload (from /details)
Status
Historical report — outside the 72-hour window
When
2026-10-29 00:00 UTC (6 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
—
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
Uptime, last 6 months Uptime, last year Uptime, last 5 years Uptime, last 30 days
1M 6M 1Y 5Y

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-11-04 04:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
tor@aaronb.cc
Family Configuration
Family Support
MyFamily Only (2) — Legacy only. Consider migrating to Happy Families. | View Full Family (2)
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Members: 2 
05FE1C8E02532BFDF22C720BEF2F85AD1EB92C20
580E3BD5AA99ECF6A4624E0A71AC42FEEB65F7A1 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

Platform
Linux — Tor 0.4.9.11 on Linux
Version
0.4.9.11 — Not Recommended
Version Status
Obsolete — Update urgently. See torproject.org/download

Exit Health & Policy

DNS Health
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
reject: 
  1-65535
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Wed, 04 Nov 2026 13:15:37 GMT.