Data as of Nov 14, 2026

95.59.246.0/24

256 residential-proxy exits · 30 days

JSC Kazakhtelecom

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
256
100% of its addresses · 30 days
Always-on exits
10
3.9% of its exits
Providers
35
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

122K observations

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • Maskify
  • NSocks
  • Oxylabs
  • PacketStream
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.59.0.0/16
since Oct 2021
AS9198Residential13,477
173 always on
JSC Kazakhtelecom
95.56.0.0/14
since Oct 2008
AS9198Residential59,030
657 always on
JSC Kazakhtelecom

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.56.0.0/14262,144KZ-KAZAKTELECOM-20080923JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZALLOCATED PASep 23, 2008abuse@telecom.kz
└ 95.59.244.0/221,024GPON_FTTH_SERVICES_KTJSC KazakhtelecomASSIGNED PAApr 14, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20080923

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

95.59.244.0/22

Routing history

Pattern
Stable
First seen
Jun 2013
Current origin since
Oct 2016 · 10 yr
Origin networks
1