View Relay "artikel5ev13c"

Fingerprint: 51562252B9CF3120FAC9CF124391697296050E74 | Operator: artikel5ev.de v2 (22 relays) ⚠ Misconfigured | Family: 22 relays | email:abuse[]artikel5ev.de... | AS12876 | Netherlands | Linux

Consensus
In Consensus (9/9 Directory Auths)
DNS Health
Healthy (12.4s, 16th percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/7 BW Auths Measured 68 Kbit/s Median
Stability
Not Overloaded | UP 2d 18h 9m ago | UP 74% (1M)
Reachability
IPv4: 9/9 | v6: 7/7 (Directory Auths)
BW Weight
0.00% of Network | 57 Mbit/s Observed By Relay
Version
0.4.9.13 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 0.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.
  • Guard: Time Known below threshold : Time Known 0.0 days is below 8 days requirement (8.0 more days needed)
    Suggestion: Time Known tracks how long authorities have observed your relay. This resets if: 1) Identity key changes, 2) Long downtime makes authorities forget you. Just keep running stably.
  • 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 0.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.
  • HSDir: Time Known below threshold : Time Known 0.0 hours below 25 hours (dir-spec default)
    Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.

Addresses
OR Address
51.15.59.15:445
[2001:bc8:1640:317d:dc00:ff:fe39:7bb3]:445
Exit Address
51.15.59.15
Reachability (Directory Authorities)
IPv4
9/9
IPv6
7/7 (2 don't test)
Location
Country
Netherlands Netherlands
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS12876
AS Name
Scaleway SAS (BGP.tools)
AS Rarity
Emerging (score: 1/5, 1.54% consensus weight, 32 operators)

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/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
IPv6 Reachability Meets (7/7 DA) 7/7 tested authorities reached relay ≥4/7 tested (majority) (≥4/7 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) 57.5 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: 0.2d (1/9 DA above threshold)
Min/Max: 0.0d / 16.2d (9/9 DA, Voting / Total Eligible)
≥6.1d - 9.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10198.2d
Uptime Below (0/9 DA) 2.8d (R) ≥5.7d - 5.7d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/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 ≥6.1d - 9.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10198.2d
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: 72.1% (0/9 DA above threshold)
Min/Max: 0.0% / 83.3% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (7/9 DA) Median: 14.0d (7/9 DA above threshold)
Min/Max: 0.0d / 20.4d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.7d
Guard Prereq: Fast Meets (9/9 DA) 9/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 ≥6.1d - 9.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10198.2d
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: 72.1% (0/9 DA above threshold)
Min/Max: 0.0% / 83.3% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (7/9 DA) Median: 14.0d (7/9 DA above threshold)
Min/Max: 0.0d / 20.4d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 57.5 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.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-10-17 23:00:36).

