bgpreport

Network · data from 2026-11-12

AS29264 CDN-CANAL-PLUS Canal+ Tech SAS

Registry name: CDN-CANAL-PLUS Canal+ Tech SAS, FR · not in PeeringDB

2IPv4 routes 0.0% RPKI valid · 100.0% with a route object
3IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
5No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS29264, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS29264, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

185.86.254.0/23 No ROA RIR databaseRIPE 673 100% 67
185.86.252.0/23 No ROA RIR databaseRIPE 672 100% 67
2a05:bd40:d17::/48 No ROA RIR databaseRIPE 635 100% 67
2a05:bd40:d13::/48 No ROA RIR databaseRIPE 633 100% 67
2a05:bd40:cd13::/48 No ROA RIR databaseRIPE 633 100% 67

AS-SET

AS29264 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 8 are in fix.csv.

  • ROA: none5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none185.86.254.0/23No ROA covers it. Add a ROA for AS29264, maxLength 23.673 of 673
ROA: none185.86.252.0/23No ROA covers it. Add a ROA for AS29264, maxLength 23.672 of 673
ROA: none2a05:bd40:d17::/48No ROA covers it. Add a ROA for AS29264, maxLength 48.635 of 636
ROA: none2a05:bd40:d13::/48No ROA covers it. Add a ROA for AS29264, maxLength 48.633 of 636
ROA: none2a05:bd40:cd13::/48No ROA covers it. Add a ROA for AS29264, maxLength 48.633 of 636

Route objects not announced

Route objects with origin AS29264 whose prefix no peer sees AS29264 announce. Many are kept on purpose (backup routes, space announced only in some places).

185.86.253.0/24RIPENo ROA
2a05:bd40::/32RIPENo ROA
2a05:bd42::/32RIPENo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.