View Relay "8382957992969166"

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

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit (8)
DNS Health: Healthy (12.7s, 23rd percentile) (via exitdnshealth.1aeo.com)
BW Verified: 5/7 BW Auths Measured 24 Mbit/s Median
Stability: Overloaded | UP 1w 1d 16h ago | UP 97% (1M)

Reachability: IPv4: 9/9 | v6: None configured(Directory Auths)
First Seen: 3mo 5d 18h ago
BW Weight: 0.00% of Network | 39 Mbit/s Observed By Relay
Version: 0.4.9.12 Not Recommended

Issues Detected:

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.
Write Bandwidth Limit Hit : Write rate-limit counter is 253 (configured rate 24.58 Mbit/s). Read and write counters increment at most once per minute per direction. They are not a count of blocked connections, the duration of throttling, or necessarily the number of events in the last 24 hours.
Suggestion: Inspect BandwidthRate and BandwidthBurst (the values reported with this hit), any relay-specific caps such as RelayBandwidthRate and RelayBandwidthBurst, the intended bandwidth budget, and actual uplink headroom. A rate-limit report is not evidence of ISP throttling. After checking that evidence and the capacity you meant to offer, review whether those limits should change. MetricsPort: tor_relay_load_global_rate_limit_reached_total{side="read"} and {side="write"}. Increases indicate additional global token-bucket limit events.
Read Bandwidth Limit Hit : Read rate-limit counter is 3,128 (configured rate 24.58 Mbit/s). Read and write counters increment at most once per minute per direction. They are not a count of blocked connections, the duration of throttling, or necessarily the number of events in the last 24 hours.
Suggestion: Inspect BandwidthRate and BandwidthBurst (the values reported with this hit), any relay-specific caps such as RelayBandwidthRate and RelayBandwidthBurst, the intended bandwidth budget, and actual uplink headroom. A rate-limit report is not evidence of ISP throttling. After checking that evidence and the capacity you meant to offer, review whether those limits should change. MetricsPort: tor_relay_load_global_rate_limit_reached_total{side="read"} and {side="write"}. Increases indicate additional global token-bucket limit events.

Notes:

Guard: WFU near threshold: Weighted Fractional Uptime is just under the Guard bar at dizum (97.6%, need ≥97.756%). 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: bandwidth near threshold: Bandwidth counted for Guard is just above the Guard bar at tor26 (17.6 Mbit/s, need ≥16.8 Mbit/s). The bar is the lower of AuthDirGuardBWGuarantee and that authority's top 25%. A dip in the bandwidth it counts can drop the Guard flag.
Suggestion: The bandwidth that counts is that authority's measurement when it has one, otherwise the relay-reported rate. Keep it above the lower of AuthDirGuardBWGuarantee (2 MB by default) and that authority's top 25%.
Rate Limit Configuration: Configured limits: Rate=24.58 Mbit/s, Burst=1.1 GB. Counters: Write=253, Read=3,128. These values are BandwidthRate and BandwidthBurst from the extra-info descriptor. RelayBandwidthRate and RelayBandwidthBurst are additional torrc caps, not the names of these values. Burst is a quantity of bytes.
Suggestion: Inspect BandwidthRate and BandwidthBurst (the values reported with this hit), any relay-specific caps such as RelayBandwidthRate and RelayBandwidthBurst, the intended bandwidth budget, and actual uplink headroom. A rate-limit report is not evidence of ISP throttling. After checking that evidence and the capacity you meant to offer, review whether those limits should change. MetricsPort: tor_relay_load_global_rate_limit_reached_total{side="read"} and {side="write"}. Increases indicate additional global token-bucket limit events.

Connectivity and Location

Addresses

OR Address: 150.40.127.161:9001
Exit Address: 150.40.127.161

Reachability (Directory Authorities)

IPv4: 9/9
IPv6: None configured

Location

Country: 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, 32 operators)

Flags and Eligibility

Current Flags (8): Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit

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)	17.6 Mbit/s – 29.6 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	Partial (7/9 DA)	Median: 13.3d (5/9 DA above threshold) Min/Max: 3.0d / 6748.0d (9/9 DA, Voting / Total Eligible)	≥2.3d - 9.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥7858.2d
Stable	Uptime	Meets (9/9 DA)	8.7d (R)	≥5.0d - 5.1d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (9/9 DA)	9/9 DA assigned Fast 17.6 Mbit/s – 29.6 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 (9/9 DA)	9/9 DA assigned Stable	≥2.3d - 9.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥7858.2d
	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.7d (R)	≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.9d Time Known
