View Relay "Unnamed"

Fingerprint: 93E85CE4C48F9EACECF5ECD7C3214830CAA68699 | Family: 1 relay | AS206264 | Hong Kong | Linux

Health Status

Consensus
In Consensus (7/7 Directory Auths)
Flags
Running, Valid, V2Dir, Fast, Exit (5)
DNS Health
Healthy (17.4s, 77th percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/6 BW Auths Measured 8 Kbit/s Median
Stability
Not Overloaded | UP 2d 22h 43m ago
Reachability
IPv4: 7/7 (Directory Auths)
First Seen
2d 21h 15m ago
BW Weight
0.00% of Network | 12 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 13 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: Time Known below threshold : Time Known 2.9 days is below 8 days requirement (5.1 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.
  • 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.

Connectivity and Location

Addresses
OR Address
server.rarechems.com
103.109.100.162:443
Exit Address
103.109.100.162
Reachability (Directory Authorities)
IPv4
7/7
Location
Country
Hong Kong Hong Kong
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS206264
AS Name
Amarutu Technology Ltd (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 2 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (5): Running: 7/7 | Valid: 7/7 | V2Dir: 7/7 | Fast: 5/7 | Stable: 0/7 | HSDir: 0/7 | Guard: 0/7 | Exit: 7/7
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (7/7 DA) 7/7 authorities reached relay ≥4/7 DA ORPort reachable
Valid Descriptor Meets (7/7 DA) 7/7 authorities assigned Valid Not blacklisted + valid descriptor (≥4/7 DA)
V2Dir DirPort Available Meets (7/7 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥4/7 DA)
Fast Speed Meets (7/7 DA) 12.9 Mbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (0/7 DA) Median: 2.9d (0/7 DA above threshold)
Min/Max: 2.9d / 2.9d (7/7 DA, Voting / Total Eligible)		 ≥9.3d - 19.5d (varies) (≥4/7 DA)
[Stricter] moria1: ≥7738.8d
Uptime Below (0/7 DA) 2.9d (R) ≥4.0d - 4.0d (varies) (≥4/7 DA)
HSDir Prereq: Fast Meets (5/7 DA) 5/7 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/7 DA) 0/7 DA assigned Stable ≥9.3d - 19.5d (varies) (≥4/7 DA)
[Stricter] moria1: ≥7738.8d
Prereq: V2Dir Meets (7/7 DA) 7/7 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥4/7 DA)
WFU Meets (7/7 DA) Majority: 100.0% (7/7 DA) ≥98.0% (≥4/7 DA)
Time Known Meets (6/7 DA) Median: 2.9d (0/7 DA above threshold)
Min/Max: 2.5d / 2.9d (7/7 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥4/7 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Meets (5/7 DA) 5/7 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/7 DA) 0/7 DA assigned Stable ≥9.3d - 19.5d (varies) (≥4/7 DA)
[Stricter] moria1: ≥7738.8d
Prereq: V2Dir Meets (7/7 DA) 7/7 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥4/7 DA)
WFU Meets (7/7 DA) Majority: 100.0% (7/7 DA) ≥98% (≥4/7 DA)
Time Known Below (0/7 DA) (need 5.1 more days) Median: 2.9d (0/7 DA above threshold)
Min/Max: 2.5d / 2.9d (7/7 DA, Voting / Total Eligible)		 ≥8 days (≥4/7 DA)
Bandwidth Below (0/7 DA) 12.9 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-288.0 Mbit/s (≥4/7 DA)
Exit Exit Policy Meets (7/7 DA) Port 80: Yes | Port 443: Yes (R) Allows ≥1 /8 on ports 80 AND 443 (≥4/7 DA)

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

Bandwidth Metrics

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

Source: CollecTor — fetched 2026-07-14 07:15:04

Measured By
5/6 Bandwidth Authorities
Not measured by: bastet
Median Measurement
8.0 Kbit/s
Min / Max
8 bit/s / 12.9 Kbit/s
Deviation
12.9 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0002% of network (8th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0006% (2th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 2d 22h 43m ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
2d 21h 15m ago (2026-07-11 10:00:00)
Last Seen
1h 15m 44s ago (2026-07-14 06:00:00)
Last Restarted
2d 22h 43m ago (2026-07-11 08:32:01)
Last Changed Address
2026-07-11 10:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-07-14 00: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 
93E85CE4C48F9EACECF5ECD7C3214830CAA68699 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

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

Exit Health & Policy

DNS Health
Status
Healthy (avg. 17.4s, 77th percentile)
Query Domain
a4021a92c3fe4154a107cae4d0eb6567.93e85ce4.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
4/4 instances succeeded
First Hop
Hyper97552 (NL) 4C531D0DD55DD8F8FB60A0C8667BE20422FA9B14
Exit Address Used
103.109.100.162
Per-Instance Results
Cross Validation Attempt 1: Success, 19.1s (cv1_w3)
Cross Validation Attempt 2: Success, 17.2s (cv2_w3)
Cross Validation Attempt 3: Success, 13.9s (cv3_w3)
Cross Validation Attempt 4: Success, 19.3s (cv4_w3)
Tested: 2026-07-13 19:15:12 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 
  23
  25
  110
  143
  445
  465
  587
  1433
  3306
  3389
  5432
  6379
  27017
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 103.109.100.162:*
reject *:23
reject *:25
reject *:110
reject *:143
reject *:445
reject *:465
reject *:587
reject *:1433
reject *:3306
reject *:3389
reject *:5432
reject *:6379
reject *:27017
accept *:*

Last fetch was at Tue, 14 Jul 2026 07:15:43 GMT.

Consensus Evaluation

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

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) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 12.9 Mbit/s | 816.0 Kbit/s 12.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.9d | 8d 2.9d | 29.3d 2.9d | 4.2d 100.0% | 98.0% 2.9d | 1.0d 2026-07-13 16:22:10 12.9 Kbit/s
dannenberg (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 12.9 Mbit/s | 816.0 Kbit/s 12.9 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.9d | 8d 2.9d | 9.3d 2.9d | 4.0d 100.0% | 98.0% 2.9d | 1.0d 2026-07-13 16:22:10 9.6 Kbit/s
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 12.9 Mbit/s | 816.0 Kbit/s 12.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.9d | 8d 2.9d | 18.3d 2.9d | 4.0d 100.0% | 98.0% 2.9d | 1.0d 2026-07-13 16:22:10 12.9 Kbit/s
faravahar (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 12.9 Mbit/s | 816.0 Kbit/s 12.9 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.9d | 8d 2.9d | 16.0d 2.9d | 4.0d 100.0% | 98.0% 2.9d | 1.0d 2026-07-13 16:22:10 3360 bit/s
maatuska (SE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 12.9 Mbit/s | 816.0 Kbit/s 12.9 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.9d | 8d 2.9d | 19.5d 2.9d | 4.0d 100.0% | 98.0% 2.9d | 1.0d 2026-07-13 16:22:10 2560 bit/s
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 12.9 Mbit/s | 8.4 Mbit/s 12.9 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.5d | 8d 2.9d | 7738.8d 2.9d | 4.1d 100.0% | 98.0% 2.5d | 9.9d 2026-07-13 16:22:10 8.0 Kbit/s
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 12.9 Mbit/s | 816.0 Kbit/s 12.9 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.9d | 8d 2.9d | 28.6d 2.9d | 4.0d 100.0% | 98.0% 2.9d | 1.0d 2026-07-13 16:22:10 8 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.