View Relay "CasjaysDevExit"

Fingerprint: 786739676ADA1A35E1082B3DE28A08E1C86ED9DC | Family: 1 relay | tor-admin@tor.casjay.nl | AS142036 | United States of America | Linux

Health Status

Consensus
In Consensus (7/8 Directory Auths)
Flags
Running, Valid, Exit (3)
DNS Health
Not Tested (via exitdnshealth.1aeo.com)
BW Verified
4/5 BW Auths Measured 8 bit/s Median
Stability
Not Overloaded | UP 9h 11m 37s ago
Reachability
IPv4: 7/9 (Directory Auths)
First Seen
6h 45m 47s ago
BW Weight
0.00% of Network | 0 Kbit/s Observed By Relay
Version
0.4.8.22 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: 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: Time Known below threshold : Time Known 0.3 days is below 8 days requirement (7.7 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 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 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
  • HSDir: Time Known below threshold : Time Known 6.9 hours below 25 hours (dir-spec default)
    Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
  • 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.
Notes:
  • Partial IPv4 reachability: 7/9 authorities can reach this relay

Connectivity and Location

Addresses
OR Address
pihole.casjay.nl
82.29.128.145:57006
Exit Address
82.29.128.145
Reachability (Directory Authorities)
IPv4
7/9
Location
Country
United States of America United States of America
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS142036
AS Name
Hosteons Pte. Ltd. (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 2 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, Exit
Eligible Flags (4): Running: 7/8 | Valid: 7/8 | V2Dir: 7/8 | Fast: 0/8 | Stable: 0/8 | HSDir: 0/8 | Guard: 0/8 | Exit: 7/8
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (7/8 DA) 7/8 authorities reached relay ≥5/8 DA ORPort reachable
IPv6 Reachability Below (0/1 DA) 0/1 tested authorities reached relay ≥1/1 tested (majority) (≥1/1 DA)
Valid Descriptor Meets (7/8 DA) 7/8 authorities assigned Valid Not blacklisted + valid descriptor (≥5/8 DA)
V2Dir DirPort Available Below (0/8 DA) No DirPort, no tunnelled-dir-server (R) Tunnelled directory via ORPort or DirPort (≥5/8 DA)
Fast Speed Below (0/8 DA) 0 bit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (0/8 DA) Median: 0.3d (0/8 DA above threshold)
Min/Max: 0.3d / 0.3d (7/8 DA, Voting / Total Eligible)		 ≥16.6d - 58.6d (varies) (≥5/8 DA)
Uptime Below (0/8 DA) 0.4d (R) ≥10.4d - 10.7d (varies) (≥5/8 DA)
HSDir Prereq: Fast Below (0/8 DA) 0/8 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/8 DA) 0/8 DA assigned Stable ≥16.6d - 58.6d (varies) (≥5/8 DA)
Prereq: V2Dir Below (0/8 DA) 0/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Meets (7/8 DA) Majority: 100.0% (7/8 DA) ≥98.0% (≥5/8 DA)
Time Known Below (0/8 DA) Median: 0.3d (0/8 DA above threshold)
Min/Max: 0.3d / 0.3d (7/8 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/8 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (0/8 DA) 0/8 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/8 DA) 0/8 DA assigned Stable ≥16.6d - 58.6d (varies) (≥5/8 DA)
Prereq: V2Dir Below (0/8 DA) 0/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Meets (7/8 DA) Majority: 100.0% (7/8 DA) ≥98% (≥5/8 DA)
Time Known Below (0/8 DA) (need 7.7 more days) Median: 0.3d (0/8 DA above threshold)
Min/Max: 0.3d / 0.3d (7/8 DA, Voting / Total Eligible)		 ≥8 days (≥5/8 DA)
Bandwidth Below (0/8 DA) 0 bit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.0 Mbit/s (≥5/8 DA)
Exit Exit Policy Meets (7/8 DA) Port 80: Yes | Port 443: Yes (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/8 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-04-29 03:45:03).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
0.00 Kbit/s
Advertised Bandwidth
Unknown
Rate Limit
851.97 Kbit/s
Burst Limit
1.70 Mbit/s
Total Data
N/A
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-04-29 03:45:03

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

Uptime and Stability

Uptime Metrics
Current Status
UP 9h 11m 37s ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
N/A
Hibernating
No
Timestamps
First Seen
6h 45m 47s ago (2026-04-28 21:00:00)
Last Seen
1h 45m 47s ago (2026-04-29 02:00:00)
Last Restarted
9h 11m 37s ago (2026-04-28 18:34:10)
Last Changed Address
2026-04-28 21:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-04-28 20: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 
786739676ADA1A35E1082B3DE28A08E1C86ED9DC (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

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

Exit Health & Policy

DNS Health
Status
Not Tested
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 82.29.128.145:*
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, 29 Apr 2026 03:45:46 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-04-29 03:45:03).

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) No — — — N No — — — — — — — — — — —
dannenberg (DE) Yes Yes Yes — N Yes Running, Valid, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.3d | 8d 0.3d | 46.1d 0.4d | 10.7d 100.0% | 98.0% 0.3d | 1.0d 2026-04-28 19:54:27 —
dizum (NL) No — — — N No — — — — — — — — — — —
faravahar (US) Yes Yes Yes — N Yes Running, Valid, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.3d | 8d 0.3d | 58.6d 0.4d | 10.7d 100.0% | 98.0% 0.3d | 1.0d 2026-04-28 19:54:27 —
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.3d | 8d 0.3d | 56.9d 0.4d | 10.7d 100.0% | 98.0% 0.3d | 1.0d 2026-04-28 19:54:27 8 bit/s
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 248.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.3d | 8d 0.3d | 63.4d 0.4d | 10.7d 100.0% | 98.0% 0.3d | 1.0d 2026-04-28 19:54:27 —
maatuska (SE) Yes Yes Yes — Y Yes Running, Valid, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 328.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.3d | 8d 0.3d | 16.6d 0.4d | 10.6d 100.0% | 98.0% 0.3d | 1.0d 2026-04-28 19:54:27 8 bit/s
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, Exit 0 bit/s | 8.4 Mbit/s 0 bit/s | 224.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.3d | 8d 0.3d | 292.0d 0.4d | 11.8d 100.0% | 98.0% 0.3d | 9.9d 2026-04-28 19:54:27 8 bit/s
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.3d | 8d 0.3d | 59.3d 0.4d | 10.8d 100.0% | 98.0% 0.3d | 1.0d 2026-04-28 19:54:27 8 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.