View Relay "Unnamed"

Fingerprint: CFA205D2B414B8DA3C915B0C03D52CA134AF727E | Family: 1 relay | AS3462 | Taiwan | Linux

Consensus
In Consensus (9/9 Directory Auths)
DNS Health
Healthy (16.8s, 29th percentile) (via exitdnshealth.1aeo.com)
BW Verified
4/6 BW Auths Measured 10 Kbit/s Median
Stability
Not Overloaded | DOWN 10h 5m 42s ago | UP 97% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
BW Weight
0.00% of Network | 10 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: bandwidth below threshold : Observed bandwidth 11 Mbit/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.6% 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 6.1 days is below 8 days requirement (1.9 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 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.6% 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
59-120-32-214.hinet-ip.hinet.net
59.120.32.214:443
Exit Address
59.120.32.214
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Taiwan Taiwan
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS3462
AS Name
Chunghwa Telecom Co., Ltd. (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 9 operators)

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 8/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) 10.7 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.5d (1/9 DA above threshold)
Min/Max: 2.0d / 20686.1d (9/9 DA, Voting / Total Eligible)
≥7.7d - 13.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7317.3d
Uptime Below (0/9 DA) 7.6d (R) ≥9.6d - 10.2d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (8/9 DA) 8/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 ≥7.7d - 13.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7317.3d
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.2% (0/9 DA above threshold)
Min/Max: 90.4% / 92.6% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 5.9d (0/9 DA above threshold)
Min/Max: 5.4d / 6.1d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Meets (8/9 DA) 8/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 ≥7.7d - 13.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7317.3d
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.2% (0/9 DA above threshold)
Min/Max: 90.4% / 92.6% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 2.1 more days) Median: 5.9d (0/9 DA above threshold)
Min/Max: 5.4d / 6.1d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 10.7 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-08-23 22:00:59).

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

Source: CollecTor — fetched 2026-08-23 22:00:59

Measured By
4/6 Bandwidth Authorities
Not measured by: faravahar, longclaw
Median Measurement
10.7 Kbit/s
Min / Max
1600 bit/s / 10.7 Kbit/s
Deviation
9.1 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0001% of network (8th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime Metrics
Current Status
DOWN 10h 5m 42s ago
Overall Uptime (1M/6M/1Y/5Y)
97.7%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (97.7%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
1w 14h 5m ago (2026-08-16 09:00:00)
Last Seen
10h 5m 42s ago (2026-08-23 13:00:00)
Last Restarted
1w 15h 6m ago (2026-08-16 07:59:31)
Last Changed Address
2026-08-16 09:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator Identity

Source: AROI Validation API — 2026-08-23 14:00 UTC

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

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

DNS Health
Status
Healthy (avg. 16.8s, 29th percentile)
Query Domain
3dfd7d9d1ac1478db56ce5b4d2f8f06b.cfa205d2.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
4/4 instances succeeded
First Hop
kinglouie (US) F0178C29874D9E3C10FFDE340E577BE3034AFD60
Exit Address Used
59.120.32.214
Per-Instance Results
Cross Validation Attempt 1: Success, 17.8s (cv1_w4)
Cross Validation Attempt 2: Success, 16.8s (cv2_w4)
Cross Validation Attempt 3: Success, 17.7s (cv3_w4)
Cross Validation Attempt 4: Success, 14.8s (cv4_w4)
Tested: 2026-08-23 07:17:46 UTC
IPv4 Exit Policy Summary
reject: 
  25
  119
  135-139
  445
  563
  1214
  4661-4666
  6346-6429
  6699
  6881-6999
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 59.120.32.214:*
reject *:25
reject *:119
reject *:135-139
reject *:445
reject *:563
reject *:1214
reject *:4661-4666
reject *:6346-6429
reject *:6699
reject *:6881-6999
accept *:*

Last fetch was at Sun, 23 Aug 2026 23:05:31 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-08-23 22:00:59).

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 N Yes Valid, V2Dir, Fast, Exit 10.7 Mbit/s | 816.0 Kbit/s 10.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 92.6% | 98% 6.1d | 8d 2.5d | 11.1d 7.6d | 9.6d 92.6% | 98.0% 6.1d | 1.0d 2026-08-23 10:18:53 10.7 Kbit/s
dannenberg (DE) Yes Yes Yes Y Yes Valid, V2Dir, Fast, Exit 10.7 Mbit/s | 816.0 Kbit/s 10.7 Mbit/s | 320.0 Mbit/s OR 16.0 Mbit/s 92.6% | 98% 6.1d | 8d 2.5d | 13.3d 7.6d | 11.6d 92.6% | 98.0% 6.1d | 1.0d 2026-08-23 10:18:53 1920 bit/s
dizum (NL) Yes Yes Yes N Yes Valid, V2Dir, Fast, Exit 10.7 Mbit/s | 816.0 Kbit/s 10.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 92.2% | 98% 5.9d | 8d 2.5d | 12.6d 7.6d | 9.9d 92.2% | 98.0% 5.9d | 1.0d 2026-08-23 10:18:53 10.7 Kbit/s
faravahar (US) Yes Yes Yes Y Yes Valid, V2Dir, Fast, Exit 10.7 Mbit/s | 816.0 Kbit/s 10.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 92.2% | 98% 5.9d | 8d 2.5d | 12.6d 7.6d | 10.2d 92.2% | 98.0% 5.9d | 1.0d 2026-08-23 10:18:53 10.7 Kbit/s
gabelmoo (DE) Yes Yes Yes Y Yes Valid, V2Dir, Fast, Exit 10.7 Mbit/s | 816.0 Kbit/s 10.7 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 92.2% | 98% 6.1d | 8d 2.5d | 13.7d 7.6d | 10.2d 92.2% | 98.0% 6.1d | 1.0d 2026-08-23 10:18:53 1840 bit/s
longclaw (US) Yes Yes Yes Y Yes Valid, V2Dir, Fast, Exit 10.7 Mbit/s | 816.0 Kbit/s 10.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 92.1% | 98% 5.9d | 8d 2.5d | 17.0d 7.6d | 10.2d 92.1% | 98.0% 5.9d | 1.0d 2026-08-23 10:18:53 10.7 Kbit/s
maatuska (SE) Yes Yes Yes N Yes Valid, V2Dir, Fast, Exit 10.7 Mbit/s | 816.0 Kbit/s 10.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 90.4% | 98% 5.7d | 8d 2.0d | 7.7d 7.6d | 10.0d 90.4% | 98.0% 5.7d | 1.0d 2026-08-23 10:18:53 10.7 Kbit/s
moria1 (US) Yes Yes Yes Y Yes Valid, V2Dir, Stable, Exit 10.7 Mbit/s | 8.4 Mbit/s 10.7 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 91.4% | 98% 5.4d | 8d 20686.1d | 7317.3d 7.6d | 9.6d 91.4% | 98.0% 5.4d | 9.9d 2026-08-23 10:18:53 4480 bit/s
tor26 (AT) Yes Yes Yes Y Yes Valid, V2Dir, Fast, Exit 10.7 Mbit/s | 816.0 Kbit/s 10.7 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 92.3% | 98% 5.9d | 8d 2.5d | 13.5d 7.6d | 10.6d 92.3% | 98.0% 5.9d | 1.0d 2026-08-23 10:18:53 1600 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.