View Relay "Quetzalcoatl"

Fingerprint: EB982941D012590035F013BDA550CBD415DD9A15 | Operator: quetzalcoatl-relays.org v2 (3 relays) ⚠ Misconfigured | Family: 2 relays | email:Quetzalcoatl_relays[]proton.me... | AS197540 | Germany | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast, Exit (5)
DNS Health
Healthy (6.8s, 8th percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/7 BW Auths Measured 79 Kbit/s Median
Stability
Not Overloaded | UP 1d 13m 21s ago
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen
3d 21h 6m ago
BW Weight
0.01% of Network | 79 Mbit/s Observed By Relay
Version
0.4.9.14 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 90.2% 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 3.5 days is below 8 days requirement (4.5 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 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 90.2% 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
5.45.102.93:9100
[2a03:4000:6:614::1]:9100
Exit Address
5.45.102.93
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS197540
AS Name
netcup GmbH (BGP.tools)
AS Rarity
Emerging (score: 1/5, 3.49% consensus weight, 174 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 7/9 | Stable: 1/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 Meets (9/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 79.0 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: 1.8d (1/9 DA above threshold)
Min/Max: 1.8d / 8788.6d (9/9 DA, Voting / Total Eligible)		 ≥6.1d - 9.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10198.2d
Uptime Below (0/9 DA) 1.0d (R) ≥5.7d - 5.7d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (7/9 DA) 7/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 (1/9 DA) 1/9 DA assigned Stable ≥6.1d - 9.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10198.2d
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: 90.1% (0/9 DA above threshold)
Min/Max: 89.3% / 90.5% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 3.5d (0/9 DA above threshold)
Min/Max: 3.2d / 3.5d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.7d
Guard Prereq: Fast Meets (7/9 DA) 7/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 (1/9 DA) 1/9 DA assigned Stable ≥6.1d - 9.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10198.2d
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: 90.1% (0/9 DA above threshold)
Min/Max: 89.3% / 90.5% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 4.5 more days) Median: 3.5d (0/9 DA above threshold)
Min/Max: 3.2d / 3.5d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 79.0 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.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-17 23:00:36).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
79.00 Mbit/s
Advertised Bandwidth
79.00 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
59 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-17 23:00:36

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

Uptime and Stability

Uptime Metrics
Current Status
UP 1d 13m 21s 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
3d 21h 6m ago (2026-10-14 03:00:00)
Last Seen
2h 6m 14s ago (2026-10-17 22:00:00)
Last Restarted
1d 13m 21s ago (2026-10-16 23:52:53)
Last Changed Address
2026-10-14 03:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-10-17 16:00 UTC

AROI Domain (?)
quetzalcoatl-relays.org
Operator Validation
Unvalidated
This Relay
Unvalidated
Error: URI-RSA: HTTP error connection timed out after 5s for URL: https://quetzalcoatl-relays.org/.well-known/tor-relay/rsa-fingerprint.txt
Contact
email:Quetzalcoatl_relays[]proton.me url:https://quetzalcoatl-relays.org proof:uri-rsa hoster:rdp.sh donationurl:https://quetzalcoatl-relays.org/#support-us btc:bc1qc5f3fvr5ftnj70gaj2q68dhg0mne0s85c7ql43 eth:0x53Ad3Ce5004A6710ee425f365F6b469CDBDB5f06 xmr:45TefH4UZFDZAkxLM6ktBhHfZ9r8cFG8T5F7fiCziV1fS21KKsbkBQmZNk5VSbPD991MAXLsH2f9nSMpsiHsDoZA6PYgHUn ciissversion:2
Family Configuration
Family Support
MyFamily Only (2) — Legacy only. Consider migrating to Happy Families. | View Full Family (2)
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Members: 2 
6B4E3C90C5A13F1BBC6A1B3DC3251B7E9527F60F
EB982941D012590035F013BDA550CBD415DD9A15 (this relay)
Alleged Member: 1
(they don't list you back) 
48A0B477399DAD29DD16A847AA8AEC53E87EECC7
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. 6.8s, 8th percentile)
Query Domain
7265c7594b22417097d05d8ae23850dd.eb982941.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
4/4 instances succeeded
First Hop
Shroud (HU) 2016F74A47A0A68D4D5B0329FCE1A1A6B0925D48
Exit Address Used
5.45.102.93
Per-Instance Results
Cross Validation Attempt 1: Success, 5.8s (cv1_w4)
Cross Validation Attempt 2: Success, 7.6s (cv2_w4)
Cross Validation Attempt 3: Success, 7.2s (cv3_w4)
Cross Validation Attempt 4: Success, 6.8s (cv4_w4)
Tested: 2026-10-17 19:21:54 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  20-21
  43
  53
  79-81
  194
  220
  389
  443
  531
  543-544
  554
  563
  636
  706
  853
  873
  902-904
  981
  989-995
  1194
  1220
  1293
  1500
  1533
  1677
  1723
  1755
  1863
  2082-2083
  2086-2087
  2095-2096
  2102-2104
  3128
  3690
  4321
  4643
  5050
  5190
  5222-5223
  5228
  5900
  6679
  8000
  8008
  8074
  8080
  8082
  8087-8088
  8332-8333
  8443
  8888
  9418
  9999-10000
  11371
  19294
  19638
  50002
  64738
IPv6 Exit Policy Summary
accept: 
  20-21
  43
  53
  79-81
  194
  220
  389
  443
  531
  543-544
  554
  563
  636
  706
  853
  873
  902-904
  981
  989-995
  1194
  1220
  1293
  1500
  1533
  1677
  1723
  1755
  1863
  2082-2083
  2086-2087
  2095-2096
  2102-2104
  3128
  3690
  4321
  4643
  5050
  5190
  5222-5223
  5228
  5900
  6679
  8000
  8008
  8074
  8080
  8082
  8087-8088
  8332-8333
  8443
  8888
  9418
  9999-10000
  11371
  19294
  19638
  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 5.45.102.93:*
accept *:20-21
accept *:43
accept *:53
accept *:79-81
accept *:194
accept *:220
accept *:389
accept *:443
accept *:531
accept *:543-544
accept *:554
accept *:563
accept *:636
accept *:706
accept *:853
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
accept *:2083
accept *:2086-2087
accept *:2095-2096
accept *:2102-2104
accept *:3128
accept *:3690
accept *:4321
accept *:4643
accept *:5050
accept *:5190
accept *:5222-5223
accept *:5228
accept *:5900
accept *:6679
accept *:8000
accept *:8008
accept *:8074
accept *:8080
accept *:8082
accept *:8087-8088
accept *:8332-8333
accept *:8443
accept *:8888
accept *:9418
accept *:9999
accept *:10000
accept *:11371
accept *:19294
accept *:19638
accept *:50002
accept *:64738
reject *:*

Last fetch was at Sun, 18 Oct 2026 00:06:03 GMT.

Consensus Evaluation

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

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 Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 79.0 Mbit/s | 816.0 Kbit/s 79.0 Mbit/s | 184.0 Mbit/s OR 16.0 Mbit/s 90.2% | 98% 3.5d | 8d 1.8d | 9.0d 1.0d | 5.7d 90.2% | 98.0% 3.5d | 1.0d 2026-10-17 17:53:00 76.8 Kbit/s
dannenberg (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 79.0 Mbit/s | 816.0 Kbit/s 79.0 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 90.5% | 98% 3.5d | 8d 1.8d | 6.1d 1.0d | 5.8d 90.5% | 98.0% 3.5d | 1.0d 2026-10-17 17:53:00 176.0 Kbit/s
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 79.0 Mbit/s | 816.0 Kbit/s 79.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 89.7% | 98% 3.5d | 8d 1.8d | 9.0d 1.0d | 5.7d 89.7% | 98.0% 3.5d | 1.0d 2026-10-17 17:53:00 79.0 Kbit/s
faravahar (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 79.0 Mbit/s | 816.0 Kbit/s 79.0 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 90.4% | 98% 3.5d | 8d 1.8d | 9.5d 1.0d | 6.3d 90.4% | 98.0% 3.5d | 1.0d 2026-10-17 17:53:00 79.0 Kbit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 79.0 Mbit/s | 816.0 Kbit/s 79.0 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 89.7% | 98% 3.5d | 8d 1.8d | 9.0d 1.0d | 5.7d 89.7% | 98.0% 3.5d | 1.0d 2026-10-17 17:53:00 264.0 Kbit/s
longclaw (US) Yes Yes Yes — Y Yes — Running, Valid, V2Dir, Fast, Exit 79.0 Mbit/s | 816.0 Kbit/s 79.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 90.1% | 98% 3.5d | 8d 1.8d | 9.2d 1.0d | 5.7d 90.1% | 98.0% 3.5d | 1.0d 2026-10-17 17:53:00 79.0 Kbit/s
maatuska (SE) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 79.0 Mbit/s | 816.0 Kbit/s 79.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 90.5% | 98% 3.5d | 8d 1.8d | 8.8d 1.0d | 5.7d 90.5% | 98.0% 3.5d | 1.0d 2026-10-17 17:53:00 79.0 Kbit/s
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, Exit 79.0 Mbit/s | 8.4 Mbit/s 79.0 Mbit/s | 192.0 Mbit/s OR 16.0 Mbit/s 89.3% | 98% 3.2d | 8d 8788.6d | 10198.2d 1.0d | 5.7d 89.3% | 98.0% 3.2d | 9.7d 2026-10-17 17:53:00 88.0 Kbit/s
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 79.0 Mbit/s | 816.0 Kbit/s 79.0 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 90.1% | 98% 3.5d | 8d 1.8d | 9.3d 1.0d | 5.7d 90.1% | 98.0% 3.5d | 1.0d 2026-10-17 17:53:00 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.