HOS-192219

BGP inherited
Cluster stats
Netblocks9
Cluster ID211609086
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
2a01:4f8:10b:1721::/64 HOS-192219 RIPE ASSIGNED ● low
2a01:4f8:120:34dd::/64 HOS-192219 RIPE ASSIGNED ● low
2a01:4f8:141:211a::/64 HOS-192219 RIPE ASSIGNED ● low
2a01:4f8:141:6268::/64 HOS-192219 RIPE ASSIGNED ● low
2a01:4f8:151:210a::/64 HOS-192219 RIPE ASSIGNED ● low
2a01:4f8:171:458::/64 HOS-192219 RIPE ASSIGNED ● low
2a01:4f8:2240:13e2::/64 HOS-192219 RIPE ASSIGNED ● low
2a01:4f9:3090:1665::/64 HOS-192219 RIPE ASSIGNED ● low
2a01:4f9:3100:35cc::/64 HOS-192219 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: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (9 of 9)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE HOS-GUN