View Relay "Unnamed"

Fingerprint: 9ECE67DAAF8A26586B9DD99E376E5FE72A48E57E | Family: 1 relay | AS45102 | Singapore | Linux

Health Status

Consensus
In Consensus (8/8 Directory Auths)
Flags
Running, Valid, V2Dir, Stable, Exit (5)
DNS Health
Healthy (14.9s, 14th percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/5 BW Auths Measured 136 bit/s Median
Stability
Overloaded | UP 3mo 1w 6d ago | UP 100% (1M)
Reachability
IPv4: 8/9 (Directory Auths)
First Seen
3w 2d 5h ago
BW Weight
0.00% of Network | 1 Mbit/s Observed By Relay
Version
0.4.8.21 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: 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.
  • 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.
  • 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.
  • Write Bandwidth Limit Hit : Write rate limit (2 Mbit/s) was hit 56,325 times. Relay is throttling outbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more upload capacity.
  • Read Bandwidth Limit Hit : Read rate limit (2 Mbit/s) was hit 67,098 times. Relay is throttling inbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more download capacity.
Notes:
  • Partial IPv4 reachability: 8/9 authorities can reach this relay
  • Rate Limit Configuration: Configured limits: Rate=2 Mbit/s, Burst=2 Mbit/s. Limits hit: Write=56,325, Read=67,098.

Connectivity and Location

Addresses
OR Address
8.215.52.126:9001
Exit Address
8.215.52.126
Reachability (Directory Authorities)
IPv4
8/9
Location
Country
Singapore Singapore
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS45102
AS Name
Alibaba (US) Technology Co., Ltd. (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 2 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Stable, Exit
Eligible Flags (5): Running: 8/8 | Valid: 8/8 | V2Dir: 8/8 | Fast: 3/8 | Stable: 8/8 | HSDir: 3/8 | Guard: 0/8 | Exit: 8/8
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (8/8 DA) 8/8 authorities reached relay ≥5/8 DA ORPort reachable
Valid Descriptor Meets (8/8 DA) 8/8 authorities assigned Valid Not blacklisted + valid descriptor (≥5/8 DA)
V2Dir DirPort Available Meets (8/8 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/8 DA)
Fast Speed Meets (8/8 DA) 1.6 Mbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Partial (7/8 DA) Median: 152.5d (6/8 DA above threshold)
Min/Max: 20.7d / 154.7d (8/8 DA, Voting / Total Eligible)		 ≥16.6d - 57.9d (varies) (≥5/8 DA)
Uptime Meets (8/8 DA) 103.9d (R) ≥10.4d - 10.9d (varies) (≥5/8 DA)
HSDir Prereq: Fast Below (3/8 DA) 3/8 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (8/8 DA) 8/8 DA assigned Stable ≥16.6d - 57.9d (varies) (≥5/8 DA)
Prereq: V2Dir Meets (8/8 DA) 8/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Meets (8/8 DA) Majority: 100.0% (6/8 DA)
Min/Med/Max: 98.8% / 100.0% / 100.0% (8/8 DA, Voting / Total Eligible)		 ≥98.0% (≥5/8 DA)
Time Known Meets (7/8 DA) Median: 142.5d (8/8 DA above threshold)
Min/Max: 9.7d / 154.7d (8/8 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/8 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (3/8 DA) 3/8 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (8/8 DA) 8/8 DA assigned Stable ≥16.6d - 57.9d (varies) (≥5/8 DA)
Prereq: V2Dir Meets (8/8 DA) 8/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Meets (8/8 DA) Majority: 100.0% (6/8 DA)
Min/Med/Max: 98.8% / 100.0% / 100.0% (8/8 DA, Voting / Total Eligible)		 ≥98% (≥5/8 DA)
Time Known Meets (8/8 DA) Median: 142.5d (8/8 DA above threshold)
Min/Max: 9.7d / 154.7d (8/8 DA, Voting / Total Eligible)		 ≥8 days (≥5/8 DA)
Bandwidth Below (0/8 DA) 1.6 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.0 Mbit/s (≥5/8 DA)
Exit Exit Policy Meets (8/8 DA) Port 80: Yes | Port 443: Yes (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/8 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-04-30 04:15:08).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
1.59 Mbit/s
Advertised Bandwidth
1.57 Mbit/s
Rate Limit
1.57 Mbit/s
Burst Limit
2.10 Mbit/s
Total Data
5.5 TB (6 months)
1mo: 370 GB | 6mo: 5.5 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-04-30 04:15:08

Measured By
5/5 Bandwidth Authorities
Median Measurement
136.0 bit/s
Min / Max
64 bit/s / 1568 bit/s
Deviation
1504 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 and Stability

Uptime Metrics
Current Status
UP 3mo 1w 6d ago
Overall Uptime (1M/6M/1Y/5Y)
100.0%/99.5%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (100.0%/99.5%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
3w 2d 5h ago (2026-04-06 23:00:00)
Last Seen
1h 15m 39s ago (2026-04-30 03:00:00)
Last Restarted
3mo 1w 6d ago (2026-01-16 07:34:47)
Last Changed Address
2026-04-06 23:00:00
[Warning] OVERLOADED — Rate limits hit W:56325 R:67098 (limit: 2 Mbit/s)
General Overload (from /details)
Status
Not Reported

OOM killer, onionskin queue saturation, or TCP port exhaustion. Flag remains 72h after last event (Tor spec 328).

File Descriptor Exhaustion (from /bandwidth)
Status
Not Reported
Rate Limits (from /bandwidth)
Rate Limit
1.57 Mbit/s
Burst Limit
2.10 Mbit/s
Write Limit Hit
56,325 times
Read Limit Hit
67,098 times
Last Reported
1 days ago
Recommendations
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-04-29 21: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 
9ECE67DAAF8A26586B9DD99E376E5FE72A48E57E (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

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

Exit Health & Policy

DNS Health
Status
Healthy (avg. 14.9s, 14th percentile)
Query Domain
99691f8be6ef46638b98bf38a6970e5a.9ece67da.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
4/4 instances succeeded
First Hop
rapoport (AT) A0EC0C1A78324AB641B7900FD1019A73C4312B0C
Exit Address Used
8.215.52.126
Per-Instance Results
Cross Validation Attempt 1: Success, 13.7s (cv1_w3)
Cross Validation Attempt 2: Success, 8.7s (cv2_w3)
Cross Validation Attempt 3: Success, 19.5s (cv3_w3)
Cross Validation Attempt 4: Success, 17.7s (cv4_w3)
Tested: 2026-04-29 19:16:42 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 
  25
  8080
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 8.215.52.126:*
reject *:25
reject *:8080
accept *:*

Last fetch was at Thu, 30 Apr 2026 04:15:38 GMT.

Consensus Evaluation

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

Per-Authority Details

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) No — — — N No — — — — — — — — — — —
dannenberg (DE) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 1.6 Mbit/s | 816.0 Kbit/s 1.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 49.5d | 8d 48.8d | 47.0d 103.9d | 10.9d 100.0% | 98.0% 49.5d | 1.0d 2026-04-29 20:34:53 1568 bit/s
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 1.6 Mbit/s | 816.0 Kbit/s 1.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 134.0d | 8d 134.0d | 42.5d 103.9d | 10.4d 100.0% | 98.0% 134.0d | 1.0d 2026-04-28 02:41:22 1568 bit/s
faravahar (US) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 1.6 Mbit/s | 816.0 Kbit/s 1.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 154.1d | 8d 154.1d | 57.9d 103.9d | 10.9d 100.0% | 98.0% 154.1d | 1.0d 2026-04-29 20:34:53 1568 bit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 1.6 Mbit/s | 816.0 Kbit/s 1.6 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 154.6d | 8d 154.6d | 57.8d 103.9d | 10.9d 100.0% | 98.0% 154.6d | 1.0d 2026-04-29 20:34:53 72 bit/s
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 1.6 Mbit/s | 816.0 Kbit/s 1.6 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 150.9d | 8d 150.9d | 63.1d 103.9d | 10.9d 100.0% | 98.0% 150.9d | 1.0d 2026-04-29 20:34:53 120 bit/s
maatuska (SE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 1.6 Mbit/s | 816.0 Kbit/s 1.6 Mbit/s | 328.0 Mbit/s OR 16.0 Mbit/s 98.8% | 98% 35.3d | 8d 20.7d | 16.6d 103.9d | 10.9d 98.8% | 98.0% 35.3d | 1.0d 2026-04-29 20:34:53 64 bit/s
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 1.6 Mbit/s | 8.4 Mbit/s 1.6 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 9.7d | 8d 154.7d | 281.3d 103.9d | 12.7d 100.0% | 98.0% 9.7d | 9.9d 2026-04-29 20:34:53 152 bit/s
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 1.6 Mbit/s | 816.0 Kbit/s 1.6 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 154.7d | 8d 154.7d | 58.1d 103.9d | 11.3d 100.0% | 98.0% 154.7d | 1.0d 2026-04-29 20:34:53 64 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.