bgpreport

Network · data from 2026-11-12

AS21137 FR-CAI Credit Agricole Corporate and Investment Bank SA

Registry name: FR-CAI Credit Agricole Corporate and Investment Bank SA, FR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS21137, 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.
145.248.192.0/24 No ROA RIR databaseRIPE 673 100% 67
145.248.193.0/24 No ROA RIR databaseRIPE 673 100% 67
145.248.194.0/24 No ROA RIR databaseRIPE 673 100% 67
145.248.195.0/24 No ROA RIR databaseRIPE 673 100% 67
145.248.196.0/24 No ROA RIR databaseRIPE 673 100% 67
145.248.197.0/24 No ROA RIR databaseRIPE 673 100% 67
145.248.198.0/24 No ROA RIR databaseRIPE 673 100% 67
145.248.199.0/24 No ROA RIR databaseRIPE 673 100% 67
145.248.202.0/23 No ROA RIR databaseRIPE 673 100% 67
145.248.204.0/24 No ROA RIR databaseRADB, RIPE 673 100% 67
194.4.140.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
194.4.141.0/24 Valid RIR databaseRIPE 673 100% 67
194.4.142.0/24 Valid RIR databaseRIPE 673 100% 67
194.4.143.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

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

  • ROA: none10
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none145.248.192.0/24No ROA covers it. Add a ROA for AS21137, maxLength 24.673 of 673
ROA: none145.248.193.0/24No ROA covers it. Add a ROA for AS21137, maxLength 24.673 of 673
ROA: none145.248.194.0/24No ROA covers it. Add a ROA for AS21137, maxLength 24.673 of 673
ROA: none145.248.195.0/24No ROA covers it. Add a ROA for AS21137, maxLength 24.673 of 673
ROA: none145.248.196.0/24No ROA covers it. Add a ROA for AS21137, maxLength 24.673 of 673
ROA: none145.248.197.0/24No ROA covers it. Add a ROA for AS21137, maxLength 24.673 of 673
ROA: none145.248.198.0/24No ROA covers it. Add a ROA for AS21137, maxLength 24.673 of 673
ROA: none145.248.199.0/24No ROA covers it. Add a ROA for AS21137, maxLength 24.673 of 673
ROA: none145.248.202.0/23No ROA covers it. Add a ROA for AS21137, maxLength 23.673 of 673
ROA: none145.248.204.0/24No ROA covers it. Add a ROA for AS21137, maxLength 24.673 of 673

Route objects not announced

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

145.248.0.0/16RIPENo ROA
145.248.192.0/21RADBNo 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.