Data as of Nov 22, 2026

178.88.116.0/25

1 residential-proxy exit · 30 days

JSC Kazakhtelecom

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

Residential-proxy exits

Proxy exits
1
0.78% of its addresses · 30 days
Providers
20
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

1.3K observations

Proxy providers listing exits

  • AETHYN_ELITE
  • BirdProxies
  • Byteful
  • CYBERYOZH
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_TURBO
  • GSocks
  • HASDATA
  • Infatica
  • MangoProxy
  • NodeProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.88.0.0/16
since Mar 2019
AS9198Residential17,027
148 always on
JSC Kazakhtelecom
178.88.0.0/14
since Dec 2009
AS9198Residential66,564
1,941 always on
JSC Kazakhtelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
178.88.0.0/14262,144KZ-KAZAKTELECOM-20091126JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZALLOCATED PANov 26, 2009abuse@telecom.kz
└ 178.88.116.0/25128GPON_FTTH_SERVICESAktauASSIGNED PANov 21, 2014abuse@telecom.kz
via KZ-KAZAKTELECOM-20091126

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

178.88.116.0/22

Routing history

Pattern
Stable
First seen
Mar 2014
Current origin since
Oct 2016 · 10 yr
Origin networks
1