KYRGYZTELEKOM-PPPOE
Data as of 2026-10-11
BGP inherited
This organisation
| Netblocks | 17 · 7,680 IPv4 addresses |
| Also registered under this name | 25 netblocks across 2 separate records |
| Record ID | 245856010 |
| Registry | RIPE |
| Customers | see 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 (17)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 185.66.252.0/24 | KYRGYZTELEKOM-PPPOE | RIPE | ASSIGNED PA | ● low |
| 185.66.253.0/24 | KYRGYZTELEKOM-PPPOE | RIPE | ASSIGNED PA | ● low |
| 185.66.254.0/24 | KYRGYZTELEKOM-PPPOE | RIPE | ASSIGNED PA | ● low |
| 185.66.255.0/24 | KYRGYZTELEKOM-PPPOE | RIPE | ASSIGNED PA | ● low |
| 213.145.132.0/22 | KYRGYZTELEKOM-PPPOE | RIPE | ASSIGNED PA | ● low |
| 213.145.136.0/24 | KYRGYZTELEKOM-PPPOE | RIPE | ASSIGNED PA | ● low |
| 213.145.137.0/24 | KYRGYZTELEKOM-PPPOE | RIPE | ASSIGNED PA | ● low |
| 213.145.138.0/24 | KYRGYZTELEKOM-PPPOE | RIPE | ASSIGNED PA | ● low |
| 213.145.139.0/24 | KYRGYZTELEKOM-PPPOE | RIPE | ASSIGNED PA | ● low |
| 213.145.140.0/24 | KYRGYZTELEKOM-PPPOE | RIPE | ASSIGNED PA | ● low |
| 213.145.142.0/24 | KYRGYZTELEKOM-PPPOE | RIPE | ASSIGNED PA | ● low |
| 213.145.143.0/24 | KYRGYZTELEKOM-PPPOE | RIPE | ASSIGNED PA | ● low |
| 213.145.145.0/24 | KYRGYZTELEKOM-PPPOE | RIPE | ASSIGNED PA | ● low |
| 213.145.146.0/24 | KYRGYZTELEKOM-PPPOE | RIPE | ASSIGNED PA | ● low |
| 213.145.147.0 – 213.145.154.255 | KYRGYZTELEKOM-PPPOE | RIPE | ASSIGNED PA | ● low |
| 213.145.155.0 – 213.145.158.255 | KYRGYZTELEKOM-PPPOE | RIPE | ASSIGNED PA | ● low |
| 213.145.159.0/24 | KYRGYZTELEKOM-PPPOE | RIPE | ASSIGNED PA | ● low |
Footprint over time
16 weekly snapshots · JSON
17
0 netblocks since 2026-07-05
2026-07-05
peak 17
2026-10-11
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(17 of 17)
RPKI-inferred operator
OJSC Kyrgyztelecom
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
KTNET-MNT