Data as of Nov 22, 2026

185.226.16.0/22

7 residential-proxy exits · 30 days

Rezocean SAS

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

Residential-proxy exits

Proxy exits
7
0.68% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
46
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

197 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.226.18.0/2404
185.226.16.0/2403

Proxy providers listing exits

  • 2Extract
  • AETHYN_BASIC
  • AETHYN_ELITE
  • Ake.net
  • AnyIP
  • BirdProxies
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FROXY
  • FastProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • HPROXY
  • HideProxy
  • Infatica
  • KocerRoxy
  • LemonBright
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXIWARE_ECO
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • RainProxy
  • SCRAPELESS
  • SOTAPROXY
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE
  • 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
185.226.16.0/221,024FR-REZOCEAN-20171016Rezocean SAS (ORG-RS207-RIPE) · FRALLOCATED PADec 13, 2019abuse@rezocean.fr
└ 185.226.16.0/24256REZOCEAN-SUBNET2REZOCEAN CustomersASSIGNED PAOct 16, 2017abuse@rezocean.fr
via FR-REZOCEAN-20171016
└ 185.226.17.0/24256REZOCEAN-SUBNET2REZOCEAN CustomersASSIGNED PAOct 16, 2017abuse@rezocean.fr
via FR-REZOCEAN-20171016
└ 185.226.18.0/24256REZOCEAN-SUBNET2REZOCEAN CustomersASSIGNED PAOct 16, 2017abuse@rezocean.fr
via FR-REZOCEAN-20171016
└ 185.226.19.0/24256REZOCEAN-SUBNET2REZOCEAN CustomersASSIGNED PAOct 16, 2017abuse@rezocean.fr
via FR-REZOCEAN-20171016

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
Oct 2017
Current origin since
Oct 2017 · 9.1 yr
Origin networks
1