Guard	Prereq: Fast	Meets (9/9 DA)	9/9 DA assigned Fast 17.6 Mbit/s – 29.6 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 (9/9 DA)	9/9 DA assigned Stable	≥2.3d - 9.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥7858.2d
	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.4% (8/9 DA above threshold) Min/Max: 97.6% / 99.6% (9/9 DA, Voting / Total Eligible)	≥98%; dizum: ≥97.756% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 16.6d (9/9 DA above threshold) Min/Max: 9.8d / 19.7d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	17.6 Mbit/s – 29.6 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 08:15:15).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 39.21 Mbit/s
Advertised Bandwidth: 24.58 Mbit/s
Rate Limit: 24.58 Mbit/s
Burst Limit: 8.59 Gbit/s
Total Data: 26 TB (6 months)
1mo: 9.4 TB | 6mo: 26 TB

Measurement (Directory Authority Verified)

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

Measured By: 5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight: 24.8 Mbit/s (median of 5 measurements)
Measured Min / Max: 17.6 Mbit/s / 29.6 Mbit/s

Network Participation: Consensus Weight: 0.0013% of network (23th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0041% (4th pctl)

History

Throughput and write/read, last 6 months

Uptime and Stability

Uptime Metrics

Current Status: UP 1w 1d 16h ago
Overall Uptime (1M/6M/1Y/5Y): 97.7%/94.4%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (97.7%/94.4%/0.0%/0.0%)
Hibernating: No

Timestamps

First Seen: 3mo 5d 18h ago (2026-07-31 15:00:00)
Last Seen: 1h 15m 43s ago (2026-11-04 08:00:00)
Last Restarted: 1w 1d 16h ago (2026-10-26 16:57:18)
Last Changed Address: 2026-07-31 15:00:00

[Warning] OVERLOADED — Rate limits hit W:253 R:3,128 (limit: 24.58 Mbit/s)

Evaluated 2026-11-04 09:15 UTC. /details snapshot 2026-11-04 08:00:00 UTC (cached 11s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 1h 30m ago).

Reported timestamps use hour precision, so the displayed minute is not an exact incident time.

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: Reported
Rate Limit: 24.58 Mbit/s
Burst Limit: 1.1 GB
Write counter: 253
Read counter: 3,128
Reported: 2026-11-03 22:00 UTC (11 hours ago)

Read and write counters increment at most once per minute per direction. They are not a count of blocked connections, the duration of throttling, or necessarily the number of events in the last 24 hours. Rate is BandwidthRate and follows this site’s bits/bytes setting. Burst is BandwidthBurst, already a byte quantity. RelayBandwidthRate and RelayBandwidthBurst are extra torrc caps, not the names of these values. A hit stays eligible for 24 hours.

What to check

Configured bandwidth limits
Inspect BandwidthRate and BandwidthBurst (the values reported with this hit), any relay-specific caps such as RelayBandwidthRate and RelayBandwidthBurst, the intended bandwidth budget, and actual uplink headroom. A rate-limit report is not evidence of ISP throttling. After checking that evidence and the capacity you meant to offer, review whether those limits should change.

MetricsPort: tor_relay_load_global_rate_limit_reached_total{side="read"} and {side="write"} — Increases indicate additional global token-bucket limit events.

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 and Family

Operator Identity

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

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: john_rt291141(at)proton(dot)me

Family Configuration

Family Support: MyFamily Only (13) — Legacy only. Consider migrating to Happy Families. | View Full Family (13)

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Members: 13

01E44F7EE449B38FA95236791E67A39786CDBDB6
1EF5EABE2FD572F4C0AEBAB6993B6DD4A29FC897
2739C3580FE65466FE93721EADA1D47478EE718C
3117B3808524C537EC8C866D6F2A0C2E790051C9
3B4B654492E48F6A2E2C0D8AAD789B1F49CD1D46 (this relay)
50DF6CC50A8E1B7F064EF093F7423E7A754C8F8B
80BFA9FB374B691641D9E76DF961D31DB94DE083
87E1475430F00544872D7D83D191CF7EB6752660
9EB2800D5F985BF24D0547FC9B7EE6F5CB7F0852
C7F7260F15CEA13AC15E897DDFAC623B6E97476F
D8573263B0D746E598B79C3266BC9204BFF900CD
F0414FB9520E5DB41E156C1B7EEF7300BDD41CF3
F6EB1D746A67E28AE775249FFD0CBBBFB94C3E45

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

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

Exit Health & Policy

DNS Health

Status

Healthy (avg. 12.7s, 23rd percentile)

Query Domain

93a4f787e96d475e9e051cce525ee794.3b4b6544.tor.exit.validator.1aeo.com

DNS Result

Resolved to 64.65.4.1

Upstream Resolver

Google (public resolver)
Google 100% (~35 estimated queries)

Cross-Validation

4/4 instances succeeded

First Hop

arbitraryKenzie4 (FI) C3F7F3E1E32A64B22B2F0734E7C7A312F993D102

Exit Address Used

150.40.127.161

Per-Instance Results

Cross Validation Attempt 1:	Success, 13.5s	(cv1_w1)
Cross Validation Attempt 2:	Success, 15.3s	(cv2_w1)
Cross Validation Attempt 3:	Success, 19.4s	(cv3_w1)
Cross Validation Attempt 4:	Success, 2.5s	(cv4_w1)

Tested: 2026-11-03 20:05:50 UTC

Source: exitdnshealth.1aeo.com

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.161:*
accept *:80
accept *:443
accept *:8080
accept *:8443
reject *:*

Last fetch was at Wed, 04 Nov 2026 09:15:43 GMT.

Consensus Evaluation

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

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, HSDir, Guard, Exit	29.6 Mbit/s (M) \| 816.0 Kbit/s	29.6 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	99.3% \| 98%	16.6d \| 8d	8.3d \| 8.4d	8.7d \| 5.2d	2026-11-03 23:02:28	29.6 Mbit/s (M)
dannenberg (DE)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit	20.0 Mbit/s (M) \| 816.0 Kbit/s	20.0 Mbit/s (M) \| 272.0 Mbit/s OR 16.8 Mbit/s	99.6% \| 98%	19.7d \| 8d	13.4d \| 9.2d	8.7d \| 5.2d	2026-11-03 23:02:28	20.0 Mbit/s (M)
dizum (NL)	Yes	Yes	Yes	—	N	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, 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.6% \| 98%	14.4d \| 8d	7.2d \| 6.6d	8.7d \| 5.1d	2026-11-03 23:02:28	24.6 Mbit/s (R)
faravahar (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	99.4% \| 98%	15.0d \| 8d	7.1d \| 6.4d	8.7d \| 5.1d	2026-11-03 23:02:28	24.6 Mbit/s (R)
gabelmoo (DE)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit	24.8 Mbit/s (M) \| 816.0 Kbit/s	24.8 Mbit/s (M) \| 248.0 Mbit/s OR 16.8 Mbit/s	99.6% \| 98%	19.7d \| 8d	13.4d \| 10.6d	8.7d \| 5.1d	2026-11-03 23:02:28	24.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	99.6% \| 98%	19.6d \| 8d	13.3d \| 10.7d	8.7d \| 5.0d	2026-11-03 23:02:28	24.6 Mbit/s (R)
maatuska (SE)	Yes	Yes	Yes	—	N	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%	14.7d \| 8d	3.0d \| 2.3d	8.7d \| 5.1d	2026-11-03 23:02:28	24.6 Mbit/s (R)
moria1 (US)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable, Guard, Exit	29.6 Mbit/s (M) \| 8.4 Mbit/s	29.6 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	99.1% \| 98%	9.8d \| 8d	6748.0d \| 7858.2d	8.7d \| 5.2d	2026-11-03 23:02:28	29.6 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	99.6% \| 98%	19.7d \| 8d	13.4d \| 10.5d	8.7d \| 5.1d	2026-11-03 23:02:28	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.

View Relay "8382957992969166"

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

Addresses

Reachability (Directory Authorities)

Location

Autonomous System

Eligibility Flag Vote Details

Capacity (Relay Reported)

Measurement (Directory Authority Verified)

History

Uptime Metrics

Timestamps

General Overload (from /details)

File Descriptor Exhaustion (from /bandwidth)

Rate Limits (from /bandwidth)

What to check

History

Operator Identity

Family Configuration

Full Exit Policy

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