Data as of Nov 17, 2026

82.200.218.0/24

8 residential-proxy exits · 30 days

JSC Kazakhtelecom

Announcement
RPKI valid
Announced by
Type
Business
81% of it

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Providers
35
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

1.9K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9HTTP
  • ASHBURNPROXIES
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • GSocks
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • LemonBright
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXY_CC
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

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.218.0/2664SHNOSPetroKazakhstan Oil Products OJSCASSIGNED PAApr 23, 2004abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.64/304DOSTYK_COMunknownASSIGNED PAJul 9, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.68/304TASHENEV_UNIVERunknownASSIGNED PAOct 14, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.72/304TAZAARNAunknownASSIGNED PANov 3, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.76/304ALAGEUMAlageum LLPASSIGNED PAFeb 8, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.80/298MUHANShymkentASSIGNED PAFeb 27, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.88/304DDST_BAUYRZHANunknownASSIGNED PAJul 2, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.92/304TOOTAMERLANMOTORSShimkentASSIGNED PAJun 10, 2022abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.96/304AIBIKESHYMKENTASSIGNED PASep 9, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.100/304FOLLISunknownASSIGNED PAJul 14, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.104/298EMU-NETEurasia UniversityASSIGNED PAJan 26, 2006abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.112/304PERFECTLOMBARDunknownASSIGNED PAOct 22, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.116/304OBRAZOVANIE_SUZAKShymkentASSIGNED PANov 8, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.120/304M-GROUPunknownASSIGNED PAJun 12, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.124/304MLOMBARDThe company with limited liability < MLOMBARD >ASSIGNED PAMar 13, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.128/304SARIAGASHSKIIRAIONNIIOTDELOBRAZOVANIYShymkentASSIGNED PAApr 12, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.132/304SARIAGASHSKIIRAIONNIIOTDELOBRAZOVANIYShymkentASSIGNED PAApr 12, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.136/304SARIAGASHSKIIRAIONNIIOTDELOBRAZOVANIYShymkentASSIGNED PAApr 12, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.140/304PRAVITELSTVOGRAZHDANTURKESTANASSIGNED PAJan 9, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.160/2816IP_KHANSP Khan MikhailASSIGNED PANov 12, 2021abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.176/2816JUSAN-MOBILETurkestan region,Turkestan,sq.160/NICHEASSIGNED PANov 1, 2022abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.200/304DCSOURCEunknownASSIGNED PASep 21, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.204/304TOOLOMBARDPARTNERKAZAHSTANSHYMKENTASSIGNED PAJun 21, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.208/304OTDSOCIALSHYMunknownASSIGNED PAMay 19, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.212/304PRAVITELSTVADLYAGRAZHDANLengerASSIGNED PASep 7, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.216/304PRAVITELSTVOGRAZHDANunknownASSIGNED PAMay 28, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.228/304TEXNICHESKI_CENTR_SOZAKShymkentASSIGNED PAFeb 29, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.232/304SINOOILLLP <Sinooil>ASSIGNED PAOct 26, 2011abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.236/304HASTEXunknownASSIGNED PAOct 29, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.240/304MLOMBARDM-Lombard LLCASSIGNED PAJul 2, 2014abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.244/304GENSTOO "Gens"ASSIGNED PAJul 8, 2020abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.218.248/298BAYLANYSNAKKZBAYLANYSNAKKZASSIGNED PAAug 12, 2020abuse@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
Business20881%31
Residential3213%3
Mobile166.3%1

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

82.200.216.0/22

Routing history

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