View Relay "ciscler3"

Fingerprint: 58F30ABA1DE6CB84355B548377FF8E00C9C898C2 | Family: 3 relays | tor[at]rohlmann[dot]org | AS201814 | Poland | Linux

Consensus
In Consensus (has Running flag)
BW Verified
Measured
Stability
Not Overloaded | DOWN 5d 18h 45m ago | UP 80% (1M)
BW Weight
0.01% of Network | 104 Mbit/s Observed By Relay
Version
0.4.9.13 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.

Addresses
OR Address
91.226.198.36:9002
[2a03:cfc0:8004::4:11b]:9002
Reachability (Directory Authorities)
Status
Reachability data unavailable
Location
Country
Poland Poland
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS201814
AS Name
MEVSPACE sp. z o.o. (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.34% consensus weight, 4 operators)

Capacity (Relay Reported)
Observed Bandwidth
104.78 Mbit/s
Advertised Bandwidth
104.78 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
60 TB (6 months)
1mo: 27 TB | 6mo: 60 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-20 08:45:05

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

Uptime Metrics
Current Status
DOWN 5d 18h 45m ago
Overall Uptime (1M/6M/1Y/5Y)
80.9%/91.3%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
47.2%/71.5%/—/—
Hibernating
No
Timestamps
First Seen
2mo 6d 19h ago (2026-09-14 14:00:00)
Last Seen
5d 18h 45m ago (2026-11-14 15:00:00)
Last Restarted
1w 4h 11m ago (2026-11-13 05:34:21)
Last Changed Address
2026-09-14 14:00:00
Overload Status: Not Overloaded. Last general overload: 6 days ago

Evaluated 2026-11-20 09:45 UTC. /details snapshot 2026-11-20 08:00:00 UTC (cached 37s ago). /bandwidth snapshot 2026-11-20 02:00:00 UTC (cached 6h 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-11-13 11: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 30 days
1M 6M

Operator Identity

Source: AROI Validation API — 2026-11-19 23:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
tor[at]rohlmann[dot]org
Family Configuration
Family Support
MyFamily Only (3) — Legacy only. Consider migrating to Happy Families. | View Full Family (3)
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Members: 3
58F30ABA1DE6CB84355B548377FF8E00C9C898C2 (this relay)
7EFE50BEEEDDB8DBB08C9231DB42703D133064C0
F3426893D7B04185645529B7F7894A03B2E4F505
Alleged Member: 1
(they don't list you back)
6CAFA03BCDE62D3225A30AA27A80F90611EE728F (not in the network)
Indirect Members: 0
none

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

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 Fri, 20 Nov 2026 09:45:32 GMT.