Data as of Nov 6, 2026
212.241.0.0/19
1,903 residential-proxy exits · 30 daysOJSC Kyrgyztelecom
Residential-proxy exits
Proxy exits
1,903
23% of its addresses · 30 days
Always-on exits
993
52% of its exits
Spread
24 of 32
/24s with at least one exit
Providers
69
selling exits here
Oct 7, 2026 – Nov 5, 2026
Exits seen per day
1.0M observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 212.241.4.0/24 | 149 | 193 | |
| 212.241.12.0/24 | 123 | 174 | |
| 212.241.28.0/24 | 106 | 142 | |
| 212.241.25.0/24 | 81 | 95 | |
| 212.241.24.0/24 | 76 | 97 | |
| 212.241.18.0/24 | 72 | 111 | |
| 212.241.16.0/24 | 70 | 88 | |
| 212.241.29.0/24 | 65 | 81 | |
| 212.241.20.0/24 | 45 | 101 | |
| 212.241.5.0/24 | 36 | 44 | |
| 212.241.13.0/24 | 31 | 44 | |
| 212.241.17.0/24 | 27 | 37 | |
| 212.241.26.0/24 | 26 | 30 | |
| 212.241.21.0/24 | 16 | 28 | |
| 212.241.19.0/24 | 15 | 23 | |
| 212.241.27.0/24 | 14 | 22 | |
| 212.241.30.0/24 | 11 | 18 | |
| 212.241.14.0/24 | 11 | 17 | |
| 212.241.15.0/24 | 9 | 18 | |
| 212.241.31.0/24 | 7 | 12 | |
| 212.241.9.0/24 | 1 | 255 | |
| 212.241.7.0/24 | 1 | 9 | |
| 212.241.6.0/24 | 1 | 5 | |
| 212.241.8.0/24 | 0 | 254 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- Ake.net
- AnyIP
- B2Proxy
- BirdProxies
- BlurPath
- BottingTools
- Bright Data
- ByteProxies
- Byteful
- CliProxy
- CoreProxy
- DataImpulse
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- GSocks
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GoProxies
- GonzoProxy
- IPFly
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonBright
- LemonPrime
- LudaxProxy
- MangoProxy
- Maskify
- MoMoProxy
- NSocks
- NodeProxy
- NovaProxy
- Novada
- Oxylabs
- PacketStream
- ProxiesVision
- Proxio
- Proxiware
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyRack
- ProxyWing
- Proxying
- Proxyma
- RainProxy
- RapidProxy
- Shifter
- Smartproxy
- StrikeProxy
- SwiftProxy
- Thordata
- ThunderProxy
- VantageProxies
- VitalExclusive
- Webshare
Announcements
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 212.241.0.0/20 since Nov 2008 | AS12997 | Residential | 1,013 362 always on | OJSC Kyrgyztelecom | |
| 212.241.16.0/20 since Nov 2008 | AS12997 | Residential | 885 631 always on | OJSC Kyrgyztelecom |
Registrations in this block
The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 212.241.0.0/19 | 8,192 | KG-KT-20080522 | OJSC Kyrgyztelecom (ORG-JK1-RIPE) · KG | ALLOCATED PA | May 22, 2008 | azolotko@ |
| └ 212.241.0.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Nov 19, 2008 | azolotko@ via KG-KT-20080522 |
| └ 212.241.1.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Nov 25, 2008 | azolotko@ via KG-KT-20080522 |
| └ 212.241.2.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Mar 9, 2012 | azolotko@ via KG-KT-20080522 |
| └ 212.241.3.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Mar 9, 2012 | azolotko@ via KG-KT-20080522 |
| └ 212.241.4.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Nov 25, 2008 | azolotko@ via KG-KT-20080522 |
| └ 212.241.5.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Nov 25, 2008 | azolotko@ via KG-KT-20080522 |
| └ 212.241.6.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Dec 29, 2008 | azolotko@ via KG-KT-20080522 |
| └ 212.241.7.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Dec 29, 2008 | azolotko@ via KG-KT-20080522 |
| └ 212.241.8.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Dec 29, 2008 | azolotko@ via KG-KT-20080522 |
| └ 212.241.9.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Dec 29, 2008 | azolotko@ via KG-KT-20080522 |
| └ 212.241.10.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Dec 29, 2008 | azolotko@ via KG-KT-20080522 |
| └ 212.241.11.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Dec 29, 2008 | azolotko@ via KG-KT-20080522 |
| └ 212.241.12.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Dec 29, 2008 | azolotko@ via KG-KT-20080522 |
| └ 212.241.13.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Dec 29, 2008 | azolotko@ via KG-KT-20080522 |
| └ 212.241.14.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Dec 29, 2008 | azolotko@ via KG-KT-20080522 |
| └ 212.241.15.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Dec 29, 2008 | azolotko@ via KG-KT-20080522 |
| └ 212.241.16.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Dec 29, 2008 | azolotko@ via KG-KT-20080522 |
| └ 212.241.17.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Dec 29, 2008 | azolotko@ via KG-KT-20080522 |
| └ 212.241.18.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Mar 29, 2010 | azolotko@ via KG-KT-20080522 |
| └ 212.241.19.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Mar 9, 2012 | azolotko@ via KG-KT-20080522 |
| └ 212.241.20.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Jan 8, 2009 | azolotko@ via KG-KT-20080522 |
| └ 212.241.21.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Jan 8, 2009 | azolotko@ via KG-KT-20080522 |
| └ 212.241.22.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Jan 8, 2009 | azolotko@ via KG-KT-20080522 |
| └ 212.241.23.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Jan 8, 2009 | azolotko@ via KG-KT-20080522 |
| └ 212.241.24.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Mar 29, 2010 | azolotko@ via KG-KT-20080522 |
| └ 212.241.25.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Mar 29, 2010 | azolotko@ via KG-KT-20080522 |
| └ 212.241.26.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Jan 8, 2009 | azolotko@ via KG-KT-20080522 |
| └ 212.241.27.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Jan 8, 2009 | azolotko@ via KG-KT-20080522 |
| └ 212.241.28.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Jan 8, 2009 | azolotko@ via KG-KT-20080522 |
| └ 212.241.29.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Jan 8, 2009 | azolotko@ via KG-KT-20080522 |
| └ 212.241.30.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Jan 8, 2009 | azolotko@ via KG-KT-20080522 |
| └ 212.241.31.0/24 | 256 | KYRGYZTELECOM_ | unknown | ASSIGNED PA | Jan 8, 2009 | azolotko@ via KG-KT-20080522 |
A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.
Network & registry
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- May 2008
- Current origin since
- May 2008 · 18 yr
- Origin networks
- 1
Whois
Registration for this announcement
- Range
- 212.
241. 0. 0/ 19 - Netname
- KG-KT-20080522
- Registrant
- OJSC Kyrgyztelecom
- Registrant country
- KG
- Organization
- OJSC Kyrgyztelecom (ORG-JK1-RIPE)
- Org country
- KG
- Type
- ALLOCATED PA
- Created
- May 22, 2008
- Updated
- Apr 16, 2019
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- KG
- Delegated
- May 22, 2008
- Status
- assigned
Report abuse
Abuse contact
- azolotko@
kt. kg - Name
- OJSC Kyrgyztelecom Contact Role
- Handle
- OKCR1-RIPE