HOS-203901

BGP inherited
Cluster stats
Netblocks8
Cluster ID211781521
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
2a01:4f8:140:5412::/64 HOS-203901 RIPE ASSIGNED ● low
2a01:4f8:162:3086::/64 HOS-203901 RIPE ASSIGNED ● low
2a01:4f8:162:308d::/64 HOS-203901 RIPE ASSIGNED ● low
2a01:4f8:221:3b89::/64 HOS-203901 RIPE ASSIGNED ● low
2a01:4f8:221:4385::/64 HOS-203901 RIPE ASSIGNED ● low
2a01:4f8:1060:20c7::/64 HOS-203901 RIPE ASSIGNED ● low
2a01:4f8:1060:2188::/64 HOS-203901 RIPE ASSIGNED ● low
2a01:4f8:2240:12c9::/64 HOS-203901 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 (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE HOS-GUN