View Relay "Aatrox"
Fingerprint: 3791D12AFD71DFE3BF643BFF3D9A2B739D160E19 |
Operator: exitnode.dk v3
(9 relays)
✓ Validated
|
Family: 9 relays
|
url:https://exitnode.dk... |
AS213693
|
Denmark
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- DNS Health
- Healthy (17.5s, 78th percentile) (via exitdnshealth.1aeo.com)
- BW Verified
- 6/7 BW Auths Measured 152 Mbit/s Median
- Stability
- Not Overloaded | UP 3d 18h 30m ago | UP 98% (1M)
- Reachability
- IPv4: 9/9 | v6: 8/8(Directory Auths)
- BW Weight
- 0.01% of Network | 121 Mbit/s Observed By Relay
- Version
- 0.4.9.17 Recommended
-
HSDir: uptime below 96 hours
: Only 4/9 authorities voted HSDir, though this relay has Fast, Stable and V2Dir
Suggestion: HSDir needs 96 hours of uptime as each authority sees it (MinUptimeHidServDirectoryV2): the time since your relay restarted, or since that authority last failed to reach it if that is shorter. Keep the relay running and reachable. -
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.
- Guard: WFU near threshold: Weighted Fractional Uptime is just above the Guard bar at moria1 (98.3%, need ≥98%) and just under the Guard bar at maatuska (97.9%, need ≥98%). Recent downtime weighs more than older downtime. Avoid restarts while it is this close; a short outage can drop the Guard flag.
Suggestion: Recent downtime weighs more than older downtime. Minimize restarts, use systemd Restart=always, and watch for OOM kills until each authority has more room above its own guard-wfu. - Guard: Time Known near threshold: Time Known is just under the Guard bar at moria1 (7.4 days, need ≥8 days). This is weighted time, so the day count is shorter than calendar uptime, and it falls while the relay is unreachable. Stay reachable so it can move clear of the bar.
Suggestion: Weighted time-known falls while the relay is unreachable and resets if the identity key changes. Authorities cap it at 8 days (AuthDirVoteGuardGuaranteeTimeKnown), about a few weeks of continuous uptime. Stay up with the same key.
Addresses
- OR Address
-
31.56.4.49:443
[2a0f:85c1:b36:16f::1]:443 - Exit Address
- 31.56.4.49
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- 8/8 (1 don't test)
Location
- Country
-
Denmark
- Interactive Map
- View in RouteFluxMap
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) | 64.0 Mbit/s – 240.0 Mbit/s (6 DA measured) 80.0 Mbit/s (3 DA relay-reported) |
≥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 (2/9 DA) | Median: 5.0d (1/9 DA above threshold) Min/Max: 1.0d / 12835.4d (9/9 DA, Voting / Total Eligible) |
≥2.3d - 8.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥12669.7d |
| Uptime | Below (0/9 DA) | 3.8d (R) | ≥5.0d - 5.1d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 64.0 Mbit/s – 240.0 Mbit/s (6 DA measured) 80.0 Mbit/s (3 DA relay-reported) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Meets (6/9 DA) | 6/9 DA assigned Stable | ≥2.3d - 8.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥12669.7d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Below (4/9 DA) | 3.8d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.7d Time Known |
|
| Guard | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 64.0 Mbit/s – 240.0 Mbit/s (6 DA measured) 80.0 Mbit/s (3 DA relay-reported) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Meets (6/9 DA) | 6/9 DA assigned Stable | ≥2.3d - 8.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥12669.7d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Partial (8/9 DA) | Median: 99.5% (8/9 DA above threshold) Min/Max: 97.9% / 99.9% (9/9 DA, Voting / Total Eligible) |
≥98% (≥5/9 DA) | |
| Time Known | Partial (8/9 DA) | Median: 9.8d (8/9 DA above threshold) Min/Max: 6.4d / 10.3d (9/9 DA, Voting / Total Eligible) |
≥8 days; E30CF7B3: ≥5 days 10 hours 41 minutes 56 seconds (≥5/9 DA) | |
| Bandwidth | Meets (9/9 DA) | 64.0 Mbit/s – 240.0 Mbit/s (6 DA measured) 80.0 Mbit/s (3 DA relay-reported) |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-248.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-11-20 08:45:05).
Capacity (Relay Reported)
- Observed Bandwidth
- 121.12 Mbit/s
- Advertised Bandwidth
- 121.12 Mbit/s
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
- 7.7 TB (1 month)
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-20 08:45:05
- Measured By
-
6/7
Bandwidth Authorities
Not measured by: faravahar - Consensus Weight
- 152.0 Mbit/s (median of 6 measurements)
- Measured Min / Max
- 64.0 Mbit/s / 240.0 Mbit/s
- Deviation
- 176.0 Mbit/s [Warning] High variation
History
Uptime Metrics
- Current Status
- UP 3d 18h 30m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 98.7%/0.0%/0.0%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (98.7%/0.0%/0.0%/0.0%)
- Hibernating
- No
Timestamps
- First Seen
- 1w 6d 7h ago (2026-11-07 02:00:00)
- Last Seen
- 1h 45m 32s ago (2026-11-20 08:00:00)
- Last Restarted
- 3d 18h 30m ago (2026-11-16 15:15:20)
- Last Changed Address
- 2026-11-07 02:00:00
Evaluated 2026-11-20 09:45 UTC. /details snapshot 2026-11-20 08:00:00 UTC (cached 37s ago). /bandwidth snapshot 2026-11-20 02: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 file-descriptor exhaustion report in available data
Rate Limits (from /bandwidth)
- Status
- No rate-limit report in available data
- 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
History
Operator Identity
Source: AROI Validation API — 2026-11-19 23:00 UTC
- AROI Domain (?)
- exitnode.dk
- Operator Validation
- Validated (9/9 relays)
- This Relay
- Validated (uri-familyid-ed25519)
- Contact
- url:https://exitnode.dk proof:uri-familyid-ed25519 ciissversion:3
Family Configuration
- Family Support
- Happy Families (9) — Has family-cert in server descriptor (guide) | View Full Family (9)
- Effective Members: 9
07FD983F5E7F5621C88919E9F0687F8C0BFFB039 11FECE9FB4FC80F7854CE1F7D67F7C5706ECCECE 3791D12AFD71DFE3BF643BFF3D9A2B739D160E19 (this relay) 507E20A235296A2167863BADCC088A5E9A07F21E 6BF6599B6A696E3B5ECB8DF0D13AB0A920F58703 A0BEBF27CE8DCD53500B1B576DB41B194B7B87F1 AA271C276A6180D43B1CC978E462D5F33DF60EE7 DF03FD7C4D8C47EFB81A570BA9FE2F8482ADFB25 FBFB46FEF809D5876E8CD838BA547B7486924D13
DNS Health
- Status
- Healthy (avg. 17.5s, 78th percentile)
- Query Domain
ed2d3fdb5499494b98e5605cd9eecf9a.3791d12a.tor.exit.validator.1aeo.com- DNS Result
-
Resolved to
64.65.4.1 - Upstream Resolver
-
Google
(public resolver)
Google 100% (~47 estimated queries) - Cross-Validation
- 4/4 instances succeeded
- First Hop
- NTH157R1 (NL) 4DC139002F7B00E41B3947BDEC44123D5396735C
- Exit Address Used
31.56.4.49- Per-Instance Results
-
Cross Validation Attempt 1: Success, 14.7s (cv1_w1) Cross Validation Attempt 2: Success, 18.4s (cv2_w1) Cross Validation Attempt 3: Success, 16.0s (cv3_w1) Cross Validation Attempt 4: Success, 21.0s (cv4_w1)
IPv4 Exit Policy Summary
reject: 25 119 135-139 445 563 1214 4661-4666 6346-6429 6699 6881-6999
IPv6 Exit Policy Summary
NoneFull 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 31.56.4.49:* reject *:25 reject *:119 reject *:135-139 reject *:445 reject *:563 reject *:1214 reject *:4661-4666 reject *:6346-6429 reject *:6699 reject *:6881-6999 accept *:*
Last fetch was at Fri, 20 Nov 2026 09:45:32 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-20 08:45: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) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| E30CF7B3 | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit | 104.0 Mbit/s (M) | 816.0 Kbit/s | 104.0 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s | 99.9% | 98% | 6.4d | 5d | 4.3d | 3.9d | 3.8d | 5.1d | 2026-11-19 15:15:38 | 104.0 Mbit/s (M) |
| dannenberg (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, Guard, Exit | 64.0 Mbit/s (M) | 816.0 Kbit/s | 64.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s | 99.5% | 98% | 10.3d | 8d | 7.1d | 8.2d | 3.8d | 5.1d | 2026-11-19 15:15:38 | 64.0 Mbit/s (M) |
| dizum (NL) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, V2Dir, Fast, Exit | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.4% | 98% | 9.8d | 8d | 5.0d | 6.8d | 3.8d | 5.1d | 2026-11-19 15:15:38 | 80.0 Mbit/s (R) |
| faravahar (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.5% | 98% | 9.8d | 8d | 5.0d | 7.0d | 3.8d | 5.1d | 2026-11-19 15:15:38 | 80.0 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Exit | 216.0 Mbit/s (M) | 816.0 Kbit/s | 216.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s | 99.5% | 98% | 9.8d | 8d | 5.0d | 8.3d | 3.8d | 5.1d | 2026-11-19 15:15:38 | 216.0 Mbit/s (M) |
| longclaw (US) | Yes | Yes | Yes | — | Y | Yes | N/T | Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit | 240.0 Mbit/s (M) | 816.0 Kbit/s | 240.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s | 99.5% | 98% | 10.3d | 8d | 7.2d | 9.1d | 3.8d | 5.1d | 2026-11-19 15:15:38 | 240.0 Mbit/s (M) |
| maatuska (SE) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, V2Dir, Fast, Exit | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 97.9% | 98% | 9.4d | 8d | 1.0d | 2.3d | 3.8d | 5.1d | 2026-11-19 15:15:38 | 80.0 Mbit/s (R) |
| moria1 (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, Exit | 152.0 Mbit/s (M) | 8.4 Mbit/s | 152.0 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s | 98.3% | 98% | 7.4d | 8d | 12835.4d | 12669.7d | 3.8d | 5.0d | 2026-11-19 15:15:38 | 152.0 Mbit/s (M) |
| tor26 (AT) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit | 208.0 Mbit/s (M) | 816.0 Kbit/s | 208.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s | 99.5% | 98% | 9.6d | 8d | 5.0d | 8.2d | 3.8d | 5.1d | 2026-11-19 15:15:38 | 208.0 Mbit/s (M) |
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
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.
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.

