View Relay "cyunexit0"

Fingerprint: CE3C219B13CFE438300600B9356CBCB9419379A7 | Family: 1 relay | 0x9900CC Sober <sober@dmt.observer> | AS215659 | United States of America | Linux

Consensus
In Consensus (9/9 Directory Auths)
DNS Health
Healthy (17.5s, 81st percentile) (via exitdnshealth.1aeo.com)
BW Verified
4/7 BW Auths Measured 1544 bit/s Median
Stability
Not Overloaded | UP 1d 4h 47m ago | UP 92% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
BW Weight
0.00% of Network | 1 Mbit/s Observed By Relay
Version
0.4.9.9 Recommended
Issues Detected:
  • Guard: requires Fast flag : Guard flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • 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: bandwidth below threshold : Observed bandwidth 0.2 MB/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
    Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM.
  • Guard: WFU below threshold : Weighted Fractional Uptime 92.0% 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.
  • Guard: Time Known below threshold : Time Known 4.5 days is below 8 days requirement (3.5 more days needed)
    Suggestion: Time Known tracks how long authorities have observed your relay. This resets if: 1) Identity key changes, 2) Long downtime makes authorities forget you. Just keep running stably.
  • 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 Fast flag : HSDir flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • 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 92.0% 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.dmt.observer
66.78.40.35:9001
[2a0f:85c1:356:a2d8::1]:9001
Exit Address
66.78.40.35
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
United States of America United States of America
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS215659
AS Name
Aokigahara SRL (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.08% consensus weight, 9 operators)

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 4/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
IPv6 Reachability Meets (6/6 DA) 6/6 tested authorities reached relay ≥4/6 tested (majority) (≥4/6 DA)
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) 1.5 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: 2.2d (1/9 DA above threshold)
Min/Max: 0.0d / 9523.4d (9/9 DA, Voting / Total Eligible)
≥27.2d - 57.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥371.6d
Uptime Below (0/9 DA) 1.2d (R) ≥8.0d - 9.2d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (4/9 DA) 4/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 ≥27.2d - 57.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥371.6d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 92.0% (0/9 DA above threshold)
Min/Max: 74.5% / 92.3% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 4.5d (0/9 DA above threshold)
Min/Max: 3.9d / 4.5d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (4/9 DA) 4/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 ≥27.2d - 57.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥371.6d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 92.0% (0/9 DA above threshold)
Min/Max: 74.5% / 92.3% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 3.5 more days) Median: 4.5d (0/9 DA above threshold)
Min/Max: 3.9d / 4.5d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 1.5 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-320.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-06-27 08:15:06).

Capacity (Relay Reported)
Observed Bandwidth
1.55 Mbit/s
Advertised Bandwidth
1.55 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
2.5 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-06-27 08:15:06

