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

213.37.78.0/23

17 residential-proxy exits · 30 days

Vodafone ONO, S.A.

Announcement
213.37.0.0/16
RPKI valid
Announced by
AS6739
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
17
3.3% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
38
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

488 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
213.37.78.0/2409
213.37.79.0/2408

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • AnyIP
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • EZProxies
  • Evomi
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PrivateByte
  • Proxy-Seller
  • Proxy4U
  • ProxyGeo
  • PuraRoute
  • Shifter
  • Smartproxy
  • VitalExclusive

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
213.37.0.0/1665,536ES-ONO-991210Vodafone ONO, S.A. (ORG-OA4-RIPE) · ESALLOCATED PA—abuse@corp.vodafone.es
└ 213.37.66.0 - 213.37.107.25510,752ONOPROVIDERASSIGNED PAJul 1, 2003abuse@corp.vodafone.es
via ES-ONO-991210

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

Who has announced 213.37.0.0/16

213.37.0.0/16

Routing history

Pattern
Rotating
First seen
May 2005
Current origin since
Oct 2009 · 17 yr
Origin networks
3
Last change of origin
Nov 2025
Recorded history

History

Handoffs
2