View Relay "NoProsperity"

Fingerprint: BF8E1F5E1907A28DD90ABA40DF364EE092984327 | Operator: cxqn.info v2 (9 relays) ✓ Validated | Family: 10 relays | xiaoqic at cs dot princeton dot edu... | AS201670 | India | Linux

Health Status

Consensus
In Consensus (7/7 Directory Auths)
Flags
Running, Valid, V2Dir, Fast (4)
BW Verified
5/6 BW Auths Measured 68 Kbit/s Median
Stability
Not Overloaded | UP 2h 40m 38s ago | UP 73% (1M)
Reachability
IPv4: 7/7 | v6: 7/7 (Directory Auths)
First Seen
1y 8mo 1w ago
BW Weight
0.01% of Network | 50 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: WFU below threshold : Weighted Fractional Uptime 78.3% 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 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 78.3% 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.
  • 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
93.185.165.199:443
[2a0c:b641:3a1:1004::3eb]:443
Reachability (Directory Authorities)
IPv4
7/7
IPv6
7/7
Location
Country
India India
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS201670
AS Name
S.C. INFOTECH-GRUP S.R.L. (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 7 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 7/7 | Valid: 7/7 | V2Dir: 7/7 | Fast: 7/7 | Stable: 1/7 | HSDir: 0/7 | Guard: 0/7 | Exit: 0/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
IPv6 Reachability Meets (7/7 DA) 7/7 tested authorities reached relay ≥4/7 tested (majority) (≥4/7 DA)
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) 50.2 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 (1/7 DA) Median: 1.2d (1/7 DA above threshold)
Min/Max: 1.1d / 17796.8d (7/7 DA, Voting / Total Eligible)		 ≥8.7d - 16.3d (varies) (≥4/7 DA)
[Stricter] moria1: ≥8211.8d
Uptime Below (0/7 DA) 0.1d (R) ≥8.1d - 8.1d (varies) (≥4/7 DA)
HSDir Prereq: Fast Meets (7/7 DA) 7/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 (1/7 DA) 1/7 DA assigned Stable ≥8.7d - 16.3d (varies) (≥4/7 DA)
[Stricter] moria1: ≥8211.8d
Prereq: V2Dir Meets (7/7 DA) 7/7 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥4/7 DA)
WFU Below (0/7 DA) Median: 77.8% (0/7 DA above threshold)
Min/Max: 75.3% / 78.3% (7/7 DA, Voting / Total Eligible)		 ≥98.0% (≥4/7 DA)
Time Known Meets (6/7 DA) Median: 11.6d (7/7 DA above threshold)
Min/Max: 9.5d / 11.9d (7/7 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥4/7 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Meets (7/7 DA) 7/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 (1/7 DA) 1/7 DA assigned Stable ≥8.7d - 16.3d (varies) (≥4/7 DA)
[Stricter] moria1: ≥8211.8d
Prereq: V2Dir Meets (7/7 DA) 7/7 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥4/7 DA)
WFU Below (0/7 DA) Median: 77.8% (0/7 DA above threshold)
Min/Max: 75.3% / 78.3% (7/7 DA, Voting / Total Eligible)		 ≥98% (≥4/7 DA)
Time Known Meets (7/7 DA) Median: 11.6d (7/7 DA above threshold)
Min/Max: 9.5d / 11.9d (7/7 DA, Voting / Total Eligible)		 ≥8 days (≥4/7 DA)
Bandwidth Meets (7/7 DA) 50.2 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-280.0 Mbit/s (≥4/7 DA)
Exit Exit Policy Below (0/7 DA) Port 80: No | Port 443: No (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-19 12:00:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
50.16 Mbit/s
Advertised Bandwidth
50.16 Mbit/s
Rate Limit
167.77 Mbit/s
Burst Limit
419.43 Mbit/s
Total Data
153 TB (5 years)
1mo: 3.5 TB | 6mo: 15 TB | 1y: 49 TB | 5y: 153 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-07-19 12:00:07

Measured By
5/6 Bandwidth Authorities
Not measured by: bastet
Median Measurement
68.0 Kbit/s
Min / Max
50.2 Kbit/s / 104.0 Kbit/s
Deviation
53.8 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0051% of network (53th pctl) | Guard: N/A | Middle: 0.0152% (74th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 2h 40m 38s ago
Overall Uptime (1M/6M/1Y/5Y)
73.3%/81.6%/88.8%/93.2%
Flag Uptime (1M/6M/1Y/5Y)
—/—/—/93.4%
Hibernating
No
Timestamps
First Seen
1y 8mo 1w ago (2024-11-08 00:00:00)
Last Seen
2h 2m ago (2026-07-19 10:00:00)
Last Restarted
2h 40m 38s ago (2026-07-19 09:21:22)
Last Changed Address
2026-04-06 23:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-07-19 03:00 UTC

AROI Domain (?)
cxqn.info
Operator Validation
Validated (9/9 relays)
This Relay
Validated (uri-rsa)
Contact
xiaoqic at cs dot princeton dot edu url:cxqn.info proof:uri-rsa ciissversion:2
Family Configuration
Family Support
MyFamily Only (10) — Legacy only. Consider migrating to Happy Families. | View Full Family (10)
Happy Families (family-cert)
Effective 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 Sun, 19 Jul 2026 12:01:52 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-07-19 12:00:07).

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 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 No — Y Yes Yes Running, Valid, V2Dir, Fast 50.2 Mbit/s | 816.0 Kbit/s 50.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 78.3% | 98% 11.9d | 8d 1.2d | 22.9d 0.1d | 8.1d 78.3% | 98.0% 11.9d | 1.0d 2026-07-19 09:21:24 50.2 Kbit/s
dannenberg (DE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast 50.2 Mbit/s | 816.0 Kbit/s 50.2 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 76.6% | 98% 11.6d | 8d 1.2d | 8.7d 0.1d | 8.1d 76.6% | 98.0% 11.6d | 1.0d 2026-07-19 09:21:24 104.0 Kbit/s
dizum (NL) Yes Yes No — N Yes Yes Running, Valid, V2Dir, Fast 50.2 Mbit/s | 816.0 Kbit/s 50.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 77.8% | 98% 11.3d | 8d 1.2d | 14.5d 0.1d | 8.1d 77.8% | 98.0% 11.3d | 1.0d 2026-07-19 09:21:24 50.2 Kbit/s
faravahar (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast 50.2 Mbit/s | 816.0 Kbit/s 50.2 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 76.1% | 98% 11.6d | 8d 1.1d | 15.1d 0.1d | 8.1d 76.1% | 98.0% 11.6d | 1.0d 2026-07-19 09:21:24 79.2 Kbit/s
maatuska (SE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast 50.2 Mbit/s | 816.0 Kbit/s 50.2 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 78.2% | 98% 11.4d | 8d 1.2d | 16.3d 0.1d | 8.1d 78.2% | 98.0% 11.4d | 1.0d 2026-07-19 09:21:24 58.4 Kbit/s
moria1 (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable 50.2 Mbit/s | 8.4 Mbit/s 50.2 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 75.3% | 98% 9.5d | 8d 17796.8d | 8211.8d 0.1d | 8.1d 75.3% | 98.0% 9.5d | 9.8d 2026-07-19 09:21:24 68.0 Kbit/s
tor26 (AT) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast 50.2 Mbit/s | 816.0 Kbit/s 50.2 Mbit/s | 256.0 Mbit/s OR 16.0 Mbit/s 78.0% | 98% 11.8d | 8d 1.2d | 22.0d 0.1d | 8.1d 78.0% | 98.0% 11.8d | 1.0d 2026-07-19 09:21:24 96.0 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.