Data as of Nov 20, 2026

213.16.18.0/24

8 residential-proxy exits · 30 days

Canal + Telecom SAS

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

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Always-on exits
2
25% of its exits
Providers
37
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

4.0K observations

Proxy providers listing exits

  • 9HTTP
  • AETHYN_ELITE
  • BirdProxies
  • BottingTools
  • Byteful
  • CYBERYOZH
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FLEETPROXY
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • HASDATA
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
213.16.0.0/198,192GP-CANALPLUSTELECOM-990630Canal + Telecom SAS (ORG-MA21-RIPE) · GPALLOCATED PAOct 28, 2002cplustelecom.abuse@canal-plus.com
└ 213.16.18.0/24256FR-MEDIASERVMediaserv RABBIT triple play customersASSIGNED PASep 25, 2007cplustelecom.abuse@canal-plus.com
via GP-CANALPLUSTELECOM-990630

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 213.16.0.0/19

213.16.0.0/19

Routing history

Pattern
Stable
First seen
Sep 2008
Current origin since
Sep 2008 · 18 yr
Origin networks
1