Data as of Nov 15, 2026

46.238.64.0/18

45 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
45
0.27% of its addresses · 30 days
Always-on exits
3
6.7% of its exits
Spread
23 of 64
/24s with at least one exit
Providers
84
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

16K observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • INSTANTSOCKS_BASIC
  • IPFly
  • IPMUSK
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LemonBright
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MagneticProxy
  • MangoProxy
  • Maskify
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • PacketStream
  • PrivateProxy
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • QUANTICDATA
  • RH7Proxy
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • StrikeProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE

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
46.238.64.0/1816,384PL-INEASP-20110204INEA sp. z o.o. (ORG-ISZO91-RIPE) · PLALLOCATED PAAug 2, 2022abuse@inea.com.pl
└ 46.238.64.0/212,048INEA-Sp-z-oounknownASSIGNED PAJan 19, 2012abuse@inea.com.pl
via PL-INEASP-20110204
└ 46.238.72.0/212,048INEA-Sp-z-oounknownASSIGNED PAJan 19, 2012abuse@inea.com.pl
via PL-INEASP-20110204
└ 46.238.80.0/221,024INEA-Sp-z-oounknownASSIGNED PAJan 19, 2012abuse@inea.com.pl
via PL-INEASP-20110204
└ 46.238.84.0/221,024INEA-Sp-z-oounknownASSIGNED PAJan 19, 2012abuse@inea.com.pl
via PL-INEASP-20110204
└ 46.238.88.0/212,048INEA-Sp-z-oounknownASSIGNED PAMar 27, 2012abuse@inea.com.pl
via PL-INEASP-20110204
└ 46.238.96.0/212,048INEA-Sp-z-oounknownASSIGNED PAJul 3, 2012abuse@inea.com.pl
via PL-INEASP-20110204
└ 46.238.104.0/212,048INEA-Sp-z-oounknownASSIGNED PAJul 3, 2012abuse@inea.com.pl
via PL-INEASP-20110204
└ 46.238.112.0/212,048INEA-Sp-z-oounknownASSIGNED PAMar 27, 2012abuse@inea.com.pl
via PL-INEASP-20110204
└ 46.238.120.0/212,048INEA-Sp-z-ooINEA NetworkASSIGNED PAMar 27, 2012abuse@inea.com.pl
via PL-INEASP-20110204

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
Feb 2011
Current origin since
Feb 2011 · 16 yr
Origin networks
1