Data as of Nov 11, 2026

217.11.76.0/24

14 residential-proxy exits · 30 days

Aspan telecom

Announcement

this exact prefix

No RPKI

Announced by

AS8720

Type

Residential

Risk

0 / 100 · Low

Residential-proxy exits

Proxy exits

5.5% of its addresses · 30 days

Always-on exits

14% of its exits

Providers

selling exits here

Oct 12, 2026 – Nov 10, 2026

Exits seen per day

5.6K observations

Proxy providers listing exits

711Proxy
911Proxy
Ake.net
AnyIP
B2Proxy
BestProxy
BirdProxies
BottingTools
Byteful
CatProxies
CoreProxy
DataImpulse
Decodo
EnigmaProxy
FastProxy
FlashProxy
HideProxy
IPFly
IPPeak
IPRoyal
LUMIPROXY
LemonBright
MarsProxies
NSocks
NiuProxy
NovaProxy
Novada
Oxylabs
ProxiesVision
Proxiware
Proxy4U
ProxyEmpire
ProxyGeo
ProxyRack
ProxyWing
PuraRoute
RainProxy
RoamProxy
Shifter
Smartproxy
Thordata
ThunderProxy
VantageProxies
VitalExclusive
Webshare
YumiProxy
ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

Prefix	Origin	Type	Proxy exits	Holder	RPKI
217.11.64.0/20 since Sep 2020	AS8720	Residential	175 5 always on	Aspan telecom

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.11.64.0/20	4,096	KZ-ASPANTELECOM-20081205	Aspan telecom (ORG-AT35-RIPE) · KZ	ALLOCATED PA	Dec 5, 2008	admin@aspan.kz
└ 217.11.76.0/24	256	ASPAN-KZ-NET	internet clients Aspan Telecom	ASSIGNED PA	Jul 28, 2017	admin@aspan.kz via KZ-ASPANTELECOM-20081205

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern: Stable
First seen: Jul 2013
Current origin since: Jul 2013 · 13 yr
Origin networks: 1