View Family relays.brokenbotnet.com Details

Relays with effective family member 9F085BE2414BEAD86BF590800528A55A857F21C8 summary:

Last updated: Fri, 03 Jul 2026 03:11:23 GMT. Refreshed every 30 minutes from the Tor directory authorities via Tor Project's onionoo API.

⏳ PENDING ONIONOO REFRESH (1)

Nickname BW Cap (149.78 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 ShinobiWashi (5) 15.85 Mbit/s    N/A UP 12h 57m 21s ago 0.0%/0.0%/0.0%/0.0% Match 173.224.219.133 FastRunningV2DirValid NA Happy Families United States of America US AS40676 Psychz Networks Linux 1d 6h 13m ago 12h 59m 22s ago N/A
⏳ 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-02 19:00 UTC

  • ShinobiWashi v3 URI-FamilyID: Relay has no family_ids in Onionoo, cannot verify ciissversion:3 proof • Proof: uri-familyid-ed25519 • FP: 9F085BE2414BEAD86BF590800528A55A857F21C8
    💡 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=9F085BE2414BEAD86BF590800528A55A857F21C8&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 (4)

Nickname BW Cap (149.78 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
ShinobiKuma (13) 54.05 Mbit/s    22 TB UP 3w 1d 18h ago 97.6%/97.2%/97.3%/0.0% —/—/96.4%/— 195.133.23.252 FastRunningV2DirValid NA Happy Families Russian Federation RU AS51659 LLC Baxet Linux 6mo 1w 1d ago 3w 1d 18h ago N/A
ShinobiKyuuryuu (13) 44.25 Mbit/s    4.6 TB UP 16h 46m 11s ago 98.3%/98.4%/98.5%/0.0% —/—/98.1%/— 216.250.97.105 FastRunningStableV2DirValid NA Happy Families Hong Kong HK AS63473 HostHatch, LLC Linux 6mo 1w 4d ago 16h 48m 12s ago N/A
ShinobiShishi (13) 24.28 Mbit/s    2.3 TB UP 7h 28m 54s ago 99.7%/98.2%/0.0%/0.0% Match 139.84.241.19 FastRunningStableV2DirValid NA Happy Families South Africa ZA AS20473 The Constant Company, LLC SunOS 5mo 3w 2d ago 7h 30m 55s ago N/A
ShinobiKaede (5) 11.35 Mbit/s    N/A UP 13h 23m 20s ago 0.0%/0.0%/0.0%/0.0% Match 38.49.219.113 FastRunningV2DirValid NA Happy Families Canada CA AS26832 Rica Web Services Linux 1d 17h 13m ago 13h 25m 21s ago N/A

⚠ MISCONFIGURED RELAYS (1)

Nickname BW Cap (149.78 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 (5) 15.85 Mbit/s    N/A UP 12h 57m 21s ago 0.0%/0.0%/0.0%/0.0% Match 173.224.219.133 FastRunningV2DirValid NA Happy Families United States of America US AS40676 Psychz Networks Linux 1d 6h 13m ago 12h 59m 22s ago N/A
⚠️ MISCONFIGURED RELAY DETAILS

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

Validation data last updated: 2026-07-02 19:00 UTC

  • ShinobiWashi v3 URI-FamilyID: Relay has no family_ids in Onionoo, cannot verify ciissversion:3 proof • Proof: uri-familyid-ed25519 • FP: 9F085BE2414BEAD86BF590800528A55A857F21C8
    💡 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=9F085BE2414BEAD86BF590800528A55A857F21C8&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.