LAYER3 INTEL
Get started
Sign in
Data as of Nov 15, 2026

217.29.97.0/24

13 residential-proxy exits · 30 days

Visovision S.L.

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

Residential-proxy exits

Proxy exits
13
5.1% of its addresses · 30 days
Providers
60
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

7.2K observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • 911Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • GeekProxy
  • Geonode
  • GhostConnect
  • GonzoProxy
  • IPCola
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LightningProxies
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NextProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PSBProxy
  • PacketStream
  • PrivateByte
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • VProxy
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
217.29.96.0/21
since Oct 2010
AS48427Residential56
5 always on
Visovision S.L.
217.29.96.0/20
since May 2025
AS48427Residential101
11 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.96.0/212,048VISOVISIONVisovision S.LASSIGNED PASep 16, 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
May 2016
Current origin since
Jul 2021 · 5.4 yr
Origin networks
1