K Ipros
KIPROS
Registry
Cluster stats
| Netblocks | 6 |
| Cluster ID | 210096213 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
5 weekly snapshots · JSON
6
0 netblocks since 2026-07-05
2026-07-05
peak 6
2026-07-19
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 31.31.217.248/29 | KIpros | RIPE | ASSIGNED PA | ● low |
| 31.31.218.160/29 | Kipros | RIPE | ASSIGNED PA | ● low |
| 82.200.247.176/30 | KIPROS | RIPE | ASSIGNED PA | ● low |
| 88.204.158.116/30 | KIPROS | RIPE | ASSIGNED PA | ● low |
| 92.46.35.52/30 | KIPROS | RIPE | ASSIGNED PA | ● low |
| 178.88.69.148/30 | KIPROS | RIPE | ASSIGNED PA | ● 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.
- LLP_KIPROS via JSC Kazteleport - subsidiary of Halyk Bank of Kazakhstan sub-allocation
- TOOKIPROS via JSC Kazakhtelecom sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(6 of 6)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
KAZTELEPORT-MNT
KNIC-MNT