Data as of Nov 16, 2026

37.228.66.0/24

6 residential-proxy exits · 30 days

Qmobile JSC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Always-on exits
1
17% of its exits
Providers
29
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

4.0K observations

Proxy providers listing exits

  • 2Captcha
  • BestProxy
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GEEKPROXY_FLEX
  • GSocks
  • GonzoProxy
  • IPOasis
  • IPPeak
  • Infatica
  • LightningProxies
  • MangoProxy
  • NSocks
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • VantageProxies
  • VibeProxies
  • VitalExclusive

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.228.64.0/212,048KZ-KAZTRANSCOM-20120410Qmobile JSC (ORG-OA9-RIPE) · KZALLOCATED PAApr 10, 2012abuse@jusanmobile.kz
└ 37.228.66.0/24256QMobile"QMobile" JSCASSIGNED PANov 14, 2017abuse@jusanmobile.kz
via KZ-KAZTRANSCOM-20120410

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jul 2012
Current origin since
Jul 2012 · 14 yr
Origin networks
1