Network · data from 2026-11-12
AS15810 BBVA-AS Banco Bilbao Vizcaya Argentaria, S.A.
Registry name: BBVA-AS Banco Bilbao Vizcaya Argentaria, S.A., ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS15810, 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.
| 89.107.176.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.24.7.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 89.107.177.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 89.107.178.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 89.107.179.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 89.107.180.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 89.107.181.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 89.107.182.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 89.107.183.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 185.24.4.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 185.24.6.0/24 | No ROA | RIR databaseRIPE | 672 100% |
AS-SET
AS15810 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 20 are in fix.csv.
- ROA: none11
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 89.107.176.0/24 | No ROA covers it. Add a ROA for AS15810, maxLength 24. |
| ROA: none | 185.24.7.0/24 | No ROA covers it. Add a ROA for AS15810, maxLength 24. |
| ROA: none | 89.107.177.0/24 | No ROA covers it. Add a ROA for AS15810, maxLength 24. |
| ROA: none | 89.107.178.0/24 | No ROA covers it. Add a ROA for AS15810, maxLength 24. |
| ROA: none | 89.107.179.0/24 | No ROA covers it. Add a ROA for AS15810, maxLength 24. |
| ROA: none | 89.107.180.0/24 | No ROA covers it. Add a ROA for AS15810, maxLength 24. |
| ROA: none | 89.107.181.0/24 | No ROA covers it. Add a ROA for AS15810, maxLength 24. |
| ROA: none | 89.107.182.0/24 | No ROA covers it. Add a ROA for AS15810, maxLength 24. |
| ROA: none | 89.107.183.0/24 | No ROA covers it. Add a ROA for AS15810, maxLength 24. |
| ROA: none | 185.24.4.0/24 | No ROA covers it. Add a ROA for AS15810, maxLength 24. |
| ROA: none | 185.24.6.0/24 | No ROA covers it. Add a ROA for AS15810, maxLength 24. |
Route objects not announced
Route objects with origin AS15810 whose prefix no peer sees AS15810 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.107.176.0/21 | RADB | No ROA |
| 185.24.4.0/22 | RADB | No ROA |
| 185.24.5.0/24 | RIPE | No ROA |
| 194.179.83.0/24 | RIPE | Invalid: origin |
| 195.53.15.0/24 | RIPE | Invalid: origin |
| 195.76.187.0/24 | RIPE | Invalid: origin |
| 213.242.94.0/24 | RIPE | No ROA |
| 2a01:7580::/32 | RIPE | No ROA |
| 2a01:7580:1::/48 | RIPE | No 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.