Data as of Nov 12, 2026

212.85.239.0/24

12 residential-proxy exits · 30 days

Comunicaciones Ronda, S.L.

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

Residential-proxy exits

Proxy exits
12
4.7% of its addresses · 30 days
Always-on exits
1
8.3% of its exits
Providers
44
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

1.1K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • Ake.net
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • Infatica
  • LUMIPROXY
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.85.238.0/23
since May 2018
AS198144Residential19
1 always on
Comunicaciones Ronda, S.L.
212.85.236.0/22
since Oct 2025
AS198144Residential37
2 always on
Comunicaciones Ronda, 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
212.85.236.0/221,024ES-COMUNICACIONESRONDA-20000519Comunicaciones Ronda, S.L. (ORG-CRS6-RIPE) · ESALLOCATED PAFeb 15, 2017albertoguerrero@charrytv.com
└ 212.85.238.0/23512COMUNICACIONESRONDAunknownASSIGNED PAAug 24, 2017albertoguerrero@charrytv.com
via ES-COMUNICACIONESRONDA-20000519

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
Aug 2025
Current origin since
Aug 2025 · 1.3 yr
Origin networks
1