bgpreport

Network · data from 2026-11-12

AS21351 Canal+ Telecom

Registry name: CANALPLUSTELECOM Canal + Telecom SAS, GP · PeeringDB

23IPv4 routes 73.9% RPKI valid · 65.2% with a route object
19IPv6 routes 78.9% RPKI valid · 89.5% with a route object
0RPKI invalid 0 origin · 0 maxLength
10No ROA 10 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
65Route objects not announced registered with origin AS21351, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS21351, 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.

154.67.36.0/22 No ROA Nonecovered by 154.67.32.0/19 673 100% 66
2c0f:f608:4100::/40 No ROA Nonecovered by 2c0f:f608:4000::/36 636 100% 67
2605:adc0:1000::/36 No ROA Nonecovered by 2605:adc0::/32 631 99% 67
154.67.0.0/17 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
154.67.128.0/17 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
154.67.2.0/24 No ROA RIR databaseAFRINIC 671 100% 66
104.250.0.0/19 No ROA RIR databaseARIN 669 99% 67
107.191.208.0/20 No ROA RIR databaseARIN, RIPE-NONAUTH 669 99% 67
2c0f:f608:4000::/36 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 636 100% 69
2605:adc0:2000::/36 No ROA RIR databaseARIN 631 99% 67
185.29.50.0/24 Valid Nonecovered by 185.29.50.0/23 673 100% 67
5.187.96.0/20 Valid Nonecovered by 5.187.96.0/19 669 99% 67
5.187.112.0/20 Valid Nonecovered by 5.187.96.0/19 669 99% 67
95.138.112.0/23 Valid Nonecovered by 95.138.0.0/17 669 99% 67
213.188.176.0/22 Valid Nonecovered by 213.188.160.0/19 669 99% 67
95.138.112.0/22 Valid Nonecovered by 95.138.0.0/17 668 99% 67
213.188.176.0/23 Valid Nonecovered by 213.188.160.0/19 668 99% 67
161.22.64.0/18 Valid Other IRR onlyRIPE-NONAUTH 668 99% 67
2803:1680:3000::/36 Valid Other IRR onlyRIPE-NONAUTH 630 99% 67
185.29.48.0/22 Valid RIR databaseRIPE 673 100% 67
185.161.8.0/24 Valid RIR databaseRIPE 673 100% 66
213.188.190.0/24 Valid RIR databaseRIPE 673 100% 67
5.187.96.0/19 Valid RIR databaseRIPE 669 99% 67
46.238.128.0/18 Valid RIR databaseRIPE 669 99% 67
93.121.128.0/17 Valid RIR databaseRIPE 669 99% 67
95.138.0.0/17 Valid RIR databaseRIPE 669 99% 67
213.16.0.0/19 Valid RIR databaseRIPE 669 99% 67
213.188.160.0/19 Valid RIR databaseRIPE 669 99% 67
2a02:1390:4000::/40 Valid RIR databaseRIPE 636 100% 67
2a02:1390:5000::/40 Valid RIR databaseRIPE 636 100% 67
2a02:1390:9000::/40 Valid RIR databaseRIPE 636 100% 67
2a02:1390:d000::/40 Valid RIR databaseRIPE 636 100% 67
2a02:1390:f000::/40 Valid RIR databaseRIPE 636 100% 67
2a02:1391:5100::/40 Valid RIR databaseRIPE 636 100% 67
2a02:1397:4000::/40 Valid RIR databaseRIPE 636 100% 67
2a02:1397:5000::/40 Valid RIR databaseRIPE 636 100% 67
2a02:1390:3000::/40 Valid RIR databaseRIPE 631 99% 67
2a02:1390:b000::/40 Valid RIR databaseRIPE 631 99% 67
2a02:1390:1000::/36 Valid RIR databaseRIPE 630 99% 67
2a02:1390:2000::/36 Valid RIR databaseRIPE 630 99% 67
2a02:1390:7000::/36 Valid RIR databaseRIPE 630 99% 67
2a02:1390:1000::/40 Valid RIR databaseRIPE 146 23% 53

AS-SET

PeeringDB's irr_as_set for AS21351: AS-CPLUSTELECOM. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS21351 isn't in the set, or no route object for AS21351 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS21351 in itNot covered
AS-CPLUSTELECOM RIPE 242575 Yes 0

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 87 are in fix.csv.

  • ROA: none10
  • Route object: none10
  • Route object: RIR2
  • Route object: not announced65
