View Relay "cryShell01"
Fingerprint: CD1D703E667366A5474E4FF6B1BE6D0C9178B2B0 |
Family: 2 relays
|
88EACE21E04C30749711DBFF2CF89265F691B... |
AS3209
|
Germany
|
Linux
- Consensus
- Not In Consensus (1/9 Directory Auths, need 5)
- BW Verified
- 1/7 BW Auths Measured 47 Kbit/s Median
- Stability
- Overloaded | DOWN 18h 7m 2s ago | UP 98% (1M)
- Reachability
- IPv4: 1/9 | v6: 1/9 (Directory Auths)
- BW Weight
- 0.00% of Network | 41 Mbit/s Observed By Relay
- Version
- 0.4.9.15 Recommended
Issues Detected:
-
Not in consensus
: Only 1/9 authorities voted for this relay (need 5)
Suggestion: Verify your relay is reachable from multiple geographic locations. Check firewall rules allow incoming connections on your ORPort from all directory authority IP addresses. -
IPv4 reachability issues
: Only 1/9 authorities can reach this relay
Suggestion: Authorities that cannot reach you: dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1, tor26. Check: 1) Firewall allows incoming TCP on ORPort, 2) No ISP-level blocking, 3) Tor is running and listening. Use 'nc -zv your-ip your-orport' from external hosts to test. -
Low bandwidth authority measurements
: Only 1/7 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities. -
General Overload Active
: Relay reported general overload at 2026-11-07 05:00 UTC. This indicates OOM killer invocation, onionskin queue saturation, or TCP port exhaustion.
Suggestion: Check CPU/memory with htop. Review logs for "out of memory" or "onionskins" warnings. Consider increasing MaxMemInQueues in torrc. Verify TCP ports available.
Addresses
- OR Address
-
ip-077-022-233-024.vkd68.pools.vodafone-ip.de
77.22.233.24:9001
[2a02:8109:111a:5300:55f:7a34:7863:8190]:9001
Reachability (Directory Authorities)
- IPv4
- 1/9
- IPv6
- 1/9
Location
- Country
-
Germany
- Interactive Map
- View in RouteFluxMap
Eligible Flags (0):
Running: 1/9 | Valid: 1/9 | V2Dir: 1/9 | Fast: 1/9 | Stable: 1/9 | HSDir: 1/9 | Guard: 1/9 | Exit: 0/9
Eligibility Flag Vote Details
| Flag | Metric | Status | Relay Value | Threshold Required |
|---|---|---|---|---|
| Running | IPv4 Reachability | Below (1/9 DA) | 1/9 authorities reached relay | ≥5/9 DA ORPort reachable |
| IPv6 Reachability | Partial (1/9 DA) | 1/9 tested authorities reached relay | ≥5/9 tested (majority) (≥5/9 DA) | |
| Valid | Descriptor | Partial (1/9 DA) | 1/9 authorities assigned Valid | Not blacklisted + valid descriptor (≥5/9 DA) |
| V2Dir | DirPort Available | Meets (1/9 DA) | Tunnelled: Yes (no DirPort) (R) | Tunnelled directory via ORPort or DirPort (≥5/9 DA) |
| Fast | Speed | Meets (9/9 DA) | 41.8 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: 6.3d (0/9 DA above threshold) | ≥3.2d - 11.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥6577.2d |
| Uptime | Meets (9/9 DA) | 7.3d (R) | ≥3.3d - 3.3d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Below (1/9 DA) | 1/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 (1/9 DA) | 1/9 DA assigned Stable | ≥3.2d - 11.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥6577.2d |
|
| Prereq: V2Dir | Below (1/9 DA) | 1/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Meets (1/9 DA) | Median: 99.1% (1/9 DA above threshold) | ≥98.0% (≥5/9 DA) | |
| Time Known | Below (1/9 DA) | Median: 15.4d (1/9 DA above threshold) | ≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.9d |
|
| Guard | Prereq: Fast | Below (1/9 DA) | 1/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 (1/9 DA) | 1/9 DA assigned Stable | ≥3.2d - 11.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥6577.2d |
|
| Prereq: V2Dir | Below (1/9 DA) | 1/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Meets (1/9 DA) | Median: 99.1% (1/9 DA above threshold) | ≥98% (≥5/9 DA) | |
| Time Known | Meets (1/9 DA) | Median: 15.4d (1/9 DA above threshold) | ≥8 days (≥5/9 DA) | |
| Bandwidth | Meets (9/9 DA) | 41.8 Mbit/s (R) | ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-280.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-11-08 08:01:41).
Capacity (Relay Reported)
- Observed Bandwidth
- 41.82 Mbit/s
- Advertised Bandwidth
- 41.82 Mbit/s
- Rate Limit
- 41.94 Mbit/s
- Burst Limit
- 67.11 Mbit/s
- Total Data
-
23 TB
(6 months)
1mo: 11 TB | 6mo: 23 TB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-08 08:01:41
- Measured By
-
1/7
Bandwidth Authorities
Not measured by: dannenberg, faravahar, gabelmoo, longclaw, moria1, tor26 - Median Measurement
- 47.2 Kbit/s
- Min / Max
- 47.2 Kbit/s / 47.2 Kbit/s
Network Participation:
Consensus Weight:
0.0022% of network
(31th pctl)
|
Guard:
N/A |
Middle:
N/A |
Exit:
N/A
Uptime Metrics
- Current Status
- DOWN 18h 7m 2s ago
- Overall Uptime (1M/6M/1Y/5Y)
- 98.9%/99.4%/0.0%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- 85.1%/90.4%/—/—
- Hibernating
- No
Timestamps
- First Seen
- 1mo 3w 6d ago (2026-09-11 10:00:00)
- Last Seen
- 18h 7m 2s ago (2026-11-07 14:00:00)
- Last Restarted
- 1w 7h 59m ago (2026-11-01 00:07:39)
- Last Changed Address
- 2026-09-11 10:00:00
[Warning] OVERLOADED
— General overload at 2026-11-07 05:00 UTC
General Overload (from /details)
- Status
- Reported
- When
- 2026-11-07 05:00 UTC (1 days ago)
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)
No rate limit data from /bandwidth endpoint.
Recommendations
- Check CPU/memory:
htop - Review
MaxMemInQueuesin torrc
Operator Identity
Source: AROI Validation API — 2026-11-07 23:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- 88EACE21E04C30749711DBFF2CF89265F691B280 cryShell <kx@cryshell.com>
Family Configuration
- Family Support
- Happy Families (2) — Has family-cert in server descriptor (guide) | View Full Family (2)
Happy Families (family-cert)
- Effective Members: 2
09587B9DE31CAAE07CDCDDB203D3D0153FE02D73 CD1D703E667366A5474E4FF6B1BE6D0C9178B2B0 (this relay)
MyFamily (legacy declarations) — none
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Sun, 08 Nov 2026 08:06:52 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-08 08:01:41).
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 | v6 | 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 | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Guard | 41.8 Mbit/s | 816.0 Kbit/s | 41.8 Mbit/s | 184.0 Mbit/s OR 16.0 Mbit/s | 99.1% | 98% | 15.4d | 8d | 6.3d | 9.7d | 7.3d | 5.7d | 99.1% | 98.0% | 15.4d | 1.0d | 2026-11-06 06:09:40 | 47.2 Kbit/s |
| dannenberg (DE) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — | — | — |
| dizum (NL) | No | — | — | — | N | No | — | — | — | — | — | — | — | — | — | — | — | — |
| faravahar (US) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — | — | — |
| gabelmoo (DE) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — | — | — |
| longclaw (US) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — | — | — |
| maatuska (SE) | No | — | — | — | N | No | — | — | — | — | — | — | — | — | — | — | — | — |
| moria1 (US) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — | — | — |
| tor26 (AT) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — | — | — |
— = 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.
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.
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.