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

95.57.232.0/24

256 residential-proxy exits · 30 days

JSC Kazakhtelecom

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

Residential-proxy exits

Proxy exits
256
100% of its addresses · 30 days
Always-on exits
6
2.3% of its exits
Providers
38
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

90K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CoreProxy
  • 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
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.56.0.0/14
since Oct 2008
AS9198Residential57,706
595 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.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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

95.57.232.0/22

Routing history

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