Data as of Nov 14, 2026

85.208.16.0/22

5 residential-proxy exits · 30 days

Avatel Telecom, SA · space held by Vaecom Telecomunicaciones, SL

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

Residential-proxy exits

Proxy exits
5
0.49% of its addresses · 30 days
Always-on exits
1
20% of its exits
Spread
2 of 4
/24s with at least one exit
Providers
39
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

493 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
85.208.18.0/2412
85.208.16.0/2403

Proxy providers listing exits

  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BottingTools
  • CatProxies
  • EZProxies
  • Evomi
  • FastProxy
  • FloppyData
  • Geonode
  • GhostConnect
  • GloryCloud
  • HideProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • IPROCKET_PREMIUM
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LudaxProxy
  • MoMoProxy
  • NextProxy
  • NiuProxy
  • NovaProxy
  • Novada
  • ProxiesVision
  • Proxy302
  • ProxyGeo
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • RoamProxy
  • SwiftProxy
  • TalorData
  • ZENPROXY_LITE

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
85.208.16.0/221,024ES-VAECOM-20190220Vaecom Telecomunicaciones, SL (ORG-VTS20-RIPE) · ESALLOCATED PAApr 21, 2023abuse@vaecom.com
└ 85.208.16.0/24256customers-01unknownASSIGNED PAFeb 21, 2019abuse@vaecom.com
via ES-VAECOM-20190220
└ 85.208.17.0/24256customers-02unknownASSIGNED PAFeb 21, 2019abuse@vaecom.com
via ES-VAECOM-20190220
└ 85.208.18.0/24256customers-03unknownASSIGNED PAFeb 21, 2019abuse@vaecom.com
via ES-VAECOM-20190220
└ 85.208.19.0/24256customers-04unknownASSIGNED PAFeb 21, 2019abuse@vaecom.com
via ES-VAECOM-20190220

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

Who has announced this prefix

Summary

Routing history

Pattern
Reactivated
First seen
Feb 2019
Current origin since
Mar 2024 · 2.6 yr
Origin networks
2
Last change of origin
Mar 2024
Recorded history

History

Handoffs
1