HOS-163666

BGP inherited
Cluster stats
Netblocks8
Cluster ID210170977
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
144.76.134.48/28 HOS-163666 RIPE LEGACY ● low
2a01:4f8:162:6414::/64 HOS-163666 RIPE ASSIGNED ● low
2a01:4f8:201:9315::/64 HOS-163666 RIPE ASSIGNED ● low
2a01:4f8:252:4110::/64 HOS-163666 RIPE ASSIGNED ● low
2a01:4f8:2190:18c4::/64 HOS-163666 RIPE ASSIGNED ● low
2a01:4f8:2b01:17ac::/64 HOS-163666 RIPE ASSIGNED ● low
2a01:4f9:3a:5605::/64 HOS-163666 RIPE ASSIGNED ● low
2a01:4f9:3080:5743::/64 HOS-163666 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 →
87.5% of checked blocks have valid RPKI ROA coverage (7 of 8)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE HOS-GUN