View Relay "CatButler"

Fingerprint: 4B0E7A0210A75278C4058A6F947369EBF27791A3 | Family: 1 relay | relay_runner8@riseup.net | AS14061 | Germany | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
5/6 BW Auths Measured 79 Kbit/s Median
Stability
Not Overloaded | UP 1w 2d 5h ago | UP 95% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
BW Weight
0.01% of Network | 79 Mbit/s Observed By Relay
Version
0.4.9.5 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 84.3% 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 84.3% 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
159.65.125.72:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS14061
AS Name
DigitalOcean, LLC (BGP.tools)
AS Rarity
Emerging (score: 1/5, 0.57% consensus weight, 67 operators)

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 0/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) 79.6 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.5d (1/9 DA above threshold)
Min/Max: 0.3d / 19492.6d (9/9 DA, Voting / Total Eligible)
≥11.3d - 53.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥366.1d
Uptime Below (0/9 DA) 9.2d (R) ≥9.8d - 12.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 ≥11.3d - 53.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥366.1d
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: 90.6% (0/9 DA above threshold)
Min/Max: 83.4% / 92.9% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 10.4d (9/9 DA above threshold)
Min/Max: 9.8d / 10.9d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
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 ≥11.3d - 53.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥366.1d
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: 90.6% (0/9 DA above threshold)
Min/Max: 83.4% / 92.9% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 10.4d (9/9 DA above threshold)
Min/Max: 9.8d / 10.9d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 79.6 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 Below (0/9 DA) Port 80: No | Port 443: No (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 20:45:07).

Capacity (Relay Reported)
Observed Bandwidth
79.61 Mbit/s
Advertised Bandwidth
79.61 Mbit/s
Rate Limit
83.89 Mbit/s
Burst Limit
83.89 Mbit/s
Total Data
808 TB (5 years)
1mo: 9.7 TB | 6mo: 71 TB | 1y: 176 TB | 5y: 808 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-15 20:45:07

Measured By
5/6 Bandwidth Authorities
Not measured by: longclaw
Median Measurement
79.6 Kbit/s
Min / Max
64.8 Kbit/s / 160.0 Kbit/s
Deviation
95.2 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0081% of network (60th pctl) | Guard: N/A | Middle: 0.0244% (85th pctl) | Exit: N/A

Uptime Metrics
Current Status
UP 1w 2d 5h ago
Overall Uptime (1M/6M/1Y/5Y)
95.9%/99.1%/99.4%/98.7%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (95.9%/99.1%/99.4%/98.7%)
Hibernating
No
Timestamps
First Seen
3y 1mo 3w ago (2023-01-18 00:00:00)
Last Seen
1h 46m 38s ago (2026-03-15 19:00:00)
Last Restarted
1w 2d 5h ago (2026-03-06 15:03:34)
Last Changed Address
2024-01-29 19:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator Identity

Source: AROI Validation API — 2026-03-15 13:00 UTC

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

Platform
Linux — Tor 0.4.9.5 on Linux
Version
0.4.9.5Recommended
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 Sun, 15 Mar 2026 20:46:37 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-03-15 20:45:07).

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 No Y Yes Running, Valid, V2Dir, Fast 79.6 Mbit/s | 816.0 Kbit/s 79.6 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 84.3% | 98% 10.4d | 8d 0.3d | 57.0d 9.2d | 11.9d 84.3% | 98.0% 10.4d | 1.0d 2026-03-15 14:09:18 64.8 Kbit/s
dannenberg (DE) Yes Yes No N Yes Running, Valid, V2Dir, Fast 79.6 Mbit/s | 816.0 Kbit/s 79.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 83.4% | 98% 10.2d | 8d 0.3d | 11.3d 9.2d | 12.7d 83.4% | 98.0% 10.2d | 1.0d 2026-03-15 14:09:18 79.6 Kbit/s
dizum (NL) Yes Yes No N Yes Valid, V2Dir, Fast 79.6 Mbit/s | 816.0 Kbit/s 79.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 86.9% | 98% 10.5d | 8d 0.3d | 43.2d 9.2d | 9.8d 86.9% | 98.0% 10.5d | 1.0d 2026-03-15 14:09:18 79.6 Kbit/s
faravahar (US) Yes Yes No N Yes Running, Valid, V2Dir, Fast 79.6 Mbit/s | 816.0 Kbit/s 79.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 88.2% | 98% 10.3d | 8d 0.4d | 53.3d 9.2d | 12.8d 88.2% | 98.0% 10.3d | 1.0d 2026-03-15 14:09:18 79.6 Kbit/s
gabelmoo (DE) Yes Yes No Y Yes Running, Valid, V2Dir, Fast 79.6 Mbit/s | 816.0 Kbit/s 79.6 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 92.9% | 98% 10.9d | 8d 0.6d | 58.4d 9.2d | 12.7d 92.9% | 98.0% 10.9d | 1.0d 2026-03-15 14:09:18 144.0 Kbit/s
longclaw (US) Yes Yes No Y Yes Running, Valid, V2Dir, Fast 79.6 Mbit/s | 816.0 Kbit/s 79.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 92.4% | 98% 9.8d | 8d 0.6d | 61.1d 9.2d | 12.8d 92.4% | 98.0% 9.8d | 1.0d 2026-03-15 14:09:18 79.6 Kbit/s
maatuska (SE) Yes Yes No Y Yes Running, Valid, V2Dir, Fast 79.6 Mbit/s | 816.0 Kbit/s 79.6 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 91.6% | 98% 10.9d | 8d 0.5d | 40.8d 9.2d | 12.7d 91.6% | 98.0% 10.9d | 1.0d 2026-03-15 14:09:18 128.0 Kbit/s
moria1 (US) Yes Yes No Y Yes Running, Valid, V2Dir, Fast, Stable 79.6 Mbit/s | 8.4 Mbit/s 79.6 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 90.6% | 98% 9.9d | 8d 19492.6d | 366.1d 9.2d | 15.4d 90.6% | 98.0% 9.8917d | 9.8919d 2026-03-15 14:09:18 88.0 Kbit/s
tor26 (AT) Yes Yes No Y Yes Running, Valid, V2Dir, Fast 79.6 Mbit/s | 816.0 Kbit/s 79.6 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 91.4% | 98% 10.8d | 8d 0.5d | 53.9d 9.2d | 12.8d 91.4% | 98.0% 10.8d | 1.0d 2026-03-15 14:09:18 160.0 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.