bgpreport

Network · data from 2026-11-12

AS20905 BancoEspanaAS Banco de Espana

Registry name: BancoEspanaAS Banco de Espana, ES · not in PeeringDB

4IPv4 routes 25.0% RPKI valid · 25.0% with a route object
4IPv6 routes 25.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No ROA 5 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS20905, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS20905, 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.
77.73.200.0/23 No ROA None 672 100% 67
77.73.202.0/23 No ROA None 672 100% 67
77.73.200.0/22 No ROA None 669 99% 67
2a03:7680::/33 No ROA Nonecovered by 2a03:7680::/32 636 100% 67
2a03:7680:8000::/33 No ROA Nonecovered by 2a03:7680::/32 636 100% 67
2a03:7680::/32 No ROA RIR databaseRIPE 635 100% 67
217.124.152.0/24 Valid RIR databaseRIPE 672 100% 67
2a02:9010:45::/48 Valid RIR databaseRIPE 636 100% 67

AS-SET

AS20905 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: none6
  • Route object: none5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none77.73.200.0/23No ROA covers it. Add a ROA for AS20905, maxLength 23.672 of 673
Route object: none77.73.200.0/23No route object for it. Add a route object with origin AS20905 in the RIR database for the space.672 of 673
ROA: none77.73.202.0/23No ROA covers it. Add a ROA for AS20905, maxLength 23.672 of 673
Route object: none77.73.202.0/23No route object for it. Add a route object with origin AS20905 in the RIR database for the space.672 of 673
ROA: none77.73.200.0/22No ROA covers it. Add a ROA for AS20905, maxLength 22.669 of 673
Route object: none77.73.200.0/22No route object for it. Add a route object with origin AS20905 in the RIR database for the space.669 of 673
ROA: none2a03:7680::/33No ROA covers it. Add a ROA for AS20905, maxLength 33.636 of 636
Route object: none2a03:7680::/33No route object for it. A route object for 2a03:7680::/32 with origin AS20905 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20905 in the RIR database for the space.636 of 636
ROA: none2a03:7680:8000::/33No ROA covers it. Add a ROA for AS20905, maxLength 33.636 of 636
Route object: none2a03:7680:8000::/33No route object for it. A route object for 2a03:7680::/32 with origin AS20905 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20905 in the RIR database for the space.636 of 636
ROA: none2a03:7680::/32No ROA covers it. Add a ROA for AS20905, maxLength 32.635 of 636

Route objects not announced

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

77.73.203.0/24RIPENo 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.