Data as of Nov 15, 2026

217.196.18.0/24

4 residential-proxy exits · 30 days

Qmobile JSC

Announcement

this exact prefix

RPKI valid

Announced by

AS35104

Type

Mobile

Risk

10 / 100 · Low

Shared address

Residential-proxy exits

Proxy exits

1.6% of its addresses · 30 days

Always-on exits

25% of its exits

Providers

selling exits here

Oct 16, 2026 – Nov 14, 2026

Exits seen per day

731 observations

Proxy providers listing exits

711Proxy
911Proxy
APROXY
ASHBURNPROXIES
BestProxy
BirdProxies
BottingTools
CROXY
FastProxy
LUMIPROXY
LemonBright
NSocks
NiuProxy
Novada
PROXY_CC
ProxyWing
RainProxy
Shifter
Smartproxy
Thordata
ThunderProxy
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.

Range	Addresses	Netname	Holder	Type	Created	Abuse contact
217.196.16.0/20	4,096	KZ-KAZTRANSCOM-20041007	Qmobile JSC (ORG-OA9-RIPE) · KZ	ALLOCATED PA	Oct 7, 2004	abuse@jusanmobile.kz
└ 217.196.18.0/24	256	JUSAN-MOBILE	"Jusan Mobile" JSC	ASSIGNED PA	Apr 27, 2017	abuse@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

Announcement Routing history RPKI & IRR Whois & abuse

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

RPKI

Route origin authorizations

ROA prefix	ASN	Max len	Anchor	Verdict
217.196.18.0/24	AS35104	/24	RIPE	RPKI valid
217.196.16.0/20	AS6453	/20	RIPE	Another network
217.196.16.0/20	AS6854	/20	RIPE	Another network
217.196.16.0/20	AS41798	/20	RIPE	Another network
217.196.16.0/20	AS43994	/20	RIPE	Another network

IRR

Route objects on the exact prefix

Origin	Registry	Description	Maintainer	Modified
AS35104	RIPE	"Jusan Mobile" JSC	MNT-ALCO-2K	Oct 25, 2021