HOS-178574

BGP inherited
Cluster stats
Netblocks9
Cluster ID210880392
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.9.218.56/29 HOS-178574 RIPE ASSIGNED PA ● low
136.243.230.152/29 HOS-178574 RIPE LEGACY ● low
2a01:4f8:151:4304::/64 HOS-178574 RIPE ASSIGNED ● low
2a01:4f8:231:23cc::/64 HOS-178574 RIPE ASSIGNED ● low
2a01:4f8:241:dc3::/64 HOS-178574 RIPE ASSIGNED ● low
2a01:4f8:241:dc4::/64 HOS-178574 RIPE ASSIGNED ● low
2a01:4f8:241:dc7::/64 HOS-178574 RIPE ASSIGNED ● low
2a01:4f8:241:dce::/64 HOS-178574 RIPE ASSIGNED ● low
2a01:4f8:241:def::/64 HOS-178574 RIPE ASSIGNED ● low

Possibly related to this organisation

what's this?
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

what's this?
RPKI hygiene: B how networks compare →
88.9% of checked blocks have valid RPKI ROA coverage (8 of 9)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE HOS-GUN