View Relay "yangwenli"

Fingerprint: 2753A4DED2584CBE86E16EAC4C37355BF07D9666 | Family: 1 relay | AS40663 | United States of America | Linux

Consensus
In Consensus (9/9 Directory Auths)
DNS Health
Healthy (18.3s, 69th percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/6 BW Auths Measured 33 Kbit/s Median
Stability
Overloaded | UP 2d 9h 17m ago | UP 100% (1M)
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
BW Weight
0.00% of Network | 36 Mbit/s Observed By Relay
Version
0.4.8.17 Not Recommended
Issues Detected:
  • HSDir: requires V2Dir (tunnelled-dir-server) : HSDir requires the relay to support tunnelled directory requests (V2Dir flag). This relay is missing V2Dir — the descriptor likely does not include tunnelled-dir-server, usually because DirCache 0 is set in torrc.
    Suggestion: Remove DirCache 0 from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includes tunnelled-dir-server. You can check with: grep tunnelled-dir-server /var/lib/tor/cached-descriptors
  • 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.
  • Tor version not recommended : Running Tor version 0.4.8.17 which is not on the recommended list.
    Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.
  • Write Bandwidth Limit Hit : Write rate limit (34 Mbit/s) was hit 210 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 (34 Mbit/s) was hit 55 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=34 Mbit/s, Burst=84 Mbit/s. Limits hit: Write=210, Read=55.

Addresses
OR Address
23.137.248.100:9001
[2602:fc24:12:81a6::1]:9001
Exit Address
23.137.248.100
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
United States of America United States of America
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS40663
AS Name
IncogNet LLC (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.09% consensus weight, 13 operators)

Current Flags (5): Running, Valid, Fast, Stable, Exit
Eligible Flags (6): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 9/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 (8/8 DA) 8/8 tested authorities reached relay ≥5/8 tested (majority) (≥5/8 DA)
Valid Descriptor Meets (9/9 DA) 9/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Below (0/9 DA) No DirPort, no tunnelled-dir-server (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 36.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 Partial (7/9 DA) Median: 112.2d (8/9 DA above threshold)
Min/Max: 6.1d / 141.3d (9/9 DA, Voting / Total Eligible)
≥17.9d - 58.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥293.7d
Uptime Below (0/9 DA) 2.4d (R) ≥3.3d - 3.4d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/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 ≥17.9d - 58.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥293.7d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Majority: 100.0% (8/9 DA)
Min/Med/Max: 99.4% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 112.1d (9/9 DA above threshold)
Min/Max: 9.5d / 141.3d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Meets (9/9 DA) 9/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 ≥17.9d - 58.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥293.7d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Majority: 100.0% (8/9 DA)
Min/Med/Max: 99.4% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 112.1d (9/9 DA above threshold)
Min/Max: 9.5d / 141.3d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 36.7 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-29 12:45:07).

Capacity (Relay Reported)
Observed Bandwidth
36.68 Mbit/s
Advertised Bandwidth
33.55 Mbit/s
Rate Limit
33.55 Mbit/s
Burst Limit
83.89 Mbit/s
Total Data
225 TB (5 years)
1mo: 6.1 TB | 6mo: 38 TB | 1y: 75 TB | 5y: 225 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-29 12:45:07

Measured By
5/6 Bandwidth Authorities
Not measured by: bastet
Median Measurement
33.6 Kbit/s
Min / Max
28.8 Kbit/s / 50.4 Kbit/s
Deviation
21.6 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0026% of network (35th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0079% (18th pctl)

Uptime Metrics
Current Status
UP 2d 9h 17m ago
Overall Uptime (1M/6M/1Y/5Y)
100.0%/99.7%/96.7%/98.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (100.0%/99.7%/96.7%/98.0%)
Hibernating
No
Timestamps
First Seen
2y 10mo 2w ago (2023-05-14 00:00:00)
Last Seen
2h 45m 55s ago (2026-03-29 10:00:00)
Last Restarted
2d 9h 17m ago (2026-03-27 03:28:25)
Last Changed Address
2024-01-29 19:00:00
[Warning] OVERLOADED — Rate limits hit W:210 R:55 (limit: 34 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
33.55 Mbit/s
Burst Limit
83.89 Mbit/s
Write Limit Hit
210 times
Read Limit Hit
55 times
Last Reported
21 hours ago
Recommendations
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic

Operator Identity

Source: AROI Validation API — 2026-03-29 05: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
2753A4DED2584CBE86E16EAC4C37355BF07D9666 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Platform
Linux — Tor 0.4.8.17 on Linux
Version
0.4.8.17Not Recommended
Version Status
Obsolete — Update urgently. See torproject.org/download

DNS Health
Status
Healthy (avg. 18.3s, 69th percentile)
Query Domain
59f6718a9efc4eb2b345c5abfcf1fa2a.2753a4de.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
2/2 instances succeeded
First Hop
FTPhalifaxRWTH (DE) A86B8708BAAC8A1FE66F0FE9270D23A364A1601B
Exit Address Used
23.137.248.100
Per-Instance Results
Cross Validation Attempt 1: Success, 22.0s (cv2_w1)
Cross Validation Attempt 2: Success, 14.5s (cv4_w1)
Tested: 2026-03-24 19:06:23 UTC
IPv4 Exit Policy Summary
accept: 
  20-21
  43
  53
  80-81
  443
  5222-5223
  6667-7000
  8008
  8082
  8332-8333
  8888
  9418
  18080-18081
  50002
  64738
IPv6 Exit Policy Summary
accept: 
  20-21
  43
  53
  80-81
  443
  5222-5223
  6667-7000
  8008
  8082
  8332-8333
  8888
  9418
  18080-18081
  50002
  64738
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 23.137.248.100:*
accept *:20-21
accept *:43
accept *:53
accept *:80-81
accept *:443
accept *:5222-5223
accept *:6667-7000
accept *:8008
accept *:8082
accept *:8332-8333
accept *:8888
accept *:9418
accept *:50002
accept *:64738
accept *:18080-18081
reject *:*

Last fetch was at Sun, 29 Mar 2026 12:45:53 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-03-29 12:45: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 v6 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 Yes Running, Valid, Fast, Stable, Exit 36.7 Mbit/s | 816.0 Kbit/s 36.7 Mbit/s | 200.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 112.1d | 8d 112.1d | 63.5d 2.4d | 3.3d 100.0% | 98.0% 112.1d | 1.0d 2026-03-28 15:28:31 33.6 Kbit/s
dannenberg (DE) Yes Yes Yes N Yes Yes Running, Valid, Fast, Stable, Exit 36.7 Mbit/s | 816.0 Kbit/s 36.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.4% | 98% 20.1d | 8d 6.1d | 17.9d 2.4d | 3.4d 99.4% | 98.0% 20.1d | 1.0d 2026-03-28 15:28:31 33.6 Kbit/s
dizum (NL) Yes Yes Yes N Yes Yes Running, Valid, Fast, Stable, Exit 36.7 Mbit/s | 816.0 Kbit/s 36.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 104.4d | 8d 104.4d | 42.9d 2.4d | 3.4d 100.0% | 98.0% 104.4d | 1.0d 2026-03-28 15:28:31 33.6 Kbit/s
faravahar (US) Yes Yes Yes N Yes Yes Running, Valid, Fast, Stable, Exit 36.7 Mbit/s | 816.0 Kbit/s 36.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 112.0d | 8d 111.9d | 56.6d 2.4d | 3.4d 100.0% | 98.0% 112.0d | 1.0d 2026-03-28 15:28:31 33.6 Kbit/s
gabelmoo (DE) Yes Yes Yes Y Yes Yes Running, Valid, Fast, Stable, Exit 36.7 Mbit/s | 816.0 Kbit/s 36.7 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 112.7d | 8d 112.7d | 62.1d 2.4d | 3.4d 100.0% | 98.0% 112.7d | 1.0d 2026-03-28 15:28:31 30.4 Kbit/s
longclaw (US) Yes Yes Yes Y Yes Running, Valid, Fast, Stable, Exit 36.7 Mbit/s | 816.0 Kbit/s 36.7 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 141.3d | 8d 141.3d | 62.6d 2.4d | 3.4d 100.0% | 98.0% 141.3d | 1.0d 2026-03-28 15:28:31 50.4 Kbit/s
maatuska (SE) Yes Yes Yes Y Yes Yes Running, Valid, Fast, Stable, Exit 36.7 Mbit/s | 816.0 Kbit/s 36.7 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 112.2d | 8d 112.2d | 50.7d 2.4d | 3.4d 100.0% | 98.0% 112.2d | 1.0d 2026-03-28 15:28:31 45.6 Kbit/s
moria1 (US) Yes Yes Yes Y Yes Yes Running, Valid, Fast, Stable, Exit 36.7 Mbit/s | 8.4 Mbit/s 36.7 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 9.5d | 8d 114.8d | 293.7d 2.4d | 4.1d 100.0% | 98.0% 9.5d | 9.9d 2026-03-28 15:28:31 41.6 Kbit/s
tor26 (AT) Yes Yes Yes Y Yes Yes Running, Valid, Fast, Stable, Exit 36.7 Mbit/s | 816.0 Kbit/s 36.7 Mbit/s | 264.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 112.6d | 8d 112.5d | 58.7d 2.4d | 3.8d 100.0% | 98.0% 112.6d | 1.0d 2026-03-28 15:28:31 28.8 Kbit/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.