Data as of Nov 20, 2026

95.56.251.0/24

20 residential-proxy exits · 30 days

JSC Kazakhtelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
30 / 100 · Medium
Recently moved
Recent change
New origin Sep 28, 2026
from AS39725 JSC Kazakhtelecom, after 7.1 years unannounced

Residential-proxy exits

Proxy exits
20
7.8% of its addresses · 30 days
Providers
54
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

3.9K observations

Proxy providers listing exits

  • 711Proxy
  • AETHYN_ELITE
  • Ake.net
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FLEETPROXY
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonode
  • HASDATA
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • QUANTICDATA
  • RainProxy
  • SOTAPROXY
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.56.0.0/16
since Dec 2018
AS9198Residential16,362
229 always on
JSC Kazakhtelecom
95.56.0.0/14
since Oct 2008
AS9198Residential60,671
845 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.56.251.0/24256IP_Internet_Company_First_PageunknownASSIGNED PASep 30, 2026abuse@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
Reactivated
First seen
Jul 2010
Current origin since
Sep 28, 2026 · 2 mo
Origin networks
2
Last change of origin
Sep 28, 2026
Recorded history

History

Handoffs
2