HOS-191673

BGP inherited
Cluster stats
Netblocks7
Cluster ID211277914
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
188.40.206.80/29 HOS-191673 RIPE ASSIGNED PA ● low
2a01:4f8:173:11dc::/64 HOS-191673 RIPE ASSIGNED ● low
2a01:4f8:173:11f1::/64 HOS-191673 RIPE ASSIGNED ● low
2a01:4f8:231:3dea::/64 HOS-191673 RIPE ASSIGNED ● low
2a01:4f8:231:3fe5::/64 HOS-191673 RIPE ASSIGNED ● low
2a01:4f8:252:2e11::/64 HOS-191673 RIPE ASSIGNED ● low
2a01:4f8:271:2ae6::/64 HOS-191673 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 (7 of 7)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE HOS-GUN