HOS-169110

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

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
2a01:4f8:121:24a3::/64 HOS-169110 RIPE ASSIGNED ● low
2a01:4f8:13b:e8c::/64 HOS-169110 RIPE ASSIGNED ● low
2a01:4f8:150:2388::/64 HOS-169110 RIPE ASSIGNED ● low
2a01:4f8:151:730d::/64 HOS-169110 RIPE ASSIGNED ● low
2a01:4f8:171:b5d::/64 HOS-169110 RIPE ASSIGNED ● low
2a01:4f8:222:2a42::/64 HOS-169110 RIPE ASSIGNED ● low
2a01:4f8:2200:2686::/64 HOS-169110 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 (7 of 7)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE HOS-GUN