View Relay "Exit01"

Fingerprint: 1D54C8ECBAE0AE8887BC876B12C7C99D5021775E | Family: 1 relay | gxqExit@example.com | AS132203 | Germany | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Exit (4)
DNS Health
Healthy (13.1s, 15th percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/7 BW Auths Measured 8 bit/s Median
Stability
Overloaded | UP 2d 13h 52m ago
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
2d 13h 2m ago
BW Weight
0.00% of Network | 1 Mbit/s Observed By Relay
Version
0.4.9.14 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: bandwidth below threshold : Observed bandwidth 1 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: WFU below threshold : Weighted Fractional Uptime 95.8% 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.
  • Guard: Time Known below threshold : Time Known 2.3 days is below 8 days requirement (5.7 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 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 95.8% 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.
  • Write Bandwidth Limit Hit : Write rate limit (1 Mbit/s) was hit 284 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 (1 Mbit/s) was hit 313 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=1 Mbit/s, Burst=307 KB. Limits hit: Write=284, Read=313.

Connectivity and Location

Addresses
OR Address
43.131.2.16:9001
Exit Address
43.131.2.16
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS132203
AS Name
Shenzhen Tencent Computer Systems Company Limited (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 4 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 3/9 | Stable: 0/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
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 Meets (9/9 DA) 1.4 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 Below (0/9 DA) Median: 2.5d (0/9 DA above threshold)
Min/Max: 0.8d / 2.5d (9/9 DA, Voting / Total Eligible)		 ≥4.8d - 7.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10748.8d
Uptime Below (0/9 DA) 2.6d (R) ≥6.1d - 6.4d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (3/9 DA) 3/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 (0/9 DA) 0/9 DA assigned Stable ≥4.8d - 7.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10748.8d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Majority: 100.0% (8/9 DA)
Min/Med/Max: 95.8% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 2.5d (0/9 DA above threshold)
Min/Max: 2.2d / 2.5d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Below (3/9 DA) 3/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 (0/9 DA) 0/9 DA assigned Stable ≥4.8d - 7.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10748.8d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Majority: 100.0% (8/9 DA)
Min/Med/Max: 95.8% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 5.5 more days) Median: 2.5d (0/9 DA above threshold)
Min/Max: 2.2d / 2.5d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 1.4 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.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-10-23 16:00:54).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
1.40 Mbit/s
Advertised Bandwidth
1.23 Mbit/s
Rate Limit
1.23 Mbit/s
Burst Limit
2.46 Mbit/s
Total Data
N/A
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-23 16:00:54

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Median Measurement
8 bit/s
Min / Max
8 bit/s / 1224 bit/s
Deviation
1216 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (0th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0000% (0th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 2d 13h 52m 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 13h 2m ago (2026-10-21 03:00:00)
Last Seen
2h 2m 11s ago (2026-10-23 14:00:00)
Last Restarted
2d 13h 52m ago (2026-10-21 02:09:47)
Last Changed Address
2026-10-21 03:00:00
[Warning] OVERLOADED — Rate limits hit W:284 R:313 (limit: 1 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
1.23 Mbit/s
Burst Limit
307 KB
Write Limit Hit
284 times
Read Limit Hit
313 times
Last Reported
1 days ago
Recommendations
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-10-23 08:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
gxqExit@example.com
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
1D54C8ECBAE0AE8887BC876B12C7C99D5021775E (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

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

Exit Health & Policy

DNS Health
Status
Healthy (avg. 13.1s, 15th percentile)
Query Domain
8e7259c7f73848e8a6c1210d7c85d6b5.1d54c8ec.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
3/3 instances succeeded
First Hop
Quintex152 (US) 0008D9640FE4947F73E355F67E20C2D290BBC72C
Exit Address Used
43.131.2.16
Per-Instance Results
Cross Validation Attempt 1: Success, 11.7s (cv1_w1)
Cross Validation Attempt 2: Success, 14.5s (cv2_w1)
Cross Validation Attempt 3: Success, 13.0s (cv3_w1)
Tested: 2026-10-22 19:05:25 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  20-23
  43
  53
  79-81
  88
  110
  143
  194
  220
  389
  443
  464-465
  531
  543-544
  554
  563
  587
  636
  706
  749
  873
  902-904
  981
  989-995
  1194
  1220
  1293
  1500
  1533
  1677
  1723
  1755
  1863
  2082-2083
  2086-2087
  2095-2096
  2102-2104
  3128
  3389
  3690
  4321
  4643
  5050
  5190
  5222-5223
  5228
  5900
  6660-6669
  6679
  6697
  8000
  8008
  8074
  8080
  8082
  8087-8088
  8232-8233
  8332-8333
  8443
  8888
  9418
  9999-10000
  11371
  18080-18081
  18089
  19294
  19638
  50002
  64738
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 43.131.2.16:*
accept *:20-23
accept *:43
accept *:53
accept *:79-81
accept *:88
accept *:110
accept *:143
accept *:194
accept *:220
accept *:389
accept *:443
accept *:464
accept *:465
accept *:531
accept *:543-544
accept *:554
accept *:563
accept *:587
accept *:636
accept *:706
accept *:749
accept *:873
accept *:902-904
accept *:981
accept *:989-995
accept *:1194
accept *:1220
accept *:1293
accept *:1500
accept *:1533
accept *:1677
accept *:1723
accept *:1755
accept *:1863
accept *:2082-2083
accept *:2086-2087
accept *:2095-2096
accept *:2102-2104
accept *:3128
accept *:3389
accept *:3690
accept *:4321
accept *:4643
accept *:5050
accept *:5190
accept *:5222-5223
accept *:5228
accept *:5900
accept *:6660-6669
accept *:6679
accept *:6697
accept *:8000
accept *:8008
accept *:8074
accept *:8080
accept *:8082
accept *:8087-8088
accept *:8232-8233
accept *:8332-8333
accept *:8443
accept *:8888
accept *:9418
accept *:9999
accept *:10000
accept *:11371
accept *:18080-18081
accept *:18089
accept *:19294
accept *:19638
accept *:50002
accept *:64738
reject *:*

Last fetch was at Fri, 23 Oct 2026 16:01:52 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-10-23 16:00:54).

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, Exit 1.4 Mbit/s | 816.0 Kbit/s 1.4 Mbit/s | 192.0 Mbit/s OR 16.0 Mbit/s 95.8% | 98% 2.3d | 8d 0.8d | 4.8d 2.6d | 6.4d 95.8% | 98.0% 2.3d | 1.0d 2026-10-23 08:15:17 8 bit/s
dannenberg (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 1.4 Mbit/s | 816.0 Kbit/s 1.4 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.5d | 8d 2.5d | 5.8d 2.6d | 6.5d 100.0% | 98.0% 2.5d | 1.0d 2026-10-23 08:15:17 8 bit/s
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 1.4 Mbit/s | 816.0 Kbit/s 1.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.5d | 8d 2.5d | 7.6d 2.6d | 6.4d 100.0% | 98.0% 2.5d | 1.0d 2026-10-23 08:15:17 1224 bit/s
faravahar (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 1.4 Mbit/s | 816.0 Kbit/s 1.4 Mbit/s | 328.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.5d | 8d 2.5d | 8.0d 2.6d | 6.9d 100.0% | 98.0% 2.5d | 1.0d 2026-10-23 08:15:17 1224 bit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 1.4 Mbit/s | 816.0 Kbit/s 1.4 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.5d | 8d 2.5d | 7.7d 2.6d | 6.5d 100.0% | 98.0% 2.5d | 1.0d 2026-10-23 08:15:17 8 bit/s
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 1.4 Mbit/s | 816.0 Kbit/s 1.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.5d | 8d 2.5d | 7.9d 2.6d | 6.4d 100.0% | 98.0% 2.5d | 1.0d 2026-10-23 08:15:17 1224 bit/s
maatuska (SE) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 1.4 Mbit/s | 816.0 Kbit/s 1.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.5d | 8d 2.5d | 7.7d 2.6d | 6.4d 100.0% | 98.0% 2.5d | 1.0d 2026-10-23 08:15:17 1224 bit/s
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 1.4 Mbit/s | 8.4 Mbit/s 1.4 Mbit/s | 200.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.5d | 10748.8d 2.6d | 6.1d 100.0% | 98.0% 2.2d | 9.8d 2026-10-23 08:15:17 8 bit/s
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 1.4 Mbit/s | 816.0 Kbit/s 1.4 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.5d | 8d 2.5d | 7.9d 2.6d | 6.7d 100.0% | 98.0% 2.5d | 1.0d 2026-10-23 08:15:17 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.