View Relay "CasjaysDevExit"

Fingerprint: A771385B8EAE7683F90050674D1250C3BB7A7B4E | Family: 1 relay | tor-admin@tor.casjay.nl | AS36352 | United States of America | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, Stable, Exit (4)
DNS Health
Relay Unreachable (failed last 3 scans) (via exitdnshealth.1aeo.com)
BW Verified
5/7 BW Auths Measured 56 bit/s Median
Stability
Not Overloaded | UP 3h 20m 21s ago | UP 17% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
5mo 1w 6d ago
BW Weight
0.00% of Network | 1 Mbit/s Observed By Relay
Version
0.4.8.21 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.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: Time Known below threshold : Time Known 5.1 days is below 8 days requirement (2.9 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.
  • 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.

Connectivity and Location

Addresses
OR Address
23.238.70.236:57006
Exit Address
23.238.70.236
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
AS36352
AS Name
HostPapa (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.16% consensus weight, 57 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, Stable, Exit
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 3/9 | Stable: 9/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 9/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) 1.4 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: 5.1d (0/9 DA above threshold)
Min/Max: 5.1d / 5.1d (9/9 DA, Voting / Total Eligible)		 ≥21.2d - 52.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥338.6d
Uptime Below (0/9 DA) 0.1d (R) ≥13.3d - 13.7d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (3/9 DA) 3/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 ≥21.2d - 52.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥338.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% (9/9 DA) ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 5.1d (0/9 DA above threshold)
Min/Max: 3.9d / 5.1d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (3/9 DA) 3/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 ≥21.2d - 52.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥338.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% (9/9 DA) ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 2.9 more days) Median: 5.1d (0/9 DA above threshold)
Min/Max: 3.9d / 5.1d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 1.4 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Meets (9/9 DA) Port 80: Yes | Port 443: Yes (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-05-27 08:45:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
1.36 Mbit/s
Advertised Bandwidth
851.97 Kbit/s
Rate Limit
851.97 Kbit/s
Burst Limit
1.70 Mbit/s
Total Data
62 GB (6 months)
1mo: 523 MB | 6mo: 62 GB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-05-27 08:45:07

Measured By
5/7 Bandwidth Authorities
Not measured by: bastet, dannenberg
Median Measurement
56 bit/s
Min / Max
8 bit/s / 848 bit/s
Deviation
840 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (2th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0000% (1th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 3h 20m 21s ago
Overall Uptime (1M/6M/1Y/5Y)
17.3%/32.9%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (17.3%/32.9%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
5mo 1w 6d ago (2025-12-15 06:00:00)
Last Seen
1h 45m 44s ago (2026-05-27 07:00:00)
Last Restarted
3h 20m 21s ago (2026-05-27 05:25:23)
Last Changed Address
2026-05-22 06:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-05-27 01:00 UTC

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

Software and Version

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

Exit Health & Policy

DNS Health
Status
Relay Unreachable (failed last 3 scans)
Error
Tor Circuit Error: Construction timed out
First Hop
Haxalicious (US) 90AAC6245388A9A9EC7050810775503004FE40BF
Exit Address Used
23.238.70.236
Tested: 2026-05-26 19:16:36 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  20-22
  43
  53
  80
  110
  143
  220
  443
  873
  989-995
  1293
  3690
  4321
  5222-5223
  8008
  8080
  8443
  8888
  9418
IPv6 Exit Policy Summary
None
Full Exit Policy
reject 0.0.0.0/8:*
reject 169.254.0.0/16:*
reject 127.0.0.0/8:*
reject 192.168.0.0/16:*
reject 10.0.0.0/8:*
reject 172.16.0.0/12:*
reject 23.238.70.236:*
accept *:20-21
accept *:22
accept *:43
accept *:53
accept *:80
accept *:110
accept *:143
accept *:220
accept *:443
accept *:873
accept *:989-995
accept *:1293
accept *:3690
accept *:4321
accept *:5222-5223
accept *:8008
accept *:8080
accept *:8443
accept *:8888
accept *:9418
reject *:*

Last fetch was at Wed, 27 May 2026 08:45:43 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-05-27 08: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 Yes — Y Yes Running, Valid, Stable, Exit 1.4 Mbit/s | 816.0 Kbit/s 1.4 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.1d | 8d 5.1d | 50.7d 0.1d | 13.3d 100.0% | 98.0% 5.1d | 1.0d 2026-05-27 07:33:07 848 bit/s
dannenberg (DE) Yes Yes Yes — Y Yes Running, Valid, Fast, Stable, Exit 1.4 Mbit/s | 816.0 Kbit/s 1.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.1d | 8d 5.1d | 46.5d 0.1d | 13.6d 100.0% | 98.0% 5.1d | 1.0d 2026-05-27 07:33:07 848 bit/s
dizum (NL) Yes Yes Yes — N Yes Running, Valid, Fast, Stable, Exit 1.4 Mbit/s | 816.0 Kbit/s 1.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.1d | 8d 5.1d | 21.2d 0.1d | 13.6d 100.0% | 98.0% 5.1d | 1.0d 2026-05-27 07:33:07 848 bit/s
faravahar (US) Yes Yes Yes — N Yes Running, Valid, Fast, Stable, Exit 1.4 Mbit/s | 816.0 Kbit/s 1.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.1d | 8d 5.1d | 52.1d 0.1d | 13.7d 100.0% | 98.0% 5.1d | 1.0d 2026-05-27 07:33:07 848 bit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, Stable, Exit 1.4 Mbit/s | 816.0 Kbit/s 1.4 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.1d | 8d 5.1d | 53.0d 0.1d | 13.8d 100.0% | 98.0% 5.1d | 1.0d 2026-05-27 07:33:07 32 bit/s
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, Stable, Exit 1.4 Mbit/s | 816.0 Kbit/s 1.4 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.1d | 8d 5.1d | 57.8d 0.1d | 13.7d 100.0% | 98.0% 5.1d | 1.0d 2026-05-27 07:33:07 56 bit/s
maatuska (SE) Yes Yes Yes — Y Yes Running, Valid, Stable, Exit 1.4 Mbit/s | 816.0 Kbit/s 1.4 Mbit/s | 328.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.1d | 8d 5.1d | 24.6d 0.1d | 13.5d 100.0% | 98.0% 5.1d | 1.0d 2026-05-27 07:33:07 32 bit/s
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, Stable, Exit 1.4 Mbit/s | 8.4 Mbit/s 1.4 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.9d | 8d 5.1d | 338.6d 0.1d | 14.1d 100.0% | 98.0% 3.9d | 9.9d 2026-05-27 07:33:07 8 bit/s
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, Stable, Exit 1.4 Mbit/s | 816.0 Kbit/s 1.4 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.1d | 8d 5.1d | 54.0d 0.1d | 13.7d 100.0% | 98.0% 5.1d | 1.0d 2026-05-27 07:33:07 32 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.