HOS-169421

BGP inherited
Cluster stats
Netblocks8
Cluster ID211106892
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
157.90.97.160/29 HOS-169421 RIPE LEGACY ● low
159.69.172.72/29 HOS-169421 RIPE ASSIGNED PA ● low
2a01:4f8:e0:1b50::/64 HOS-169421 RIPE ASSIGNED ● low
2a01:4f8:172:1826::/64 HOS-169421 RIPE ASSIGNED ● low
2a01:4f8:2210:1aa4::/64 HOS-169421 RIPE ASSIGNED ● low
2a01:4f9:2a:25eb::/64 HOS-169421 RIPE ASSIGNED ● low
2a01:4f9:3a:47e0::/64 HOS-169421 RIPE ASSIGNED ● low
2a01:4f9:3081:344e::/64 HOS-169421 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