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

5.63.114.4/30

No anonymizer space · no proxy exits in 30 days

JSC Kazakhtelecom

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

Residential-proxy exits

Proxy exits
9
100% of its addresses · listed by providers
Providers
43
selling exits here

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • CROXY
  • CliProxy
  • Datarama
  • EZProxies
  • Evomi
  • FastProxy
  • Geonode
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • Kookey
  • LUMIPROXY
  • LemonBright
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Proxiware
  • ProxyEmpire
  • ProxyGeo
  • ProxyWing
  • Proxyma
  • RainProxy
  • RapidProxy
  • Shifter
  • Smartproxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
5.63.64.0/18
since Jun 2012
AS9198Residential2,724
27 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.114.4/304IP_ERMAGAMBETOVZHEunknownASSIGNED PAMay 20, 2026abuse@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

AnnouncementRouting historyRPKI & IRRWhois & abuse
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