View Relay "mentoreth7"

Fingerprint: 23899620429B1B0E726AC927EF86BEBDE10F1D0C | Family: 32 relays | mentor@palokaj.co | AS60404 | Netherlands | Linux

Consensus
In Consensus (9/9 Directory Auths)
DNS Health
Healthy (15.2s, 47th percentile) (via exitdnshealth.1aeo.com)
BW Verified
6/7 BW Auths Measured 312 Mbit/s Median
Stability
Not Overloaded | UP 6d 3h 37m ago | UP 97% (1M)
Reachability
IPv4: 9/9 | v6: 8/8(Directory Auths)
BW Weight
0.02% of Network | 195 Mbit/s Observed By Relay
Version
0.4.9.17 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.
Notes:
  • Guard: WFU near threshold: Weighted Fractional Uptime is just under the Guard bar at maatuska (97.97%, need ≥98%). 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.

Addresses
OR Address
5.2.69.82:9008
[2a04:52c0:2000:501::82]:9008
Exit Address
5.2.69.82
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
AS60404
AS Name
The Infrastructure Group B.V. (BGP.tools)
AS Rarity
Emerging (score: 1/5, 1.08% consensus weight, 32 operators)

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: 8/9 | HSDir: 7/9 | Guard: 7/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) 168.0 Mbit/s – 424.0 Mbit/s (6 DA measured)
80.0 Mbit/s (3 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 (3/9 DA) Median: 7.1d (1/9 DA above threshold)
Min/Max: 1.3d / 20770.1d (9/9 DA, Voting / Total Eligible)
≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12663.9d
Uptime Meets (9/9 DA) 6.2d (R) ≥5.0d - 5.1d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
168.0 Mbit/s – 424.0 Mbit/s (6 DA measured)
80.0 Mbit/s (3 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 (8/9 DA) 8/9 DA assigned Stable ≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12663.9d
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) 6.2d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.6d Time Known
Guard Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
168.0 Mbit/s – 424.0 Mbit/s (6 DA measured)
80.0 Mbit/s (3 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 (8/9 DA) 8/9 DA assigned Stable ≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12663.9d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Partial (7/9 DA) Median: 99.3% (7/9 DA above threshold)
Min/Max: 78.8% / 100.0% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 13.9d (9/9 DA above threshold)
Min/Max: 6.8d / 14.1d (9/9 DA, Voting / Total Eligible)
≥8 days; E30CF7B3: ≥5 days 11 hours 43 minutes 50 seconds (≥5/9 DA)
Bandwidth Meets (9/9 DA) 168.0 Mbit/s – 424.0 Mbit/s (6 DA measured)
80.0 Mbit/s (3 DA relay-reported)
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-248.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-20 10:15:05).

Capacity (Relay Reported)
Observed Bandwidth
195.09 Mbit/s
Advertised Bandwidth
195.09 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
2.0 PB (5 years)
1mo: 50 TB | 6mo: 356 TB | 1y: 731 TB | 5y: 2.0 PB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-20 10:15:05

Measured By
6/7 Bandwidth Authorities
Not measured by: faravahar
Consensus Weight
312.0 Mbit/s (median of 6 measurements)
Measured Min / Max
168.0 Mbit/s / 424.0 Mbit/s
Deviation
256.0 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0212% of network (85th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0657% (88th pctl)
History

Uptime Metrics
Current Status
UP 6d 3h 37m ago
Overall Uptime (1M/6M/1Y/5Y)
97.4%/98.6%/99.1%/97.3%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (97.4%/98.6%/99.1%/97.3%)
Hibernating
No
Timestamps
First Seen
3y 3mo 3w ago (2023-07-27 00:00:00)
Last Seen
1h 15m 38s ago (2026-11-20 09:00:00)
Last Restarted
6d 3h 37m ago (2026-11-14 06:37:51)
Last Changed Address
2026-10-21 17:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-20 10:15 UTC. /details snapshot 2026-11-20 09:00:00 UTC (cached 14s ago). /bandwidth snapshot 2026-11-20 02:00:00 UTC (cached 7h 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 Identity

Source: AROI Validation API — 2026-11-19 23: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 (32) — Has family-cert in server descriptor (guide) | View Full Family (32)
Happy Families (family-cert)
Effective Members: 32
00F19562A86F8E4E076918AC9F0319E52AE89180
041D964CBA77F593A86ECE2033F6894AC89A5820
0691FB6B5113FF36F0F6BAEF93348DD8C7BDAAD7
0817BBF1C8593C0AEB1562EB175523F664F0C2DF
0E29222CA653CE4F94FDBF8DF16D2597D473EC74
108FB2FBC24A2D965F44E4F433961E53E6B7F88B
109AFCCFA6DA6E14F03D50ECDBD5B71D487C9F68
11729F39201A8A1335B08C20257AEB6303E4178D
18A9D33515E504795927782AE723C234B979BD6A
1EC88F31B78A86664EE0EAF2EF39214FE0B60491
23899620429B1B0E726AC927EF86BEBDE10F1D0C (this relay)
30626238638AE65194814663A4651AFC04BC8D60
346F72D3C67467ADFA427D09A6F234D93153D594
3973392DD6BCC4F4561462EB419F72AD3F7CDA01
3A9A4AB48B2CA532CC2DD2AB01706319E2007914
43D29158118DC17C1F5C23941D4C3BA9DB582FFC
451D39DA869DA58AB043DC2D4B3A213F1E6932EF
5AF6EA8063B7AA0CD73955C4A30CA059D9BBDA9F
6C44AFCB0BBB4795681F61FE2DEDD9DDD35A2A5C
6DAD7AF818F4E1CDA7909DF2E4018A998BE21113
72C20EA8201E21CDCD6BC3E26794F0EFB1F25DDB
73F2F7416C8EAE8427B0649C53037A30E9F387C0
75986882FC3737694E3A2189981C94376BA6A400
85FA2F5A6B85EC706C90E31B68C57BFD13F1B355
8EF1AF7A96A53D3716BAFAADF0E616D74359461D
95AF093EF2D58AA2B906A0CFEACFBEA5F8F45E2B
A3093B729A57672AE0717CDF3B09E33826F36582
A5E662AB4A4644E55D6C37D56468B57ADA8D0F6B
A75ECA19CB9B7607F6577C03E6EC7DFB2819F7EB
B4503836255E021B66A6B01F4C3B05089FE63D91
C1F53BDCB5FFE7369B1ECD0E354C08F8C57E7798
CCA1324B9223282C00BD67F7A51A38E29F2400D7
MyFamily (legacy declarations) — none

Platform
Linux — Tor 0.4.9.17 on Linux
Version
0.4.9.17 — Recommended
Version Status
Recommended

DNS Health
Status
Healthy (avg. 15.2s, 47th percentile)
Query Domain
82a5833ad8be4117b276ffde82e5def6.23899620.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Upstream Resolver
Local /24 (exit's own network)
Local /24 >99%, Local AS <1% (~160 estimated queries)
Cross-Validation
4/4 instances succeeded
First Hop
Quintex198 (US) 65AE4E40402F4B331B0417FDCE0001D82115C2D4
Exit Address Used
5.2.69.82
Per-Instance Results
Cross Validation Attempt 1: Success, 12.2s (cv1_w1)
Cross Validation Attempt 2: Success, 12.2s (cv2_w1)
Cross Validation Attempt 3: Success, 19.5s (cv3_w1)
Cross Validation Attempt 4: Success, 16.8s (cv4_w1)
Tested: 2026-11-19 20:05:20 UTC
IPv4 Exit Policy Summary
reject: 
  25
  119
  135-139
  445
  563
  1214
  4661-4666
  6346-6429
  6699
  6881-6999
IPv6 Exit Policy Summary
reject: 
  25
  119
  135-139
  445
  563
  1214
  4661-4666
  6346-6429
  6699
  6881-6999
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 Fri, 20 Nov 2026 10:15:38 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-11-20 10:15:05).

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)
E30CF7B3 Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 168.0 Mbit/s (M) | 816.0 Kbit/s 168.0 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 6.8d | 5d 6.8d | 3.9d 6.2d | 5.1d 2026-11-19 22:56:07 168.0 Mbit/s (M)
dannenberg (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 424.0 Mbit/s (M) | 816.0 Kbit/s 424.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 99.3% | 98% 13.9d | 8d 7.1d | 8.2d 6.2d | 5.1d 2026-11-19 22:56:07 424.0 Mbit/s (M)
dizum (NL) Yes Yes Yes — N Yes Yes 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.9% | 98% 13.9d | 8d 6.7d | 6.8d 6.2d | 5.1d 2026-11-19 22:56:07 80.0 Mbit/s (R)
faravahar (US) Yes Yes Yes — Y Yes Yes 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 99.3% | 98% 14.0d | 8d 7.1d | 7.0d 6.2d | 5.1d 2026-11-19 22:56:07 80.0 Mbit/s (R)
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 344.0 Mbit/s (M) | 816.0 Kbit/s 344.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 99.2% | 98% 14.1d | 8d 7.1d | 8.3d 6.2d | 5.1d 2026-11-19 22:56:07 344.0 Mbit/s (M)
longclaw (US) Yes Yes Yes — Y Yes N/T Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 408.0 Mbit/s (M) | 816.0 Kbit/s 408.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 99.3% | 98% 14.0d | 8d 7.1d | 9.1d 6.2d | 5.1d 2026-11-19 22:56:07 408.0 Mbit/s (M)
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 97.97% | 98% 13.2d | 8d 1.3d | 2.3d 6.2d | 5.1d 2026-11-19 22:56:07 80.0 Mbit/s (R)
moria1 (US) Yes Yes Yes — Y Yes Yes Valid, V2Dir, Fast, Stable, Exit 240.0 Mbit/s (M) | 8.4 Mbit/s 240.0 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 78.8% | 98% 10.0d | 8d 20770.1d | 12663.9d 6.2d | 5.0d 2026-11-19 22:56:07 240.0 Mbit/s (M)
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 312.0 Mbit/s (M) | 816.0 Kbit/s 312.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 99.3% | 98% 14.0d | 8d 7.1d | 8.3d 6.2d | 5.1d 2026-11-19 22:56:07 312.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.