Data as of Nov 11, 2026

213.16.3.0/24

3 residential-proxy exits · 30 days

Canal + Telecom SAS

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
2
67% of its exits
Providers
41
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

17K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • DataImpulse
  • Decodo
  • EZProxies
  • Evomi
  • FlashProxy
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPCola
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • MoMoProxy
  • NextProxy
  • Novada
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • Shifter
  • SwiftProxy
  • Thordata
  • YumiProxy

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.3.0/24256FR-MEDIASERVMediaserv Dialup customersASSIGNED PAOct 6, 2004cplustelecom.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