Data as of Nov 11, 2026

93.185.77.0/24

37 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
37
14% of its addresses · 30 days
Always-on exits
1
2.7% of its exits
Providers
43
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

6.3K observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • Evomi
  • GSocks
  • Geonix
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LUMIPROXY
  • LemonBright
  • LemonPrime
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
93.185.72.0/21
since Apr 2020
AS35104Mobile81
2 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
93.185.64.0/204,096KZ-KAZTRANSCOM-20080606Qmobile JSC (ORG-OA9-RIPE) · KZALLOCATED PAJun 6, 2008abuse@jusanmobile.kz
└ 93.185.75.0 - 93.185.77.255768QMOBILE"QMobile" JSCASSIGNED PASep 15, 2017abuse@jusanmobile.kz
via KZ-KAZTRANSCOM-20080606

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
Feb 2009
Current origin since
Feb 2009 · 18 yr
Origin networks
1