View Relay "Quetzalcoatl"
Fingerprint: 4BEE5C00CC10E85D574814E9747BAE0E22A208EB |
Operator: quetzalcoatl-relays.org v2
(35 relays)
⚠ Misconfigured
|
Family: 8 relays
|
email:Quetzalcoatl_relays[]proton.me... |
AS197540
|
Germany
|
Linux
- Consensus
- In Consensus (6/9 Directory Auths)
- DNS Health
- Not Tested (via exitdnshealth.1aeo.com)
- BW Verified
- 0/7 BW Auths Measured 160 Kbit/s Median
- Stability
- Incomplete | UP 2d 16h 26m ago
- Reachability
- IPv4: 6/9 | v6: 5/5(Directory Auths)
- BW Weight
- 0.00% of Network | 1 Mbit/s Observed By Relay
- Version
- 0.4.9.14 Recommended
Issues Detected:
-
Not getting the Fast flag
: Only 2/9 authorities vote Fast (5 needed). bastet, dannenberg, gabelmoo 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). longclaw and maatuska used the relay-reported 1.6 Mbit/s. bastet, dannenberg, gabelmoo 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 have no time-known history (2663 seconds). dannenberg, gabelmoo, longclaw, maatuska and moria1 have known this relay for 1.9 hours–2.6 days.
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, maatuska 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 0/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:
- Partial IPv4 reachability: 6/9 authorities can reach this relay
Suggestion: Some authorities cannot reach you: dizum, faravahar, tor26. This may be temporary or due to geographic routing issues.
Addresses
- OR Address
-
188.68.41.191:9100
[2a03:4000:17:a15:d4db:fbff:fef4:8b7b]:9100
Reachability (Directory Authorities)
- IPv4
- 6/9
- IPv6
- 5/5 (1 don't test)
Location
- Country
-
Germany
- Interactive Map
- View in RouteFluxMap
Eligible Flags (4):
Running: 6/9 | Valid: 6/9 | V2Dir: 6/9 | Fast: 2/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 6/9
Eligibility Flag Vote Details
| Flag | Metric | Status | Relay Value | Threshold Required |
|---|---|---|---|---|
| Running | IPv4 Reachability | Meets (6/9 DA) | 6/9 authorities reached relay | ≥5/9 DA ORPort reachable |
| IPv6 Reachability | Meets (5/5 DA) | 5/5 tested authorities reached relay | ≥3/5 tested (majority) (≥3/5 DA) | |
| Valid | Descriptor | Meets (6/9 DA) | 6/9 authorities assigned Valid | Not blacklisted + valid descriptor (≥5/9 DA) |
| V2Dir | DirPort Available | Meets (6/9 DA) | Tunnelled: Yes (no DirPort) (R) | Tunnelled directory via ORPort or DirPort (≥5/9 DA) |
| Fast | Speed | Below (2/9 DA) | 1.6 Mbit/s (2 DA relay-reported) 0 bit/s (4 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.0d / 2.6d (6/9 DA, Voting / Total Eligible) |
≥5.3d - 8.1d (varies) (≥5/9 DA) [Stricter] moria1: ≥10120.4d |
| Uptime | Below (0/9 DA) | 2.7d (R) | ≥6.0d - 6.2d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Below (2/9 DA) | 2/9 DA assigned Fast 1.6 Mbit/s (2 DA relay-reported) 0 bit/s (4 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 | ≥5.3d - 8.1d (varies) (≥5/9 DA) [Stricter] moria1: ≥10120.4d |
|
| Prereq: V2Dir | Meets (6/9 DA) | 6/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Below (0/9 DA) | 2.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 (2/9 DA) | 2/9 DA assigned Fast 1.6 Mbit/s (2 DA relay-reported) 0 bit/s (4 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 | ≥5.3d - 8.1d (varies) (≥5/9 DA) [Stricter] moria1: ≥10120.4d |
|
| Prereq: V2Dir | Meets (6/9 DA) | 6/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Partial (6/9 DA) | Majority: 100.0% (6/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.0d / 2.6d (6/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Below (0/9 DA) | 1.6 Mbit/s (2 DA relay-reported) 0 bit/s (4 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 (6/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-26 19:15:05).
Capacity (Relay Reported)
- Observed Bandwidth
- 1.65 Mbit/s
- Advertised Bandwidth
- 1.65 Mbit/s
- 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-26 19:15:05
- Measured By
-
0/7
Bandwidth Authorities
Not measured by: bastet, dannenberg, faravahar, gabelmoo, longclaw, moria1, tor26 - Consensus Weight
- 160.0 Kbit/s (Unmeasured)
- Measured Min / Max
- N/A / N/A
Network Participation:
Consensus Weight:
0.0000% of network
(3th pctl)
|
Guard:
N/A |
Middle:
N/A |
Exit:
0.0000% (1th pctl)
Uptime Metrics
- Current Status
- UP 2d 16h 26m 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 15m 35s ago (2026-10-26 17:00:00)
- Last Seen
- 1h 15m 35s ago (2026-10-26 18:00:00)
- Last Restarted
- 2d 16h 26m ago (2026-10-24 02:49:03)
- Last Changed Address
- 2026-10-26 17:00:00
Overload status:
Incomplete — not every signal could be evaluated.
(No bandwidth record available for this relay)
Evaluated 2026-10-26 19:15 UTC. /details snapshot 2026-10-26 18:00:00 UTC (cached 29s ago). /bandwidth snapshot 2026-10-26 16:00:00 UTC (cached 2h 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 Identity
Source: AROI Validation API — 2026-10-26 11: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
- Both — Happy Families (30 / 94%) and MyFamily (2 / 6%) | View Full Family (8)
Happy Families (family-cert)
- Effective Members: 30
18283F41623F59578113DA0F11AD5A3874602354 1E46CD6F8734C1BEF4BF942B0017F33AC84D8685 2460EE73DCB1CE4AC871BD08BE4EED8C1F7AC996 344E5D32193B1A1308EE344ACF10CA145A2D693C 3F1D7AC18431B4C2BB34D28F19B077C0892B1A2A 4BEE5C00CC10E85D574814E9747BAE0E22A208EB (this relay) 5DD2B83A757AAADE63892807872C25D98CE83CAB 6F9D6592AB9C0C7118D5477164DCA50820F1A659 7BF989AF8175F82E3EDA2D338E32F31509E2491D 7C2A551735455F5EE572784DBA41A5E6C27A52F9 8040B8098830EFDC8E92B8784AF6D75DF27F6CF1 8639DC7964FFF276A84E182CDB978A8F4A9499FB 8F4A890392F02686557C733470E74E40A7435C9C 9254B64D48B306937F9558746E0E9A09BA2CF9D5 9B334101F5E08420EBFEF33986693C70BD32F643 A1645FCBDBB729FA0DA918A2BCE20DA49C9EF29A A579F2004CD4F0BDF43CA86F067EB724E6A807DF B21DA489F515D17E70326EB011177485254BC682 BF773990E2CD3908C908EA0895186AF1543A4A78 C01268A8374E464E0107B4F4C1B8703E5BA06410 C4F5A81670BED70D62945B197D4F0C2456A42D3B D7E04CDF164DEF4554C1C017585E85122308E16C E14B02FBAD3CDD598650B3F6E05711B8FAE4B31D E773026AF2EB80DF34A8A318F9A0B0DAE04B9827 EE2377C0BB60991A5BA69797938AAB1BA929F2E3 EFB3C9A7DD66207DDB8674EDBEB7ECA35CCB403D F1297B319B7139280ED70B2B7FC08DF1EC601AB7 F49A88EFBA90167FB1C1FA529FB451A035CCDC4D F958DC794B681146A730BA5D8B7C0439EF3E95A2 FB064F843066BD8D936E390834BED4AB655AAD76
MyFamily (legacy declarations)
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 188.68.41.191:* 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 Mon, 26 Oct 2026 19:15:34 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-10-26 19:15:05).
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) | 192.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.0d | 8d | 0.0d | 5.3d | 2.7d | 6.1d | 2026-10-26 14:44:15 | 1.6 Mbit/s (R) |
| dannenberg (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Exit | 0 bit/s (U) | 816.0 Kbit/s | 0 bit/s (U) | 296.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 2.6d | 8d | 2.6d | 6.5d | 2.7d | 6.3d | 2026-10-26 14:44:15 | 1.6 Mbit/s (R) |
| dizum (NL) | No | — | — | — | N | No | — | — | — | — | — | — | — | — | — | — |
| faravahar (US) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — |
| gabelmoo (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Exit | 0 bit/s (U) | 816.0 Kbit/s | 0 bit/s (U) | 272.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.3d | 8d | 0.3d | 8.1d | 2.7d | 6.1d | 2026-10-26 14:44:15 | 1.6 Mbit/s (R) |
| longclaw (US) | Yes | Yes | Yes | — | Y | Yes | N/T | Running, Valid, V2Dir, Fast, Exit | 1.6 Mbit/s (R) | 816.0 Kbit/s | 1.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.1d | 8d | 0.1d | 8.3d | 2.7d | 6.3d | 2026-10-26 14:44:15 | 1.6 Mbit/s (R) |
| maatuska (SE) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, V2Dir, Fast, Exit | 1.6 Mbit/s (R) | 816.0 Kbit/s | 1.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.1d | 8d | 0.1d | 8.1d | 2.7d | 6.1d | 2026-10-26 14:44:15 | 1.6 Mbit/s (R) |
| 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% | 2.3d | 8d | 2.6d | 10120.4d | 2.7d | 6.3d | 2026-10-26 14:44:15 | 1.6 Mbit/s (R) |
| tor26 (AT) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — |
N/T = this authority does not test IPv6 • — = not in this vote • 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 (
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (
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.
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.
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.