Data as of Nov 21, 2026

178.88.116.0/24

1 residential-proxy exit · 30 days

JSC Kazakhtelecom

Announcement
RPKI valid
Announced by
Type
Business
50% of it

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
20
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

1.2K observations

Proxy providers listing exits

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

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.88.0.0/16
since Mar 2019
AS9198Residential17,127
149 always on
JSC Kazakhtelecom
178.88.0.0/14
since Dec 2009
AS9198Residential67,226
1,980 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
└ 178.88.116.128/25128MTNMCKAZAKTELECOMJSCProject "Parental Control"ASSIGNED 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.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Business12850%1
Residential12850%1

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