Data as of Nov 16, 2026

82.200.206.0/24

7 residential-proxy exits · 30 days

JSC Kazakhtelecom

Announcement
RPKI valid
Announced by
Type
Business
98% of it

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Always-on exits
2
29% of its exits
Providers
50
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

1.5K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9HTTP
  • APROXY
  • ASHBURNPROXIES
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CROXY
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • PROXY_CC
  • Proxies.fo
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • ProxyWing
  • RainProxy
  • Shifter
  • Smartproxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
82.200.128.0/17
since May 2005
AS9198Residential843
72 always on
JSC Kazakhtelecom

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
82.200.128.0/1732,768KZ-KAZAKTELECOM-20030918JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZALLOCATED PASep 18, 2003abuse@telecom.kz
└ 82.200.206.0/304IP_SPACEPavlodar c. Mira st. 14ASSIGNED PAMar 3, 2022abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.4/304MLOMBARDThe company with limited liability <MLOMBARD>ASSIGNED PASep 22, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.8/304TARASENKONVPAVLODARASSIGNED PAJan 30, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.12/304KGKPAKSUZHAYAUMPAVLODARASSIGNED PAJan 31, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.16/304GYOPSHERBRAIONAPAVLODARASSIGNED PASep 12, 2022abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.20/304DISunknownASSIGNED PANov 2, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.24/304IPKAMERCELIPKAMERCELASSIGNED PASep 1, 2011abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.28/304TOODCGERTISPAVLODARASSIGNED PAAug 29, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.32/2732IP_Lorer_CorporationLorer AndreyASSIGNED PADec 5, 2011abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.64/304BAKBogatyr Akses KomirASSIGNED PAMar 21, 2006abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.68/304APBaizakovaPAVLODARASSIGNED PAJun 22, 2020abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.72/304DISPavlodarASSIGNED PASep 8, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.76/304MIKRK_GCHPPavlodarASSIGNED PASep 2, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.84/304TOOOSTINPAVLODARASSIGNED PAMar 3, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.88/298TOOBARSNORDPAVLODARASSIGNED PAJun 26, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.96/304DISPavlodarASSIGNED PASep 8, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.100/304DISPavlodarASSIGNED PASep 8, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.104/304PFNTBPF NTBASSIGNED PAOct 12, 2007abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.108/304TOOUPNKPVPAVLODARASSIGNED PAMar 16, 2016abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.112/304AKIMATGU Apparat Akima OblastiASSIGNED PAMay 29, 2007abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.116/304SHKOLAYALTYNSARINAAKSUASSIGNED PAJun 20, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.120/304DKSELROZPAVLODARASSIGNED PAFeb 3, 2020abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.124/304GSMNETGSM KazakhstanASSIGNED PADec 23, 2011abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.128/304IACJC Information Centre-RegistrationASSIGNED PASep 27, 2016abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.132/304AIRASTANASJSC Air AstanaASSIGNED PAAug 16, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.136/304komGosuchrezhdenieshkola7AKSUASSIGNED PAApr 30, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.140/304IP_DBDPavlodarASSIGNED PAAug 6, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.144/304MKLOMBARDKZThe company with limited liability MKLOMBARDASSIGNED PASep 24, 2014abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.148/304PS-6unknownASSIGNED PAFeb 18, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.152/304MIKRK_GCHPPavlodarASSIGNED PASep 2, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.156/304GUPOOBESPECHENIYUKACHVSFEREOBRAZPavlodarASSIGNED PAJan 20, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.160/304MIKRK_GCHPPavlodarASSIGNED PASep 2, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.164/304TOODCSOURCEunknownASSIGNED PAJul 2, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.168/304AOEEKPAVLODARASSIGNED PAMar 6, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.172/304TOOSOUZTMPAVLODARASSIGNED PAFeb 20, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.176/304GKKPDETSKYIECOZENTRunknownASSIGNED PAJul 16, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.180/304TOOSTELVGPPAVLODARASSIGNED PAFeb 26, 2013abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.184/304MTNMCKAZAKTELECOMJSCBGP (DTV)ASSIGNED PADec 15, 2014abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.188/304GYIKONOMunknownASSIGNED PAJul 17, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.192/2816MTNMCKazakhtelecomDSCAlmatyASSIGNED PADec 8, 2015abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.208/304SHKOLAYALTYNSARINAAKSUASSIGNED PAJun 20, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.212/304KAZPOSTPavlodarASSIGNED PASep 25, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.216/304GIMNAZIIA7unknownASSIGNED PAJul 17, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.220/304TOO12MESYACPAVLODARASSIGNED PAOct 26, 2016abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.224/304TOOITSPACEPAVLODARASSIGNED PAFeb 4, 2020abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.228/304MINFINunknownASSIGNED PAFeb 13, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.232/304SOSH3IRTIRTISHSKASSIGNED PAFeb 19, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.236/304GYOTDZEMAKSYPAVLODARASSIGNED PASep 9, 2022abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.240/304DISJuniper MX960 DPCASSIGNED PAFeb 18, 2014abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.244/304AOMAIKAINPAVLODARASSIGNED PAJun 17, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.206.248/298DISPavlodarASSIGNED PASep 8, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Business25298%51
Residential41.6%1

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

82.200.204.0/22

Routing history

Pattern
Stable
First seen
Aug 2005
Current origin since
Aug 2005 · 21 yr
Origin networks
1