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 (2)
BW Verified
5/7 BW Auths Measured 40 Kbit/s Median
Stability
Overloaded | UP 10h 45m 10s ago | UP 88% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
1mo 2w 1d ago
BW Weight
0.00% of Network | 1 Mbit/s Observed By Relay
Version
0.4.9.13 Recommended
Issues Detected:
  • Not getting the Fast flag : Only 3/9 authorities vote Fast (5 needed). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 32.0 Kbit/s – 104.0 Kbit/s, below the Fast threshold (816.0 Kbit/s; moria1: 8.4 Mbit/s). faravahar judged it by bandwidth not shown in the votes. Its consensus weight, the median of the 5 bandwidth-scanner measurements, is 40.0 Kbit/s.
    Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports. A low measurement means the scanners see your relay underperforming compared with other relays that report a similar speed. Clients only build circuits through Fast relays, so a relay near the threshold can gain and lose most of its traffic from one hourly consensus to the next.
  • Guard: requires Fast flag : Guard flag requires having the Fast flag first
    Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports.
  • 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 : 0/9 authorities credit this relay with enough bandwidth for Guard (5 needed): at least 16.8 Mbit/s (AuthDirGuardBWGuarantee) or a place in their top 25% (80.0 Mbit/s – 272.0 Mbit/s). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 32.0 Kbit/s – 104.0 Kbit/s. dizum, longclaw and maatuska used the relay-reported 816.0 Kbit/s.
    Suggestion: Guard requires a bandwidth of at least AuthDirGuardBWGuarantee (16.8 Mbit/s by default) or one in the top 25% of relays, judged by each authority the same way as for Fast. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx.
  • Guard: WFU below threshold : Weighted Fractional Uptime 85.1% 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: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports.
  • 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: 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 1 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 202 times. Relay is throttling inbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more download capacity.
Notes:

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 (2): Running, Valid
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 3/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 Below (0/9 DA) No DirPort, no tunnelled-dir-server (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Below (3/9 DA) 32.0 Kbit/s – 104.0 Kbit/s (5 DA measured)
816.0 Kbit/s (3 DA relay-reported)
faravahar: not published		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (1/9 DA) Median: 1.8d (1/9 DA above threshold)
Min/Max: 1.8d / 17288.5d (9/9 DA, Voting / Total Eligible)		 ≥6.2d - 8.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10360.2d
Uptime Below (0/9 DA) 0.4d (R) ≥5.7d - 5.9d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (3/9 DA) 3/9 DA assigned Fast
32.0 Kbit/s – 104.0 Kbit/s (5 DA measured)
816.0 Kbit/s (3 DA relay-reported)
faravahar: not published		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/9 DA) 1/9 DA assigned Stable ≥6.2d - 8.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10360.2d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Below (0/9 DA) 0.4d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥10.0d Time Known
Guard Prereq: Fast Below (3/9 DA) 3/9 DA assigned Fast
32.0 Kbit/s – 104.0 Kbit/s (5 DA measured)
816.0 Kbit/s (3 DA relay-reported)
faravahar: not published		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/9 DA) 1/9 DA assigned Stable ≥6.2d - 8.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10360.2d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 85.5% (0/9 DA above threshold)
Min/Max: 84.9% / 86.9% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 12.2d (9/9 DA above threshold)
Min/Max: 10.1d / 12.4d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 32.0 Kbit/s – 104.0 Kbit/s (5 DA measured)
816.0 Kbit/s (3 DA relay-reported)
faravahar: not published		 ≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-272.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-10-18 21:45:05).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
1.24 Mbit/s
Advertised Bandwidth
819.20 Kbit/s
Rate Limit
819.20 Kbit/s
Burst Limit
1.64 Mbit/s
Total Data
52 GB (6 months)
1mo: 29 GB | 6mo: 52 GB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-18 21:45:05

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight
40.0 Kbit/s (median of 5 measurements)
Measured Min / Max
32.0 Kbit/s / 104.0 Kbit/s
Deviation
72.0 Kbit/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
History
Throughput and write/read, last 6 months Throughput and write/read, last 30 days
1M 6M

Uptime and Stability

