bgpreport

Network · data from 2026-11-12

AS50758 Airbus-Defence-and-Space Airbus Defence and Space SAS

Registry name: Airbus-Defence-and-Space Airbus Defence and Space SAS, FR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS50758, 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.
46.31.163.0/24 Valid Nonecovered by 46.31.160.0/21 672 100% 67
46.31.164.0/24 Valid Nonecovered by 46.31.160.0/21 672 100% 67
46.31.165.0/24 Valid Nonecovered by 46.31.160.0/21 672 100% 67
46.31.166.0/24 Valid Nonecovered by 46.31.160.0/21 672 100% 67
46.31.160.0/21 Valid RIR databaseRIPE 672 100% 67
46.31.160.0/24 Valid RIR databaseRIPE 672 100% 67
46.31.161.0/24 Valid RIR databaseRIPE 672 100% 67
46.31.162.0/24 Valid RIR databaseRIPE 672 100% 67
46.31.167.0/24 Valid RIR databaseRIPE 672 100% 67
213.190.12.0/24 Valid RIR databaseRIPE 672 100% 67
213.190.13.0/24 Valid RIR databaseRIPE 672 100% 67
213.190.14.0/24 Valid RIR databaseRIPE 672 100% 67
213.190.15.0/24 Valid RIR databaseRIPE 672 100% 67

AS-SET

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

  • Route object: none4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none46.31.163.0/24No route object for it. A route object for 46.31.160.0/21 with origin AS50758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50758 in the RIR database for the space.672 of 673
Route object: none46.31.164.0/24No route object for it. A route object for 46.31.160.0/21 with origin AS50758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50758 in the RIR database for the space.672 of 673
Route object: none46.31.165.0/24No route object for it. A route object for 46.31.160.0/21 with origin AS50758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50758 in the RIR database for the space.672 of 673
Route object: none46.31.166.0/24No route object for it. A route object for 46.31.160.0/21 with origin AS50758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50758 in the RIR database for the space.672 of 673

Route objects not announced

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

213.190.12.0/22RIPENo ROA
2a0a:2a40::/29RIPEValid

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.