Data as of Nov 12, 2026

178.237.128.0/22

5 residential-proxy exits · 30 days

Avatel Telecom, SA

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

Residential-proxy exits

Proxy exits
5
0.49% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
42
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

1.9K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
178.237.129.0/2403
178.237.128.0/2401
178.237.131.0/2401

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • AnyIP
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_PREMIUM

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
178.237.128.0/204,096ES-AVATELTELECOM-20100625Avatel Telecom, SA (ORG-WBS4-RIPE) · ESALLOCATED PAJun 25, 2010abuse@avatel.es
└ 178.237.128.0 - 178.237.141.2553,584TELEALHAMATelealhama S.L.ASSIGNED PAJun 28, 2010abuse@avatel.es
via ES-AVATELTELECOM-20100625

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 178.237.128.0/20

178.237.128.0/20

Routing history

Pattern
Rotating
First seen
Jul 2010
Current origin since
Jan 2024 · 2.9 yr
Origin networks
2
Last change of origin
Jan 2024
Recorded history

History

Handoffs
1