LAYER3 INTEL
Get started
Sign in
Data as of Nov 15, 2026

217.196.19.0/24

7 residential-proxy exits · 30 days

Qmobile JSC

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

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Always-on exits
5
71% of its exits
Providers
40
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

5.8K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • APROXY
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • CROXY
  • DataImpulse
  • Decodo
  • Evomi
  • FastProxy
  • FlashProxy
  • Geonode
  • IPRoyal
  • InfiniteProxies
  • KocerRoxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • NSocks
  • NiuProxy
  • Oxylabs
  • PROXY_CC
  • PrivateProxy
  • Proxy4U
  • ProxyRack
  • ProxyWing
  • RainProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • 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.19.0/24256JUSAN-MOBILE"Jusan Mobile" JSCASSIGNED PAJul 24, 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Mar 2009
Current origin since
Mar 2009 · 18 yr
Origin networks
1