MTNMC_Kazakhtelecom

BGP inherited
Cluster stats
Netblocks10 · 502 IPv4 addresses
All fragments 343 blocks across 4 clusters
Cluster ID210112574
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
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-19

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
82.200.156.160/30 MTNMC_Kazakhtelecom RIPE ASSIGNED PA ● low
82.200.207.64/27 MTNMC_Kazakhtelecom RIPE ASSIGNED PA ● low
88.204.203.156/30 MTNMC_Kazakhtelecom RIPE ASSIGNED PA ● low
89.218.39.192/26 MTNMC_Kazakhtelecom RIPE ASSIGNED PA ● low
89.218.60.0/25 MTNMC_Kazakhtelecom RIPE ASSIGNED PA ● low
89.218.60.128/26 MTNMC_Kazakhtelecom RIPE ASSIGNED PA ● low
178.88.173.48/28 MTNMC_Kazakhtelecom RIPE ASSIGNED PA ● low
178.88.173.64/26 MTNMC_Kazakhtelecom RIPE ASSIGNED PA ● low
178.88.173.128/25 MTNMC_Kazakhtelecom RIPE ASSIGNED PA ● low
178.91.251.144/29 MTNMC_Kazakhtelecom RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “MTNMC Kazakhtelecom” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
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 (10 of 10)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE KNIC-MNT