Data as of Nov 10, 2026

95.57.232.0/22

1,024 residential-proxy exits · 30 days

JSC Kazakhtelecom

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

Residential-proxy exits

Proxy exits
1,024
100% of its addresses · 30 days
Always-on exits
24
2.3% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
42
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

358K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
95.57.233.0/247256
95.57.232.0/246256
95.57.234.0/246256
95.57.235.0/245256

Proxy providers listing exits

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

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.56.0.0/14
since Oct 2008
AS9198Residential57,047
959 always on
JSC Kazakhtelecom

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.56.0.0/14262,144KZ-KAZAKTELECOM-20080923JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZALLOCATED PASep 23, 2008abuse@telecom.kz
└ 95.57.232.0/221,024GPON_FTTH_SERVICESJSC KazakhtelecomASSIGNED PAJan 31, 2020abuse@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

Summary

Routing history

Pattern
Stable
First seen
Feb 2018
Current origin since
Feb 2018 · 8.8 yr
Origin networks
1