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

217.196.26.0/23

6 residential-proxy exits · 30 days

Qmobile JSC

Announcement
this exact prefix
RPKI valid
Announced by
AS35104
Type
Mobile

Residential-proxy exits

Proxy exits
6
1.2% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
16
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

246 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
217.196.26.0/2403
217.196.27.0/2403

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • BestProxy
  • CROXY
  • FastProxy
  • LUMIPROXY
  • LemonBright
  • NSocks
  • NiuProxy
  • RainProxy
  • Shifter
  • Smartproxy
  • ThunderProxy
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
217.196.26.0/24
since Apr 2010
AS35104Mobile3Qmobile JSC
217.196.27.0/24
since Jul 2010
AS35104Mobile3Qmobile 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
217.196.16.0/204,096KZ-KAZTRANSCOM-20041007Qmobile JSC (ORG-OA9-RIPE) · KZALLOCATED PAOct 7, 2004abuse@jusanmobile.kz
└ 217.196.26.0/23512JUSAN-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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Nov 2018
Current origin since
Apr 2020 · 6.6 yr
Origin networks
1