HOS-154161

BGP inherited
Cluster stats
Netblocks7
Cluster ID210876462
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
136.243.227.32/29 HOS-154161 RIPE LEGACY ● low
2a01:4f8:10b:2356::/64 HOS-154161 RIPE ASSIGNED ● low
2a01:4f8:161:1109::/64 HOS-154161 RIPE ASSIGNED ● low
2a01:4f8:171:124d::/64 HOS-154161 RIPE ASSIGNED ● low
2a01:4f8:221:29a0::/64 HOS-154161 RIPE ASSIGNED ● low
2a01:4f8:242:1c09::/64 HOS-154161 RIPE ASSIGNED ● low
2a01:4f8:271:2bcb::/64 HOS-154161 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 →
85.7% of checked blocks have valid RPKI ROA coverage (6 of 7)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE HOS-GUN