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

178.91.18.0/23

256 residential-proxy exits · 30 days

JSC Kazakhtelecom

Announcement
this exact prefix
RPKI valid
Announced by
AS9198
Type
Residential
Recent change
New origin Oct 22, 2026
from AS9198 JSC Kazakhtelecom

Residential-proxy exits

Proxy exits
256
50% of its addresses · 30 days
Always-on exits
254
>99% of its exits
Spread
1 of 2
/24s with at least one exit
Providers
29
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

310K observations

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPRoyal
  • Infatica
  • Kookey
  • LemonBright
  • Maskify
  • Oxylabs
  • PacketStream
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.88.0.0/14
since Dec 2009
AS9198Residential64,548
1,642 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.91.16.0/212,048MTNMCKAZAKTELECOMJSCJSC Kazakhtelecom, Kazakhstan Online BackboneASSIGNED PASep 16, 2015abuse@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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

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