LAYER3 INTEL
Get started
Sign in
Data as of Nov 12, 2026

82.200.182.0/24

9 residential-proxy exits · 30 days

JSC Kazakhtelecom

Announcement
82.200.182.0/23
RPKI valid
Announced by
AS9198
Type
Business
81% of it

Residential-proxy exits

Proxy exits
9
3.5% of its addresses · 30 days
Providers
40
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

7.3K observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • 9Proxy
  • Ake.net
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CROXY
  • CliProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GSocks
  • Geonode
  • GonzoProxy
  • IPPeak
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
82.200.128.0/17
since May 2005
AS9198Residential815
40 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.182.0/304MINTRUDASOCZASHRKunknownASSIGNED PAMar 2, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.4/304MTEKHSERVICEAktobeASSIGNED PAJan 18, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.8/304NEO_ASIANEO AsiaASSIGNED PASep 17, 2009abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.12/304MTNMC_Kazakhtelecom_JSCAktobeASSIGNED PAMay 19, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.16/298TOOCKiZAIGERIMTOO CKiZ AIGERIMASSIGNED PASep 17, 2009abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.24/298GUAAKIMAAOAktobeASSIGNED PAJun 16, 2021abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.32/304TOODAYMEKSunknownASSIGNED PAJul 29, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.36/304OBLTERRITORINSPEKTSIYAAktobeASSIGNED PAJan 13, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.40/304TOOVAMOunknownASSIGNED PASep 10, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.44/304FORTEBANKunknownASSIGNED PAJun 5, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.48/304TOOOAAMANATKUZETAktobeASSIGNED PAJan 23, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.52/304FORTEBANKunknownASSIGNED PAJun 5, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.56/304UILROSZPAktobeASSIGNED PAJan 23, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.64/304IP_KoylibaevKoylibaev AmirzhanASSIGNED PANov 11, 2011abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.68/304KGUTEMIRDYSSunknownASSIGNED PAOct 14, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.72/298TOOSBURSERVISTOOSBURSERVISASSIGNED PAOct 31, 2014abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.80/304AKMURDISTRIBAKMURDISTRIBASSIGNED PANov 19, 2010abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.84/304RGPNNSRSSZunknownASSIGNED PAOct 27, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.96/304SHKOLAYASNOEGUUTVSAKTunknownASSIGNED PAJun 8, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.100/304AOKTKin AktobeASSIGNED PAMay 19, 2009abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.112/304AFTOODOKNISGAFTOODOKNISGASSIGNED PAMay 22, 2006abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.116/304TRAYOTDELOBRAZOVANIYAunknownASSIGNED PASep 17, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.120/304TRAYOTDELOBRAZOVANIYAunknownASSIGNED PASep 17, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.124/304EVRAZIAN-FUDS-KORPOREISHNAktobe city, Sankibay Batyra st.1ASSIGNED PADec 29, 2022abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.128/304SHKOLABELOGORKAGUUTVSAKTunknownASSIGNED PAMay 8, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.132/304GORPSIHOLOGMEDPEDKONSULT4unknownASSIGNED PAApr 23, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.136/304SHKOLA17GUUTVSAKTunknownASSIGNED PAMay 4, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.140/304CCBANKunknownASSIGNED PAJan 30, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.144/304MKLOMBARDKZunknownASSIGNED PAMar 5, 2020abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.148/304GHARYSHKZunknownASSIGNED PAMar 13, 2020abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.152/304IPBAIZHARKINOVAMunknownASSIGNED PAAug 18, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.156/304GUMARTUKROKFKSAktobeASSIGNED PAJan 30, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.160/304TOOEVERESTSAktobeASSIGNED PAJan 17, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.164/304MIKRK_GCHPAktobeASSIGNED PAOct 17, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.168/304AOPASSAZHPEREVOZKIAktobeASSIGNED PAFeb 1, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.172/304KGUCPSIRGIZAktobeASSIGNED PAApr 2, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.176/304MKLOMBARDKZThe company with limited liability <MKLOMBARD>ASSIGNED PAJun 28, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.180/304MKLOMBARDKZThe company with limited liability <MKLOMBARD>ASSIGNED PAJun 28, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.184/304IPADILBEKAktobeASSIGNED PAApr 21, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.188/304KARAUYLSELAKIMATunknownASSIGNED PAFeb 16, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.200/304MKLOMBARDKZThe company with limited liability < MKLOMBARD >ASSIGNED PAJul 13, 2016abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.208/304MTNMCKAZAKTELECOMJSCJSC KazakhtelecomASSIGNED PAJan 18, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.212/304GKPOCPZGUUZAOAktobeASSIGNED PADec 31, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.216/304ASTANAEXPOTRADELTDAktobeASSIGNED PAJun 20, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.224/304Speed_TestAktobeASSIGNED PASep 22, 2020abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.228/304IP_Centrall_ApparatAktobeASSIGNED PAOct 7, 2020abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.232/304IP_Centrall_ApparatAktobeASSIGNED PAOct 7, 2020abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.236/304MINTRUDASOCZASHRKunknownASSIGNED PAMar 5, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.240/304MTNMC_Kazakhtelecom_DSCAktobeASSIGNED PAMar 27, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.248/304FRGPPHVKMERKAAktobeASSIGNED PAApr 24, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.182.252/304TOOOHRANASHUNARTOOOHRANASHUNARASSIGNED PANov 9, 2016abuse@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%49
Residential4819%8

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

82.200.182.0/23

Routing history

Pattern
Stable
First seen
Oct 2014
Current origin since
Oct 2014 · 12 yr
Origin networks
1