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

37.228.67.0/24

7 residential-proxy exits · 30 days

Qmobile JSC

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

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Providers
52
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

1.3K observations

Proxy providers listing exits

  • 911Proxy
  • APROXY
  • ASHBURNPROXIES
  • AnyIP
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CROXY
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • FastProxy
  • GSocks
  • Geonix
  • GloryCloud
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • Infatica
  • KindProxy
  • Kookey
  • LemonBright
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • PROXY_CC
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

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.67.0/24256QMobile"QMobile" JSCASSIGNED PAJul 26, 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
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