Data as of Nov 10, 2026

37.150.2.0/23

256 residential-proxy exits · 30 days

JSC Kazakhtelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Recent change
New origin Oct 22, 2026
from AS9198 JSC Kazakhtelecom

Residential-proxy exits

Proxy exits
256
50% of its addresses · 30 days
Always-on exits
255
>99% of its exits
Spread
1 of 2
/24s with at least one exit
Providers
28
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

297K observations

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • Decodo
  • Evomi
  • FlashProxy
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPRoyal
  • Infatica
  • Kookey
  • LemonBright
  • Maskify
  • Oxylabs
  • PacketStream
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.150.0.0/18
since Dec 2018
AS9198Residential3,903
815 always on
JSC Kazakhtelecom
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 the announcement: those covering it, widest first, then every record inside it, 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.0.0/212,048MTNMCKAZAKTELECOMJSCJSC Kazakhtelecom, Kazakhstan Online BackboneASSIGNED PASep 16, 2015abuse@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

Summary

Routing history

Pattern
Stable
First seen
Nov 2017
Current origin since
Oct 22, 2026 · under a month
Origin networks
1