Data as of Nov 10, 2026

178.88.167.0/24

3 residential-proxy exits · 30 days

JSC Kazakhtelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low
Recent change
New origin Nov 6, 2026
its first announcement on record

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
15
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

299 observations

Proxy providers listing exits

  • ByteProxies
  • Byteful
  • GSocks
  • Geonix
  • Geonode
  • HideProxy
  • Infatica
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • ProxyGeo
  • Proxyma
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.88.0.0/16
since Mar 2019
AS9198Residential16,395
189 always on
JSC Kazakhtelecom
178.88.0.0/14
since Dec 2009
AS9198Residential63,746
2,065 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
178.88.0.0/14262,144KZ-KAZAKTELECOM-20091126JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZALLOCATED PANov 26, 2009abuse@telecom.kz
└ 178.88.167.0/24256IP_DIS_KZTSC Kazakhtelecom, Direction of Information SystemsASSIGNED PAJul 22, 2021abuse@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

Summary

Routing history

Pattern
Stable
First seen
Nov 6, 2026
Current origin since
Nov 6, 2026 · under a month
Origin networks
1