Data as of Nov 22, 2026

213.16.12.0/24

6 residential-proxy exits · 30 days

Canal + Telecom SAS

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

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Providers
46
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

4.1K observations

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FlashProxy
  • GEEKPROXY_TURBO
  • Geonode
  • GoProxies
  • GonzoProxy
  • HASDATA
  • IP2WORLD
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • KindProxy
  • LOKIPROXY
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NextProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYSCRAPE
  • Proxy-Cheap
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • Thordata
  • YumiProxy
  • ZENPROXY_LITE

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.12.0/24256FR-MEDIASERVRabbit Double Play (Phone + Internet) Mediaserv broadband ADSL 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