Data as of Nov 15, 2026

217.196.23.0/24

5 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
5
2.0% of its addresses · 30 days
Providers
28
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

566 observations

Proxy providers listing exits

  • AnyIP
  • BottingTools
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • GSocks
  • Infatica
  • KocerRoxy
  • LemonBright
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxiware
  • Proxy302
  • ProxyWing
  • RH7Proxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • 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
217.196.16.0/204,096KZ-KAZTRANSCOM-20041007Qmobile JSC (ORG-OA9-RIPE) · KZALLOCATED PAOct 7, 2004abuse@jusanmobile.kz
└ 217.196.23.0/24256JUSAN-MOBILE"Jusan Mobile" JSCASSIGNED PAMay 4, 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 2010
Current origin since
Jul 2010 · 16 yr
Origin networks
1