View Relay "death"

Fingerprint: 872BE4C147B7071C248D32EFF561D7468AC94A82 | Family: 1 relay | Satanist <admin AT 2cb dot su> | AS215659 | Romania | Linux

Consensus
In Consensus (9/9 Directory Auths)
DNS Health
Healthy (16.9s, 82nd percentile) (via exitdnshealth.1aeo.com)
BW Verified
7/8 BW Auths Measured 27 Kbit/s Median
Stability
Not Overloaded | UP 2w 1d 4h ago | UP 88% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
BW Weight
0.00% of Network | 39 Mbit/s Observed By Relay
Version
0.4.9.11 Recommended
Issues Detected:
  • 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 94.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 94.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.

Addresses
OR Address
tor-exit.ro.2cb.li
93.113.25.109:9001
Exit Address
93.113.25.109
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Romania Romania
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS215659
AS Name
Aokigahara SRL (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.11% consensus weight, 12 operators)

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 9/9
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (9/9 DA) 9/9 authorities reached relay ≥5/9 DA ORPort reachable
Valid Descriptor Meets (9/9 DA) 9/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Meets (9/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 39.1 Mbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (1/9 DA) Median: 3.6d (1/9 DA above threshold)
Min/Max: 1.8d / 15511.3d (9/9 DA, Voting / Total Eligible)
≥8.1d - 12.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9049.6d
Uptime Meets (9/9 DA) 15.2d (R) ≥7.3d - 7.5d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/9 DA) 1/9 DA assigned Stable ≥8.1d - 12.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9049.6d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (1/9 DA) Median: 94.0% (1/9 DA above threshold)
Min/Max: 84.7% / 98.6% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 13.3d (8/9 DA above threshold)
Min/Max: 7.6d / 13.9d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/9 DA) 1/9 DA assigned Stable ≥8.1d - 12.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9049.6d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (1/9 DA) Median: 94.0% (1/9 DA above threshold)
Min/Max: 84.7% / 98.6% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 13.3d (8/9 DA above threshold)
Min/Max: 7.6d / 13.9d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 39.1 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-304.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Meets (9/9 DA) Port 80: Yes | Port 443: Yes (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/9 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-07-25 12:45:10).

Capacity (Relay Reported)
Observed Bandwidth
39.07 Mbit/s
Advertised Bandwidth
39.07 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
63 TB (1 year)
1mo: 4.6 TB | 6mo: 56 TB | 1y: 63 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-07-25 12:45:10

