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

37.150.124.136/30

No anonymizer space · no proxy exits in 30 days

JSC Kazakhtelecom

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

Residential-proxy exits

Proxy exits
10
100% of its addresses · listed by providers
Always-on exits
2
20% of its exits
Providers
39
selling exits here

Proxy providers listing exits

  • 2Captcha
  • ASHBURNPROXIES
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • HydraProxy
  • IPPeak
  • Infatica
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.150.0.0/15
since Mar 2012
AS9198Residential29,927
1,071 always on
JSC Kazakhtelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
37.150.0.0/15131,072KZ-KAZAKTELECOM-20120306JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZALLOCATED PAMar 6, 2012abuse@telecom.kz
└ 37.150.124.136/304GUKTIunknownASSIGNED PAMar 16, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20120306

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

37.150.96.0/19

Routing history

Pattern
Stable
First seen
May 2012
Current origin since
Oct 2016 · 10 yr
Origin networks
1