View Relay "centurion"

Fingerprint: BB4465B1EF3E765068C8D7231E316EF68B571499 | Family: 1 relay | admin@centurion.link | AS1136 | Netherlands | Linux

Consensus
In Consensus (8/8 Directory Auths)
BW Verified
4/5 BW Auths Measured 956 bit/s Median
Stability
Overloaded | UP 3d 13h 39m ago | UP 41% (1M)
Reachability
IPv4: 8/9 (Directory Auths)
BW Weight
0.00% of Network | 1 Mbit/s Observed By Relay
Version
0.4.9.6 Recommended
Issues Detected:
  • Guard: requires Fast flag : Guard flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • 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: bandwidth below threshold : Observed bandwidth 0.2 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 42.8% 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 Fast flag : HSDir flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • 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 42.8% 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.
  • General Overload Active : Relay reported general overload at 2026-04-14 09:00 UTC. This indicates OOM killer invocation, onionskin queue saturation, or TCP port exhaustion.
    Suggestion: Check CPU/memory with htop. Review logs for "out of memory" or "onionskins" warnings. Consider increasing MaxMemInQueues in torrc. Verify TCP ports available.
Notes:
  • Partial IPv4 reachability: 8/9 authorities can reach this relay

Addresses
OR Address
86-81-131-200.fixed.kpn.net
86.81.131.200:8100
Reachability (Directory Authorities)
IPv4
8/9
Location
Country
Netherlands Netherlands
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS1136
AS Name
KPN B.V. (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.38% consensus weight, 17 operators)

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (3): Running: 8/8 | Valid: 8/8 | V2Dir: 8/8 | Fast: 3/8 | Stable: 1/8 | HSDir: 0/8 | Guard: 0/8 | Exit: 0/8
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (8/8 DA) 8/8 authorities reached relay ≥5/8 DA ORPort reachable
Valid Descriptor Meets (8/8 DA) 8/8 authorities assigned Valid Not blacklisted + valid descriptor (≥5/8 DA)
V2Dir DirPort Available Meets (8/8 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/8 DA)
Fast Speed Meets (8/8 DA) 1.8 Mbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (1/8 DA) Median: 3.6d (1/8 DA above threshold)
Min/Max: 3.4d / 12550.1d (8/8 DA, Voting / Total Eligible)
≥32.5d - 59.0d (varies) (≥5/8 DA)
[Stricter] moria1: ≥317.9d
Uptime Below (0/8 DA) 3.6d (R) ≥7.0d - 7.2d (varies) (≥5/8 DA)
HSDir Prereq: Fast Below (3/8 DA) 3/8 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/8 DA) 1/8 DA assigned Stable ≥32.5d - 59.0d (varies) (≥5/8 DA)
[Stricter] moria1: ≥317.9d
Prereq: V2Dir Meets (8/8 DA) 8/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Below (0/8 DA) Median: 42.7% (0/8 DA above threshold)
Min/Max: 42.1% / 71.9% (8/8 DA, Voting / Total Eligible)
≥98.0% (≥5/8 DA)
Time Known Meets (8/8 DA) Median: 21.1d (8/8 DA above threshold)
Min/Max: 10.0d / 21.9d (8/8 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/8 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (3/8 DA) 3/8 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/8 DA) 1/8 DA assigned Stable ≥32.5d - 59.0d (varies) (≥5/8 DA)
[Stricter] moria1: ≥317.9d
Prereq: V2Dir Meets (8/8 DA) 8/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Below (0/8 DA) Median: 42.7% (0/8 DA above threshold)
Min/Max: 42.1% / 71.9% (8/8 DA, Voting / Total Eligible)
≥98% (≥5/8 DA)
Time Known Meets (8/8 DA) Median: 21.1d (8/8 DA above threshold)
Min/Max: 10.0d / 21.9d (8/8 DA, Voting / Total Eligible)
≥8 days (≥5/8 DA)
Bandwidth Below (0/8 DA) 1.8 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-304.0 Mbit/s (≥5/8 DA)
Exit Exit Policy Below (0/8 DA) Port 80: No | Port 443: No (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/8 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-04-14 22:45:08).

Capacity (Relay Reported)
Observed Bandwidth
1.84 Mbit/s
Advertised Bandwidth
1.64 Mbit/s
Rate Limit
1.64 Mbit/s
Burst Limit
4.10 Mbit/s
Total Data
4.5 TB (5 years)
1mo: 4.7 GB | 6mo: 78 GB | 1y: 794 GB | 5y: 4.5 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-04-14 22:45:08

