View Relay "artikel5ev13c"

Operator: artikel5ev.de (23 relays) 🚫 Unauthorized | Family: 21 relays | email:abuse[]artikel5ev.de... | AS12876 | Netherlands | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Exit, Fast, Running, V2Dir, Valid (5)
BW Verified
2/6 BW Auths Measured 920 bit/s Median
Stability
Not Overloaded | UP 4h 25m 26s ago | UP 4% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
2y 6mo 3w ago
BW Weight
0.00% of Network | 925 Kbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • Guard: bandwidth below threshold : Observed bandwidth 0.1 MB/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
    Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM.
  • 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.
  • 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).
  • 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: 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.
  • 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.
  • Low bandwidth authority measurements : Only 2/6 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
    Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.

Connectivity and Location

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
Location
Country
Netherlands Netherlands
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS12876
AS Name
SCALEWAY S.A.S. (BGP.tools)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 6/9 | Stable: 2/9 | HSDir: 0/9 | Guard: 0/9 (need ≥5/9 for flag)
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Fast Speed Meets (≥100 KB/s) 925.7 Kbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below Median: 0.1d (1/9 DA above threshold)
Min/Max: 0.0d / 435.6d (9/9 DA, Voting / Total Eligible)		 ≥22.2d - 53.8d (varies)
[Stricter] moria1: ≥406.4d
Uptime Below 0.2d (R) ≥10.0d - 11.0d (varies)
HSDir Prereq: Stable Below 2/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: Fast Meets 6/9 authorities assigned Fast flag ≥5/9 authorities
WFU Below Median: 90.7% (2/9 DA above threshold)
Min/Max: 0.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98.0%
Time Known Meets Median: 18.9d (7/9 DA above threshold)
Min/Max: 0.0d / 435.6d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Meets 6/9 authorities assigned Fast flag ≥5/9 authorities
Prereq: Stable Below 2/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: V2Dir Meets 9/9 authorities assigned V2Dir flag ≥5/9 authorities
WFU Below Median: 90.7% (2/9 DA above threshold)
Min/Max: 0.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98% (all authorities)
Time Known Meets Median: 18.9d (7/9 DA above threshold)
Min/Max: 0.0d / 435.6d (9/9 DA, Voting / Total Eligible)		 ≥8 days (all authorities)
Bandwidth Below 925.7 Kbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-01-29 10:15:07).

Last fetch was at Thu, 29 Jan 2026 10:15:43 GMT.

Nickname
artikel5ev13c
Fingerprint
51562252B9CF3120FAC9CF124391697296050E74
AROI (?)
artikel5ev.de
Contact
email:abuse[]artikel5ev.de url:https://artikel5ev.de proof:uri-rsa ciissversion:2
IPv4 Exit Policy Summary 
accept: 
  80-81
  443
IPv6 Exit Policy Summary 
accept: 
  80-81
  443
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 *:*
Effective Family Members: 21 (View) 
0BC8BA32CC3CB0F598E0C92778F7C0946DFBCE91
166264168E8CCCBB2444ADE0F0A22E4E6DDEF6FD
195712E96FD1C1B18D14D09E9E4E7A6416E23B2C
1AA683E036EA10AA6E078D40498CC7234F6424B9
26C28F29B611DF4DE23ACF5D9DC1EB4895EF5E8B
282CAAF0E11DAD47DD73D553DC20B51099A257BB
4D0DF468DC816F8096702C2DA2C6FD67561F81C8
51562252B9CF3120FAC9CF124391697296050E74
780D50DCCD7F3C831E5E750F41866497C1263F76
88C8F99559FEEB7C29E2EB196AACD734390D6289
9DEB16841863A939257160445052C606ECA46D25
AF7094B62864DE941DCD88A2F0DBAFECF3997E47
B1F926DA3895A89AF288623F5A4F913979299C53
C36C76992198329C0D8F34E01D092BF2ACE0B6B0
CE5EF4FB644544DB2F430A60CC6EB86FD7E29BA6
D4CA7FD04DABF6E2CB679426F5AA3205B640D147
DC2191663DD4BAECB34F949CCAC3FDA004CE5BCE
E22694E83DA7BCF30DDAF5780EEF394CD0370CC4
E8018E2C62E982758DBC173E3FEE26C917B353B1
F3B2CC8C2AB331150E096DD1DB8810E4A43F399D
FC077C25B8DBB3132D397D7DF03C92BFC14C9D76
Alleged Family Members: 3 
20D9D2A69FBE8B3454F6286059F6BD95E74EFD9D
4B170481AC4C3EC3603B9F4443C2E24B929D0429
89C7E852CC2FA537ED78775ADC3BEA24672B4154
Indirect Family Members: 2 
20D9D2A69FBE8B3454F6286059F6BD95E74EFD9D
4B170481AC4C3EC3603B9F4443C2E24B929D0429
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
925.70 Kbit/s | 925.70 Kbit/s| 8.59 Gbit/s| 8.59 Gbit/s  Not Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | N/A | 0.00%
OR Address
51.15.59.15:445, [2001:bc8:1640:317d:dc00:ff:fe39:7bb3]:445
Exit Address
none
Dir Address
none
Country
Netherlands Netherlands
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS12876 | SCALEWAY S.A.S. (BGP.tools)
Flags: 5
Exit Exit Fast Fast Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
Match Overall Uptime (4.8%/84.1%/92.0%/96.3%)
Uptime (1M/6M/1Y/5Y)
4.8%/84.1%/92.0%/96.3%
Uptime / Downtime
UP 4h 25m 26s ago
Seen (First | Last)
2y 6mo 3w ago (2023-07-09 00:00:00) | 1h 17m 15s ago (2026-01-29 09:00:00)
Last Restarted
4h 26m 57s ago (2026-01-29 05:50:18)
Last Changed Address or Port
2024-11-18 12:00:00
Hibernating
No
Platform (Short | Long)
Linux | Tor 0.4.8.21 on Linux
Version (Running | Recommended | Status)
0.4.8.21 | Yes | recommended

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-01-29 10:15:07).

  • Consensus Status (need ≥5/9): In Consensus — 9/9 authorities voted.
  • Flag Eligibility (need ≥5/9 for flag): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 6/9 | Stable: 2/9 | HSDir: 0/9 | Guard: 0/9
  • Reachability: IPv4: 9/9 | IPv6: 6/0
  • Consensus Weight (Dir. Auth.): Median: 920 bit/s | Min: 920 bit/s | Max: 2480 bit/s [Warning] High deviation
  • Identified Issues:
    • Guard: bandwidth below threshold: Observed bandwidth 0.1 MB/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
      • Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM.
    • 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.
    • 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).
    • 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: 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.
    • 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.
    • Low bandwidth authority measurements: Only 2/6 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
      • Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.

