View Relay "skankhunt42de1"
Fingerprint: C570ADADA8EF3435B3743A505768FECAC93299B9 |
Operator: tor.skankhunt42.pw v3
(5 relays)
✓ Validated
|
Family: 1 relay
|
email:admin[]skankhunt42.pw... |
AS31898
|
United States of America
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- BW Verified
- 7/8 BW Auths Measured 72 Kbit/s Median
- Stability
- Overloaded | UP 4d 13h 37m ago | UP 89% (1M)
- Reachability
- IPv4: 9/9 | v6: 8/8 (Directory Auths)
- BW Weight
- 0.00% of Network | 48 Mbit/s Observed By Relay
- Version
- 0.4.9.11 Recommended
Issues Detected:
-
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: WFU below threshold
: Weighted Fractional Uptime 97.9% 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 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: WFU below threshold
: WFU 97.9% below 98% required for HSDir
Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency. -
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. -
General Overload Active
: Relay reported general overload at 2026-07-24 21: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
-
158.180.25.241:443
[2603:c020:8014:beef:0:178c:5783:1c4e]:443
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- 8/8 (1 don't test)
Location
- Country
-
United States of America
- Interactive Map
- View in RouteFluxMap
Eligible Flags (4):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 2/9 | HSDir: 1/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 |
| IPv6 Reachability | Meets (8/8 DA) | 8/8 tested authorities reached relay | ≥5/8 tested (majority) (≥5/8 DA) | |
| Valid | Descriptor | Meets (9/9 DA) | 9/9 authorities assigned Valid | Not blacklisted + valid descriptor (≥5/9 DA) |
| V2Dir | DirPort Available | Meets (9/9 DA) | Tunnelled: Yes (no DirPort) (R) | Tunnelled directory via ORPort or DirPort (≥5/9 DA) |
| Fast | Speed | Meets (9/9 DA) | 48.7 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 (1/9 DA) | Median: 4.0d (1/9 DA above threshold) Min/Max: 2.6d / 16307.4d (9/9 DA, Voting / Total Eligible) |
≥8.0d - 12.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥9298.7d |
| Uptime | Below (0/9 DA) | 4.6d (R) | ≥7.2d - 7.5d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Meets (9/9 DA) | 9/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 (2/9 DA) | 2/9 DA assigned Stable | ≥8.0d - 12.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥9298.7d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Below (2/9 DA) | Median: 97.8% (2/9 DA above threshold) Min/Max: 96.5% / 99.6% (9/9 DA, Voting / Total Eligible) |
≥98.0% (≥5/9 DA) | |
| Time Known | Meets (8/9 DA) | Median: 16.9d (8/9 DA above threshold) Min/Max: 7.8d / 19.3d (9/9 DA, Voting / Total Eligible) |
≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥10.0d |
|
| Guard | Prereq: Fast | Meets (9/9 DA) | 9/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 (2/9 DA) | 2/9 DA assigned Stable | ≥8.0d - 12.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥9298.7d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Below (2/9 DA) | Median: 97.8% (2/9 DA above threshold) Min/Max: 96.5% / 99.6% (9/9 DA, Voting / Total Eligible) |
≥98% (≥5/9 DA) | |
| Time Known | Meets (8/9 DA) | Median: 16.9d (8/9 DA above threshold) Min/Max: 7.8d / 19.3d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Meets (9/9 DA) | 48.7 Mbit/s (R) | ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-304.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-07-25 10:15:09).
Capacity (Relay Reported)
- Observed Bandwidth
- 48.65 Mbit/s
- Advertised Bandwidth
- 48.65 Mbit/s
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
-
30 TB
(1 year)
1mo: 6.0 TB | 6mo: 27 TB | 1y: 30 TB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-07-25 10:15:09
- Measured By
-
7/8
Bandwidth Authorities
Not measured by: bastet - Median Measurement
- 72.8 Kbit/s
- Min / Max
- 31.2 Kbit/s / 104.0 Kbit/s
- Deviation
- 72.8 Kbit/s [Warning] High variation
Network Participation:
Consensus Weight:
0.0046% of network
(50th pctl)
|
Guard:
N/A |
Middle:
0.0138% (71th pctl) |
Exit:
N/A
Uptime Metrics
- Current Status
- UP 4d 13h 37m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 89.7%/97.8%/97.5%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (89.7%/97.8%/97.5%/0.0%)
- Hibernating
- No
Timestamps
- First Seen
- 6mo 3w 3d ago (2026-01-01 17:00:00)
- Last Seen
- 1h 16m 26s ago (2026-07-25 10:00:00)
- Last Restarted
- 4d 13h 37m ago (2026-07-20 21:39:20)
- Last Changed Address
- 2026-04-06 23:00:00
[Warning] OVERLOADED
— General overload at 2026-07-24 21:00 UTC
General Overload (from /details)
- Status
- Reported
- When
- 2026-07-24 21:00 UTC (14 hours 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-07-25 03:00 UTC
- AROI Domain (?)
- tor.skankhunt42.pw
- Operator Validation
- Validated (5/5 relays)
- This Relay
- Validated (uri-familyid-ed25519)
- Contact
- email:admin[]skankhunt42.pw url:tor.skankhunt42.pw proof:uri-familyid-ed25519 matrix:@motho:skankhunt42.pw cost:30.00EUR offlinemasterkey:y signingkeylifetime:7 autoupdate:y confmgmt:ansible ciissversion:3 trafficacct:unmetered xmr:85CUCzb6nighLSfhJT8nXwRfmqqogiAsyekwVNbP3QrXUkCtMbutWiGTCp1S2NJw5oLDoY4J9ZUtEepsV6ciZpsCLAzwmWQ
Family Configuration
- Family Support
- Happy Families (5) — Has family-cert in server descriptor (guide)
Happy Families (family-cert)
- Effective Members: 5
08D02A1FED163C03BA68E642C9D133C4FB59B9D4 4FA9ED57FA5D838573C488235C68736EA3037DB5 57E7AD67EB72B189EE9F5272909DFF7EC5373E92 C570ADADA8EF3435B3743A505768FECAC93299B9 (this relay) EBF514BF64D6E08CA4FB9255DB9516A87F023351
MyFamily (legacy declarations) — none
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Sat, 25 Jul 2026 11:16:24 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-07-25 10:15:09).
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 | 48.7 Mbit/s | 816.0 Kbit/s | 48.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 97.9% | 98% | 19.3d | 8d | 4.0d | 16.7d | 4.6d | 7.2d | 97.9% | 98.0% | 19.3d | 1.0d | 2026-07-24 23:17:54 | 48.6 Kbit/s |
| dannenberg (DE) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast | 48.7 Mbit/s | 816.0 Kbit/s | 48.7 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s | 97.5% | 98% | 17.1d | 8d | 3.1d | 8.0d | 4.6d | 7.4d | 97.5% | 98.0% | 17.1d | 1.0d | 2026-07-24 23:17:54 | 88.0 Kbit/s |
| dizum (NL) | Yes | Yes | No | — | N | Yes | Yes | Running, Valid, V2Dir, Fast | 48.7 Mbit/s | 816.0 Kbit/s | 48.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 97.8% | 98% | 16.9d | 8d | 4.0d | 11.7d | 4.6d | 7.4d | 97.8% | 98.0% | 16.9d | 1.0d | 2026-07-24 23:17:54 | 48.6 Kbit/s |
| faravahar (US) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir | 48.7 Mbit/s | 816.0 Kbit/s | 48.7 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s | 97.9% | 98% | 18.7d | 8d | 6.6d | 11.9d | 4.6d | 7.7d | 97.9% | 98.0% | 18.7d | 1.0d | 2026-07-24 23:17:54 | 104.0 Kbit/s |
| gabelmoo (DE) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast | 48.7 Mbit/s | 816.0 Kbit/s | 48.7 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s | 99.6% | 98% | 7.8d | 7d | 2.6d | 12.3d | 4.6d | 7.5d | 99.6% | 98.0% | 7.8d | 1.0d | 2026-07-24 23:17:54 | 96.0 Kbit/s |
| longclaw (US) | Yes | Yes | No | — | Y | Yes | — | Running, Valid, V2Dir, Fast | 48.7 Mbit/s | 816.0 Kbit/s | 48.7 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s | 97.2% | 98% | 11.6d | 8d | 3.5d | 24.7d | 4.6d | 8.1d | 97.2% | 98.0% | 11.6d | 1.0d | 2026-07-24 23:17:54 | 55.2 Kbit/s |
| maatuska (SE) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast | 48.7 Mbit/s | 816.0 Kbit/s | 48.7 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s | 97.8% | 98% | 16.6d | 8d | 3.5d | 12.5d | 4.6d | 8.1d | 97.8% | 98.0% | 16.6d | 1.0d | 2026-07-24 23:17:54 | 72.8 Kbit/s |
| moria1 (US) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable | 48.7 Mbit/s | 8.4 Mbit/s | 48.7 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s | 96.5% | 98% | 9.9d | 8d | 16307.4d | 9298.7d | 4.6d | 7.5d | 96.5% | 98.0% | 9.9d | 10.0d | 2026-07-24 23:17:54 | 31.2 Kbit/s |
| tor26 (AT) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast | 48.7 Mbit/s | 816.0 Kbit/s | 48.7 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s | 98.1% | 98% | 18.7d | 8d | 4.7d | 16.7d | 4.6d | 7.5d | 98.1% | 98.0% | 18.7d | 1.0d | 2026-07-24 23:17:54 | 74.4 Kbit/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.
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.