View Relay "as214958tor8"

Fingerprint: 053ED0352F49F5D974DE17EA980CFEACAD869982 | Family: 7 relays | tor@as214958.net | AS8283 | Netherlands | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast, Stable, HSDir, Guard (7)
BW Verified
5/7 BW Auths Measured 69 Mbit/s Median
Stability
Not Overloaded | UP 4d 1h 40m ago | UP 100% (1M)
Reachability
IPv4: 9/9 | v6: 8/8(Directory Auths)
First Seen
1y 3d 19h ago
BW Weight
0.00% of Network | 64 Mbit/s Observed By Relay
Version
0.4.9.15 Recommended
No issues detected. Relay appears to be operating normally.

Connectivity and Location

Addresses
OR Address
tor1-8.ams1.as214958.net
94.142.241.153:3306
[2a0e:8f02:f017::16]:3306
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Netherlands Netherlands
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS8283
AS Name
Netwerkvereniging Coloclue (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.51% consensus weight, 4 operators)

Flags and Eligibility

Current Flags (7): Running, Valid, V2Dir, Fast, Stable, HSDir, Guard
Eligible Flags (7): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 9/9 | HSDir: 9/9 | Guard: 9/9 | Exit: 0/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) 52.8 Mbit/s – 71.2 Mbit/s (5 DA measured)
58.7 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 (8/9 DA) Median: 21.9d (8/9 DA above threshold)
Min/Max: 5.0d / 1131.1d (9/9 DA, Voting / Total Eligible)		 ≥2.3d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.9d
Uptime Below (0/9 DA) 4.1d (R) ≥5.2d - 5.3d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
52.8 Mbit/s – 71.2 Mbit/s (5 DA measured)
58.7 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.3d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.9d
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) 4.1d (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
52.8 Mbit/s – 71.2 Mbit/s (5 DA measured)
58.7 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.3d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.9d
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: 98.7% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98%; dizum: ≥97.774% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 22.9d (9/9 DA above threshold)
Min/Max: 9.8d / 32.6d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 52.8 Mbit/s – 71.2 Mbit/s (5 DA measured)
58.7 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 Below (0/9 DA) Port 80: No | Port 443: No (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 11:15:19).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
64.00 Mbit/s
Advertised Bandwidth
58.72 Mbit/s
Rate Limit
58.72 Mbit/s
Burst Limit
58.72 Mbit/s
Total Data
331 TB (5 years)
1mo: 26 TB | 6mo: 158 TB | 1y: 331 TB | 5y: 331 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-04 11:15:19

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight
69.6 Mbit/s (median of 5 measurements)
Measured Min / Max
52.8 Mbit/s / 71.2 Mbit/s
Network Participation: Consensus Weight: 0.0041% of network (46th pctl) | Guard: 0.0086% (35th pctl) | Middle: 0.0032% (44th pctl) | Exit: N/A
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 4d 1h 40m ago
Overall Uptime (1M/6M/1Y/5Y)
100.0%/99.2%/99.2%/99.2%
Flag Uptime (1M/6M/1Y/5Y)
99.9%/93.7%/94.7%/93.6%
Hibernating
No
Timestamps
First Seen
1y 3d 19h ago (2025-10-31 17:00:00)
Last Seen
1h 15m 40s ago (2026-11-04 11:00:00)
Last Restarted
4d 1h 40m ago (2026-10-31 10:34:52)
Last Changed Address
2026-05-10 00:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-04 12:15 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 25s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 4h 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
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 03:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
tor@as214958.net
Family Configuration
Family Support
Both — Happy Families (7 / 100%) and MyFamily (0 / 0%) | View Full Family (7)
MyFamily (legacy declarations)
Effective Members: 0
none
Alleged Members: 3
(they don't list you back) 
2FDB1719E6A5E6110F93CE3AC5E841F9B3A2B726
BDC63B4DFC74F55882F1387F65259D6468215D2F (not in the network)
DD068520C3C34EA4223DBD82A111E5AADC419EB7
Indirect Members: 2
(they list you, you don't list them) 
2FDB1719E6A5E6110F93CE3AC5E841F9B3A2B726
DD068520C3C34EA4223DBD82A111E5AADC419EB7

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
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
reject: 
  1-65535
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Wed, 04 Nov 2026 12:15:39 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-11-04 11:15:19).

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 No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 52.8 Mbit/s (M) | 816.0 Kbit/s 52.8 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 99.8% | 98% 18.7d | 8d 10.4d | 8.4d 4.1d | 5.2d 2026-11-04 07:35:00 52.8 Mbit/s (M)
dannenberg (DE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 71.2 Mbit/s (M) | 816.0 Kbit/s 71.2 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 32.6d | 8d 21.9d | 9.3d 4.1d | 5.3d 2026-11-04 07:35:00 71.2 Mbit/s (M)
dizum (NL) Yes Yes No — N Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 58.7 Mbit/s (R) | 816.0 Kbit/s 58.7 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 98.7% | 98% 20.1d | 8d 12.8d | 6.7d 4.1d | 5.3d 2026-11-04 07:35:00 58.7 Mbit/s (R)
faravahar (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 58.7 Mbit/s (R) | 816.0 Kbit/s 58.7 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.9% | 98% 22.9d | 8d 13.7d | 6.5d 4.1d | 5.3d 2026-11-04 07:35:00 58.7 Mbit/s (R)
gabelmoo (DE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 64.8 Mbit/s (M) | 816.0 Kbit/s 64.8 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 32.6d | 8d 30.8d | 10.7d 4.1d | 5.3d 2026-11-04 07:35:00 64.8 Mbit/s (M)
longclaw (US) Yes Yes No — Y Yes N/T Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 58.7 Mbit/s (R) | 816.0 Kbit/s 58.7 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 32.6d | 8d 30.9d | 10.9d 4.1d | 5.3d 2026-11-04 07:35:00 58.7 Mbit/s (R)
maatuska (SE) Yes Yes No — N Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 58.7 Mbit/s (R) | 816.0 Kbit/s 58.7 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.5% | 98% 21.4d | 8d 5.0d | 2.3d 4.1d | 5.3d 2026-11-04 07:35:00 58.7 Mbit/s (R)
moria1 (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 70.4 Mbit/s (M) | 8.4 Mbit/s 70.4 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 9.8d | 8d 1131.1d | 7607.9d 4.1d | 5.3d 2026-11-04 07:35:00 70.4 Mbit/s (M)
tor26 (AT) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 69.6 Mbit/s (M) | 816.0 Kbit/s 69.6 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 32.6d | 8d 30.8d | 10.6d 4.1d | 5.3d 2026-11-04 07:35:00 69.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.