Network · data from 2026-11-12
AS274010 AS274010 - BANCO BILBAO VIZCAYA ARGENTARIA COLOMBIA S.A.
Registry name: AS274010 - BANCO BILBAO VIZCAYA ARGENTARIA COLOMBIA S.A., CO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS274010, 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.
| 190.145.228.0/23 | Invalid: origin | Other origin only | 85 13% |
| 186.145.132.1/32 | Invalid: maxLength | Nonecovered by 186.145.132.0/23 | 1 0%low visibility |
| 186.145.132.2/32 | Invalid: maxLength | Nonecovered by 186.145.132.0/23 | 1 0%low visibility |
| 186.145.132.0/24 | Valid | Nonecovered by 186.145.132.0/23 | 671 100% |
| 186.145.133.0/24 | Valid | Nonecovered by 186.145.132.0/23 | 671 100% |
| 213.236.5.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 213.236.6.0/24 | Valid | RIR databaseLACNIC | 669 99% |
AS-SET
AS274010 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 11 are in fix.csv.
- ROA: origin1
- ROA: maxLength2
- Route object: none5
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 190.145.228.0/23 | ROAs covering it name AS10620, AS14080, AS32787, not AS274010. If AS274010 should announce it, add a ROA for AS274010. |
| Route object: none | 190.145.228.0/23 | Route objects for it name AS14080, AS32787. Add a route object with origin AS274010 in the RIR database for the space. |
| ROA: maxLength | 186.145.132.1/32 | ROA 186.145.132.0/23 AS274010 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 186.145.132.1/32. |
| Route object: none | 186.145.132.1/32 | No route object for it. A route object for 186.145.132.0/23 with origin AS274010 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS274010 in the RIR database for the space. |
| ROA: maxLength | 186.145.132.2/32 | ROA 186.145.132.0/23 AS274010 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 186.145.132.2/32. |
| Route object: none | 186.145.132.2/32 | No route object for it. A route object for 186.145.132.0/23 with origin AS274010 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS274010 in the RIR database for the space. |
| Route object: none | 186.145.132.0/24 | No route object for it. A route object for 186.145.132.0/23 with origin AS274010 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274010 in the RIR database for the space. |
| Route object: none | 186.145.133.0/24 | No route object for it. A route object for 186.145.132.0/23 with origin AS274010 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274010 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS274010 whose prefix no peer sees AS274010 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 158.172.220.0/23 | RIPE | Valid |
| 181.60.101.0/24 | LACNIC | Valid |
| 186.145.132.0/23 | LACNIC | Valid |
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.