View Relay "4222246869172484"

Fingerprint: 1EF5EABE2FD572F4C0AEBAB6993B6DD4A29FC897 | Family: 15 relays | john_rt291141(at)proton(dot)me | AS211507 | Netherlands | Linux

Consensus
In Consensus (9/9 Directory Auths)
DNS Health
Healthy (16.3s, 63rd percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/6 BW Auths Measured 24 Kbit/s Median
Stability
Not Overloaded | UP 2d 5h 57m ago | UP 7% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
BW Weight
0.00% of Network | 53 Mbit/s Observed By Relay
Version
0.4.8.22 Recommended
Issues Detected:
  • Guard: requires Stable flag : Guard flag requires having the Stable flag first
    Suggestion: Get Stable flag by maintaining consistent uptime. Stable requires uptime and MTBF at or above network median (typically 2-3 weeks of stable running).
  • Guard: WFU below threshold : Weighted Fractional Uptime 9.0% is below 98% requirement
    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.
  • Not eligible for Stable flag : Uptime or MTBF below network median for most authorities
    Suggestion: Stable flag requires uptime/MTBF at or above network median. Keep your relay running continuously for 2-3 weeks. Avoid restarts. Use reliable hardware and network connection.
  • HSDir: requires Stable flag : HSDir flag requires having the Stable flag first
    Suggestion: Get Stable flag by maintaining consistent uptime. Stable requires uptime and MTBF at or above network median (typically 2-3 weeks of stable running). Avoid restarts.
  • HSDir: WFU below threshold : WFU 9.0% below 98% required for HSDir
    Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.
  • 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.

Addresses
OR Address
lain.185.132.53.46.aluy.net
185.132.53.46:9001
Exit Address
185.132.53.46
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Netherlands Netherlands
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS211507
AS Name
Julian Achter (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.30% consensus weight, 9 operators)

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 5/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/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) 53.9 Mbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (1/9 DA) Median: 2.3d (1/9 DA above threshold)
Min/Max: 1.1d / 20483.7d (9/9 DA, Voting / Total Eligible)
≥11.3d - 53.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥366.0d
Uptime Below (0/9 DA) 2.2d (R) ≥9.7d - 12.6d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (5/9 DA) 5/9 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/9 DA) 1/9 DA assigned Stable ≥11.3d - 53.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥366.0d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 9.0% (0/9 DA above threshold)
Min/Max: 0.1% / 9.9% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 26.5d (9/9 DA above threshold)
Min/Max: 9.7d / 26.6d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Meets (5/9 DA) 5/9 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/9 DA) 1/9 DA assigned Stable ≥11.3d - 53.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥366.0d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 9.0% (0/9 DA above threshold)
Min/Max: 0.1% / 9.9% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 26.5d (9/9 DA above threshold)
Min/Max: 9.7d / 26.6d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 53.9 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-296.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-03-15 19:15:08).

Capacity (Relay Reported)
Observed Bandwidth
53.86 Mbit/s
Advertised Bandwidth
24.58 Mbit/s
Rate Limit
24.58 Mbit/s
Burst Limit
8.59 Gbit/s
Total Data
390 GB (6 months)
1mo: 9.2 GB | 6mo: 390 GB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-15 19:15:08

