Data as of Nov 11, 2026

178.91.253.0/24

28 residential-proxy exits · 30 days

JSC Kazakhtelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
28
11% of its addresses · 30 days
Always-on exits
14
50% of its exits
Providers
60
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

8.0K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FlashProxy
  • GSocks
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LUMIPROXY
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PrivateProxy
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxyma
  • RainProxy
  • RapidProxy
  • ResiProxies
  • RoamProxy
  • Shifter
  • Smartproxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • Webshare
  • ZENPROXY_PREMIUM

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.253.0/24256NAZARBAEVYNIVERNAZARBAEVYNIVERASSIGNED PASep 9, 2010abuse@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
Jun 2010
Current origin since
Nov 2016 · 10 yr
Origin networks
1