Data as of Nov 12, 2026

185.48.149.0/24

38 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
38
15% of its addresses · 30 days
Always-on exits
2
5.3% of its exits
Providers
57
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

7.3K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • Kookey
  • LUMIPROXY
  • LemonBright
  • LemonPrime
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RoamProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
185.48.148.0/23
since Apr 2020
AS35104Mobile65
16 always on
Qmobile JSC

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.149.0/24256JUSAN-MOBILE"Jusan Mobile" JSCASSIGNED PAJul 31, 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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Apr 2014
Current origin since
Apr 2014 · 13 yr
Origin networks
1