Measured By
7/8 Bandwidth Authorities
Not measured by: bastet
Median Measurement
27.2 Kbit/s
Min / Max
6960 bit/s / 40.0 Kbit/s
Deviation
33.0 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0015% of network (26th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0046% (11th pctl)

Uptime Metrics
Current Status
UP 2w 1d 4h ago
Overall Uptime (1M/6M/1Y/5Y)
88.6%/96.2%/96.5%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
—/—/94.2%/—
Hibernating
No
Timestamps
First Seen
6mo 3w 3d ago (2026-01-02 07:00:00)
Last Seen
1h 45m 52s ago (2026-07-25 11:00:00)
Last Restarted
2w 1d 4h ago (2026-07-10 08:29:50)
Last Changed Address
2026-04-06 23:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Platform
Linux — Tor 0.4.9.11 on Linux
Version
0.4.9.11Recommended
Version Status
Recommended

DNS Health
Status
Healthy (avg. 16.9s, 82nd percentile)
Query Domain
29f191862039473a96a5f7639144f93b.872be4c1.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
4/4 instances succeeded
First Hop
fluffypancakes008ca (CA) 6A8376AA00F4236E7770691B3F94FBCCBEB3DBB8
Exit Address Used
93.113.25.109
Per-Instance Results
Cross Validation Attempt 1: Success, 15.0s (cv1_w3)
Cross Validation Attempt 2: Success, 20.9s (cv2_w3)
Cross Validation Attempt 3: Success, 13.9s (cv3_w3)
Cross Validation Attempt 4: Success, 17.8s (cv4_w3)
Tested: 2026-07-25 07:14:21 UTC
IPv4 Exit Policy Summary
reject: 
  25
  465
  587
IPv6 Exit Policy Summary
None
Full Exit Policy
reject 0.0.0.0/8:*
reject 169.254.0.0/16:*
reject 127.0.0.0/8:*
reject 192.168.0.0/16:*
reject 10.0.0.0/8:*
reject 172.16.0.0/12:*
reject 93.113.25.109:*
reject *:25
reject *:465
reject *:587
accept *:*

Last fetch was at Sat, 25 Jul 2026 12:45:49 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-07-25 12:45:10).

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 Yes Y Yes Running, Valid, V2Dir, Fast, Exit 39.1 Mbit/s | 816.0 Kbit/s 39.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 94.1% | 98% 13.3d | 8d 3.8d | 16.5d 15.2d | 7.3d 94.1% | 98.0% 13.3d | 1.0d 2026-07-24 18:53:22 39.1 Kbit/s
dannenberg (DE) Yes Yes Yes Y Yes Running, Valid, V2Dir, Fast, Exit 39.1 Mbit/s | 816.0 Kbit/s 39.1 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 94.0% | 98% 13.9d | 8d 3.2d | 8.1d 15.2d | 7.4d 94.0% | 98.0% 13.9d | 1.0d 2026-07-24 18:53:22 24.8 Kbit/s
dizum (NL) Yes Yes Yes N Yes Running, Valid, V2Dir, Fast, Exit 39.1 Mbit/s | 816.0 Kbit/s 39.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 93.9% | 98% 12.7d | 8d 3.6d | 11.7d 15.2d | 7.4d 93.9% | 98.0% 12.7d | 1.0d 2026-07-24 18:53:22 39.1 Kbit/s
faravahar (US) Yes Yes Yes Y Yes Running, Valid, V2Dir, Fast, Exit 39.1 Mbit/s | 816.0 Kbit/s 39.1 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 93.3% | 98% 13.8d | 8d 3.1d | 11.9d 15.2d | 7.7d 93.3% | 98.0% 13.8d | 1.0d 2026-07-24 18:53:22 20.0 Kbit/s
gabelmoo (DE) Yes Yes Yes Y Yes Running, Valid, V2Dir, Fast, Exit 39.1 Mbit/s | 816.0 Kbit/s 39.1 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 98.6% | 98% 8.4d | 7d 2.2d | 12.2d 15.2d | 7.4d 98.6% | 98.0% 8.4d | 1.0d 2026-07-24 18:53:22 27.2 Kbit/s
longclaw (US) Yes Yes Yes Y Yes Running, Valid, V2Dir, Fast, Exit 39.1 Mbit/s | 816.0 Kbit/s 39.1 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 84.7% | 98% 7.6d | 8d 1.8d | 23.1d 15.2d | 7.9d 84.7% | 98.0% 7.6d | 1.0d 2026-07-24 18:53:22 21.6 Kbit/s
maatuska (SE) Yes Yes Yes Y Yes Running, Valid, V2Dir, Fast, Exit 39.1 Mbit/s | 816.0 Kbit/s 39.1 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 94.3% | 98% 13.5d | 8d 3.9d | 12.5d 15.2d | 7.9d 94.3% | 98.0% 13.5d | 1.0d 2026-07-24 18:53:22 6960 bit/s
moria1 (US) Yes Yes Yes Y Yes Running, Valid, V2Dir, Fast, Stable, Exit 39.1 Mbit/s | 8.4 Mbit/s 39.1 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 92.6% | 98% 9.6d | 8d 15511.3d | 9049.6d 15.2d | 7.5d 92.6% | 98.0% 9.6d | 9.8d 2026-07-24 18:53:22 40.0 Kbit/s
tor26 (AT) Yes Yes Yes Y Yes Running, Valid, V2Dir, Fast, Exit 39.1 Mbit/s | 816.0 Kbit/s 39.1 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 94.1% | 98% 13.9d | 8d 3.9d | 16.7d 15.2d | 7.5d 94.1% | 98.0% 13.9d | 1.0d 2026-07-24 18:53:22 30.4 Kbit/s

— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known

Bandwidth Values Explained:
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.
Stable Uptime (Two Data Sources):
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.