ChangePrefix or setDetailFull-table peers
ROA: none154.67.36.0/22No ROA covers it. Add a ROA for AS21351, maxLength 22.673 of 673
Route object: none154.67.36.0/22No route object for it. A route object for 154.67.32.0/19 with origin AS21351 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21351 in the RIR database for the space.673 of 673
ROA: none2c0f:f608:4100::/40No ROA covers it. Add a ROA for AS21351, maxLength 40.636 of 636
Route object: none2c0f:f608:4100::/40No route object for it. A route object for 2c0f:f608:4000::/36 with origin AS21351 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21351 in the RIR database for the space.636 of 636
ROA: none2605:adc0:1000::/36No ROA covers it. Add a ROA for AS21351, maxLength 36.631 of 636
Route object: none2605:adc0:1000::/36No route object for it. A route object for 2605:adc0::/32 with origin AS21351 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21351 in the RIR database for the space.631 of 636
ROA: none154.67.0.0/17No ROA covers it. Add a ROA for AS21351, maxLength 17.673 of 673
ROA: none154.67.128.0/17No ROA covers it. Add a ROA for AS21351, maxLength 17.673 of 673
ROA: none154.67.2.0/24No ROA covers it. Add a ROA for AS21351, maxLength 24.671 of 673
ROA: none104.250.0.0/19No ROA covers it. Add a ROA for AS21351, maxLength 19.669 of 673
ROA: none107.191.208.0/20No ROA covers it. Add a ROA for AS21351, maxLength 20.669 of 673
ROA: none2c0f:f608:4000::/36No ROA covers it. Add a ROA for AS21351, maxLength 36.636 of 636
ROA: none2605:adc0:2000::/36No ROA covers it. Add a ROA for AS21351, maxLength 36.631 of 636
Route object: none185.29.50.0/24No route object for it. A route object for 185.29.50.0/23 with origin AS21351 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21351 in the RIR database for the space.673 of 673
Route object: none5.187.96.0/20No route object for it. A route object for 5.187.96.0/19 with origin AS21351 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21351 in the RIR database for the space.669 of 673
Route object: none5.187.112.0/20No route object for it. A route object for 5.187.96.0/19 with origin AS21351 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21351 in the RIR database for the space.669 of 673
Route object: none95.138.112.0/23No route object for it. A route object for 95.138.0.0/17 with origin AS21351 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21351 in the RIR database for the space.669 of 673
Route object: none213.188.176.0/22No route object for it. A route object for 213.188.160.0/19 with origin AS21351 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21351 in the RIR database for the space.669 of 673
Route object: none95.138.112.0/22No route object for it. A route object for 95.138.0.0/17 with origin AS21351 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21351 in the RIR database for the space.668 of 673
Route object: none213.188.176.0/23No route object for it. A route object for 213.188.160.0/19 with origin AS21351 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21351 in the RIR database for the space.668 of 673
Route object: RIR161.22.64.0/18Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.668 of 673
Route object: RIR2803:1680:3000::/36Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.630 of 636

Route objects not announced

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

5.187.114.0/24RIPEValid
5.187.115.0/24RIPEValid
46.238.143.0/24RIPEValid
46.238.160.0/24RIPEValid
46.238.175.0/24RIPEValid
93.121.207.0/24RIPEValid
93.121.254.0/24RIPEValid
95.138.100.0/24RIPEValid
154.67.0.0/16RIPE-NONAUTHNo ROA
154.67.0.0/19AFRINICNo ROA
154.67.32.0/19AFRINICNo ROA
154.67.64.0/19AFRINICNo ROA
154.67.64.0/24AFRINICNo ROA
154.67.96.0/19AFRINICNo ROA
154.67.128.0/19AFRINICNo ROA
154.67.160.0/19AFRINICNo ROA
154.67.192.0/19AFRINICNo ROA
154.67.224.0/19AFRINICNo ROA
154.67.255.0/24RIPE-NONAUTHNo ROA
164.160.224.0/20RIPE-NONAUTHNo ROA
185.29.50.0/23RIPEValid
213.16.1.0/24RIPEValid
213.16.2.0/24RIPEValid
213.16.3.0/24RIPEValid
213.16.7.0/24RIPEValid
213.16.8.0/24RIPEValid
213.16.11.0/24RIPEValid
213.16.13.0/24RIPEValid
213.16.15.0/24RIPEValid
213.16.16.0/24RIPEValid
213.16.17.0/24RIPEValid
213.16.19.0/24RIPEValid
213.16.20.0/24RIPEValid
213.16.22.0/24RIPEValid
213.16.23.0/24RIPEValid
213.16.24.0/24RIPEValid
213.16.25.0/24RIPEValid
213.16.26.0/24RIPEValid
213.16.27.0/24RIPEValid
213.16.28.0/24RIPEValid
213.16.30.0/24RIPEValid
213.16.31.0/24RIPEValid
213.188.164.0/24RIPEValid
213.188.165.0/24RIPEValid
213.188.166.0/23RIPEValid
213.188.172.0/24RIPEValid
213.188.178.0/24RIPEValid
213.188.179.0/24RIPEValid
213.188.180.0/24RIPEValid
213.188.184.0/24RIPEValid
2605:adc0::/32ARINNo ROA
2803:1680::/32RIPE-NONAUTHNo ROA
2a02:1390::/32RIPEValid
2a02:1390:2000::/40RIPEValid
2a02:1390:6000::/40RIPEValid
2a02:1390:7000::/40RIPEValid
2a02:1390:f100::/40RIPEValid
2a02:1390:f500::/40RIPEValid
2a02:1397:6000::/40RIPEValid
2a02:1397:9000::/40RIPEValid
2c0f:f608::/32RIPE-NONAUTHNo ROA
2c0f:f608:6000::/36RIPE-NONAUTHNo ROA
2c0f:f608:f200::/40RIPE-NONAUTHNo ROA
2c0f:f608:f400::/40RIPE-NONAUTHNo ROA
2c0f:f608:f600::/40RIPE-NONAUTHNo 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.