bgpreport

Network · data from 2026-11-12

AS49940 FIRABCN-AS FERIA INTERNACIONAL DE BARCELONA

Registry name: FIRABCN-AS FERIA INTERNACIONAL DE BARCELONA, ES · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS49940, 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.
37.34.71.0/24 No ROA Nonecovered by 37.34.70.0/23 671 100% 67
37.34.70.0/23 No ROA RIR databaseRIPE 672 100% 67
95.215.120.0/24 No ROA RIR databaseRIPE 672 100% 67
95.215.121.0/24 No ROA RIR databaseRIPE 672 100% 67
95.215.122.0/24 No ROA RIR databaseRIPE 672 100% 67
95.215.123.0/24 No ROA RIR databaseRIPE 672 100% 67
37.34.64.0/24 No ROA RIR databaseRIPE 671 100% 67
37.34.65.0/24 No ROA RIR databaseRIPE 671 100% 67
37.34.66.0/24 No ROA RIR databaseRIPE 671 100% 67
37.34.67.0/24 No ROA RIR databaseRIPE 671 100% 67
37.34.68.0/24 No ROA RIR databaseRIPE 671 100% 67
37.34.69.0/24 No ROA RIR databaseRIPE 671 100% 67
37.34.70.0/24 No ROA RIR databaseRIPE 669 99% 67
2a05:f8c0::/29 No ROA RIR databaseRIPE 634 100% 68

AS-SET

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

  • ROA: none14
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none37.34.71.0/24No ROA covers it. Add a ROA for AS49940, maxLength 24.671 of 673
Route object: none37.34.71.0/24No route object for it. A route object for 37.34.70.0/23 with origin AS49940 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49940 in the RIR database for the space.671 of 673
ROA: none37.34.70.0/23No ROA covers it. Add a ROA for AS49940, maxLength 23.672 of 673
ROA: none95.215.120.0/24No ROA covers it. Add a ROA for AS49940, maxLength 24.672 of 673
ROA: none95.215.121.0/24No ROA covers it. Add a ROA for AS49940, maxLength 24.672 of 673
ROA: none95.215.122.0/24No ROA covers it. Add a ROA for AS49940, maxLength 24.672 of 673
ROA: none95.215.123.0/24No ROA covers it. Add a ROA for AS49940, maxLength 24.672 of 673
ROA: none37.34.64.0/24No ROA covers it. Add a ROA for AS49940, maxLength 24.671 of 673
ROA: none37.34.65.0/24No ROA covers it. Add a ROA for AS49940, maxLength 24.671 of 673
ROA: none37.34.66.0/24No ROA covers it. Add a ROA for AS49940, maxLength 24.671 of 673
ROA: none37.34.67.0/24No ROA covers it. Add a ROA for AS49940, maxLength 24.671 of 673
ROA: none37.34.68.0/24No ROA covers it. Add a ROA for AS49940, maxLength 24.671 of 673
ROA: none37.34.69.0/24No ROA covers it. Add a ROA for AS49940, maxLength 24.671 of 673
ROA: none37.34.70.0/24No ROA covers it. Add a ROA for AS49940, maxLength 24.669 of 673
ROA: none2a05:f8c0::/29No ROA covers it. Add a ROA for AS49940, maxLength 29.634 of 636

Route objects not announced

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

2a05:f8c0:2::/48RIPENo ROA
2a05:f8c0:3::/48RIPENo 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.