View Relay "casaholiday"

Fingerprint: 1523C502A9754B6B42CCA5EB402A833CFF0E402D | Family: 1 relay | aholiday@yahoo.com | AS23033 | United States of America | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, Stable (3)
BW Verified
5/6 BW Auths Measured 104 bit/s Median
Stability
Overloaded | UP 1w 3d 22h ago | UP 100% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
11y 11mo 2w ago
BW Weight
0.00% of Network | 940 Kbit/s Observed By Relay
Version
0.4.9.5 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: 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.
  • 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 V2Dir (tunnelled-dir-server) : HSDir requires the relay to support tunnelled directory requests (V2Dir flag). This relay is missing V2Dir — the descriptor likely does not include tunnelled-dir-server, usually because DirCache 0 is set in torrc.
    Suggestion: Remove DirCache 0 from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includes tunnelled-dir-server. You can check with: grep tunnelled-dir-server /var/lib/tor/cached-descriptors
  • 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.
  • Write Bandwidth Limit Hit : Write rate limit (2 Mbit/s) was hit 2 times. Relay is throttling outbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more upload capacity.
  • Read Bandwidth Limit Hit : Read rate limit (2 Mbit/s) was hit 187 times. Relay is throttling inbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more download capacity.
Notes:
  • Rate Limit Configuration: Configured limits: Rate=2 Mbit/s, Burst=3 Mbit/s. Limits hit: Write=2, Read=187.

Connectivity and Location

Addresses
OR Address
209.90.224.5:39001
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
AS23033
AS Name
Wowrack.com (BGP.tools)
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Flags and Eligibility

Current Flags (3): Running, Valid, Stable
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 4/9 | Stable: 9/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 Below (0/9 DA) No DirPort, no tunnelled-dir-server (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 940.8 Kbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Partial (8/9 DA) Median: 88.2d (9/9 DA above threshold)
Min/Max: 86.5d / 104.8d (9/9 DA, Voting / Total Eligible)		 ≥11.3d - 55.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥347.6d
Uptime Below (0/9 DA) 10.9d (R) ≥12.0d - 14.4d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (4/9 DA) 4/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 Meets (9/9 DA) 9/9 DA assigned Stable ≥11.3d - 55.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥347.6d
Prereq: V2Dir Below (0/9 DA) 0/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: 100.0% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 88.1d (9/9 DA above threshold)
Min/Max: 9.5d / 88.6d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Below (4/9 DA) 4/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 Meets (9/9 DA) 9/9 DA assigned Stable ≥11.3d - 55.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥347.6d
Prereq: V2Dir Below (0/9 DA) 0/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: 100.0% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 88.1d (9/9 DA above threshold)
Min/Max: 9.5d / 88.6d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 940.8 Kbit/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 14:45:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
940.76 Kbit/s
Advertised Bandwidth
819.20 Kbit/s
Rate Limit
819.20 Kbit/s
Burst Limit
1.64 Mbit/s
Total Data
1.8 TB (5 years)
1mo: 2.8 GB | 6mo: 187 GB | 1y: 571 GB | 5y: 1.8 TB
Measurement (Directory Authority Verified)

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

Measured By
5/6 Bandwidth Authorities
Not measured by: longclaw
Median Measurement
104 bit/s
Min / Max
24 bit/s / 816 bit/s
Deviation
792 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (1th pctl) | Guard: N/A | Middle: 0.0000% (1th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 1w 3d 22h ago
Overall Uptime (1M/6M/1Y/5Y)
100.0%/74.8%/58.9%/62.3%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (100.0%/74.8%/58.9%/62.3%)
Hibernating
No
Timestamps
First Seen
11y 11mo 2w ago (2014-04-07 12:00:00)
Last Seen
2h 16m 23s ago (2026-03-15 13:00:00)
Last Restarted
1w 3d 22h ago (2026-03-04 17:07:01)
Last Changed Address
2023-03-24 08:00:00
[Warning] OVERLOADED — Rate limits hit W:2 R:187 (limit: 2 Mbit/s)
General Overload (from /details)
Status
Not Reported

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)
Rate Limit
2.05 Mbit/s
Burst Limit
3.28 Mbit/s
Write Limit Hit
2 times
Read Limit Hit
187 times
Last Reported
23 hours ago
Recommendations
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic

Operator and Family

Operator Identity

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

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

Software and Version

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

Exit Health & Policy

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 15:16:21 GMT.

Consensus Evaluation

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

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 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, Stable 940.8 Kbit/s | 816.0 Kbit/s 940.8 Kbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 88.1d | 8d 88.0d | 59.7d 10.9d | 13.6d 100.0% | 98.0% 88.1d | 1.0d 2026-03-14 16:25:35 104 bit/s
dannenberg (DE) Yes Yes No — N Yes Running, Valid, Fast, Stable 940.8 Kbit/s | 816.0 Kbit/s 940.8 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 87.7d | 8d 87.6d | 11.3d 10.9d | 14.3d 100.0% | 98.0% 87.7d | 1.0d 2026-03-14 16:25:35 816 bit/s
dizum (NL) Yes Yes No — N Yes Running, Valid, Fast, Stable 940.8 Kbit/s | 816.0 Kbit/s 940.8 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 88.6d | 8d 88.5d | 45.8d 10.9d | 12.0d 100.0% | 98.0% 88.6d | 1.0d 2026-03-14 16:25:35 816 bit/s
faravahar (US) Yes Yes No — N Yes Running, Valid, Fast, Stable 940.8 Kbit/s | 816.0 Kbit/s 940.8 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 88.0d | 8d 87.9d | 55.1d 10.9d | 14.5d 100.0% | 98.0% 88.0d | 1.0d 2026-03-14 16:25:35 816 bit/s
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, Stable 940.8 Kbit/s | 816.0 Kbit/s 940.8 Kbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 88.6d | 8d 88.5d | 61.4d 10.9d | 14.4d 100.0% | 98.0% 88.6d | 1.0d 2026-03-14 16:25:35 24 bit/s
longclaw (US) Yes Yes No — Y Yes Running, Valid, Fast, Stable 940.8 Kbit/s | 816.0 Kbit/s 940.8 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 86.5d | 8d 86.5d | 62.0d 10.9d | 14.5d 100.0% | 98.0% 86.5d | 1.0d 2026-03-14 16:25:35 816 bit/s
maatuska (SE) Yes Yes No — Y Yes Running, Valid, Stable 940.8 Kbit/s | 816.0 Kbit/s 940.8 Kbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 88.2d | 8d 88.2d | 40.2d 10.9d | 14.3d 100.0% | 98.0% 88.2d | 1.0d 2026-03-14 16:25:35 24 bit/s
moria1 (US) Yes Yes No — Y Yes Running, Valid, Stable 940.8 Kbit/s | 8.4 Mbit/s 940.8 Kbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 9.5d | 8d 104.8d | 347.6d 10.9d | 15.5d 100.0% | 98.0% 9.5d | 9.8d 2026-03-14 16:25:35 80 bit/s
tor26 (AT) Yes Yes No — Y Yes Running, Valid, Stable 940.8 Kbit/s | 816.0 Kbit/s 940.8 Kbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 88.6d | 8d 88.5d | 55.7d 10.9d | 14.5d 100.0% | 98.0% 88.6d | 1.0d 2026-03-14 16:25:35 24 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.