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

82.200.207.0/24

3 residential-proxy exits · 30 days

JSC Kazakhtelecom

Announcement
82.200.204.0/22
RPKI valid
Announced by
AS9198
Type
Business
83% of it

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
23
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

284 observations

Proxy providers listing exits

  • BestProxy
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • GSocks
  • GonzoProxy
  • Infatica
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • VantageProxies

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.207.0/304ENPFAO <NPF GNPF>ASSIGNED PAJul 27, 2012abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.4/304ENPFAO <NPF GNPF>ASSIGNED PAJul 27, 2012abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.8/304ENPFAO <NPF GNPF>ASSIGNED PAJul 27, 2012abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.12/304DVLineDVLineASSIGNED PANov 5, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.16/298IP_DBDunknownASSIGNED PAOct 7, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.24/304DISJSC Kazakhtelecom, Direction of Information SystemASSIGNED PAAug 10, 2012abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.28/304DISJSC Kazakhtelecom, Direction of Information SystemASSIGNED PAAug 10, 2012abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.32/304RGUMINISTERSTVOFINANSOVRKunknownASSIGNED PAFeb 27, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.36/304BOGATYRSOSHMaiskASSIGNED PAJul 11, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.40/304AOPAVRECHPAOPAVLODARSKIYRECHNOIPORTASSIGNED PASep 28, 2012abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.44/304OtdpredAKTOGAIASSIGNED PAApr 19, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.48/304GUZANSOCPRPAVPavlodarASSIGNED PADec 31, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.52/304MIKRK_GCHPunknownASSIGNED PANov 9, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.56/304TOOVIAMEDISunknownASSIGNED PAMar 20, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.60/304GYORSEKSHERBRAIONAPAVLODARASSIGNED PASep 9, 2022abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.64/2732MTNMC_KazakhtelecomGoogleASSIGNED PAJun 2, 2021abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.96/2816IP_ITSHEFF_KZLLC ITSHEFF.KZASSIGNED PAApr 23, 2021abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.112/298IP_NBILLC «nbi»ASSIGNED PAOct 16, 2020abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.128/2732PAVLODARENERGOPAVLODARENERGOASSIGNED PAAug 24, 2015abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.160/2816DISIlya ChernushenkoASSIGNED PAAug 21, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.176/2816DISKirill RulASSIGNED PAAug 21, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.192/304KGUSOSH12EKIBASTUZASSIGNED PAFeb 24, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.196/304TOOUPNKPVPAVLODARASSIGNED PANov 30, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.200/298TOORUBIKOM2PavlodarASSIGNED PAApr 24, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.208/304Speed_TestPavlodarASSIGNED PASep 22, 2020abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.212/304RGUMINISTERSTVOFINANSOVRKunknownASSIGNED PAFeb 27, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.216/298DISPavel OgiyASSIGNED PAFeb 8, 2013abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.224/304DISPavlodarASSIGNED PASep 8, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.228/304DISSC Kazakhtelecom, Information Technology DivisionASSIGNED PAApr 30, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.236/304GUOTDELZANZTOSTIPAVLPavlodarASSIGNED PADec 30, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.240/298SMARTNETSMARTNETASSIGNED PAFeb 11, 2013abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.248/304RGUMINISTERSTVOFINANSOVRKunknownASSIGNED PAMar 2, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20030918
└ 82.200.207.252/304RGUMINISTERSTVOFINANSOVRKunknownASSIGNED PAMar 2, 2026abuse@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%3

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

82.200.204.0/22

Routing history

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