Measured By
4/7 Bandwidth Authorities
Not measured by: bastet, dannenberg, longclaw
Median Measurement
1544 bit/s
Min / Max
64 bit/s / 1544 bit/s
Deviation
1480 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (2th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0000% (1th pctl)

Uptime Metrics
Current Status
UP 1d 4h 47m ago
Overall Uptime (1M/6M/1Y/5Y)
92.7%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (92.7%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
5d 4h 15m ago (2026-06-22 05:00:00)
Last Seen
1h 15m 45s ago (2026-06-27 08:00:00)
Last Restarted
1d 4h 47m ago (2026-06-26 04:28:06)
Last Changed Address
2026-06-22 05:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator Identity

Source: AROI Validation API — 2026-06-27 01:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
0x9900CC Sober <sober@dmt.observer>
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1
CE3C219B13CFE438300600B9356CBCB9419379A7 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

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

DNS Health
Status
Healthy (avg. 17.5s, 81st percentile)
Query Domain
dbdf020934044b7db35f9cb2bede9b71.ce3c219b.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
3/3 instances succeeded
First Hop
Dentist2 (CZ) 83470E89482FC1F4DF519468EAF779BAEE86A767
Exit Address Used
66.78.40.35
Per-Instance Results
Cross Validation Attempt 1: Success, 21.2s (cv1_w3)
Cross Validation Attempt 2: Success, 17.8s (cv3_w3)
Cross Validation Attempt 3: Success, 13.6s (cv4_w3)
Tested: 2026-06-26 19:16:40 UTC
IPv4 Exit Policy Summary
accept: 
  20-21
  43
  53
  80
  110
  143
  220
  443
  873
  989-993
  995
  1194
  1293
  3690
  4321
  5222-5223
  5228
  9418
  11371
  64738
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 66.78.40.35:*
accept *:20-21
accept *:989-990
accept *:43
accept *:4321
accept *:53
accept *:80
accept *:443
accept *:110
accept *:143
accept *:993
accept *:220
accept *:995
accept *:873
accept *:991
accept *:992
accept *:1194
accept *:1293
accept *:3690
accept *:5222-5223
accept *:5228
accept *:9418
accept *:11371
accept *:64738
reject *:*

Last fetch was at Sat, 27 Jun 2026 09:15:43 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-06-27 08:15:06).

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 1.5 Mbit/s | 816.0 Kbit/s 1.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 92.0% | 98% 4.5d | 8d 2.2d | 57.5d 1.2d | 8.0d 92.0% | 98.0% 4.5d | 1.0d 2026-06-26 23:11:18 1544 bit/s
dannenberg (DE) Yes Yes Yes Y Yes Valid, V2Dir, Fast, Exit 1.5 Mbit/s | 816.0 Kbit/s 1.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 74.5% | 98% 4.0d | 8d 0.0d | 27.2d 1.2d | 8.6d 74.5% | 98.0% 4.0d | 1.0d 2026-06-26 23:11:18 1544 bit/s
dizum (NL) Yes Yes Yes N Yes Running, Valid, V2Dir, Fast, Exit 1.5 Mbit/s | 816.0 Kbit/s 1.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 92.3% | 98% 4.5d | 8d 1.7d | 46.1d 1.2d | 10.6d 92.3% | 98.0% 4.5d | 1.0d 2026-06-26 23:11:18 1544 bit/s
faravahar (US) Yes Yes Yes N Yes Running, Valid, V2Dir, Fast, Exit 1.5 Mbit/s | 816.0 Kbit/s 1.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 92.0% | 98% 4.5d | 8d 2.2d | 57.5d 1.2d | 9.7d 92.0% | 98.0% 4.5d | 1.0d 2026-06-26 23:11:18 1544 bit/s
gabelmoo (DE) Yes Yes Yes Y Yes Running, Valid, V2Dir, Exit 1.5 Mbit/s | 816.0 Kbit/s 1.5 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 92.3% | 98% 4.5d | 8d 2.3d | 57.6d 1.2d | 9.3d 92.3% | 98.0% 4.5d | 1.0d 2026-06-26 23:11:18 64 bit/s
longclaw (US) Yes Yes Yes Y Yes Running, Valid, V2Dir, Exit 1.5 Mbit/s | 816.0 Kbit/s 1.5 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 92.3% | 98% 4.5d | 8d 2.3d | 57.2d 1.2d | 9.2d 92.3% | 98.0% 4.5d | 1.0d 2026-06-26 23:11:18 1544 bit/s
maatuska (SE) Yes Yes Yes Y Yes Running, Valid, V2Dir, Exit 1.5 Mbit/s | 816.0 Kbit/s 1.5 Mbit/s | 320.0 Mbit/s OR 16.0 Mbit/s 92.0% | 98% 4.5d | 8d 2.2d | 41.3d 1.2d | 8.9d 92.0% | 98.0% 4.5d | 1.0d 2026-06-26 23:11:18 64 bit/s
moria1 (US) Yes Yes Yes Y Yes Running, Valid, V2Dir, Stable, Exit 1.5 Mbit/s | 8.4 Mbit/s 1.5 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 91.1% | 98% 3.9d | 8d 9523.4d | 371.6d 1.2d | 8.5d 91.1% | 98.0% 3.9d | 9.9d 2026-06-26 23:11:18 176 bit/s
tor26 (AT) Yes Yes Yes Y Yes Valid, V2Dir, Exit 1.5 Mbit/s | 816.0 Kbit/s 1.5 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 74.6% | 98% 3.9d | 8d 0.0d | 57.2d 1.2d | 10.1d 74.6% | 98.0% 3.9d | 1.0d 2026-06-26 23:11:18 72 bit/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.