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

2.134.13.44/30

1 residential-proxy exit · 30 days

JSC Kazakhtelecom

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

Residential-proxy exits

Proxy exits
1
25% of its addresses · 30 days
Providers
39
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

58 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LemonLabs
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
2.132.0.0/14
since Jan 2011
AS9198Residential62,166
1,842 always on
JSC Kazakhtelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
2.132.0.0/14262,144KZ-KAZAKTELECOM-20101223JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZALLOCATED PADec 23, 2010abuse@telecom.kz
└ 2.134.13.44/304GUSOSH4BAYANAULASSIGNED PAMar 17, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223

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

2.134.0.0/18

Routing history

Pattern
Stable
First seen
Jan 2011
Current origin since
Oct 2016 · 10 yr
Origin networks
1