Summary: Your Relay vs Consensus

Green = meets threshold, Red = below threshold, Yellow = partial.

Metric Dir Auth Measured Dir Auth Threshold Status
In Consensus (Dir. Auth.) 9/9 authorities ≥5/9 (majority) IN CONSENSUS
Running (IPv4 Reachable) 9/9 authorities reached this relay ≥5/9 (majority) RUNNING
Valid 9/9 (Running + Valid Descriptor) ≥5/9 (majority) VALID
Consensus Weight (Dir. Auth.) 920 bit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 90.7% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 18.9 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 925.7 Kbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported) 0.2d ≥10.0d - 11.0d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 0 days ≥22.2d - 53.8d (typical)
[Stricter] moria1: ≥406.4d 		BELOW - 2/9
Fast Speed (Relay Reported) 925.7 Kbit/s ≥800.0 Kbit/s (guarantee) OR ≥816.0 Kbit/s (typical)
[Stricter] moria1: ≥8.4 Mbit/s 		MEETS - ≥100 KB/s guarantee
HSDir WFU (Dir. Auth., wfu) 90.7% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 18.9 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d 		BELOW - 0/9
IPv6 Reachable (Dir. Auth.) 6/6 tested ≥4/6 (majority) REACHABLE

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 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 Y Yes Yes Valid, V2Dir, Exit 925.7 Kbit/s | 816.0 Kbit/s 925.7 Kbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 50.3d 0.2d | 11.6d 0.0% | 98.0% 0.0d | 1.0d 2026-01-29 05:50:21 920 bit/s
dannenberg (DE) Yes Yes N Yes Yes Running, Valid, V2Dir, Fast, Exit 925.7 Kbit/s | 816.0 Kbit/s 925.7 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 90.7% | 98% 18.9d | 8d 0.1d | 22.2d 0.2d | 11.1d 90.7% | 98.0% 18.9d | 1.0d 2026-01-29 05:50:21 920 bit/s
dizum (NL) Yes Yes N Yes — Running, Valid, V2Dir, Fast, Stable, Exit 925.7 Kbit/s | 816.0 Kbit/s 925.7 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 47.4d | 8d 47.0d | 34.5d 0.2d | 11.0d 100.0% | 98.0% 47.4d | 1.0d 2026-01-29 05:50:21 920 bit/s
faravahar (US) Yes Yes N Yes Yes Running, Valid, V2Dir, Fast, Exit 925.7 Kbit/s | 816.0 Kbit/s 925.7 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 93.4% | 98% 25.3d | 8d 0.1d | 47.4d 0.2d | 10.0d 93.4% | 98.0% 25.3d | 1.0d 2026-01-29 05:50:21 920 bit/s
gabelmoo (DE) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast, Exit 925.7 Kbit/s | 816.0 Kbit/s 925.7 Kbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 88.7% | 98% 15.0d | 8d 0.1d | 53.8d 0.2d | 11.1d 88.7% | 98.0% 15.0d | 1.0d 2026-01-29 05:50:21 2480 bit/s
longclaw (US) Yes Yes Y Yes — Running, Valid, V2Dir, Fast, Stable, Exit 925.7 Kbit/s | 816.0 Kbit/s 925.7 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 435.6d | 8d 435.6d | 54.6d 0.2d | 10.6d 100.0% | 98.0% 435.6d | 1.0d 2026-01-29 05:50:21 920 bit/s
maatuska (SE) Yes Yes Y Yes Yes Running, Valid, V2Dir, Exit 925.7 Kbit/s | 816.0 Kbit/s 925.7 Kbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 86.1% | 98% 12.0d | 8d 0.0d | 55.1d 0.2d | 10.2d 86.1% | 98.0% 12.0d | 1.0d 2026-01-29 05:50:21 920 bit/s
moria1 (US) Yes Yes Y Yes — Valid, V2Dir, Exit 925.7 Kbit/s | 8.4 Mbit/s 925.7 Kbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 406.4d 0.2d | 10.7d 0.0% | 98.0% 0.0d | 9.9d 2026-01-29 05:50:21 920 bit/s
tor26 (AT) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast, Exit 925.7 Kbit/s | 816.0 Kbit/s 925.7 Kbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 94.3% | 98% 29.0d | 8d 0.1d | 55.7d 0.2d | 12.0d 94.3% | 98.0% 29.0d | 1.0d 2026-01-29 05:50:21 2080 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). This is your relay's self-reported uptime from its 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.