View Relay "sixsevenbrainrot"
Fingerprint: E6CD2FC512DD9CF9190867AF80BE033901D474CC |
Family: 1 relay
|
d0139071@gmail.com |
AS9318
|
Korea, Republic of
|
Linux
- Consensus
- In Consensus (has Running flag)
- BW Verified
- Measured
- Stability
- Not Overloaded | DOWN 3d 11h 15m ago | UP 88% (1M)
- Reachability
- N/A
- BW Weight
- 0.00% of Network | 64 Mbit/s Observed By Relay
- Version
- 0.4.9.15 Recommended
- Recent Overload Reported: Relay reported general overload 3 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
- 1.235.159.83:443
Reachability (Directory Authorities)
- Status
- Reachability data unavailable
Location
- Country
-
Korea, Republic of
- Interactive Map
- View in RouteFluxMap
Capacity (Relay Reported)
- Observed Bandwidth
- 64.27 Mbit/s
- Advertised Bandwidth
- 62.91 Mbit/s
- Rate Limit
- 62.91 Mbit/s
- Burst Limit
- 104.86 Mbit/s
- Total Data
-
21 TB
(6 months)
1mo: 9.5 TB | 6mo: 21 TB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-04 11:15:19
- Measured By
- Yes (≥3 authorities)
History
Uptime Metrics
- Current Status
- DOWN 3d 11h 15m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 88.0%/95.9%/0.0%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (88.0%/95.9%/0.0%/0.0%)
- Hibernating
- No
Timestamps
- First Seen
- 3mo 9h 15m ago (2026-08-06 03:00:00)
- Last Seen
- 3d 11h 15m ago (2026-11-01 01:00:00)
- Last Restarted
- 3d 17h 13m ago (2026-10-31 19:02:20)
- Last Changed Address
- 2026-08-06 03:00:00
Evaluated 2026-11-04 12:15 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 25s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 4h 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-31 22:00 UTC (3 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
Operator Identity
Source: AROI Validation API — 2026-11-04 03:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- d0139071@gmail.com
Family Configuration
- Family Support
- None — No family membership configured
- Effective Members: 0
- none
- Effective Member: 1
E6CD2FC512DD9CF9190867AF80BE033901D474CC (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 12:15:39 GMT.