Data as of Nov 10, 2026

37.150.63.76/30

No anonymizer space · no proxy exits in 30 days

JSC Kazakhtelecom

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

Residential-proxy exits

Proxy exits
12
100% of its addresses · listed by providers
Always-on exits
3
25% of its exits
Providers
41
selling exits here

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • BestProxy
  • BirdProxies
  • BottingTools
  • Byteful
  • DataImpulse
  • Evomi
  • FastProxy
  • FlashProxy
  • Geonode
  • GloryCloud
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonBright
  • NSocks
  • NiuProxy
  • Novada
  • Proxiware
  • Proxy4U
  • ProxyRack
  • ProxyWing
  • RainProxy
  • RapidProxy
  • RolaProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.150.0.0/15
since Mar 2012
AS9198Residential29,567
1,244 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.63.76/304TOOZHANELSECURITYAtyrauASSIGNED PAJul 30, 2025abuse@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

Routing timeline

Covering aggregate above, the prefix's own history below

37.150.0.0/18

Routing history

Pattern
Stable
First seen
Apr 2012
Current origin since
Dec 2018 · 7.9 yr
Origin networks
1