Capacity (Relay Reported)
Observed Bandwidth
57.47 Mbit/s
Advertised Bandwidth
57.47 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
1.5 TB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-17 23:00:36

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Median Measurement
68.0 Kbit/s
Min / Max
57.5 Kbit/s / 80.0 Kbit/s
Network Participation: Consensus Weight: 0.0049% of network (47th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0148% (23th pctl)

Uptime Metrics
Current Status
UP 2d 18h 9m ago
Overall Uptime (1M/6M/1Y/5Y)
74.7%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (74.7%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
2w 8h 6m ago (2026-10-03 15:00:00)
Last Seen
2h 6m 44s ago (2026-10-17 21:00:00)
Last Restarted
2d 18h 9m ago (2026-10-15 04:57:09)
Last Changed Address
2026-10-03 15:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator Identity

Source: AROI Validation API — 2026-10-17 14:00 UTC

AROI Domain (?)
artikel5ev.de
Operator Validation
Unvalidated
This Relay
Unvalidated
Error: URI-RSA: HTTP error 404 for artikel5ev.de at URL: https://artikel5ev.de/.well-known/tor-relay/rsa-fingerprint.txt. Used domain cache after 6 attempts.
Contact
email:abuse[]artikel5ev.de url:https://artikel5ev.de proof:uri-rsa ciissversion:2

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

DNS Health
Status
Healthy (avg. 12.4s, 16th percentile)
Query Domain
a56f30df142c475cb818e806f086744f.51562252.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
4/4 instances succeeded
First Hop
eo213 (US) E49758CA33FCFC08C9C9F183D3D3822D703D885B
Exit Address Used
51.15.59.15
Per-Instance Results
Cross Validation Attempt 1: Success, 0.7s (cv1_w2)
Cross Validation Attempt 2: Success, 19.7s (cv2_w2)
Cross Validation Attempt 3: Success, 11.9s (cv3_w2)
Cross Validation Attempt 4: Success, 17.4s (cv4_w2)
Tested: 2026-10-17 19:10:56 UTC
IPv4 Exit Policy Summary
accept: 
  80-81
  443
IPv6 Exit Policy Summary
accept: 
  80-81
  443
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 51.15.59.15:*
reject 202.91.160.0/20:*
reject 195.34.150.227:*
reject 188.172.236.167:*
reject 138.128.150.139/24:*
reject 178.63.119.153:*
reject 5.145.168.0/21:*
reject 77.81.112.0/22:*
reject 77.81.116.0/22:*
reject 91.192.108.0/22:*
reject 93.93.64.0/21:*
reject 185.50.196.0/22:*
reject 195.78.228.0/22:*
reject 217.61.128.0/22:*
reject 85.13.242.162:*
reject 138.201.57.222:*
reject 51.255.49.37:*
accept *:80-81
accept *:443
reject *:*

Last fetch was at Sat, 17 Oct 2026 23:06:30 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-10-17 23:00:36).

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 (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 Yes Valid, V2Dir, Fast, Exit 57.5 Mbit/s | 816.0 Kbit/s 57.5 Mbit/s | 184.0 Mbit/s OR 16.0 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 9.0d 2.8d | 5.7d 0.0% | 98.0% 0.0d | 1.0d 2026-10-17 12:15:06 68.0 Kbit/s
dannenberg (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 57.5 Mbit/s | 816.0 Kbit/s 57.5 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 71.4% | 98% 14.1d | 8d 0.2d | 6.1d 2.8d | 5.8d 71.4% | 98.0% 14.1d | 1.0d 2026-10-17 12:15:06 76.8 Kbit/s
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 57.5 Mbit/s | 816.0 Kbit/s 57.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 72.1% | 98% 14.4d | 8d 0.2d | 9.0d 2.8d | 5.7d 72.1% | 98.0% 14.4d | 1.0d 2026-10-17 12:15:06 57.5 Kbit/s
faravahar (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 57.5 Mbit/s | 816.0 Kbit/s 57.5 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 72.7% | 98% 14.0d | 8d 0.2d | 9.5d 2.8d | 6.3d 72.7% | 98.0% 14.0d | 1.0d 2026-10-17 12:15:06 57.5 Kbit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 57.5 Mbit/s | 816.0 Kbit/s 57.5 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 71.8% | 98% 14.3d | 8d 0.2d | 9.0d 2.8d | 5.7d 71.8% | 98.0% 14.3d | 1.0d 2026-10-17 12:15:06 80.0 Kbit/s
longclaw (US) Yes Yes Yes — Y Yes — Running, Valid, V2Dir, Fast, Stable, Exit 57.5 Mbit/s | 816.0 Kbit/s 57.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 83.3% | 98% 20.4d | 8d 16.2d | 9.2d 2.8d | 5.7d 83.3% | 98.0% 20.4d | 1.0d 2026-10-17 12:15:06 57.5 Kbit/s
maatuska (SE) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 57.5 Mbit/s | 816.0 Kbit/s 57.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 72.6% | 98% 13.8d | 8d 0.2d | 8.8d 2.8d | 5.7d 72.6% | 98.0% 13.8d | 1.0d 2026-10-17 12:15:06 57.5 Kbit/s
moria1 (US) Yes Yes Yes — Y Yes — Valid, V2Dir, Fast, Exit 57.5 Mbit/s | 8.4 Mbit/s 57.5 Mbit/s | 192.0 Mbit/s OR 16.0 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 10198.2d 2.8d | 5.7d 0.0% | 98.0% 0.0d | 9.7d 2026-10-17 12:15:06 76.8 Kbit/s
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 57.5 Mbit/s | 816.0 Kbit/s 57.5 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 72.2% | 98% 13.7d | 8d 0.2d | 9.3d 2.8d | 5.7d 72.2% | 98.0% 13.7d | 1.0d 2026-10-17 12:15:06 72.8 Kbit/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.