Measured By
5/6 Bandwidth Authorities
Not measured by: longclaw
Median Measurement
24.6 Kbit/s
Min / Max
8 bit/s / 59.2 Kbit/s
Deviation
59.2 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (0th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0000% (0th pctl)

Uptime Metrics
Current Status
UP 2d 5h 57m ago
Overall Uptime (1M/6M/1Y/5Y)
7.3%/23.6%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (7.3%/23.6%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
1mo 2w 1d ago (2026-01-29 14:00:00)
Last Seen
1h 15m 39s ago (2026-03-15 18:00:00)
Last Restarted
2d 5h 57m ago (2026-03-13 13:17:44)
Last Changed Address
2026-01-29 14:00:00
Overload Status: Not Overloaded — No overload conditions reported.

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

DNS Health
Status
Healthy (avg. 16.3s, 63rd percentile)
Query Domain
c0cff120360949b4bf947d94d79e1271.1ef5eabe.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
4/4 instances succeeded
First Hop
ParadiseTorRelay3 (SE) 803BBA187F5277709D2BE1D8B647DB4EB28B8F21
Exit Address Used
185.132.53.46
Per-Instance Results
Cross Validation Attempt 1: Success, 19.4s (cv1_w1)
Cross Validation Attempt 2: Success, 16.0s (cv2_w1)
Cross Validation Attempt 3: Success, 15.6s (cv3_w1)
Cross Validation Attempt 4: Success, 14.0s (cv4_w1)
Tested: 2026-03-15 07:05:28 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 185.132.53.46:*
accept *:80
accept *:443
accept *:8080
accept *:8443
reject *:*

Last fetch was at Sun, 15 Mar 2026 19:15:38 GMT.

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

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 (Relay|T) Guard BW (Relay|Threshold) Guard WFU (M|T) Guard TK (M|T) Stable MTBF (M|T) Stable Uptime (Relay|T) HSDir WFU (M|T) HSDir TK (M|T) Desc Published Cons Wt (Authority)
bastet (US) Yes Yes Yes Y Yes Running, Valid, V2Dir, Exit 53.9 Mbit/s | 816.0 Kbit/s 53.9 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 9.0% | 98% 26.6d | 8d 2.3d | 56.9d 2.2d | 11.9d 9.0% | 98.0% 26.6d | 1.0d 2026-03-15 03:06:01 8 bit/s
dannenberg (DE) Yes Yes Yes N Yes Running, Valid, V2Dir, Fast, Exit 53.9 Mbit/s | 816.0 Kbit/s 53.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 9.0% | 98% 26.5d | 8d 2.3d | 11.3d 2.2d | 12.6d 9.0% | 98.0% 26.5d | 1.0d 2026-03-15 03:06:01 24.6 Kbit/s
dizum (NL) Yes Yes Yes N Yes Running, Valid, V2Dir, Fast, Exit 53.9 Mbit/s | 816.0 Kbit/s 53.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 9.0% | 98% 26.6d | 8d 2.3d | 43.1d 2.2d | 9.7d 9.0% | 98.0% 26.6d | 1.0d 2026-03-15 03:06:01 24.6 Kbit/s
faravahar (US) Yes Yes Yes N Yes Running, Valid, V2Dir, Fast, Exit 53.9 Mbit/s | 816.0 Kbit/s 53.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 9.0% | 98% 26.6d | 8d 2.3d | 53.0d 2.2d | 12.7d 9.0% | 98.0% 26.6d | 1.0d 2026-03-15 03:06:01 24.6 Kbit/s
gabelmoo (DE) Yes Yes Yes Y Yes Running, Valid, V2Dir, Exit 53.9 Mbit/s | 816.0 Kbit/s 53.9 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 9.0% | 98% 26.6d | 8d 2.3d | 58.1d 2.2d | 12.6d 9.0% | 98.0% 26.6d | 1.0d 2026-03-15 03:06:01 8 bit/s
longclaw (US) Yes Yes Yes Y Yes Running, Valid, V2Dir, Fast, Exit 53.9 Mbit/s | 816.0 Kbit/s 53.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 9.9% | 98% 24.0d | 8d 2.3d | 61.0d 2.2d | 12.7d 9.9% | 98.0% 24.0d | 1.0d 2026-03-15 03:06:01 24.6 Kbit/s
maatuska (SE) Yes Yes Yes Y Yes Running, Valid, V2Dir, Fast, Exit 53.9 Mbit/s | 816.0 Kbit/s 53.9 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 8.1% | 98% 26.5d | 8d 1.1d | 40.7d 2.2d | 12.6d 8.1% | 98.0% 26.5d | 1.0d 2026-03-15 03:06:01 59.2 Kbit/s
moria1 (US) Yes Yes Yes Y Yes Valid, V2Dir, Stable, Exit 53.9 Mbit/s | 8.4 Mbit/s 53.9 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 0.1% | 98% 9.7d | 8d 20483.7d | 366.0d 2.2d | 15.4d 0.1% | 98.0% 9.7d | 9.9d 2026-03-15 03:06:01 8 bit/s
tor26 (AT) Yes Yes Yes Y Yes Running, Valid, V2Dir, Exit 53.9 Mbit/s | 816.0 Kbit/s 53.9 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 9.4% | 98% 25.4d | 8d 2.3d | 53.7d 2.2d | 12.7d 9.4% | 98.0% 25.4d | 1.0d 2026-03-15 03:06:01 8 bit/s

— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known

Bandwidth Values Explained:
Relay Reported = Your relay's self-reported bandwidth from its descriptor (observed_bandwidth). Used for flag eligibility (Guard, Fast).
Authority Measured = Bandwidth measured by authority's sbws scanner. Used for consensus weight (path selection probability).
Why different? Authorities verify your reported bandwidth independently. 6 of 9 authorities run bandwidth scanners; 3 use relay-reported values directly.
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.