Data as of Nov 11, 2026

80.87.32.0/20

12 residential-proxy exits · 30 days

INEA sp. z o.o.

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

Residential-proxy exits

Proxy exits
12
0.29% of its addresses · 30 days
Always-on exits
1
8.3% of its exits
Spread
5 of 16
/24s with at least one exit
Providers
45
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

1.1K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FloppyData
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPOasis
  • Infatica
  • LemonBright
  • MangoProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RolaProxy
  • Shifter
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

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
80.87.32.0/204,096PL-INEASP-20090415INEA sp. z o.o. (ORG-ISZO91-RIPE) · PLALLOCATED PAAug 2, 2022abuse@inea.com.pl
└ 80.87.32.0/221,024INEA-Sp-z-ooINEA Sp. z o.o.ASSIGNED PAJun 14, 2019abuse@inea.com.pl
via PL-INEASP-20090415
└ 80.87.36.0/23512INEA-Sp-z-ooINEA Sp. z o.o.ASSIGNED PAJun 14, 2019abuse@inea.com.pl
via PL-INEASP-20090415
└ 80.87.38.48/2816INEA-Sp-z-oounknownASSIGNED PAJun 14, 2019abuse@inea.com.pl
via PL-INEASP-20090415
└ 80.87.39.0/24256INEA-Sp-z-ooINEA Sp. z o.o.ASSIGNED PAJun 14, 2019abuse@inea.com.pl
via PL-INEASP-20090415
└ 80.87.40.0/212,048INEA-Sp-z-ooINEA Sp. z o.o.ASSIGNED PAMar 23, 2015abuse@inea.com.pl
via PL-INEASP-20090415

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
Stable
First seen
Apr 2009
Current origin since
Mar 2015 · 12 yr
Origin networks
2
Last change of origin
Mar 2015
Recorded history

History

Handoffs
1