View Relay "mentoreth3"

Fingerprint: `A5E662AB4A4644E55D6C37D56468B57ADA8D0F6B` | Family: 24 relays | mentor@palokaj.co | AS60404 | Netherlands | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Fast, Stable, Exit (6)
DNS Health: Healthy (14.1s, 37th percentile) (via exitdnshealth.1aeo.com)
BW Verified: 5/7 BW Auths Measured 408 Mbit/s Median
Stability: Not Overloaded | UP 6d 6h 28m ago | UP 97% (1M)

Reachability: IPv4: 9/9 | v6: 8/8(Directory Auths)
First Seen: 2y 10mo 1w ago
BW Weight: 0.03% of Network | 202 Mbit/s Observed By Relay
Version: 0.4.9.15 Recommended

Issues Detected:

Guard: WFU below threshold : 4/9 authorities meet guard-wfu (≥98%; dizum: ≥97.84099999999999%; 5 needed). bastet, dizum, faravahar, maatuska and moria1 measured 61.6%–97.9%.
Suggestion: WFU measures recent uptime (recent downtime weighs more heavily). To improve: 1) Minimize restarts, 2) Use systemd with Restart=always, 3) Monitor for OOM kills, 4) Schedule updates during low-traffic periods.
HSDir: uptime below 96 hours : Only 3/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.

Connectivity and Location

Addresses

OR Address: 5.2.69.82:9004
[2a04:52c0:2000:501::82]:9004
Exit Address: 5.2.69.82

Reachability (Directory Authorities)

