View Relay "X7G2P9M4LQ"

Family: 1 relay | AS135377 | Viet Nam | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, V2Dir, Valid (3)
BW Verified
5/6 BW Auths Measured 136 bit/s Median
Stability
Not Overloaded | UP 5h 10m 27s ago | UP 5% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
10mo 2w 3d ago
BW Weight
0.00% of Network | 1 Mbit/s Observed By Relay
Version
0.4.8.10 Not Recommended
Issues Detected:
  • Guard: bandwidth below threshold : Observed bandwidth 0.1 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.
  • Guard: Time Known below threshold : Time Known 1.9 days is below 8 days requirement (6.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.
  • 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: 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.
  • 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.
  • 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.10 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.

Connectivity and Location

Addresses
OR Address
152.32.223.224:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Viet Nam Viet Nam
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS135377
AS Name
UCLOUD INFORMATION TECHNOLOGY (HK) LIMITED (BGP.tools)

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: 0/9 | HSDir: 0/9 | Guard: 0/9 (need ≥5/9 for flag)
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Fast Speed Meets (≥100 KB/s) 1.0 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below Median: 1.9d (0/9 DA above threshold)
Min/Max: 1.9d / 1.9d (9/9 DA, Voting / Total Eligible)		 ≥22.2d - 53.9d (varies)
[Stricter] moria1: ≥405.5d
Uptime Below 0.2d (R) ≥15.8d - 16.3d (varies)
HSDir Prereq: Stable Below 0/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: Fast Below 4/9 authorities assigned Fast flag ≥5/9 authorities
WFU Meets Majority: 100.0% (9/9 DA) ≥98.0%
Time Known Below Median: 1.9d (0/9 DA above threshold)
Min/Max: 1.7d / 1.9d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below 4/9 authorities assigned Fast flag ≥5/9 authorities
Prereq: Stable Below 0/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: V2Dir Meets 9/9 authorities assigned V2Dir flag ≥5/9 authorities
WFU Meets Majority: 100.0% (9/9 DA) ≥98% (all authorities)
Time Known Below (need 6.1 more days) Median: 1.9d (0/9 DA above threshold)
Min/Max: 1.7d / 1.9d (9/9 DA, Voting / Total Eligible)		 ≥8 days (all authorities)
Bandwidth Below 1.0 Mbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s

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

Last fetch was at Thu, 29 Jan 2026 07:15:43 GMT.

Nickname
X7G2P9M4LQ
Fingerprint
A117E225821AADEC0D5C401CCC52790E9FFA41B9
AROI (?)
none
Contact
none
IPv4 Exit Policy Summary 
reject: 
  1-65535
IPv6 Exit Policy Summary 
none
Exit Policy 
reject *:*
Effective Family Member: 1 
A117E225821AADEC0D5C401CCC52790E9FFA41B9
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
1.02 Mbit/s | 1.02 Mbit/s| 8.59 Gbit/s| 8.59 Gbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | 0.00% | N/A
OR Address
152.32.223.224:9001
Exit Address
none
Dir Address
none
Country
Viet Nam Viet Nam
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS135377 | UCLOUD INFORMATION TECHNOLOGY (HK) LIMITED (BGP.tools)
Flags: 3
Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
Match Overall Uptime (5.8%/0.0%/31.0%/0.0%)
Uptime (1M/6M/1Y/5Y)
5.8%/0.0%/31.0%/0.0%
Uptime / Downtime
UP 5h 10m 27s ago
Seen (First | Last)
10mo 2w 3d ago (2025-03-18 03:00:00) | 1h 17m 12s ago (2026-01-29 06:00:00)
Last Restarted
5h 11m 54s ago (2026-01-29 02:05:18)
Last Changed Address or Port
2025-03-18 03:00:00
Hibernating
No
Platform (Short | Long)
Linux | Tor 0.4.8.10 on Linux
Version (Running | Recommended | Status)
0.4.8.10 | No | obsolete

Consensus Evaluation

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

  • Consensus Status (need ≥5/9): In Consensus — 9/9 authorities voted.
  • Flag Eligibility (need ≥5/9 for flag): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 4/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9
  • Reachability: IPv4: 9/9
  • Consensus Weight (Dir. Auth.): Median: 136 bit/s | Min: 8 bit/s | Max: 1024 bit/s [Warning] High deviation
  • Identified Issues:
    • Guard: bandwidth below threshold: Observed bandwidth 0.1 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.
    • Guard: Time Known below threshold: Time Known 1.9 days is below 8 days requirement (6.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.
    • 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: 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.
    • 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.
    • 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.10 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.

Summary: Your Relay vs Consensus

Green = meets threshold, Red = below threshold, Yellow = partial.

Metric Dir Auth Measured Dir Auth Threshold Status
In Consensus (Dir. Auth.) 9/9 authorities ≥5/9 (majority) IN CONSENSUS
Running (IPv4 Reachable) 9/9 authorities reached this relay ≥5/9 (majority) RUNNING
Valid 9/9 (Running + Valid Descriptor) ≥5/9 (majority) VALID
Consensus Weight (Dir. Auth.) 136 bit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 100.0% ≥98% (all authorities) MEETS
Guard TK (Dir. Auth., tk) 1.9 days ≥8 days (all authorities) BELOW - need 6.1 more days
Guard BW (Relay Reported) 1.0 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported) 0.2d ≥15.8d - 16.3d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 2 days ≥22.2d - 53.9d (typical)
[Stricter] moria1: ≥405.5d 		BELOW - 0/9
Fast Speed (Relay Reported) 1.0 Mbit/s ≥800.0 Kbit/s (guarantee) OR ≥816.0 Kbit/s (typical)
[Stricter] moria1: ≥8.4 Mbit/s 		MEETS - ≥100 KB/s guarantee
HSDir WFU (Dir. Auth., wfu) 100.0% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 1.9 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d 		BELOW - 0/9

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 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 Y Yes Running, Valid, V2Dir 1.0 Mbit/s | 816.0 Kbit/s 1.0 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.9d | 8d 1.9d | 50.4d 0.2d | 16.7d 100.0% | 98.0% 1.9d | 1.0d 2026-01-29 02:06:21 136 bit/s
dannenberg (DE) Yes Yes N Yes Running, Valid, V2Dir, Fast 1.0 Mbit/s | 816.0 Kbit/s 1.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.9d | 8d 1.9d | 22.2d 0.2d | 16.5d 100.0% | 98.0% 1.9d | 1.0d 2026-01-29 02:06:21 1024 bit/s
dizum (NL) Yes Yes N Yes Running, Valid, V2Dir, Fast 1.0 Mbit/s | 816.0 Kbit/s 1.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.9d | 8d 1.9d | 35.2d 0.2d | 16.3d 100.0% | 98.0% 1.9d | 1.0d 2026-01-29 02:06:21 1024 bit/s
faravahar (US) Yes Yes N Yes Running, Valid, V2Dir, Fast 1.0 Mbit/s | 816.0 Kbit/s 1.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.9d | 8d 1.9d | 47.3d 0.2d | 15.8d 100.0% | 98.0% 1.9d | 1.0d 2026-01-29 02:06:21 1024 bit/s
gabelmoo (DE) Yes Yes Y Yes Running, Valid, V2Dir 1.0 Mbit/s | 816.0 Kbit/s 1.0 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.9d | 8d 1.9d | 53.9d 0.2d | 16.3d 100.0% | 98.0% 1.9d | 1.0d 2026-01-29 02:06:21 8 bit/s
longclaw (US) Yes Yes Y Yes Running, Valid, V2Dir, Fast 1.0 Mbit/s | 816.0 Kbit/s 1.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.9d | 8d 1.9d | 54.6d 0.2d | 16.1d 100.0% | 98.0% 1.9d | 1.0d 2026-01-29 02:06:21 1024 bit/s
maatuska (SE) Yes Yes Y Yes Running, Valid, V2Dir 1.0 Mbit/s | 816.0 Kbit/s 1.0 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.9d | 8d 1.9d | 55.0d 0.2d | 15.9d 100.0% | 98.0% 1.9d | 1.0d 2026-01-29 02:06:21 40 bit/s
moria1 (US) Yes Yes Y Yes Running, Valid, V2Dir 1.0 Mbit/s | 8.4 Mbit/s 1.0 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.7d | 8d 1.9d | 405.5d 0.2d | 16.5d 100.0% | 98.0% 1.7d | 9.9d 2026-01-29 02:06:21 120 bit/s
tor26 (AT) Yes Yes Y Yes Running, Valid, V2Dir 1.0 Mbit/s | 816.0 Kbit/s 1.0 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.9d | 8d 1.9d | 55.6d 0.2d | 17.1d 100.0% | 98.0% 1.9d | 1.0d 2026-01-29 02:06:21 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). This is your relay's self-reported uptime from its 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.