View Relay "TheShadowRoute04"
Fingerprint: BF3373E63AF7929728C0EE65560D3D338AA0F50A |
Family: 20 relays
|
email:tor-node+shdrt04[]hobi.one... |
AS215288
|
Italy
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- BW Verified
- 5/7 BW Auths Measured 36 Mbit/s Median
- Stability
- Overloaded | UP 5d 19h 47m ago | UP 99% (1M)
- Reachability
- IPv4: 9/9 | v6: 8/8(Directory Auths)
- BW Weight
- 0.00% of Network | 45 Mbit/s Observed By Relay
- Version
- 0.4.9.14 Not 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). -
Not eligible for Stable flag
: 1/9 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska and tor26 do not.
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. -
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. -
Tor version not recommended
: Running Tor version 0.4.9.14 which is not on the recommended list.
Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases. -
General Overload Active
: Relay reported general overload at 2026-11-03 14:00 UTC. Reported timestamps use hour precision, so the displayed minute is not an exact incident time. The flag does not identify which trigger fired. Investigation paths are Tor's internal OOM handling, dropped ntor onionskins, and TCP port exhaustion.
Suggestion: Inspect CPU and memory with htop, Tor service logs, host or container memory headroom, and the effective MaxMemInQueues. When the process was killed or restarted, check kernel OOM logs separately. A kernel OOM kill is a different mechanism from Tor freeing memory itself. MetricsPort: tor_relay_load_oom_bytes_total. Broken down by subsys. An increase measures bytes freed by Tor’s internal OOM handling. It is not an invocation count and it is not proof of a kernel OOM kill. Review Tor’s onionskin and drop messages, and whether the CPU is saturated or contended. The general-overload flag does not say this trigger fired. MetricsPort: tor_relay_load_onionskins_total{type="ntor",action="dropped"} and {type="ntor_v3",action="dropped"}. Compare each with the matching action="processed" series. Inspect both supported handshake types. Review Tor logs, socket usage, and the host’s ephemeral-port allocation. On Linux, ss -s and reading net.ipv4.ip_local_port_range are useful starting checks. MetricsPort: tor_relay_load_tcp_exhaustion_total. An increase records additional exhaustion events. See the Tor overload troubleshooting guide.
Addresses
- OR Address
-
151.242.132.110:9001
[2a14:7581:9f20:1512::110]:9001
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- 8/8 (1 don't test)
Location
- Country
-
Italy
- Interactive Map
- View in RouteFluxMap
Eligible Flags (4):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 4/9 | HSDir: 2/9 | Guard: 4/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) | 24.8 Mbit/s – 45.6 Mbit/s (5 DA measured) 41.9 Mbit/s (4 DA relay-reported) |
≥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: 4.9d (1/9 DA above threshold) Min/Max: 2.3d / 15009.4d (9/9 DA, Voting / Total Eligible) |
≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
| Uptime | Meets (9/9 DA) | 5.8d (R) | ≥5.2d - 5.3d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 24.8 Mbit/s – 45.6 Mbit/s (5 DA measured) 41.9 Mbit/s (4 DA relay-reported) |
≥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 (4/9 DA) | 4/9 DA assigned Stable | ≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Partial (7/9 DA) | 5.8d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known |
|
| Guard | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 24.8 Mbit/s – 45.6 Mbit/s (5 DA measured) 41.9 Mbit/s (4 DA relay-reported) |
≥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 (4/9 DA) | 4/9 DA assigned Stable | ≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Partial (8/9 DA) | Median: 99.0% (8/9 DA above threshold) Min/Max: 97.5% / 99.3% (9/9 DA, Voting / Total Eligible) |
≥98%; dizum: ≥97.84099999999999% (≥5/9 DA) | |
| Time Known | Meets (9/9 DA) | Median: 14.6d (9/9 DA above threshold) Min/Max: 9.8d / 18.8d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Meets (9/9 DA) | 24.8 Mbit/s – 45.6 Mbit/s (5 DA measured) 41.9 Mbit/s (4 DA relay-reported) |
≥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-11-04 12:45:10).
Capacity (Relay Reported)
- Observed Bandwidth
- 45.57 Mbit/s
- Advertised Bandwidth
- 41.94 Mbit/s
- Rate Limit
- 41.94 Mbit/s
- Burst Limit
- 41.94 Mbit/s
- Total Data
-
44 TB
(6 months)
1mo: 16 TB | 6mo: 44 TB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-04 12:45:10
- Measured By
-
5/7
Bandwidth Authorities
Not measured by: faravahar, longclaw - Consensus Weight
- 36.8 Mbit/s (median of 5 measurements)
- Measured Min / Max
- 24.8 Mbit/s / 45.6 Mbit/s
- Deviation
- 20.8 Mbit/s [Warning] High variation
Network Participation:
Consensus Weight:
0.0019% of network
(28th pctl)
|
Guard:
N/A |
Middle:
0.0055% (54th pctl) |
Exit:
N/A
History
Uptime Metrics
- Current Status
- UP 5d 19h 47m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 99.6%/99.7%/0.0%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (99.6%/99.7%/0.0%/0.0%)
- Hibernating
- No
Timestamps
- First Seen
- 3mo 11h 45m ago (2026-08-06 02:00:00)
- Last Seen
- 2h 45m 39s ago (2026-11-04 11:00:00)
- Last Restarted
- 5d 19h 47m ago (2026-10-29 17:58:20)
- Last Changed Address
- 2026-08-06 02:00:00
[Warning] OVERLOADED
— General overload at 2026-11-03 14:00 UTC
Evaluated 2026-11-04 13:45 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 42s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 6h ago).
Reported timestamps use hour precision, so the displayed minute is not an exact incident time.
General Overload (from /details)
- Status
- Reported
- When
- 2026-11-03 14:00 UTC (23 hours ago)
The general-overload flag does not say which trigger fired. Possible paths are Tor’s internal memory handling, dropped ntor handshakes, and TCP port exhaustion. Allium treats a valid report as eligible for 72 hours; that cutoff is not proof the relay recovered then.
File Descriptor Exhaustion (from /bandwidth)
- Status
- No file-descriptor exhaustion report in available data
Rate Limits (from /bandwidth)
- Status
- Historical report — outside the 24-hour window
- Rate Limit
- 41.94 Mbit/s
- Burst Limit
- 5.2 MB
- Write counter
- 970
- Read counter
- 116
- Reported
- 2026-11-03 13:00 UTC (1 day ago)
Read and write counters increment at most once per minute per direction. They are not a count of blocked connections, the duration of throttling, or necessarily the number of events in the last 24 hours. Rate is BandwidthRate and follows this site’s bits/bytes setting. Burst is BandwidthBurst, already a byte quantity. RelayBandwidthRate and RelayBandwidthBurst are extra torrc caps, not the names of these values. A hit stays eligible for 24 hours.
What to check
-
Tor internal memory pressure
Inspect CPU and memory with htop, Tor service logs, host or container memory headroom, and the effective MaxMemInQueues. When the process was killed or restarted, check kernel OOM logs separately. A kernel OOM kill is a different mechanism from Tor freeing memory itself.MetricsPort:
tor_relay_load_oom_bytes_total— Broken down by subsys. An increase measures bytes freed by Tor’s internal OOM handling. It is not an invocation count and it is not proof of a kernel OOM kill. -
ntor handshake pressure
Review Tor’s onionskin and drop messages, and whether the CPU is saturated or contended. The general-overload flag does not say this trigger fired.MetricsPort:
tor_relay_load_onionskins_total{type="ntor",action="dropped"} and {type="ntor_v3",action="dropped"}— Compare each with the matching action="processed" series. Inspect both supported handshake types. -
TCP port exhaustion
Review Tor logs, socket usage, and the host’s ephemeral-port allocation. On Linux, ss -s and reading net.ipv4.ip_local_port_range are useful starting checks.MetricsPort:
tor_relay_load_tcp_exhaustion_total— An increase records additional exhaustion events.
About these reports and MetricsPort
Allium’s eligibility windows are applied to the reported timestamps: 72 hours for general overload and file-descriptor exhaustion, 24 hours for a rate-limit hit. A report at the cutoff is historical. An older report can remain visible after Onionoo or Allium’s cache still has it. The cutoff does not prove the relay recovered at that moment. Allium caches the bandwidth document for 12 hours by default. The snapshot time is when Onionoo published that document. It is not the relay’s event time, and it is not necessarily the extra-info publication time. Cache age is how old Allium’s copy is.
MetricsPort counters are cumulative. Compare samples, and account for process restarts. A nonzero total alone does not show ongoing activity. Gauges describe current values. An unavailable metric is unknown, not zero. Allium does not have this relay’s MetricsPort readings and does not invent them.
The port below is an example for an endpoint you have already configured. MetricsPort must be enabled with restricted access and must not be exposed publicly. Setup stays in the Tor overload troubleshooting guide.
curl http://127.0.0.1:9035/metrics
History
Operator Identity
Source: AROI Validation API — 2026-11-04 04:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- email:tor-node+shdrt04[]hobi.one abuse:tor-node+shdrt04[]hobi.one uplinkbw:40 memory:6144 virtualization:lxc os:Alpine tls:openssl confmgmt:ansible ciissversion:2 trafficacct:unmetered
Family Configuration
- Family Support
- Happy Families (20) — Has family-cert in server descriptor (guide) | View Full Family (20)
Happy Families (family-cert)
- Effective Members: 20
2DD73B17000067A07E59523BF7F7285F40ED014C 4882C1FEE58BAA9D041E1D75B5E7857C3BF880BF 4C8D6E6829EB48BB241E7496A1792E25CDA0FB81 510D171AAE593787911A2AB3838AEF05A4806CAB 5CF32C63C48D773116418AE4B7CCB14B3F70F865 6A614F676D7B9D8E0DAE23E01E5060E04823F742 808930973311DE582088B5A86F89D7B833FA5805 8C7F1C134BA5DC0B9C7C7B1CDAB288B102D75E49 91D66445EBE11BB058E9ED1ED92C7FED325F62E4 BF199B3F78B263562C4B5EE6BB540728A6E9E654 BF3373E63AF7929728C0EE65560D3D338AA0F50A (this relay) BF401B3A2CC40D610D54CE4ABCAD3E9A607032E6 BF6925AF87FEA93E21FEBC9DE4A24AD47796A87D C7233996E702CDB7FCFD52F60C91F5CBF924F54D C93CD2856690EF004AC05F4FC68CA2EC6C62F294 CB68894ECC86E3074C15C4FE2EECEB6313E0F7DB D99E2901A6AABD8F7A05CBDA04F39B11B920D776 E762EF5F57C87C25154937426A0E7574AFDDB667 F55FA70145866CE4C091A6716B1E93354F532B82 F99C1B20A93EA0DCCC098E04442B99316824B2F2
MyFamily (legacy declarations) — none
- Platform
- Linux — Tor 0.4.9.14 on Linux
- Version
- 0.4.9.14 — Not Recommended
- Version Status
- Obsolete — Update urgently. See torproject.org/download
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Wed, 04 Nov 2026 13:45:39 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-04 12:45:10).
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 (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 | Yes | Running, Valid, V2Dir, Fast | 44.8 Mbit/s (M) | 816.0 Kbit/s | 44.8 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 98.6% | 98% | 14.8d | 8d | 3.6d | 8.4d | 5.8d | 5.2d | 2026-11-03 20:29:44 | 44.8 Mbit/s (M) |
| dannenberg (DE) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, Guard | 36.8 Mbit/s (M) | 816.0 Kbit/s | 36.8 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s | 99.3% | 98% | 15.4d | 8d | 5.3d | 9.3d | 5.8d | 5.3d | 2026-11-03 20:29:44 | 36.8 Mbit/s (M) |
| dizum (NL) | Yes | Yes | No | — | N | Yes | Yes | Running, Valid, V2Dir, Fast | 41.9 Mbit/s (R) | 816.0 Kbit/s | 41.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 97.5% | 98% | 14.3d | 8d | 4.9d | 6.7d | 5.8d | 5.3d | 2026-11-03 20:29:44 | 41.9 Mbit/s (R) |
| faravahar (US) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, Guard | 41.9 Mbit/s (R) | 816.0 Kbit/s | 41.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.3% | 98% | 18.8d | 8d | 6.2d | 6.5d | 5.8d | 5.3d | 2026-11-03 20:29:44 | 41.9 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast | 30.4 Mbit/s (M) | 816.0 Kbit/s | 30.4 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s | 99.0% | 98% | 14.3d | 8d | 3.9d | 10.8d | 5.8d | 5.3d | 2026-11-03 20:29:44 | 30.4 Mbit/s (M) |
| longclaw (US) | Yes | Yes | No | — | Y | Yes | N/T | Running, Valid, V2Dir, Fast | 41.9 Mbit/s (R) | 816.0 Kbit/s | 41.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.0% | 98% | 15.2d | 8d | 4.5d | 10.9d | 5.8d | 5.3d | 2026-11-03 20:29:44 | 41.9 Mbit/s (R) |
| maatuska (SE) | Yes | Yes | No | — | N | Yes | Yes | Running, Valid, V2Dir, Fast | 41.9 Mbit/s (R) | 816.0 Kbit/s | 41.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 98.1% | 98% | 13.7d | 8d | 2.3d | 2.4d | 5.8d | 5.3d | 2026-11-03 20:29:44 | 41.9 Mbit/s (R) |
| moria1 (US) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Guard | 45.6 Mbit/s (M) | 8.4 Mbit/s | 45.6 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 98.5% | 98% | 9.8d | 8d | 15009.4d | 7607.5d | 5.8d | 5.3d | 2026-11-03 20:29:44 | 45.6 Mbit/s (M) |
| tor26 (AT) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Guard | 24.8 Mbit/s (M) | 816.0 Kbit/s | 24.8 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s | 99.2% | 98% | 14.6d | 8d | 5.5d | 10.6d | 5.8d | 5.3d | 2026-11-03 20:29:44 | 24.8 Mbit/s (M) |
N/T = this authority does not test IPv6 • — = not in this vote • 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 (
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (
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.
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.
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.