HOS-164923

BGP inherited
Cluster stats
Netblocks8
Cluster ID211609167
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
2a01:4f8:10b:76a::/64 HOS-164923 RIPE ASSIGNED ● low
2a01:4f8:171:c0e::/64 HOS-164923 RIPE ASSIGNED ● low
2a01:4f8:231:2ad4::/64 HOS-164923 RIPE ASSIGNED ● low
2a01:4f9:4a:4968::/64 HOS-164923 RIPE ASSIGNED ● low
2a01:4f9:3070:2ac5::/64 HOS-164923 RIPE ASSIGNED ● low
2a01:4f9:3080:2943::/64 HOS-164923 RIPE ASSIGNED ● low
2a01:4f9:3081:4219::/64 HOS-164923 RIPE ASSIGNED ● low
2a01:4f9:3081:4d40::/64 HOS-164923 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 (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE HOS-GUN