Data as of Nov 11, 2026

93.185.72.0/21

81 residential-proxy exits · 30 days

Qmobile JSC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Mobile

Residential-proxy exits

Proxy exits
81
4.0% of its addresses · 30 days
Always-on exits
2
2.5% of its exits
Spread
7 of 8
/24s with at least one exit
Providers
69
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

15K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • HideProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • ResiProxies
  • Shifter
  • Smartproxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
93.185.73.0/24
since Apr 2009
AS35104Mobile7Qmobile JSC
93.185.74.0/24
since May 2009
AS35104Mobile6Qmobile JSC
93.185.75.0/24
since Nov 2009
AS35104Mobile4Qmobile JSC
93.185.76.0/24
since Jan 2009
AS35104Mobile8Qmobile JSC
93.185.77.0/24
since Feb 2009
AS35104Mobile37
1 always on
Qmobile JSC
93.185.78.0/24
since Apr 2009
AS35104Mobile15
1 always on
Qmobile JSC
93.185.79.0/24
since Jun 2009
AS35104Mobile4Qmobile 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.72.0/24256QMOBILE"QMobile" JSCASSIGNED PAAug 7, 2017abuse@jusanmobile.kz
via KZ-KAZTRANSCOM-20080606
└ 93.185.73.0/24256QMOBILE"QMobile" JSCASSIGNED PASep 11, 2017abuse@jusanmobile.kz
via KZ-KAZTRANSCOM-20080606
└ 93.185.74.0/24256QMOBILE"QMobile" JSCASSIGNED PASep 11, 2017abuse@jusanmobile.kz
via KZ-KAZTRANSCOM-20080606
└ 93.185.75.0 - 93.185.77.255768QMOBILE"QMobile" JSCASSIGNED PASep 15, 2017abuse@jusanmobile.kz
via KZ-KAZTRANSCOM-20080606
└ 93.185.78.0/24256QMOBILE"QMobile" JSCASSIGNED PANov 10, 2026abuse@jusanmobile.kz
via KZ-KAZTRANSCOM-20080606
└ 93.185.79.0/24256QMOBILE"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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Dec 2009
Current origin since
Apr 2020 · 6.6 yr
Origin networks
1