Measured By
4/5 Bandwidth Authorities
Not measured by: gabelmoo
Median Measurement
956.0 bit/s
Min / Max
112 bit/s / 1632 bit/s
Deviation
1520 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (2th pctl) | Guard: N/A | Middle: 0.0000% (2th pctl) | Exit: N/A

Uptime Metrics
Current Status
UP 3d 13h 39m ago
Overall Uptime (1M/6M/1Y/5Y)
41.6%/46.3%/72.5%/87.5%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (41.6%/46.3%/72.5%/87.5%)
Hibernating
No
Timestamps
First Seen
1w 1d 45m ago (2026-04-06 23:00:00)
Last Seen
5h 45m 49s ago (2026-04-14 18:00:00)
Last Restarted
3d 13h 39m ago (2026-04-11 10:06:13)
Last Changed Address
2026-04-06 23:00:00
[Warning] OVERLOADED — General overload at 2026-04-14 09:00 UTC
General Overload (from /details)
Status
Reported
When
2026-04-14 09:00 UTC (14 hours ago)

OOM killer, onionskin queue saturation, or TCP port exhaustion. Flag remains 72h after last event (Tor spec 328).

File Descriptor Exhaustion (from /bandwidth)
Status
Not Reported
Rate Limits (from /bandwidth)

No rate limit data from /bandwidth endpoint.

Recommendations
  • Check CPU/memory: htop
  • Review MaxMemInQueues in torrc

Operator Identity

Source: AROI Validation API — 2026-04-14 15:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
admin@centurion.link
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1
BB4465B1EF3E765068C8D7231E316EF68B571499 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

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

DNS Health
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
reject: 
  1-65535
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Tue, 14 Apr 2026 23:45:47 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-04-14 22:45: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) No N No
dannenberg (DE) Yes Yes No N Yes Running, Valid, V2Dir, Fast 1.8 Mbit/s | 816.0 Kbit/s 1.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 42.8% | 98% 21.1d | 8d 3.6d | 32.5d 3.6d | 7.1d 42.8% | 98.0% 21.1d | 1.0d 2026-04-14 10:14:03 1632 bit/s
dizum (NL) Yes Yes No N Yes Running, Valid, V2Dir, Fast 1.8 Mbit/s | 816.0 Kbit/s 1.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 42.6% | 98% 21.7d | 8d 3.6d | 42.0d 3.6d | 7.0d 42.6% | 98.0% 21.7d | 1.0d 2026-04-14 10:14:03 1632 bit/s
faravahar (US) Yes Yes No N Yes Running, Valid, V2Dir, Fast 1.8 Mbit/s | 816.0 Kbit/s 1.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 42.7% | 98% 21.1d | 8d 3.6d | 59.3d 3.6d | 7.2d 42.7% | 98.0% 21.1d | 1.0d 2026-04-14 10:14:03 1632 bit/s
gabelmoo (DE) Yes Yes No Y Yes Running, Valid, V2Dir 1.8 Mbit/s | 816.0 Kbit/s 1.8 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 42.1% | 98% 21.9d | 8d 3.6d | 59.3d 3.6d | 7.3d 42.1% | 98.0% 21.9d | 1.0d 2026-04-14 10:14:03 1632 bit/s
longclaw (US) Yes Yes No Y Yes Running, Valid, V2Dir 1.8 Mbit/s | 816.0 Kbit/s 1.8 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 42.7% | 98% 20.2d | 8d 3.4d | 59.0d 3.6d | 7.2d 42.7% | 98.0% 20.2d | 1.0d 2026-04-14 10:14:03 216 bit/s
maatuska (SE) Yes Yes No Y Yes Running, Valid, V2Dir 1.8 Mbit/s | 816.0 Kbit/s 1.8 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 42.8% | 98% 21.0d | 8d 3.6d | 59.0d 3.6d | 7.0d 42.8% | 98.0% 21.0d | 1.0d 2026-04-14 10:14:03 128 bit/s
moria1 (US) Yes Yes No Y Yes Running, Valid, V2Dir, Stable 1.8 Mbit/s | 8.4 Mbit/s 1.8 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 71.9% | 98% 10.0d | 8d 12550.1d | 317.9d 3.6d | 8.0d 71.9% | 98.0% 10.0d | 9.9d 2026-04-14 10:14:03 280 bit/s
tor26 (AT) Yes Yes No Y Yes Running, Valid, V2Dir 1.8 Mbit/s | 816.0 Kbit/s 1.8 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 42.7% | 98% 21.1d | 8d 3.6d | 58.8d 3.6d | 7.3d 42.7% | 98.0% 21.1d | 1.0d 2026-04-14 10:14:03 112 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.