View Relay "Nasus"

Fingerprint: 11FECE9FB4FC80F7854CE1F7D67F7C5706ECCECE | Operator: exitnode.dk v3 (7 relays) ✓ Validated | Family: 7 relays | url:https://exitnode.dk... | AS214209 | South Africa | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast, Stable, Guard, Exit (7)
DNS Health
Healthy (10.6s, 15th percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/7 BW Auths Measured 704 Mbit/s Median
Stability
Not Overloaded | UP 17h 10m 21s ago | UP 98% (1M)
Reachability
IPv4: 9/9 | v6: None configured(Directory Auths)
First Seen
3mo 1w 5d ago
BW Weight
0.04% of Network | 429 Mbit/s Observed By Relay
Version
0.4.9.15 Recommended
Issues Detected:
  • HSDir: uptime below 96 hours : Only 0/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.
Notes:
  • Guard: WFU near threshold: Weighted Fractional Uptime is just above the Guard bar at dizum (98.2%, need ≥97.84099999999999%) and maatuska (98.2%, 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.

Connectivity and Location

Addresses
OR Address
exitnode.eu
143.20.185.77:443
Exit Address
143.20.185.77
Reachability (Directory Authorities)
IPv4
9/9
IPv6
None configured
Location
Country
South Africa South Africa
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS214209
AS Name
Internet Magnate (Pty) Ltd (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.12% consensus weight, 8 operators)

Flags and Eligibility

Current Flags (7): Running, Valid, V2Dir, Fast, Stable, Guard, Exit
Eligible Flags (7): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 8/9 | HSDir: 0/9 | Guard: 8/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) 320.0 Mbit/s – 800.0 Mbit/s (5 DA measured)
80.0 Mbit/s (4 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: 9.8d (5/9 DA above threshold)
Min/Max: 2.0d / 7581.8d (9/9 DA, Voting / Total Eligible)		 ≥2.4d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.5d
Uptime Below (0/9 DA) 0.7d (R) ≥5.2d - 5.3d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
320.0 Mbit/s – 800.0 Mbit/s (5 DA measured)
80.0 Mbit/s (4 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 (8/9 DA) 8/9 DA assigned Stable ≥2.4d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.5d
Prereq: V2Dir Meets (9/9 DA) 9/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.8d Time Known
Guard Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
320.0 Mbit/s – 800.0 Mbit/s (5 DA measured)
80.0 Mbit/s (4 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 (8/9 DA) 8/9 DA assigned Stable ≥2.4d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.5d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Median: 99.5% (9/9 DA above threshold)
Min/Max: 98.2% / 99.6% (9/9 DA, Voting / Total Eligible)		 ≥98%; dizum: ≥97.84099999999999% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 15.1d (9/9 DA above threshold)
Min/Max: 9.8d / 15.7d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 320.0 Mbit/s – 800.0 Mbit/s (5 DA measured)
80.0 Mbit/s (4 DA relay-reported)		 ≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-272.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-04 12:45:10).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
429.01 Mbit/s
Advertised Bandwidth
429.01 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
173 TB (6 months)
1mo: 112 TB | 6mo: 173 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-04 12:45:10

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight
704.0 Mbit/s (median of 5 measurements)
Measured Min / Max
320.0 Mbit/s / 800.0 Mbit/s
Deviation
480.0 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0445% of network (97th pctl) | Guard: N/A | Middle: N/A | Exit: 0.1448% (98th pctl)
History
Throughput and write/read, last 6 months Throughput and write/read, last 30 days
1M 6M

Uptime and Stability

Uptime Metrics
Current Status
UP 17h 10m 21s ago
Overall Uptime (1M/6M/1Y/5Y)
98.8%/98.2%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (98.8%/98.2%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
3mo 1w 5d ago (2026-07-24 22:00:00)
Last Seen
2h 45m 39s ago (2026-11-04 11:00:00)
Last Restarted
17h 10m 21s ago (2026-11-03 20:35:18)
Last Changed Address
2026-07-24 22:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-04 13:45 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 42s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 6h 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
Uptime, last 6 months Uptime, last 30 days
1M 6M

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-11-04 04:00 UTC

AROI Domain (?)
exitnode.dk
Operator Validation
Validated (7/7 relays)
This Relay
Validated (uri-familyid-ed25519)
Contact
url:https://exitnode.dk proof:uri-familyid-ed25519 ciissversion:3
Family Configuration
Family Support
Happy Families (7) — Has family-cert in server descriptor (guide) | View Full Family (7)
MyFamily (legacy declarations) — none

Software and Version

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

Exit Health & Policy

DNS Health
Status
Healthy (avg. 10.6s, 15th percentile)
Query Domain
ba959c31906b438f800a76666ed8c5e1.11fece9f.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Upstream Resolver
Google (public resolver)
Google 100% (~45 estimated queries)
Cross-Validation
4/4 instances succeeded
First Hop
eo221 (US) ADDDAF17F461AD1FFC27A70288D06E1BFE1F2818
Exit Address Used
143.20.185.77
Per-Instance Results
Cross Validation Attempt 1: Success, 0.3s (cv1_w1)
Cross Validation Attempt 2: Success, 13.2s (cv2_w1)
Cross Validation Attempt 3: Success, 6.3s (cv3_w1)
Cross Validation Attempt 4: Success, 22.6s (cv4_w1)
Tested: 2026-11-03 20:05:18 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 
  135-139
  445
  1214
  4661-4666
  6346-6429
  6699
  6881-6999
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 143.20.185.77:*
reject *:135-139
reject *:445
reject *:1214
reject *:4661-4666
reject *:6346-6429
reject *:6699
reject *:6881-6999
accept *:*

Last fetch was at Wed, 04 Nov 2026 13:45:39 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-11-04 12:45:10).

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 (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 Running, Valid, V2Dir, Fast, Stable, Guard, Exit 320.0 Mbit/s (M) | 816.0 Kbit/s 320.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 99.4% | 98% 15.1d | 8d 7.1d | 8.4d 0.7d | 5.2d 2026-11-03 20:35:20 320.0 Mbit/s (M)
dannenberg (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, Guard, Exit 800.0 Mbit/s (M) | 816.0 Kbit/s 800.0 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 99.6% | 98% 15.7d | 8d 9.9d | 9.3d 0.7d | 5.3d 2026-11-03 20:35:20 800.0 Mbit/s (M)
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, 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 98.2% | 98% 14.9d | 8d 8.7d | 6.7d 0.7d | 5.3d 2026-11-03 20:35:20 80.0 Mbit/s (R)
faravahar (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, 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% 13.7d | 8d 6.2d | 6.5d 0.7d | 5.3d 2026-11-03 20:35:20 80.0 Mbit/s (R)
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, Guard, Exit 800.0 Mbit/s (M) | 816.0 Kbit/s 800.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 99.6% | 98% 15.5d | 8d 9.8d | 10.8d 0.7d | 5.3d 2026-11-03 20:35:20 800.0 Mbit/s (M)
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, 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.6% | 98% 15.5d | 8d 9.8d | 10.9d 0.7d | 5.3d 2026-11-03 20:35:20 80.0 Mbit/s (R)
maatuska (SE) Yes Yes Yes — N 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 98.2% | 98% 12.7d | 8d 2.0d | 2.4d 0.7d | 5.3d 2026-11-03 20:35:20 80.0 Mbit/s (R)
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, Guard, Exit 496.0 Mbit/s (M) | 8.4 Mbit/s 496.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 99.3% | 98% 9.8d | 8d 7581.8d | 7607.5d 0.7d | 5.3d 2026-11-03 20:35:20 496.0 Mbit/s (M)
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, Guard, Exit 704.0 Mbit/s (M) | 816.0 Kbit/s 704.0 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 99.6% | 98% 15.6d | 8d 9.8d | 10.6d 0.7d | 5.3d 2026-11-03 20:35:20 704.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

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.