View Relay "Unnamed"

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

Consensus
In Consensus (9/9 Directory Auths)
DNS Health
Healthy (17.4s, 79th percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/6 BW Auths Measured 192 bit/s Median
Stability
Overloaded | UP 1mo 4w 6h ago | UP 100% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
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 30,042 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 36,079 times. Relay is throttling inbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more download capacity.
Notes:
  • Rate Limit Configuration: Configured limits: Rate=2 Mbit/s, Burst=2 Mbit/s. Limits hit: Write=30,042, Read=36,079.

Addresses
OR Address
8.215.52.126:9001
Exit Address
8.215.52.126
Reachability (Directory Authorities)
IPv4
9/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)

Current Flags (5): Running, Valid, V2Dir, Stable, Exit
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 4/9 | Stable: 9/9 | HSDir: 3/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) 1.6 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 Partial (6/9 DA) Median: 108.0d (7/9 DA above threshold)
Min/Max: 5.4d / 108.9d (9/9 DA, Voting / Total Eligible)
≥11.3d - 55.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥347.6d
Uptime Meets (9/9 DA) 58.3d (R) ≥12.0d - 14.4d (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 Meets (9/9 DA) 9/9 DA assigned Stable ≥11.3d - 55.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥347.6d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Majority: 100.0% (7/9 DA)
Min/Med/Max: 89.0% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 105.8d (9/9 DA above threshold)
Min/Max: 9.6d / 108.6d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
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 Meets (9/9 DA) 9/9 DA assigned Stable ≥11.3d - 55.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥347.6d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Majority: 100.0% (7/9 DA)
Min/Med/Max: 89.0% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 105.8d (9/9 DA above threshold)
Min/Max: 9.6d / 108.6d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 1.6 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-296.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-03-15 13:15:07).

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
4.9 TB (6 months)
1mo: 427 GB | 6mo: 4.9 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-15 13:15:07

Measured By
5/6 Bandwidth Authorities
Not measured by: longclaw
Median Measurement
192 bit/s
Min / Max
56 bit/s / 1568 bit/s
Deviation
1512 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 1mo 4w 6h ago
Overall Uptime (1M/6M/1Y/5Y)
100.0%/99.3%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (100.0%/99.3%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
4mo 3d 10h ago (2025-11-12 03:00:00)
Last Seen
1h 45m 55s ago (2026-03-15 12:00:00)
Last Restarted
1mo 4w 6h ago (2026-01-16 07:34:47)
Last Changed Address
2025-11-12 03:00:00
[Warning] OVERLOADED — Rate limits hit W:30042 R:36079 (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
30,042 times
Read Limit Hit
36,079 times
Last Reported
5 hours ago
Recommendations
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic

Operator Identity

Source: AROI Validation API — 2026-03-15 06: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

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

DNS Health
Status
Healthy (avg. 17.4s, 79th percentile)
Query Domain
2ea3775fd8404a3d9a66a15451034cd0.9ece67da.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
4/4 instances succeeded
First Hop
Truck (RO) 411361FDBEE704CEE86BF599257E117BC1F7063B
Exit Address Used
8.215.52.126
Per-Instance Results
Cross Validation Attempt 1: Success, 20.2s (cv1_w3)
Cross Validation Attempt 2: Success, 18.6s (cv2_w3)
Cross Validation Attempt 3: Success, 19.1s (cv3_w3)
Cross Validation Attempt 4: Success, 11.7s (cv4_w3)
Tested: 2026-03-15 07:17:37 UTC
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 Sun, 15 Mar 2026 13:45:53 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-03-15 13:15:07).

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, Stable, Exit 1.6 Mbit/s | 816.0 Kbit/s 1.6 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 108.2d | 8d 108.2d | 59.7d 58.3d | 13.6d 100.0% | 98.0% 108.2d | 1.0d 2026-03-14 14:37:05 192 bit/s
dannenberg (DE) Yes Yes Yes N Yes Running, Valid, V2Dir, Fast, Stable, Exit 1.6 Mbit/s | 816.0 Kbit/s 1.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 89.0% | 98% 14.6d | 8d 5.4d | 11.3d 58.3d | 14.3d 89.0% | 98.0% 14.6d | 1.0d 2026-03-14 14:37:05 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% 91.1d | 8d 91.1d | 45.8d 58.3d | 12.0d 100.0% | 98.0% 91.1d | 1.0d 2026-03-14 14:37:05 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% 108.0d | 8d 108.0d | 55.1d 58.3d | 14.5d 100.0% | 98.0% 108.0d | 1.0d 2026-03-14 14:37:05 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 | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 108.6d | 8d 108.6d | 61.4d 58.3d | 14.4d 100.0% | 98.0% 108.6d | 1.0d 2026-03-14 14:37:05 64 bit/s
longclaw (US) Yes Yes Yes Y 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% 105.8d | 8d 105.8d | 62.0d 58.3d | 14.5d 100.0% | 98.0% 105.8d | 1.0d 2026-03-14 14:37:05 1568 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 | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 40.4d | 8d 39.7d | 40.2d 58.3d | 14.3d 100.0% | 98.0% 40.4d | 1.0d 2026-03-14 14:37:05 56 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 | 216.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 9.6d | 8d 108.9d | 347.6d 58.3d | 15.5d 100.0% | 98.0% 9.6d | 9.8d 2026-03-14 14:37:05 192 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% 108.6d | 8d 108.6d | 55.7d 58.3d | 14.5d 100.0% | 98.0% 108.6d | 1.0d 2026-03-14 14:37:05 56 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.