Data as of Nov 12, 2026

5.187.96.0/20

49 residential-proxy exits · 30 days

Canal + Telecom SAS

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

Residential-proxy exits

Proxy exits
49
1.2% of its addresses · 30 days
Always-on exits
3
6.1% of its exits
Spread
13 of 16
/24s with at least one exit
Providers
72
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

21K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FuseProxy
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonBright
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MarsProxies
  • MoMoProxy
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • RealProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • Webshare
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
5.187.96.0/19
since Sep 2012
AS21351Residential94
6 always on
Canal + Telecom SAS

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
5.187.96.0/198,192GP-CANALPLUSTELECOM-20120810Canal + Telecom SAS (ORG-MA21-RIPE) · GPALLOCATED PAAug 10, 2012cplustelecom.abuse@canal-plus.com
└ 5.187.96.0/24256FR-MEDIASERVMediaservASSIGNED PAAug 31, 2012cplustelecom.abuse@canal-plus.com
via GP-CANALPLUSTELECOM-20120810
└ 5.187.97.0/24256FR-MEDIASERVMediaservASSIGNED PAAug 31, 2012cplustelecom.abuse@canal-plus.com
via GP-CANALPLUSTELECOM-20120810
└ 5.187.98.0/24256FR-MEDIASERVMediaservASSIGNED PAAug 31, 2012cplustelecom.abuse@canal-plus.com
via GP-CANALPLUSTELECOM-20120810
└ 5.187.99.0/24256FR-MEDIASERVMediaservASSIGNED PAAug 31, 2012cplustelecom.abuse@canal-plus.com
via GP-CANALPLUSTELECOM-20120810
└ 5.187.100.0/24256FR-MEDIASERVMediaservASSIGNED PAAug 31, 2012cplustelecom.abuse@canal-plus.com
via GP-CANALPLUSTELECOM-20120810
└ 5.187.101.0/24256FR-MEDIASERVMediaservASSIGNED PAAug 31, 2012cplustelecom.abuse@canal-plus.com
via GP-CANALPLUSTELECOM-20120810
└ 5.187.102.0/24256FR-MEDIASERVMediaservASSIGNED PAAug 31, 2012cplustelecom.abuse@canal-plus.com
via GP-CANALPLUSTELECOM-20120810
└ 5.187.103.0/24256FR-MEDIASERVMediaservASSIGNED PAAug 31, 2012cplustelecom.abuse@canal-plus.com
via GP-CANALPLUSTELECOM-20120810
└ 5.187.104.0/24256FR-MEDIASERVMediaservASSIGNED PAAug 31, 2012cplustelecom.abuse@canal-plus.com
via GP-CANALPLUSTELECOM-20120810
└ 5.187.105.0/24256FR-MEDIASERVMediaservASSIGNED PAAug 31, 2012cplustelecom.abuse@canal-plus.com
via GP-CANALPLUSTELECOM-20120810
└ 5.187.106.0/24256FR-MEDIASERVMediaservASSIGNED PAAug 31, 2012cplustelecom.abuse@canal-plus.com
via GP-CANALPLUSTELECOM-20120810
└ 5.187.107.0/24256FR-MEDIASERVMediaservASSIGNED PAAug 31, 2012cplustelecom.abuse@canal-plus.com
via GP-CANALPLUSTELECOM-20120810
└ 5.187.108.0/24256FR-MEDIASERVMediaservASSIGNED PAAug 31, 2012cplustelecom.abuse@canal-plus.com
via GP-CANALPLUSTELECOM-20120810
└ 5.187.109.0/24256FR-MEDIASERVMediaservASSIGNED PAAug 31, 2012cplustelecom.abuse@canal-plus.com
via GP-CANALPLUSTELECOM-20120810
└ 5.187.110.0/24256FR-MEDIASERVMediaservASSIGNED PAAug 31, 2012cplustelecom.abuse@canal-plus.com
via GP-CANALPLUSTELECOM-20120810
└ 5.187.111.0/24256FR-MEDIASERVMediaservASSIGNED PAAug 31, 2012cplustelecom.abuse@canal-plus.com
via GP-CANALPLUSTELECOM-20120810

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
May 2023
Current origin since
May 2023 · 3.5 yr
Origin networks
1