View Relay "Quetzalcoatl"

Fingerprint: F49A88EFBA90167FB1C1FA529FB451A035CCDC4D | Operator: quetzalcoatl-relays.org v2 (27 relays) ⚠ Misconfigured | Family: 1 relay | email:Quetzalcoatl_relays[]proton.me... | AS197540 | Germany | Linux

Health Status

Consensus
In Consensus (5/9 Directory Auths)
Flags
Running, Valid, V2Dir, Exit (4)
DNS Health
Not Tested (via exitdnshealth.1aeo.com)
BW Verified
2/7 BW Auths Measured
Stability
Incomplete | UP 16h 45m 57s ago
Reachability
IPv4: 5/9 | v6: 4/8 (Directory Auths)
First Seen
2h 45m 9s ago
BW Weight
0 Kbit/s Observed By Relay
Version
0.4.9.14 Recommended
Issues Detected:
  • Not getting the Fast flag : Only 0/9 authorities vote Fast (5 needed). dannenberg and gabelmoo measured this relay at 8.0 Kbit/s, below the Fast threshold (816.0 Kbit/s). longclaw used the relay-reported unknown, below the Fast threshold (816.0 Kbit/s). bastet and moria1 counted this relay as 0 (no measurement, relay-reported bandwidth ignored).
    Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports. A low measurement means the scanners see your relay underperforming compared with other relays that report a similar speed. Clients only build circuits through Fast relays, so a relay near the threshold can gain and lose most of its traffic from one hourly consensus to the next.
  • Guard: requires Fast flag : Guard flag requires having the Fast flag first
    Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports.
  • 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 : 0/9 authorities credit this relay with enough bandwidth for Guard (5 needed): at least 16.8 Mbit/s (AuthDirGuardBWGuarantee) or a place in their top 25% (80.0 Mbit/s – 296.0 Mbit/s). dannenberg and gabelmoo measured this relay at 8.0 Kbit/s. longclaw used the relay-reported unknown. bastet and moria1 counted this relay as 0 (no measurement, relay-reported bandwidth ignored).
    Suggestion: Guard requires a bandwidth of at least AuthDirGuardBWGuarantee (16.8 Mbit/s by default) or one in the top 25% of relays, judged by each authority the same way as for Fast. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx.
  • Guard: Time Known below threshold : 0/9 authorities meet guard-tk (≥8 days; 5 needed). bastet, dannenberg, gabelmoo, longclaw and moria1 have known this relay for 1.9 hours–16.0 hours.
    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 : 0/9 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). bastet, dannenberg, gabelmoo, longclaw and moria1 do not.
    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: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports.
  • 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.
  • Low bandwidth authority measurements : Only 2/7 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
    Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.
Notes:

Connectivity and Location

Addresses
OR Address
185.183.157.214:9100
[2a03:4000:1d:b7a:782f:17ff:fef0:a708]:9100
Reachability (Directory Authorities)
IPv4
5/9
IPv6
4/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.80% consensus weight, 178 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 5/9 | Valid: 5/9 | V2Dir: 5/9 | Fast: 0/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 5/9
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (5/9 DA) 5/9 authorities reached relay ≥5/9 DA ORPort reachable
IPv6 Reachability Partial (4/8 DA) 4/8 tested authorities reached relay ≥5/8 tested (majority) (≥5/8 DA)
Valid Descriptor Meets (5/9 DA) 5/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Meets (5/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Below (0/9 DA) 8.0 Kbit/s (2 DA measured)
0 bit/s (1 DA relay-reported)
0 bit/s (2 DA unmeasured, counted as 0)		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (0/9 DA) Median: 0.2d (0/9 DA above threshold)
Min/Max: 0.1d / 0.7d (5/9 DA, Voting / Total Eligible)		 ≥4.8d - 7.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10869.1d
Uptime Below (0/9 DA) 0.7d (R) ≥6.1d - 6.5d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (0/9 DA) 0/9 DA assigned Fast
8.0 Kbit/s (2 DA measured)
0 bit/s (1 DA relay-reported)
0 bit/s (2 DA unmeasured, counted as 0)		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥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: ≥10869.1d
Prereq: V2Dir Meets (5/9 DA) 5/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Below (0/9 DA) 0.7d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.9d Time Known
Guard Prereq: Fast Below (0/9 DA) 0/9 DA assigned Fast
8.0 Kbit/s (2 DA measured)
0 bit/s (1 DA relay-reported)
0 bit/s (2 DA unmeasured, counted as 0)		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥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: ≥10869.1d
Prereq: V2Dir Meets (5/9 DA) 5/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Partial (5/9 DA) Majority: 100.0% (5/9 DA above threshold) ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) Median: 0.2d (0/9 DA above threshold)
Min/Max: 0.1d / 0.7d (5/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 8.0 Kbit/s (2 DA measured)
0 bit/s (1 DA relay-reported)
0 bit/s (2 DA unmeasured, counted as 0)		 ≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-296.0 Mbit/s) (≥5/9 DA)
Exit Exit Policy Meets (5/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 19:45:05).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
0.00 Kbit/s
Advertised Bandwidth
Unknown
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
N/A
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-23 19:45:05

