Data as of Nov 14, 2026

82.200.183.0/24

5 residential-proxy exits · 30 days

JSC Kazakhtelecom

Announcement
RPKI valid
Announced by
Type
Business
83% of it

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
1
20% of its exits
Providers
31
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

1.9K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • Infatica
  • LemonBright
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
82.200.128.0/17
since May 2005
AS9198Residential820
52 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.183.0/298MINOBRAZINAYKI1MINOBRAZINAYKI1ASSIGNED PAJun 16, 2015abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.8/298GUSREDSHKOLA17GUSREDSHKOLA17ASSIGNED PAApr 10, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.24/298MINOBRAZINAYKI21MINOBRAZINAYKI21ASSIGNED PAJun 16, 2015abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.32/298TOOKZTURKMUNAITOOKZTURKMUNAIKENKIYAKASSIGNED PANov 30, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.40/298AONITAO <Nacion`lnye Informacionnye Tehnologii>ASSIGNED PASep 19, 2013abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.48/298MINOBRAZINAYKI35MINOBRAZINAYKI35ASSIGNED PAJun 16, 2015abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.56/298MINOBRAZINAYKI37MINOBRAZINAYKI37ASSIGNED PAJun 16, 2015abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.64/298GUKAZSREDOBSHKOLA39GUKAZSREDOBSHKOLA39ASSIGNED PAApr 10, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.80/298MINOBRAZINAYKI28MINOBRAZINAYKI28ASSIGNED PAJun 16, 2015abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.88/298GUSREDSHKOLA40GUSREDSHKOLA40ASSIGNED PAJul 28, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.96/298MINOBRAZINAYKI51MINOBRAZINAYKI51ASSIGNED PAJun 16, 2015abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.104/298KGUAOSKTLKGUAOSKTLASSIGNED PASep 3, 2015abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.112/298GUSREDSHKOLA19GUSREDSHKOLA19ASSIGNED PAMar 13, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.120/298MINOBRAZINAYKI23MINOBRAZINAYKI23ASSIGNED PAJun 16, 2015abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.136/298GUSREDNSHKOLA26GUSREDNSHKOLA26ASSIGNED PAJan 19, 2016abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.144/298MINOBRAZINAYKI24MINOBRAZINAYKI24ASSIGNED PAJun 16, 2015abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.152/298RG_BRANDSThe company with limited liability RG BRANDS KAZASSIGNED PAFeb 8, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.160/298TOOENERGOSISTEMAAktobeASSIGNED PADec 31, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.168/298ALGAMEKTEPBAKSHA1ALGAMEKTEPBAKSHA1ASSIGNED PAJul 21, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.176/298ALGARAYOTDELOBRAZOVANIYAALGARAYOTDELOBRAZOVANIYAASSIGNED PAJul 28, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.184/298ALGARAYOTDELOBRAZOVANIYAALGARAYOTDELOBRAZOVANIYAASSIGNED PAJul 27, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.192/304TOOOBITTAktobeASSIGNED PAJul 29, 2021abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.196/304MINFINunknownASSIGNED PAFeb 12, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.200/304BAIGROZSPROGRAMunknownASSIGNED PASep 21, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.204/304TOOQAZAQREPUBLICAktobeASSIGNED PADec 4, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.216/304GLOBALWINEAKTOBEAktobeASSIGNED PASep 5, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.220/304TOOKZTRADINGAktobeASSIGNED PAMay 24, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.224/304KGU_SHOKALALYCEIINTERNATURALSKASSIGNED PAJan 6, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.228/304TOOAVISLGSAktobeASSIGNED PAMay 24, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.244/304RAISONSECURITIESLIMITEDAktobeASSIGNED PADec 22, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.248/304FNAOPDGAOAktobeASSIGNED PAFeb 21, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.183.252/304IPKARAKENOVAMAAktobeASSIGNED PAOct 25, 2019abuse@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
Business21283%32
Residential4417%5

Network & registry

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