Data as of Nov 10, 2026

82.200.173.76/30

No anonymizer space · no proxy exits in 30 days

JSC Kazakhtelecom

Announcement
RPKI valid
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
3
75% of its addresses · listed by providers
Providers
24
selling exits here

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Evomi
  • FlashProxy
  • Geonode
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • LemonBright
  • NSocks
  • Oxylabs
  • PrivateProxy
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Shifter
  • Thordata
  • ThunderProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
82.200.160.0/20
since Aug 2005
AS9198Residential85
4 always on
JSC Kazakhtelecom
82.200.128.0/17
since May 2005
AS9198Residential762
38 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.173.76/304SIMAKSLLP Simaks SolanoASSIGNED PASep 23, 2015abuse@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.

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

82.200.173.0/24

Routing history

Pattern
Stable
First seen
Feb 2006
Current origin since
Dec 2018 · 7.9 yr
Origin networks
1