HOS-178305

BGP inherited
Cluster stats
Netblocks8
Cluster ID211046639
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
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.9.216.112/28 HOS-178305 RIPE ASSIGNED PA ● low
136.243.209.176/28 HOS-178305 RIPE LEGACY ● low
136.243.252.80/28 HOS-178305 RIPE LEGACY ● low
2a01:4f8:10b:2d8::/64 HOS-178305 RIPE ASSIGNED ● low
2a01:4f8:241:a63::/64 HOS-178305 RIPE ASSIGNED ● low
2a01:4f8:242:5524::/64 HOS-178305 RIPE ASSIGNED ● low
2a01:4f8:251:317::/64 HOS-178305 RIPE ASSIGNED ● low
2a01:4f8:272:24d9::/64 HOS-178305 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: C how networks compare →
75.0% of checked blocks have valid RPKI ROA coverage (6 of 8)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE HOS-GUN