View Relay "baiarenitzulera"

Fingerprint: 41E16D677F75DC72D31258D06130B618799742CF | Operator: ryan.eus v2 (1 relay) ⚠ Misconfigured | Family: 1 relay | url:ryan.eus/contacte proof:dns-rsa... | AS7029 | United States of America | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
4/7 BW Auths Measured 9 Kbit/s Median
Stability
Not Overloaded | UP 2d 7h 11m ago
Reachability
IPv4: 9/9 (Directory Auths)
BW Weight
0.00% of Network | 8 Mbit/s Observed By Relay
Version
0.4.9.8 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: bandwidth below threshold : Observed bandwidth 1.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: Time Known below threshold : Time Known 2.2 days is below 8 days requirement (5.8 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.
  • 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
h219.21.40.69.dynamic.ip.windstream.net
69.40.21.219:9151
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
United States of America United States of America
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS7029
AS Name
Windstream Communications LLC (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 2 operators)

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 5/9 | Stable: 0/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) 9.0 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 (0/9 DA) Median: 2.2d (0/9 DA above threshold)
Min/Max: 1.1d / 2.2d (9/9 DA, Voting / Total Eligible)
≥29.0d - 53.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥328.2d
Uptime Below (0/9 DA) 2.3d (R) ≥6.9d - 7.0d (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 (0/9 DA) 0/9 DA assigned Stable ≥29.0d - 53.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥328.2d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Majority: 100.0% (8/9 DA)
Min/Med/Max: 98.7% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 2.2d (0/9 DA above threshold)
Min/Max: 2.0d / 2.2d (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 (0/9 DA) 0/9 DA assigned Stable ≥29.0d - 53.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥328.2d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Majority: 100.0% (8/9 DA)
Min/Med/Max: 98.7% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 5.8 more days) Median: 2.2d (0/9 DA above threshold)
Min/Max: 2.0d / 2.2d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 9.0 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-320.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-06-13 07:15:08).

Capacity (Relay Reported)
Observed Bandwidth
8.95 Mbit/s
Advertised Bandwidth
8.95 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
N/A
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-06-13 07:15:08

Measured By
4/7 Bandwidth Authorities
Not measured by: bastet, dannenberg, tor26
Median Measurement
9.0 Kbit/s
Min / Max
8 bit/s / 9.0 Kbit/s
Deviation
8.9 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0001% of network (9th pctl) | Guard: N/A | Middle: 0.0004% (16th pctl) | Exit: N/A

Uptime Metrics
Current Status
UP 2d 7h 11m ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
2d 7h 15m ago (2026-06-11 01:00:00)
Last Seen
1h 15m 39s ago (2026-06-13 07:00:00)
Last Restarted
2d 7h 11m ago (2026-06-11 01:04:17)
Last Changed Address
2026-06-11 01:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator Identity

Source: AROI Validation API — 2026-06-13 00:00 UTC

AROI Domain (?)
ryan.eus
Operator Validation
Unvalidated
This Relay
Unvalidated
Error: DNS-RSA: Lookup failed, no TXT record answer for ryan.eus
Contact
url:ryan.eus/contacte proof:dns-rsa ciissversion:2
Family Configuration
Family Support
MyFamily Only (1) — Legacy only. Consider migrating to Happy Families.
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1
41E16D677F75DC72D31258D06130B618799742CF (this relay)
Alleged Member: 1
(they don't list you back)
CAC5CE9C4CC6925068FF24E5B365D0D6E9DED2F5
Indirect Members: 0
none

Platform
Linux — Tor 0.4.9.8 on Linux
Version
0.4.9.8Recommended
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 Sat, 13 Jun 2026 08:15:38 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-06-13 07: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 No Y Yes Running, Valid, V2Dir 9.0 Mbit/s | 816.0 Kbit/s 9.0 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.2d | 54.9d 2.3d | 7.8d 100.0% | 98.0% 2.2d | 1.0d 2026-06-12 21:21:37 9.0 Kbit/s
dannenberg (DE) Yes Yes No Y Yes Running, Valid, V2Dir, Fast 9.0 Mbit/s | 816.0 Kbit/s 9.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.2d | 30.0d 2.3d | 7.3d 100.0% | 98.0% 2.2d | 1.0d 2026-06-12 21:21:37 9.0 Kbit/s
dizum (NL) Yes Yes No N Yes Running, Valid, V2Dir, Fast 9.0 Mbit/s | 816.0 Kbit/s 9.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 98.7% | 98% 2.1d | 8d 1.1d | 32.2d 2.3d | 7.0d 98.7% | 98.0% 2.1d | 1.0d 2026-06-12 21:21:37 9.0 Kbit/s
faravahar (US) Yes Yes No N Yes Running, Valid, V2Dir, Fast 9.0 Mbit/s | 816.0 Kbit/s 9.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.2d | 50.8d 2.3d | 7.0d 100.0% | 98.0% 2.2d | 1.0d 2026-06-12 21:21:37 9.0 Kbit/s
gabelmoo (DE) Yes Yes No Y Yes Running, Valid, V2Dir 9.0 Mbit/s | 816.0 Kbit/s 9.0 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.2d | 53.4d 2.3d | 7.2d 100.0% | 98.0% 2.2d | 1.0d 2026-06-12 21:21:37 8 bit/s
longclaw (US) Yes Yes No Y Yes Running, Valid, V2Dir, Fast 9.0 Mbit/s | 816.0 Kbit/s 9.0 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.2d | 58.1d 2.3d | 7.0d 100.0% | 98.0% 2.2d | 1.0d 2026-06-12 21:21:37 5120 bit/s
maatuska (SE) Yes Yes No Y Yes Running, Valid, V2Dir, Fast 9.0 Mbit/s | 816.0 Kbit/s 9.0 Mbit/s | 320.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.2d | 29.0d 2.3d | 7.0d 100.0% | 98.0% 2.2d | 1.0d 2026-06-12 21:21:37 2400 bit/s
moria1 (US) Yes Yes No Y Yes Valid, V2Dir 9.0 Mbit/s | 8.4 Mbit/s 9.0 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.0d | 8d 2.2d | 328.2d 2.3d | 7.3d 100.0% | 98.0% 2.0d | 9.9d 2026-06-12 21:21:37 4080 bit/s
tor26 (AT) Yes Yes No Y Yes Running, Valid, V2Dir 9.0 Mbit/s | 816.0 Kbit/s 9.0 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.2d | 55.4d 2.3d | 6.9d 100.0% | 98.0% 2.2d | 1.0d 2026-06-12 21:21:37 9.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.