HOS-11

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

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.9.53.15/32 HOS-11 RIPE ASSIGNED PA ● low
85.10.242.16/29 HOS-11 RIPE ASSIGNED PA ● low
157.90.47.224/29 HOS-11 RIPE LEGACY ● low
213.239.227.23/32 HOS-11 RIPE ASSIGNED PA ● low
213.239.227.102/32 HOS-11 RIPE ASSIGNED PA ● low
2a01:4f8:a0:73c8::/64 HOS-11 RIPE ASSIGNED ● low
2a01:4f8:171:1601::/64 HOS-11 RIPE ASSIGNED ● low
2a01:4f8:172:152b::/64 HOS-11 RIPE ASSIGNED ● low
2a01:4f8:fff3:40::/64 HOS-11 RIPE ASSIGNED ● low
2a01:4f9:3090:1203::/64 HOS-11 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 (10 of 10)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE HOS-GUN