Uptime Metrics
Current Status
UP 10h 45m 10s ago
Overall Uptime (1M/6M/1Y/5Y)
88.7%/73.1%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (88.7%/73.1%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
1mo 2w 1d ago (2026-09-03 17:00:00)
Last Seen
1h 45m 10s ago (2026-10-18 21:00:00)
Last Restarted
10h 45m 10s ago (2026-10-18 12:00:00)
Last Changed Address
2026-09-03 17:00:00
[Warning] OVERLOADED — Rate limits hit W:1 R:202 (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
410 KB
Write Limit Hit
1 times
Read Limit Hit
202 times
Last Reported
15 hours ago
Recommendations
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic
History
Uptime, last 6 months Uptime, last 30 days
1M 6M

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-10-18 15: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.13 on Linux
Version
0.4.9.13 — 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, 18 Oct 2026 22:45:09 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-10-18 21:45:05).

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 (BW|T) Guard BW (BW|Threshold) Guard WFU (M|T) Guard TK (M|T) Stable MTBF (M|T) Stable Uptime (Relay|T) Desc Published Cons Wt (Authority)
bastet (US) Yes Yes No — Y Yes Running, Valid 104.0 Kbit/s (M) | 816.0 Kbit/s 104.0 Kbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 85.1% | 98% 12.4d | 8d 1.9d | 8.9d 0.4d | 5.7d 2026-10-18 12:01:00 104.0 Kbit/s (M)
dannenberg (DE) Yes Yes No — Y Yes Running, Valid 40.0 Kbit/s (M) | 816.0 Kbit/s 40.0 Kbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 85.5% | 98% 12.3d | 8d 1.8d | 6.2d 0.4d | 6.1d 2026-10-18 12:01:00 40.0 Kbit/s (M)
dizum (NL) Yes Yes No — N Yes Running, Valid, Fast 816.0 Kbit/s (R) | 816.0 Kbit/s 816.0 Kbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 84.9% | 98% 12.4d | 8d 1.8d | 8.8d 0.4d | 5.7d 2026-10-18 12:01:00 816.0 Kbit/s (R)
faravahar (US) Yes Yes No — Y Yes Running, Valid not published | 816.0 Kbit/s not published | 264.0 Mbit/s OR 16.8 Mbit/s 85.2% | 98% 12.2d | 8d 1.8d | 9.2d 0.4d | 6.6d 2026-10-18 12:01:00 816.0 Kbit/s (R)
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid 40.0 Kbit/s (M) | 816.0 Kbit/s 40.0 Kbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 86.4% | 98% 12.3d | 8d 1.9d | 8.9d 0.4d | 6.0d 2026-10-18 12:01:00 40.0 Kbit/s (M)
longclaw (US) Yes Yes No — Y Yes Running, Valid, Fast 816.0 Kbit/s (R) | 816.0 Kbit/s 816.0 Kbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 86.2% | 98% 12.1d | 8d 1.8d | 9.1d 0.4d | 5.7d 2026-10-18 12:01:00 816.0 Kbit/s (R)
maatuska (SE) Yes Yes No — N Yes Running, Valid, Fast 816.0 Kbit/s (R) | 816.0 Kbit/s 816.0 Kbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 85.2% | 98% 12.0d | 8d 1.9d | 8.8d 0.4d | 5.7d 2026-10-18 12:01:00 816.0 Kbit/s (R)
moria1 (US) Yes Yes No — Y Yes Running, Valid, Stable 88.0 Kbit/s (M) | 8.4 Mbit/s 88.0 Kbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 86.9% | 98% 10.1d | 8d 17288.5d | 10360.2d 0.4d | 5.9d 2026-10-18 12:01:00 88.0 Kbit/s (M)
tor26 (AT) Yes Yes No — Y Yes Running, Valid 32.0 Kbit/s (M) | 816.0 Kbit/s 32.0 Kbit/s (M) | 264.0 Mbit/s OR 16.8 Mbit/s 85.9% | 98% 12.2d | 8d 1.8d | 9.2d 0.4d | 6.2d 2026-10-18 12:01:00 32.0 Kbit/s (M)

— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known • Bandwidth source: (M) bandwidth-scanner measurement, (R) relay-reported, (U) unmeasured, counted as 0

Bandwidth Values Explained:
Measured (M) = An authority's bandwidth-scanner measurement of your relay (Measured= in its vote). An authority that has one uses it for the Fast and Guard flags, and the consensus weight is the median of these measurements when 3 or more authorities have one.
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (Bandwidth= in every vote). An authority without a measurement uses it for flags, unless it has measurements for enough other relays (ignoring-advertised-bws=1); then your relay counts as 0 (U). It sets the consensus weight only when fewer than 3 authorities measured the relay, capped at 20 KB/s (maxunmeasuredbw) while 3 or more authorities publish measurements.
Not published = The authority has no measurement of your relay in its vote and ignores relay-reported bandwidth, yet it voted Fast or its vote has no measurements at all: it judges your relay by a measurement kept from an earlier bandwidth file (0 if none), which its vote doesn't show.
Why different? A low measurement means the bandwidth scanners see your relay underperforming compared with other relays that report a similar speed. Votes list both values in kilobytes per second. Rules: Assigning flags in a vote, Computing a consensus.
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.