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

82.200.186.0/24

12 residential-proxy exits · 30 days

JSC Kazakhtelecom

Announcement
82.200.184.0/22
RPKI valid
Announced by
AS9198
Type
Business
72% of it

Residential-proxy exits

Proxy exits
12
4.7% of its addresses · 30 days
Always-on exits
2
17% of its exits
Providers
54
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

6.4K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9Proxy
  • APROXY
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CROXY
  • CliProxy
  • Decodo
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPOasis
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYSALE
  • PROXY_CC
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
82.200.128.0/17
since May 2005
AS9198Residential837
68 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.186.0/298KMGAUTOMATIONAtyrauASSIGNED PAMay 26, 2022abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.8/298ARCTICARCTICASSIGNED PAMay 23, 2016abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.24/298TOOTTKAtyrauASSIGNED PASep 14, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.32/304DETSADKYZGALDAKunknownASSIGNED PASep 23, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.36/304PTIANPZPTIANPZASSIGNED PAOct 11, 2016abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.48/304ELCOMKKKAtyrauASSIGNED PAMar 10, 2022abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.52/304QAZAQGAZAIMAQunknownASSIGNED PAAug 17, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.56/298RUSMOTORSRUSMOTORSASSIGNED PAOct 25, 2016abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.64/304KBKBETONunknownASSIGNED PAJun 26, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.68/304PRIRODNYIREZERVATAtyrauASSIGNED PAFeb 15, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.72/298ZIGERMUNAIGAZZIGERMUNAIGAZASSIGNED PAOct 27, 2016abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.96/304PC-2_1150AtyrauASSIGNED PAJun 15, 2022abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.100/304SULTANGUBIEVSULTANGUBIEVASSIGNED PAOct 4, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.104/304SULTANGUBIEVSULTANGUBIEVASSIGNED PAOct 4, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.108/304SULTANGUBIEVSULTANGUBIEVASSIGNED PAOct 4, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.112/304SULTANGUBIEVSULTANGUBIEVASSIGNED PAOct 4, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.116/304NYSANBAEVASHCOLANYSANBAEVASHCOLAASSIGNED PAOct 4, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.120/304MOMYSHYLUSHCOLAMOMYSHYLUSHCOLAASSIGNED PAOct 4, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.124/304OTDELOBRAZOVANIYunknownAGGREGATED-BY-LIRMar 17, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.128/304URALMETALLINVESTURALMETALLINVESTASSIGNED PANov 17, 2016abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.132/304NURTILEKSERVICEunknownASSIGNED PAJun 23, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.136/298TIMALCONSULTINGTIMALCONSULTINGASSIGNED PANov 17, 2016abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.144/304CASPIANROYALFISHCASPIANROYALFISHASSIGNED PANov 23, 2016abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.148/304ANTARESAKPANTARESAKPASSIGNED PAJul 31, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.160/304APPARATMASLIHunknownASSIGNED PAOct 12, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.164/304APPARATMASLIHunknownASSIGNED PAOct 12, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.184/304DZHULKASHEVADZHULKASHEVAASSIGNED PAJan 25, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.200/304MEDKOLLEDZHAtyrauASSIGNED PAMay 26, 2022abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.204/304BOLASHAKATYRAUAtyrauASSIGNED PAAug 11, 2022abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.208/304OROZOVANIA53unknownASSIGNED PAOct 6, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.216/304OTDELKULTYRYSPORTAOTDELKULTYRYSPORTAASSIGNED PAFeb 24, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.220/304ATYRVINEPROunknownASSIGNED PASep 25, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.224/304OCSGROUPLIMunknownASSIGNED PASep 25, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.228/304GALIYLLAGALIYLLAASSIGNED PAMar 14, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.232/304APPARATAKIMAunknownASSIGNED PASep 28, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.236/304OBSLUJLISPRESTARunknownASSIGNED PASep 30, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.240/304DETSADKYZGALDAKunknownASSIGNED PASep 25, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.244/304DEPARTAMENTUSTICIIDEPARTAMENTUSTICIIASSIGNED PAMar 17, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.248/304DEPARTAMENTUSTICIIDEPARTAMENTUSTICIIASSIGNED PAMar 17, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.186.252/304DEPARTAMENTUSTICIIDEPARTAMENTUSTICIIASSIGNED PAMar 17, 2017abuse@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
Business18472%40
Residential7228%7

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
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