Data as of Nov 13, 2026

5.63.113.48/30

1 residential-proxy exit · 30 days

JSC Kazakhtelecom

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

Residential-proxy exits

Proxy exits
1
25% of its addresses · 30 days
Always-on exits
1
100% of its exits
Providers
35
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

17 observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • 9Proxy
  • AnyIP
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Evomi
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonode
  • GonzoProxy
  • IPROCKET_PREMIUM
  • Infatica
  • LUMIPROXY
  • LemonBright
  • MangoProxy
  • NSocks
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
5.63.64.0/18
since Jun 2012
AS9198Residential2,739
30 always on
JSC Kazakhtelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
5.63.64.0/1816,384KZ-KAZAKTELECOM-20120612JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZALLOCATED PAJun 12, 2012abuse@telecom.kz
└ 5.63.113.48/304SEYPHLOMBARDAstanaASSIGNED PANov 11, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612

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

5.63.112.0/20

Routing history

Pattern
Stable
First seen
Jan 2014
Current origin since
Sep 2016 · 10 yr
Origin networks
1