View Relay "anduinExit01"

Fingerprint: 5D263037FC175596B3A344132B0B755EB8FB1D1C | Family: 1 relay | 1024D/CF154167 Eirik Oeverby <ltning... | AS62248 | Norway | FreeBSD

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit (8)
DNS Health
Healthy (16.6s, 73rd percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/7 BW Auths Measured 43 Mbit/s Median
Stability
Not Overloaded | UP 2mo 2w 1d ago | UP 100% (1M)
Reachability
IPv4: 9/9 | v6: 8/8(Directory Auths)
First Seen
13y 4mo 1w ago
BW Weight
0.00% of Network | 58 Mbit/s Observed By Relay
Version
0.4.9.11 Not Recommended
Issues Detected:
  • 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.
  • Tor version not recommended : Running Tor version 0.4.9.11 which is not on the recommended list.
    Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.

Connectivity and Location

Addresses
OR Address
exit01.tor.anduin.net
185.42.170.203:443
[2a01:6560:0:102::103:10]:443
Exit Address
185.42.170.203
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Norway Norway
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS62248
AS Name
MODIRUM MDPAY OU (BGP.tools)
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Flags and Eligibility

Current Flags (8): Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit
Eligible Flags (8): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 9/9 | HSDir: 9/9 | Guard: 9/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) 40.0 Mbit/s – 68.8 Mbit/s (5 DA measured)
41.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 Partial (7/9 DA) Median: 32.1d (8/9 DA above threshold)
Min/Max: 8.4d / 94.2d (9/9 DA, Voting / Total Eligible)		 ≥2.4d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.5d
Uptime Meets (9/9 DA) 75.6d (R) ≥5.2d - 5.3d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
40.0 Mbit/s – 68.8 Mbit/s (5 DA measured)
41.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 (9/9 DA) 9/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 Meets (9/9 DA) 75.6d (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
40.0 Mbit/s – 68.8 Mbit/s (5 DA measured)
41.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 (9/9 DA) 9/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: 100.0% (9/9 DA above threshold)
Min/Max: 99.5% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98%; dizum: ≥97.84099999999999% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 47.3d (9/9 DA above threshold)
Min/Max: 9.9d / 94.1d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 40.0 Mbit/s – 68.8 Mbit/s (5 DA measured)
41.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
58.26 Mbit/s
Advertised Bandwidth
40.96 Mbit/s
Rate Limit
40.96 Mbit/s
Burst Limit
61.44 Mbit/s
Total Data
596 TB (5 years)
1mo: 19 TB | 6mo: 86 TB | 1y: 138 TB | 5y: 596 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
43.2 Mbit/s (median of 5 measurements)
Measured Min / Max
40.0 Mbit/s / 68.8 Mbit/s
Deviation
28.8 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0026% of network (33th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0086% (10th pctl)
History
Throughput and write/read, last 6 months Throughput and write/read, last year Throughput and write/read, last 5 years Throughput and write/read, last 30 days
1M 6M 1Y 5Y

Uptime and Stability

Uptime Metrics
Current Status
UP 2mo 2w 1d ago
Overall Uptime (1M/6M/1Y/5Y)
100.0%/99.8%/99.9%/99.9%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (100.0%/99.8%/99.9%/99.9%)
Hibernating
No
Timestamps
First Seen
13y 4mo 1w ago (2013-06-27 00:00:00)
Last Seen
2h 45m 39s ago (2026-11-04 11:00:00)
Last Restarted
2mo 2w 1d ago (2026-08-20 23:55:26)
Last Changed Address
2026-04-06 23: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 year Uptime, last 5 years Uptime, last 30 days
1M 6M 1Y 5Y

Operator and Family

Operator Identity

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

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
1024D/CF154167 Eirik Oeverby <ltning dash tor AT anduin dot net>
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
5D263037FC175596B3A344132B0B755EB8FB1D1C (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

Platform
FreeBSD — Tor 0.4.9.11 on FreeBSD
Version
0.4.9.11 — Not Recommended
Version Status
Obsolete — Update urgently. See torproject.org/download

Exit Health & Policy

DNS Health
Status
Healthy (avg. 16.6s, 73rd percentile)
Query Domain
f78f08d900f4405999e3a852090019c8.5d263037.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Upstream Resolver
Cloudflare (public resolver)
Cloudflare 32%, Quad9 25%, Other 22%, Google 21% (~59 estimated queries)
Cross-Validation
4/4 instances succeeded
First Hop
goldnpapi (US) 83485F2080D6754BAACA3127327611F678B29CC1
Exit Address Used
185.42.170.203
Per-Instance Results
Cross Validation Attempt 1: Success, 17.0s (cv1_w2)
Cross Validation Attempt 2: Success, 12.5s (cv2_w2)
Cross Validation Attempt 3: Success, 14.6s (cv3_w2)
Cross Validation Attempt 4: Success, 22.5s (cv4_w2)
Tested: 2026-11-03 20:10:03 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  20-23
  43
  53
  79-81
  110
  143
  443
  531
  554
  563
  636
  706
  989-995
  1193-1195
  1533
  1723
  1755
  1863
  2102-2104
  3690
  4321
  5190
  5222-5223
  5228
  5900
  6660-6669
  6679
  6697
  8000
  8008
  8074
  8080
  8332-8333
  8443
  9418
  11371
  12350
  19294
  23456
  33033
IPv6 Exit Policy Summary
accept: 
  20-23
  43
  53
  79-81
  110
  143
  443
  531
  554
  563
  636
  706
  989-995
  1193-1195
  1533
  1723
  1755
  1863
  2102-2104
  3690
  4321
  5190
  5222-5223
  5228
  5900
  6660-6669
  6679
  6697
  8000
  8008
  8074
  8080
  8332-8333
  8443
  9418
  11371
  12350
  19294
  23456
  33033
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.42.170.203:*
accept *:20-23
accept *:43
accept *:53
accept *:79-81
accept *:110
accept *:143
accept *:443
accept *:531
accept *:554
accept *:563
accept *:636
accept *:706
accept *:989-995
accept *:1193-1195
accept *:1533
accept *:1723
accept *:1755
accept *:1863
accept *:2102-2104
accept *:3690
accept *:4321
accept *:5190
accept *:5222-5223
accept *:5228
accept *:5900
accept *:6660-6669
accept *:6679
accept *:6697
accept *:8000
accept *:8008
accept *:8074
accept *:8080
accept *:8332-8333
accept *:8443
accept *:9418
accept *:11371
accept *:12350
accept *:19294
accept *:23456
accept *:33033
reject *:*

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 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, Fast, Stable, HSDir, Guard, Exit 68.8 Mbit/s (M) | 816.0 Kbit/s 68.8 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 99.9% | 98% 29.7d | 8d 23.5d | 8.4d 75.6d | 5.2d 2026-11-03 21:56:11 68.8 Mbit/s (M)
dannenberg (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 43.2 Mbit/s (M) | 816.0 Kbit/s 43.2 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 48.0d | 8d 33.6d | 9.3d 75.6d | 5.3d 2026-11-03 21:56:11 43.2 Mbit/s (M)
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 41.0 Mbit/s (R) | 816.0 Kbit/s 41.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.5% | 98% 47.3d | 8d 32.1d | 6.7d 75.6d | 5.3d 2026-11-03 21:56:11 41.0 Mbit/s (R)
faravahar (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 41.0 Mbit/s (R) | 816.0 Kbit/s 41.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 29.2d | 8d 17.8d | 6.5d 75.6d | 5.3d 2026-11-03 21:56:11 41.0 Mbit/s (R)
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 40.0 Mbit/s (M) | 816.0 Kbit/s 40.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 94.1d | 8d 94.1d | 10.8d 75.6d | 5.3d 2026-11-03 21:56:11 40.0 Mbit/s (M)
longclaw (US) Yes Yes Yes — Y Yes N/T Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 41.0 Mbit/s (R) | 816.0 Kbit/s 41.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 75.4d | 8d 75.3d | 10.9d 75.6d | 5.3d 2026-11-03 21:56:11 41.0 Mbit/s (R)
maatuska (SE) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 41.0 Mbit/s (R) | 816.0 Kbit/s 41.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.7% | 98% 48.2d | 8d 8.4d | 2.4d 75.6d | 5.3d 2026-11-03 21:56:11 41.0 Mbit/s (R)
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 47.2 Mbit/s (M) | 8.4 Mbit/s 47.2 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 9.9d | 8d 94.2d | 7607.5d 75.6d | 5.3d 2026-11-03 21:56:11 47.2 Mbit/s (M)
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 41.6 Mbit/s (M) | 816.0 Kbit/s 41.6 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 19.6d | 8d 9.6d | 10.6d 75.6d | 5.3d 2026-11-03 21:56:11 41.6 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.