View Relay "DangDongDai"

Fingerprint: 49CC8033C445AA0B05AD6C977BBC8DBDF4C519D1 | Family: 1 relay | dangdongdai@lortemail.dk | AS9009 | Germany | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir (3)
BW Verified
4/6 BW Auths Measured
Stability
Overloaded | UP 21h 33m 35s ago
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
20h 2m 4s ago
BW Weight
0.00% of Network | 0 Kbit/s Observed By Relay
Version
0.4.9.11 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: 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: WFU below threshold : Weighted Fractional Uptime 10.4% 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.
  • 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 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.
  • 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 10.4% 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.
  • StaleDesc flag assigned : Relay descriptor is older than 18 hours
    Suggestion: Your relay is not publishing fresh descriptors. Check: 1) Tor process is running, 2) Network connectivity, 3) Clock is synchronized (NTP). Restart Tor if needed.
  • Write Bandwidth Limit Hit : Write rate limit (25 Mbit/s) was hit 189 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 (25 Mbit/s) was hit 191 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=25 Mbit/s, Burst=6.3 MB. Limits hit: Write=189, Read=191.

Connectivity and Location

Addresses
OR Address
93.177.73.98:16843
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS9009
AS Name
M247 Europe SRL (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.23% consensus weight, 21 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 4/9 | Stable: 2/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 0/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 Below (0/9 DA) 0 bit/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.2d (2/9 DA above threshold)
Min/Max: 1.6d / 2614.1d (9/9 DA, Voting / Total Eligible)		 ≥9.0d - 14.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥6326.9d
Uptime Below (0/9 DA) 0.9d (R) ≥10.4d - 10.7d (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 Below (2/9 DA) 2/9 DA assigned Stable ≥9.0d - 14.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥6326.9d
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: 10.4% (0/9 DA above threshold)
Min/Max: 7.6% / 58.7% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 23.5d (9/9 DA above threshold)
Min/Max: 9.5d / 53.5d (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 Below (2/9 DA) 2/9 DA assigned Stable ≥9.0d - 14.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥6326.9d
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: 10.4% (0/9 DA above threshold)
Min/Max: 7.6% / 58.7% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 23.5d (9/9 DA above threshold)
Min/Max: 9.5d / 53.5d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 0 bit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Below (0/9 DA) Port 80: No | Port 443: No (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-26 16:01:15).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
0.00 Kbit/s
Advertised Bandwidth
Unknown
Rate Limit
25.17 Mbit/s
Burst Limit
50.33 Mbit/s
Total Data
276 TB (5 years)
1mo: 8.9 TB | 6mo: 48 TB | 1y: 80 TB | 5y: 276 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-08-26 16:01:15

Measured By
4/6 Bandwidth Authorities
Not measured by: faravahar, longclaw
Median Measurement
0 bit/s
Min / Max
0 bit/s / 20.0 Kbit/s
Network Participation: Consensus Weight: 0.0009% of network (21th pctl) | Guard: N/A | Middle: 0.0026% (34th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 21h 33m 35s 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
20h 2m 4s ago (2026-08-25 21:00:00)
Last Seen
3h 2m 4s ago (2026-08-26 14:00:00)
Last Restarted
21h 33m 35s ago (2026-08-25 19:28:29)
Last Changed Address
2026-08-25 21:00:00
[Warning] OVERLOADED — Rate limits hit W:189 R:191 (limit: 25 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
25.17 Mbit/s
Burst Limit
6.3 MB
Write Limit Hit
189 times
Read Limit Hit
191 times
Last Reported
24 days ago
Recommendations
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-08-26 09:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
dangdongdai@lortemail.dk
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
49CC8033C445AA0B05AD6C977BBC8DBDF4C519D1 (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
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
reject: 
  1-65535
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Wed, 26 Aug 2026 17:01:53 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-08-26 16:01:15).

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 No — N Yes Running, Valid, V2Dir, StaleDesc 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 10.4% | 98% 23.4d | 8d 2.1d | 12.9d 0.9d | 10.4d 10.4% | 98.0% 23.4d | 1.0d 2026-08-25 19:50:52 [Stale] —
dannenberg (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, StaleDesc 0 bit/s | 816.0 Kbit/s 0 bit/s | 328.0 Mbit/s OR 16.0 Mbit/s 7.6% | 98% 24.4d | 8d 1.6d | 14.9d 0.9d | 12.4d 7.6% | 98.0% 24.4d | 1.0d 2026-08-25 19:50:52 [Stale] 16.0 Kbit/s
dizum (NL) Yes Yes No — N Yes Running, Valid, V2Dir, StaleDesc 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 10.1% | 98% 23.2d | 8d 2.0d | 14.4d 0.9d | 10.7d 10.1% | 98.0% 23.2d | 1.0d 2026-08-25 19:50:52 [Stale] —
faravahar (US) Yes Yes No — Y Yes Running, Valid, V2Dir, StaleDesc 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 10.6% | 98% 23.5d | 8d 2.3d | 14.1d 0.9d | 10.8d 10.6% | 98.0% 23.5d | 1.0d 2026-08-25 19:50:52 [Stale] —
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, StaleDesc 0 bit/s | 816.0 Kbit/s 0 bit/s | 296.0 Mbit/s OR 16.0 Mbit/s 9.0% | 98% 23.0d | 8d 1.8d | 14.9d 0.9d | 10.8d 9.0% | 98.0% 23.0d | 1.0d 2026-08-25 19:50:52 [Stale] 16.0 Kbit/s
longclaw (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Stable, StaleDesc 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 58.7% | 98% 53.5d | 8d 27.6d | 17.8d 0.9d | 10.7d 58.7% | 98.0% 53.5d | 1.0d 2026-08-25 19:50:52 [Stale] —
maatuska (SE) Yes Yes No — N Yes Running, Valid, V2Dir, StaleDesc 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 11.7% | 98% 23.7d | 8d 2.5d | 9.0d 0.9d | 10.6d 11.7% | 98.0% 23.7d | 1.0d 2026-08-25 19:50:52 [Stale] —
moria1 (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable, StaleDesc 0 bit/s | 8.4 Mbit/s 0 bit/s | 208.0 Mbit/s OR 16.0 Mbit/s 16.3% | 98% 9.5d | 8d 2614.1d | 6326.9d 0.9d | 10.5d 16.3% | 98.0% 9.5d | 9.8d 2026-08-25 19:50:52 [Stale] 20.0 Kbit/s
tor26 (AT) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, StaleDesc 0 bit/s | 816.0 Kbit/s 0 bit/s | 288.0 Mbit/s OR 16.0 Mbit/s 10.1% | 98% 24.6d | 8d 2.2d | 15.5d 0.9d | 11.3d 10.1% | 98.0% 24.6d | 1.0d 2026-08-25 19:50:52 [Stale] 16.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.