KZ-ORBICOM-NET

Data as of 2026-11-08
BGP inherited
This organisation
Netblocks10
Record ID265044051
RegistryRIPE
Customerssee who runs inside 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 · report an issue

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
217.15.180.212/30 KZ-ORBICOM-NET RIPE ASSIGNED PA ● low
217.15.180.232/30 KZ-ORBICOM-NET RIPE ASSIGNED PA ● low
217.15.182.100/30 KZ-ORBICOM-NET RIPE ASSIGNED PA ● low
217.15.182.128/30 KZ-ORBICOM-NET RIPE ASSIGNED PA ● low
217.15.185.172/30 KZ-ORBICOM-NET RIPE ASSIGNED PA ● low
217.15.186.120/30 KZ-ORBICOM-NET RIPE ASSIGNED PA ● low
217.15.188.120/30 KZ-ORBICOM-NET RIPE ASSIGNED PA ● low
217.15.188.252/30 KZ-ORBICOM-NET RIPE ASSIGNED PA ● low
217.15.189.156/30 KZ-ORBICOM-NET RIPE ASSIGNED PA ● low
217.15.190.184/30 KZ-ORBICOM-NET RIPE ASSIGNED PA ● low

Footprint over time

20 weekly snapshots · JSON
10 -1 netblocks since 2026-07-05
2026-07-05 peak 11 2026-11-08

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (10 of 10)
No discrepancies found among checked blocks.

NIC Handles

AS25534-MNT DUMY-RIPE DUMY-RIPE