View Relay "6191910807813824"

Fingerprint: D8573263B0D746E598B79C3266BC9204BFF900CD | Family: 13 relays | john_rt291141(at)proton(dot)me | AS211619 | Netherlands | Linux

Consensus
In Consensus (9/9 Directory Auths)
DNS Health
Healthy (12.9s, 25th percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/7 BW Auths Measured 22 Mbit/s Median
Stability
Not Overloaded | UP 1w 1d 20h ago | UP 97% (1M)
Reachability
IPv4: 9/9 | v6: None configured(Directory Auths)
BW Weight
0.00% of Network | 38 Mbit/s Observed By Relay
Version
0.4.9.12 Not Recommended
Issues Detected:
  • 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.
  • Tor version not recommended : Running Tor version 0.4.9.12 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.

Addresses
OR Address
vps36636.maxko-hosting.net
150.40.127.22:9001
Exit Address
150.40.127.22
Reachability (Directory Authorities)
IPv4
9/9
IPv6
None configured
Location
Country
Netherlands Netherlands
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS211619
AS Name
MAXKO d.o.o. (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.47% consensus weight, 33 operators)

Current Flags (6): Running, Valid, V2Dir, Fast, Stable, Exit
Eligible Flags (6): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 5/9 | HSDir: 4/9 | Guard: 4/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) 16.8 Mbit/s – 28.0 Mbit/s (5 DA measured)
24.6 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 (1/9 DA) Median: 5.2d (1/9 DA above threshold)
Min/Max: 2.0d / 14155.1d (9/9 DA, Voting / Total Eligible)
≥2.4d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.5d
Uptime Meets (9/9 DA) 8.9d (R) ≥5.2d - 5.3d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
16.8 Mbit/s – 28.0 Mbit/s (5 DA measured)
24.6 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 (5/9 DA) 5/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 Partial (8/9 DA) 8.9d (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
16.8 Mbit/s – 28.0 Mbit/s (5 DA measured)
24.6 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 (5/9 DA) 5/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 Partial (6/9 DA) Median: 98.5% (6/9 DA above threshold)
Min/Max: 96.8% / 98.6% (9/9 DA, Voting / Total Eligible)
≥98%; dizum: ≥97.84099999999999% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 16.7d (9/9 DA above threshold)
Min/Max: 9.6d / 17.1d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 16.8 Mbit/s – 28.0 Mbit/s (5 DA measured)
24.6 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).

Capacity (Relay Reported)
Observed Bandwidth
38.68 Mbit/s
Advertised Bandwidth
24.58 Mbit/s
Rate Limit
24.58 Mbit/s
Burst Limit
8.59 Gbit/s
Total Data
31 TB (6 months)
1mo: 11 TB | 6mo: 31 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
22.4 Mbit/s (median of 5 measurements)
Measured Min / Max
16.8 Mbit/s / 28.0 Mbit/s
Network Participation: Consensus Weight: 0.0011% of network (21th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0036% (4th pctl)
History
Throughput and write/read, last 6 months Throughput and write/read, last 30 days
1M 6M

Uptime Metrics
Current Status
UP 1w 1d 20h ago
Overall Uptime (1M/6M/1Y/5Y)
97.0%/98.2%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (97.0%/98.2%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
3mo 5d 19h ago (2026-07-31 18:00:00)
Last Seen
2h 45m 39s ago (2026-11-04 11:00:00)
Last Restarted
1w 1d 20h ago (2026-10-26 16:58:48)
Last Changed Address
2026-07-31 18: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

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

DNS Health
Status
Healthy (avg. 12.9s, 25th percentile)
Query Domain
d90a0cf7be8142bfaec5a210554e2860.d8573263.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Upstream Resolver
Not enough data
Google 100% (~12 estimated queries)
Cross-Validation
4/4 instances succeeded
First Hop
DFRI130 (SE) 7860F0AD272C7045A27C67CD215D467D8E679F45
Exit Address Used
150.40.127.22
Per-Instance Results
Cross Validation Attempt 1: Success, 13.6s (cv1_w3)
Cross Validation Attempt 2: Success, 10.4s (cv2_w3)
Cross Validation Attempt 3: Success, 11.9s (cv3_w3)
Cross Validation Attempt 4: Success, 15.7s (cv4_w3)
Tested: 2026-11-03 20:15:39 UTC
IPv4 Exit Policy Summary
accept: 
  80
  443
  8080
  8443
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 150.40.127.22:*
accept *:80
accept *:443
accept *:8080
accept *:8443
reject *:*

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

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

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, Exit 24.8 Mbit/s (M) | 816.0 Kbit/s 24.8 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 98.1% | 98% 15.8d | 8d 4.4d | 8.4d 8.9d | 5.2d 2026-11-04 01:14:06 24.8 Mbit/s (M)
dannenberg (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 22.4 Mbit/s (M) | 816.0 Kbit/s 22.4 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 98.5% | 98% 17.1d | 8d 5.2d | 9.3d 8.9d | 5.3d 2026-11-04 01:14:06 22.4 Mbit/s (M)
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 24.6 Mbit/s (R) | 816.0 Kbit/s 24.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 96.8% | 98% 15.4d | 8d 4.1d | 6.7d 8.9d | 5.3d 2026-11-04 01:14:06 24.6 Mbit/s (R)
faravahar (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 24.6 Mbit/s (R) | 816.0 Kbit/s 24.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 98.5% | 98% 17.1d | 8d 4.4d | 6.5d 8.9d | 5.3d 2026-11-04 01:14:06 24.6 Mbit/s (R)
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 16.8 Mbit/s (M) | 816.0 Kbit/s 16.8 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 98.6% | 98% 16.7d | 8d 5.2d | 10.8d 8.9d | 5.3d 2026-11-04 01:14:06 16.8 Mbit/s (M)
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 24.6 Mbit/s (R) | 816.0 Kbit/s 24.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 98.5% | 98% 17.0d | 8d 5.2d | 10.9d 8.9d | 5.3d 2026-11-04 01:14:06 24.6 Mbit/s (R)
maatuska (SE) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 24.6 Mbit/s (R) | 816.0 Kbit/s 24.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 97.3% | 98% 16.1d | 8d 2.0d | 2.4d 8.9d | 5.3d 2026-11-04 01:14:06 24.6 Mbit/s (R)
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, Exit 28.0 Mbit/s (M) | 8.4 Mbit/s 28.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 97.4% | 98% 9.6d | 8d 14155.1d | 7607.5d 8.9d | 5.3d 2026-11-04 01:14:06 28.0 Mbit/s (M)
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 17.6 Mbit/s (M) | 816.0 Kbit/s 17.6 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 98.6% | 98% 17.1d | 8d 5.2d | 10.6d 8.9d | 5.3d 2026-11-04 01:14:06 17.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.