Measured By
2/7 Bandwidth Authorities
Not measured by: bastet, faravahar, longclaw, moria1, tor26
Consensus Weight
0 bit/s (Unmeasured)
Measured Min / Max
8.0 Kbit/s / 8.0 Kbit/s
Network Participation: Consensus Weight: N/A | Guard: N/A | Middle: N/A | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 16h 45m 57s ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
N/A
Hibernating
No
Timestamps
First Seen
2h 45m 9s ago (2026-10-23 18:00:00)
Last Seen
1h 45m 9s ago (2026-10-23 19:00:00)
Last Restarted
16h 45m 57s ago (2026-10-23 03:59:12)
Last Changed Address
2026-10-23 18:00:00
Overload status: Incomplete — not every signal could be evaluated. (No bandwidth record available for this relay)

Evaluated 2026-10-23 20:45 UTC. /details snapshot 2026-10-23 19:00:00 UTC (cached 10s ago). /bandwidth snapshot 2026-10-23 13:00:00 UTC (cached 6h 30m ago).

General Overload (from /details)
Status
No general overload report in available data
File Descriptor Exhaustion (from /bandwidth)
Status
No bandwidth record available for this relay
Rate Limits (from /bandwidth)
Status
No bandwidth record available for this relay
Rate Limit
—
Burst Limit
—
Write counter
—
Read counter
—
About these reports and MetricsPort

Allium’s eligibility windows are applied to the reported timestamps: 72 hours for general overload and file-descriptor exhaustion, 24 hours for a rate-limit hit. A report at the cutoff is historical. An older report can remain visible after Onionoo or Allium’s cache still has it. The cutoff does not prove the relay recovered at that moment. Allium caches the bandwidth document for 12 hours by default. The snapshot time is when Onionoo published that document. It is not the relay’s event time, and it is not necessarily the extra-info publication time. Cache age is how old Allium’s copy is.

MetricsPort counters are cumulative. Compare samples, and account for process restarts. A nonzero total alone does not show ongoing activity. Gauges describe current values. An unavailable metric is unknown, not zero. Allium does not have this relay’s MetricsPort readings and does not invent them.

The port below is an example for an endpoint you have already configured. MetricsPort must be enabled with restricted access and must not be exposed publicly. Setup stays in the Tor overload troubleshooting guide. 

curl http://127.0.0.1:9035/metrics

Operator and Family

Operator Identity

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

AROI Domain (?)
quetzalcoatl-relays.org
Operator Validation
Unvalidated
This Relay
Unvalidated
Error: Not yet processed by validator (relay may be new)
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
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
F49A88EFBA90167FB1C1FA529FB451A035CCDC4D (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
Not Tested
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 185.183.157.214:*
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 Fri, 23 Oct 2026 20:45:08 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-10-23 19:45:05).

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 (BW|T) Guard BW (BW|Threshold) Guard WFU (M|T) Guard TK (M|T) Stable MTBF (M|T) Stable Uptime (Relay|T) Desc Published Cons Wt (Authority)
bastet (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 200.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 4.8d 0.7d | 6.5d 2026-10-23 17:35:19 —
dannenberg (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 8.0 Kbit/s (M) | 816.0 Kbit/s 8.0 Kbit/s (M) | 296.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.7d | 8d 0.7d | 5.8d 0.7d | 6.6d 2026-10-23 17:35:19 —
dizum (NL) No — — — N No — — — — — — — — — —
faravahar (US) No — — — Y No — — — — — — — — — —
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 8.0 Kbit/s (M) | 816.0 Kbit/s 8.0 Kbit/s (M) | 264.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 7.7d 0.7d | 6.5d 2026-10-23 17:35:19 —
longclaw (US) Yes Yes Yes — Y Yes — Running, Valid, V2Dir, Exit 0 bit/s (R) | 816.0 Kbit/s 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.2d | 8d 0.2d | 7.8d 0.7d | 6.5d 2026-10-23 17:35:19 —
maatuska (SE) No — — — N No — — — — — — — — — —
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s (U) | 8.4 Mbit/s 0 bit/s (U) | 200.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.6d | 8d 0.7d | 10869.1d 0.7d | 6.1d 2026-10-23 17:35:19 —
tor26 (AT) No — — — Y No — — — — — — — — — —

— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known • Bandwidth source: (M) bandwidth-scanner measurement, (R) relay-reported, (U) unmeasured, counted as 0

Bandwidth Values Explained:
Measured (M) = An authority's bandwidth-scanner measurement of your relay (Measured= in its vote). An authority that has one uses it for the Fast and Guard flags, and the consensus weight is the median of these measurements when 3 or more authorities have one.
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (Bandwidth= in every vote). An authority without a measurement uses it for flags, unless it has measurements for enough other relays (ignoring-advertised-bws=1); then your relay counts as 0 (U). It sets the consensus weight only when fewer than 3 authorities measured the relay, capped at 20 KB/s (maxunmeasuredbw) while 3 or more authorities publish measurements.
Not published = The authority has no measurement of your relay in its vote and ignores relay-reported bandwidth, yet it voted Fast or its vote has no measurements at all: it judges your relay by a measurement kept from an earlier bandwidth file (0 if none), which its vote doesn't show.
Why different? A low measurement means the bandwidth scanners see your relay underperforming compared with other relays that report a similar speed. Votes list both values in kilobytes per second. Rules: Assigning flags in a vote, Computing a consensus.
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.