Data as of Nov 16, 2026

217.196.24.0/24

3 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
3
1.2% of its addresses · 30 days
Providers
26
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

260 observations

Proxy providers listing exits

  • BottingTools
  • Byteful
  • CatProxies
  • CliProxy
  • Evomi
  • FastProxy
  • Geonode
  • IPFly
  • IPPeak
  • InfiniteProxies
  • LudaxProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • ProxyGeo
  • PuraRoute
  • Q2IP
  • RainProxy
  • Shifter
  • Thordata
  • 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
217.196.16.0/204,096KZ-KAZTRANSCOM-20041007Qmobile JSC (ORG-OA9-RIPE) · KZALLOCATED PAOct 7, 2004abuse@jusanmobile.kz
└ 217.196.24.0/24256JUSAN-MOBILE"Jusan Mobile" JSCASSIGNED PANov 3, 2017abuse@jusanmobile.kz
via KZ-KAZTRANSCOM-20041007

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