View Family relays.brokenbotnet.com Details

Relays with effective family member 7E87EC2F20A371E32E6672A6D04B55471BC5D369 summary:

Last updated: Tue, 14 Jul 2026 07:15:43 GMT. Refreshed every 30 minutes from the Tor directory authorities via Tor Project's onionoo API.

⏳ PENDING ONIONOO REFRESH (1)

Nickname BW Cap (303.19 Mbit/s) Total Data Uptime/Downtime Uptime (1M/6M/1Y/5Y) Flag Uptime (1M/6M/1Y/5Y) IPv4 Flags DNS Family Country AS Number AS Name Platform First Seen Last Restarted IPv6
v3 ShinobiHouou (7) 6.57 Mbit/s    899 MB UP 20h 43m 23s ago 0.0%/0.0%/0.0%/0.0% Match 157.10.253.140 FastRunningV2DirValid NA Happy Families Indonesia ID AS136052 PT Cloud Hosting... Linux 2d 23h 16m ago 20h 44m 33s ago 2001:470:36:6d8::1337:c0de
⏳ WAITING FOR ONIONOO TO REFRESH

These relays declared ciissversion:3 but Onionoo hasn't picked up family_ids yet. This is transient — Onionoo refreshes hourly; expect resolution within 24 hours of restarting Tor with the happy-family directive.

Validation data last updated: 2026-07-14 00:00 UTC

  • ShinobiHouou v3 URI-FamilyID: Relay has no family_ids in Onionoo, cannot verify ciissversion:3 proof • Proof: uri-familyid-ed25519 • FP: 7E87EC2F20A371E32E6672A6D04B55471BC5D369
    💡 Fix: Run 'tor --keygen-family <file>' on the relay, configure Tor's happy-family directive to use <file>.secret_family_key, restart, and wait for Onionoo to refresh (typically < 24h).
    📋 Paste: curl "https://onionoo.torproject.org/details?lookup=7E87EC2F20A371E32E6672A6D04B55471BC5D369&fields=family_ids" | jq # should show your .public_family_id within 24h of restarting Tor

💡 No action needed if you recently changed torrc; wait < 24h. If still pending after 24h: verify FamilyId line in torrc and that .secret_family_key is in Tor KeyDir.
📖 See the AROI Specification for guidance.

✓ VALIDATED RELAYS (6)

Nickname BW Cap (303.19 Mbit/s) Total Data Uptime/Downtime Uptime (1M/6M/1Y/5Y) Flag Uptime (1M/6M/1Y/5Y) IPv4 Flags DNS Family Country AS Number AS Name Platform First Seen Last Restarted IPv6
ShinobiWashi (16) 201.51 Mbit/s    835 GB UP 1w 3d 15h ago 99.0%/0.0%/0.0%/0.0% Match 173.224.219.133 FastGuardRunningStableV2DirValid NA Happy Families United States of America US AS40676 Psychz Networks Linux 1w 5d 10h ago 1w 3d 15h ago 2604:6600:8:3::2df
ShinobiKuma (16) 39.31 Mbit/s    24 TB UP 1w 3d 16h ago 98.7%/97.1%/97.3%/0.0% —/—/96.5%/— 195.133.23.252 FastRunningV2DirValid NA Happy Families Russian Federation RU AS51659 LLC Baxet Linux 6mo 2w 5d ago 1w 3d 16h ago 2001:470:1f15:16b::1337:c0de
ShinobiMamori (16) 19.32 Mbit/s    4.4 TB UP 2d 15h 22m ago 100.0%/100.0%/100.0%/0.0% Match 158.51.109.143 FastRunningStableV2DirValid NA Happy Families Japan JP AS18526 DDPS Networks, LLC Linux 7mo 1d 16m ago 2d 15h 23m ago 2602:fd6f:100:1f::1337:c0de
ShinobiKaede (16) 17.78 Mbit/s    186 GB UP 1w 3d 16h ago 99.3%/0.0%/0.0%/0.0% 99.5%/—/—/— 38.49.219.113 FastHSDirRunningStableV2DirValid NA Happy Families Canada CA AS26832 Rica Web Services Linux 1w 5d 21h ago 1w 3d 16h ago 2602:ffd5:767:3::1337:c0de
ShinobiBusouge (16) 9.91 Mbit/s    1.4 TB UP 1w 1h 36m ago 90.6%/98.2%/97.8%/0.0% 90.1%/97.0%/96.1%/— 124.217.248.240 FastRunningV2DirValid NA Happy Families Malaysia MY AS45839 Shinjiru... Linux 6mo 2w 15h ago 1w 1h 37m ago 2001:470:36:597::1337:c0de
ShinobiTora (16) 8.78 Mbit/s    2.1 TB UP 1d 20h 20m ago 99.6%/99.9%/99.9%/0.0% 96.2%/98.1%/98.1%/— 158.247.199.231 FastRunningStableV2DirValid NA Happy Families Korea, Republic of KR AS20473 The Constant Company, LLC OpenBSD 6mo 3w 2d ago 1d 20h 21m ago 2401:c080:1c01:68e::1337:c0de

⚠ MISCONFIGURED RELAYS (1)

Nickname BW Cap (303.19 Mbit/s) Total Data Uptime/Downtime Uptime (1M/6M/1Y/5Y) Flag Uptime (1M/6M/1Y/5Y) IPv4 Flags DNS Family Country AS Number AS Name Platform First Seen Last Restarted IPv6
ShinobiHouou (7) 6.57 Mbit/s    899 MB UP 20h 43m 23s ago 0.0%/0.0%/0.0%/0.0% Match 157.10.253.140 FastRunningV2DirValid NA Happy Families Indonesia ID AS136052 PT Cloud Hosting... Linux 2d 23h 16m ago 20h 44m 33s ago 2001:470:36:6d8::1337:c0de
⚠️ MISCONFIGURED RELAY DETAILS

These relays have AROI configured but validation failed due to errors.

Validation data last updated: 2026-07-14 00:00 UTC

  • ShinobiHouou v3 URI-FamilyID: Relay has no family_ids in Onionoo, cannot verify ciissversion:3 proof • Proof: uri-familyid-ed25519 • FP: 7E87EC2F20A371E32E6672A6D04B55471BC5D369
    💡 Fix: Run 'tor --keygen-family <file>' on the relay, configure Tor's happy-family directive to use <file>.secret_family_key, restart, and wait for Onionoo to refresh (typically < 24h).
    📋 Paste: curl "https://onionoo.torproject.org/details?lookup=7E87EC2F20A371E32E6672A6D04B55471BC5D369&fields=family_ids" | jq # should show your .public_family_id within 24h of restarting Tor

💡 Fix: Check DNS records, renew SSL certificates, or verify server connectivity.
📖 See the AROI Specification for guidance.