Data as of Nov 21, 2026

217.29.104.0/24

5 residential-proxy exits · 30 days

Visovision S.L.

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Providers
24
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

76 observations

Proxy providers listing exits

  • AnyIP
  • BUYPERSONALPROXY
  • BlurPath
  • CliProxy
  • Evomi
  • FROXY
  • FastProxy
  • HPROXY
  • IPFly
  • IPPeak
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • NovProxy
  • PROXYSAVER
  • Proxiware
  • ProxyGeo
  • PuraRoute
  • SCRAPELESS
  • SPYDERPROXY_BASIC
  • ThunderProxy
  • VantageProxies
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
217.29.104.0/21
since Apr 2011
AS48427Residential46
6 always on
Visovision S.L.
217.29.96.0/20
since May 2025
AS48427Residential103
9 always on
Visovision S.L.

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.29.96.0/204,096ES-VISOVISION-20081017Visovision S.L. (ORG-VS24-RIPE) · ESALLOCATED PAOct 17, 2008visovision@visovision.com
└ 217.29.104.0/212,048VISOVISIONVisovision S.LASSIGNED PADec 15, 2010visovision@visovision.com
via ES-VISOVISION-20081017

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
Oct 2016
Current origin since
Jun 2021 · 5.5 yr
Origin networks
1