Data as of Nov 16, 2026

185.48.150.0/24

21 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
21
8.2% of its addresses · 30 days
Always-on exits
2
9.5% of its exits
Providers
55
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

2.1K observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • 9HTTP
  • APROXY
  • ASHBURNPROXIES
  • AnyIP
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CROXY
  • CliProxy
  • EnigmaProxy
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • GEEKPROXY_FLEX
  • GSocks
  • Geonix
  • HELODATA
  • IPFly
  • IPPeak
  • Infatica
  • KocerRoxy
  • LUMIPROXY
  • LemonBright
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYLANE
  • PROXYSALE
  • PROXYSCRAPE
  • PROXY_CC
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyGeo
  • 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
185.48.148.0/221,024KZ-KAZTRANSCOM1-20140221Qmobile JSC (ORG-KJ13-RIPE) · KZALLOCATED PAFeb 21, 2014abuse@jusanmobile.kz
└ 185.48.150.0/24256JUSAN-MOBILE"Jusan Mobile" JSCASSIGNED PAJun 15, 2017abuse@jusanmobile.kz
via KZ-KAZTRANSCOM1-20140221

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
Mar 2014
Current origin since
Mar 2014 · 13 yr
Origin networks
1