IPv4: 9/9
IPv6: 8/8 (1 don't test)

Location

Country: Netherlands
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS60404
AS Name: The Infrastructure Group B.V. (BGP.tools)
AS Rarity: Emerging (score: 1/5, 1.05% consensus weight, 32 operators)

Flags and Eligibility

Current Flags (6): Running, Valid, V2Dir, Fast, Stable, 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
Running	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)	272.0 Mbit/s – 472.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 (1/9 DA)	Median: 5.4d (1/9 DA above threshold) Min/Max: 1.5d / 20755.9d (9/9 DA, Voting / Total Eligible)	≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d
Stable	Uptime	Meets (9/9 DA)	6.3d (R)	≥5.2d - 5.3d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (9/9 DA)	9/9 DA assigned Fast 272.0 Mbit/s – 472.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 (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 (7/9 DA)	6.3d (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 272.0 Mbit/s – 472.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 (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	Below (4/9 DA)	Median: 97.9% (4/9 DA above threshold) Min/Max: 61.6% / 98.3% (9/9 DA, Voting / Total Eligible)	≥98%; dizum: ≥97.84099999999999% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 15.3d (9/9 DA above threshold) Min/Max: 9.5d / 15.4d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	272.0 Mbit/s – 472.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: 202.92 Mbit/s
Advertised Bandwidth: 202.92 Mbit/s
Rate Limit: 8.59 Gbit/s
Burst Limit: 8.59 Gbit/s
Total Data: 1.9 PB (5 years)
1mo: 59 TB | 6mo: 355 TB | 1y: 769 TB | 5y: 1.9 PB

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: 408.0 Mbit/s (median of 5 measurements)
Measured Min / Max: 272.0 Mbit/s / 472.0 Mbit/s

Network Participation: Consensus Weight: 0.0258% of network (89th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0839% (92th pctl)

History

Throughput and write/read, last 6 months

Uptime and Stability

Uptime Metrics

Current Status: UP 6d 6h 28m ago
Overall Uptime (1M/6M/1Y/5Y): 97.2%/98.6%/99.1%/97.5%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (97.2%/98.6%/99.1%/97.5%)
Hibernating: No

Timestamps

First Seen: 2y 10mo 1w ago (2024-01-01 00:00:00)
Last Seen: 2h 15m 37s ago (2026-11-04 11:00:00)
Last Restarted: 6d 6h 28m ago (2026-10-29 06:47:35)
Last Changed Address: 2026-10-21 17:00:00

Overload Status: Not Overloaded — No overload conditions reported.

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

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: mentor@palokaj.co

Family Configuration

Family Support: Happy Families (24) — Has family-cert in server descriptor (guide) | View Full Family (24)

Happy Families (family-cert)

Effective Members: 24

00F19562A86F8E4E076918AC9F0319E52AE89180
041D964CBA77F593A86ECE2033F6894AC89A5820
0691FB6B5113FF36F0F6BAEF93348DD8C7BDAAD7
0817BBF1C8593C0AEB1562EB175523F664F0C2DF
0E29222CA653CE4F94FDBF8DF16D2597D473EC74
109AFCCFA6DA6E14F03D50ECDBD5B71D487C9F68
11729F39201A8A1335B08C20257AEB6303E4178D
18A9D33515E504795927782AE723C234B979BD6A
1EC88F31B78A86664EE0EAF2EF39214FE0B60491
23899620429B1B0E726AC927EF86BEBDE10F1D0C
30626238638AE65194814663A4651AFC04BC8D60
346F72D3C67467ADFA427D09A6F234D93153D594
3973392DD6BCC4F4561462EB419F72AD3F7CDA01
43D29158118DC17C1F5C23941D4C3BA9DB582FFC
451D39DA869DA58AB043DC2D4B3A213F1E6932EF
6DAD7AF818F4E1CDA7909DF2E4018A998BE21113
73F2F7416C8EAE8427B0649C53037A30E9F387C0
75986882FC3737694E3A2189981C94376BA6A400
85FA2F5A6B85EC706C90E31B68C57BFD13F1B355
A3093B729A57672AE0717CDF3B09E33826F36582
A5E662AB4A4644E55D6C37D56468B57ADA8D0F6B (this relay)
A75ECA19CB9B7607F6577C03E6EC7DFB2819F7EB
B4503836255E021B66A6B01F4C3B05089FE63D91
CCA1324B9223282C00BD67F7A51A38E29F2400D7

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. 14.1s, 37th percentile)

Query Domain

007d326b9eeb4232af3ebcf091492178.a5e662ab.tor.exit.validator.1aeo.com

DNS Result

Resolved to 64.65.4.1

Upstream Resolver

Local /24 (exit's own network)
Local /24 100% (~94 estimated queries)

Cross-Validation

3/3 instances succeeded

First Hop

coconutty (PL) 98A52BC6C0BEC68258C4B208C56994D998F1710E

Exit Address Used

5.2.69.82

Per-Instance Results

Cross Validation Attempt 1:	Success, 17.6s	(cv1_w3)
Cross Validation Attempt 2:	Success, 12.2s	(cv2_w3)
Cross Validation Attempt 3:	Success, 12.6s	(cv4_w3)

Tested: 2026-11-03 20:15:43 UTC

Source: exitdnshealth.1aeo.com

IPv4 Exit Policy Summary

IPv6 Exit Policy Summary

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 5.2.69.82:*
reject *:25
reject *:119
reject *:135-139
reject *:445
reject *:563
reject *:1214
reject *:4661-4666
reject *:6346-6429
reject *:6699
reject *:6881-6999
accept *:*

Last fetch was at Wed, 04 Nov 2026 13:15:37 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, Exit	344.0 Mbit/s (M) \| 816.0 Kbit/s	344.0 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	97.9% \| 98%	15.4d \| 8d	4.5d \| 8.4d	6.3d \| 5.2d	2026-11-03 18:08:21	344.0 Mbit/s (M)
dannenberg (DE)	Yes	Yes	Yes	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard, Exit	472.0 Mbit/s (M) \| 816.0 Kbit/s	472.0 Mbit/s (M) \| 272.0 Mbit/s OR 16.8 Mbit/s	98.2% \| 98%	15.4d \| 8d	5.4d \| 9.3d	6.3d \| 5.3d	2026-11-03 18:08:21	472.0 Mbit/s (M)
dizum (NL)	Yes	Yes	Yes	—	N	Yes	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	95.9% \| 98%	12.5d \| 8d	3.7d \| 6.7d	6.3d \| 5.3d	2026-11-03 18:08:21	80.0 Mbit/s (R)
faravahar (US)	Yes	Yes	Yes	—	Y	Yes	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	97.9% \| 98%	13.3d \| 8d	3.8d \| 6.5d	6.3d \| 5.3d	2026-11-03 18:08:21	80.0 Mbit/s (R)
gabelmoo (DE)	Yes	Yes	Yes	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit	416.0 Mbit/s (M) \| 816.0 Kbit/s	416.0 Mbit/s (M) \| 248.0 Mbit/s OR 16.8 Mbit/s	98.3% \| 98%	15.3d \| 8d	5.5d \| 10.8d	6.3d \| 5.3d	2026-11-03 18:08:21	416.0 Mbit/s (M)
longclaw (US)	Yes	Yes	Yes	—	Y	Yes	N/T	Running, Valid, V2Dir, Fast, Stable, HSDir, 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.1% \| 98%	15.3d \| 8d	5.4d \| 10.9d	6.3d \| 5.3d	2026-11-03 18:08:21	80.0 Mbit/s (R)
maatuska (SE)	Yes	Yes	Yes	—	N	Yes	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	96.2% \| 98%	12.5d \| 8d	1.5d \| 2.4d	6.3d \| 5.3d	2026-11-03 18:08:21	80.0 Mbit/s (R)
moria1 (US)	Yes	Yes	Yes	—	Y	Yes	Yes	Valid, V2Dir, Fast, Stable, Exit	272.0 Mbit/s (M) \| 8.4 Mbit/s	272.0 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	61.6% \| 98%	9.5d \| 8d	20755.9d \| 7607.5d	6.3d \| 5.3d	2026-11-03 18:08:21	272.0 Mbit/s (M)
tor26 (AT)	Yes	Yes	Yes	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit	408.0 Mbit/s (M) \| 816.0 Kbit/s	408.0 Mbit/s (M) \| 256.0 Mbit/s OR 16.8 Mbit/s	98.2% \| 98%	15.3d \| 8d	5.4d \| 10.6d	6.3d \| 5.3d	2026-11-03 18:08:21	408.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.

View Relay "mentoreth3"

Fingerprint: A5E662AB4A4644E55D6C37D56468B57ADA8D0F6B | Family: 24 relays | mentor@palokaj.co | AS60404 | 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)

History

Operator Identity

Family Configuration

Full Exit Policy

Fingerprint: `A5E662AB4A4644E55D6C37D56468B57ADA8D0F6B` | Family: 24 relays | mentor@palokaj.co | AS60404 | Netherlands | Linux