Data as of Nov 13, 2026

217.196.28.0/24

5 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

2.0% of its addresses · 30 days

Providers

selling exits here

Oct 14, 2026 – Nov 12, 2026

Exits seen per day

40 observations

Proxy providers listing exits

AnyIP
BestProxy
FastProxy
LemonBright
RainProxy
Shifter
Smartproxy
Thordata
ThunderProxy

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.28.0/25	128	JUSAN-MOBILE	"Jusan Mobile" JSC	ASSIGNED PA	Sep 7, 2016	abuse@jusanmobile.kz via KZ-KAZTRANSCOM-20041007
└ 217.196.28.128/25	128	JUSAN-MOBILE	"Jusan Mobile" JSC	ASSIGNED PA	May 16, 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: Apr 2007
Current origin since: Apr 2007 · 20 yr
Origin networks: 1

RPKI

Route origin authorizations

ROA prefix	ASN	Max len	Anchor	Verdict
217.196.28.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