Data as of Nov 20, 2026

82.200.184.0/24

8 residential-proxy exits · 30 days

JSC Kazakhtelecom

Announcement
RPKI valid
Announced by
Type
Business
73% of it

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Providers
37
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

204 observations

Proxy providers listing exits

  • 711Proxy
  • 9HTTP
  • Ake.net
  • BestProxy
  • BirdProxies
  • BottingTools
  • Byteful
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • KocerRoxy
  • LUMIPROXY
  • LemonBright
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • Proxyma
  • PuraRoute
  • RainProxy
  • RoamProxy
  • Shifter
  • Smartproxy
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
82.200.128.0/17
since May 2005
AS9198Residential870
80 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.184.0/2732IP_IshkaraevAnuarbek IshkaraevASSIGNED PAApr 28, 2010abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.32/304GORODSCAYPOLICLINICA2GORODSCAYPOLICLINICA2ASSIGNED PAMay 6, 2011abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.36/304SBERBANKSBERBANKASSIGNED PAApr 20, 2011abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.40/304AKKISTAPPARATunknownASSIGNED PAApr 7, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.48/304TRANSPOETHOLDYNGunknownASSIGNED PAMar 18, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.52/304MIALYSHKOLAMIALYSHKOLAASSIGNED PAApr 26, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.56/304TOOTITANEXPERTAtyrauASSIGNED PAOct 21, 2022abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.60/304SHKOLAERKINOVASHKOLAERKINOVAASSIGNED PAAug 24, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.64/304AKKISTAPPARATunknownASSIGNED PAFeb 26, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.68/304RAUANNALCORAUANNALCOASSIGNED PAMay 23, 2011abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.72/304ATYRKOMYTunknownASSIGNED PASep 23, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.76/304YASLISAD17AtyrauASSIGNED PAJan 11, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.80/304DETSAD30AtyrauASSIGNED PAMay 13, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.84/304MEGAPOLIS_KAZunknownASSIGNED PAAug 25, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.88/304DETSKAIADEREVNYAunknownASSIGNED PAFeb 23, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.92/304YASLIKUNSHUAKunknownASSIGNED PAJul 13, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.100/304EMBAMUNAIAVTOMATICAEMBAMUNAIAVTOMATICAASSIGNED PAJun 24, 2011abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.104/298OTBASY_BANKunknownASSIGNED PAOct 14, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.112/298OTBASY_BANKunknownASSIGNED PAOct 14, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.120/304ZEFIRKAunknownASSIGNED PAJun 22, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.124/304KURMANGAZYAKIMATunknownASSIGNED PAJun 11, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.144/304YASLISADKOKTEMGULIunknownASSIGNED PANov 3, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.148/304AMANATAMANATASSIGNED PADec 3, 2015abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.176/2816PSNKAZSTROYPSNKAZSTROYASSIGNED PAAug 11, 2011abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.192/304SHCOLA32SHCOLA32ASSIGNED PAOct 4, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.196/304MIYLYHOSPITALMIYLYHOSPITALASSIGNED PANov 9, 2011abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.200/304AMANATAMANATASSIGNED PADec 3, 2015abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.204/304KAIYRSHAHTYMUZSCHOOLAtyrauASSIGNED PAJan 11, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.208/298Fabrika_ResheniFabrika ResheniASSIGNED PAJan 30, 2009abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.224/304INDERAYEZOVAINDERAYEZOVAASSIGNED PAApr 14, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.228/304SREDNAYSHCOLAAYEZOVASREDNAYSHCOLAAYEZOVAASSIGNED PAApr 27, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.232/304GAITYEIVENCHERSAtyrauASSIGNED PADec 24, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.236/304SELENASAAunknownASSIGNED PAApr 8, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.184.240/304AITIESAtyrauskaya oblast', Inderskiy rayon, p. Inderborskiy, ul. Promzona b/nASSIGNED PAAug 27, 2022abuse@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
Business18873%34
Residential6827%6

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

82.200.184.0/22

Routing history

Pattern
Stable
First seen
Aug 2005
Current origin since
Oct 2016 · 10 yr
Origin networks
1