Data as of Nov 13, 2026

217.11.72.0/24

20 residential-proxy exits · 30 days

Aspan telecom

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
20
7.8% of its addresses · 30 days
Providers
38
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

538 observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • APROXY
  • ASHBURNPROXIES
  • BestProxy
  • BottingTools
  • Byteful
  • CROXY
  • DataImpulse
  • Decodo
  • EZProxies
  • Evomi
  • FastProxy
  • GeekProxy
  • Geonode
  • LUMIPROXY
  • LemonBright
  • NSocks
  • NiuProxy
  • NovaProxy
  • Oxylabs
  • PROXYSALE
  • PROXY_CC
  • PSBProxy
  • PrivateByte
  • Proxy302
  • Proxy4U
  • ProxyGeo
  • Proxying
  • Q2IP
  • RainProxy
  • ResiProxies
  • Shifter
  • Smartproxy
  • Thordata
  • VProxy
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
217.11.64.0/20
since Sep 2020
AS8720Residential175
8 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.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
217.11.64.0/204,096KZ-ASPANTELECOM-20081205Aspan telecom (ORG-AT35-RIPE) · KZALLOCATED PADec 5, 2008admin@aspan.kz
└ 217.11.72.0/24256ASPAN-KZ-NETTOO Aspan TelecomASSIGNED PAJul 28, 2017admin@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

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Feb 2013
Current origin since
Feb 2013 · 14 yr
Origin networks
1