HOS-204476

BGP inherited
Cluster stats
Netblocks8
Cluster ID210247151
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
65.21.21.80/29 HOS-204476 RIPE ASSIGNED PA ● low
136.243.238.8/29 HOS-204476 RIPE LEGACY ● low
167.235.215.80/29 HOS-204476 RIPE LEGACY ● low
2a01:4f8:222:1e4b::/64 HOS-204476 RIPE ASSIGNED ● low
2a01:4f8:241:5868::/64 HOS-204476 RIPE ASSIGNED ● low
2a01:4f8:261:3a08::/64 HOS-204476 RIPE ASSIGNED ● low
2a01:4f8:262:12e8::/64 HOS-204476 RIPE ASSIGNED ● low
2a01:4f9:3080:1362::/64 HOS-204476 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