HOS-39117

BGP inherited
Cluster stats
Netblocks10
Cluster ID210984504
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 (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.9.207.230/32 HOS-39117 RIPE ASSIGNED PA ● low
5.9.207.248/32 HOS-39117 RIPE ASSIGNED PA ● low
176.9.67.7/32 HOS-39117 RIPE ASSIGNED PA ● low
176.9.109.221/32 HOS-39117 RIPE ASSIGNED PA ● low
176.9.135.177/32 HOS-39117 RIPE ASSIGNED PA ● low
178.63.30.136/32 HOS-39117 RIPE ASSIGNED PA ● low
2a01:4f8:10a:3b20::/64 HOS-39117 RIPE ASSIGNED ● low
2a01:4f8:121:269::/64 HOS-39117 RIPE ASSIGNED ● low
2a01:4f8:160:936f::/64 HOS-39117 RIPE ASSIGNED ● low
2a01:4f8:2190:2380::/64 HOS-39117 RIPE ASSIGNED ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (10 of 10)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE HOS-GUN