Data as of Nov 16, 2026

84.236.156.0/24

8 residential-proxy exits · 30 days

Aire Networks del Mediterraneo SL Unipersonal

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

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Always-on exits
1
13% of its exits
Providers
42
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

1.1K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • FROXY
  • FlashProxy
  • FloppyData
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GonzoProxy
  • Infatica
  • KocerRoxy
  • Kookey
  • LemonBright
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • RainProxy
  • RapidProxy
  • Shifter
  • StrikeProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
84.236.156.0/22
since Jun 2009
AS29119Internet provider40
1 always on
Aire Networks del Mediterraneo SL Unipersonal
84.236.128.0/17
since Dec 2012
AS29119Internet provider1,340
297 always on
Aire Networks del Mediterraneo SL Unipersonal

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
84.236.128.0/1732,768ES-AIRENETWORKS-20090409Aire Networks del Mediterraneo SL Unipersonal (ORG-ANDM1-RIPE) · ESALLOCATED PAAug 23, 2019abuse@airenetworks.es
└ 84.236.156.0/24256LCR-NET-20171118-8LCR END UsersASSIGNED PAJan 13, 2025abuse@airenetworks.es
via ES-AIRENETWORKS-20090409

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