Data as of Nov 15, 2026

80.242.211.0/24

6 residential-proxy exits · 30 days

Qmobile JSC

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

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Always-on exits
4
67% of its exits
Providers
49
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

16K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • AnyIP
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • LightningProxies
  • MangoProxy
  • Maskify
  • NSocks
  • NodeProxy
  • NovaProxy
  • Novada
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • RapidProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

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
80.242.208.0/204,096KZ-KAZTRANSCOM-20090916Qmobile JSC (ORG-OA9-RIPE) · KZALLOCATED PAOct 11, 2017abuse@jusanmobile.kz
└ 80.242.211.0/24256QMOBILE"QMobile" JSCASSIGNED PAOct 13, 2021abuse@jusanmobile.kz
via KZ-KAZTRANSCOM-20090916

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
Nov 2013
Current origin since
Mar 2018 · 8.6 yr
Origin networks
2
Last change of origin
Mar 2018
Recorded history

History

Handoffs
1