Data as of Nov 22, 2026

217.29.110.0/24

3 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
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
38
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

5.1K observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • Bright Data
  • Byteful
  • EnigmaProxy
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • GSocks
  • HELODATA
  • IPFly
  • IPPeak
  • Infatica
  • KocerRoxy
  • LOKIPROXY
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXIWARE_ECO
  • PYPROXY
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
217.29.104.0/21
since Apr 2011
AS48427Residential47
6 always on
Visovision S.L.
217.29.96.0/20
since May 2025
AS48427Residential104
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
May 2016
Current origin since
Jan 2017 · 9.8 yr
Origin networks
1