bgpreport

Network · data from 2026-11-12

AS211320 BONAREAENERGIA Bonarea Energia SLU

Registry name: BONAREAENERGIA Bonarea Energia SLU, ES · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS211320, 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.
195.77.119.0/24 Invalid: origin None 3 0%low visibility 3
185.26.138.0/24 Valid RIR databaseRIPE 673 100% 67
185.26.139.0/24 Valid RIR databaseRIPE 672 100% 67
212.118.57.0/24 Valid RIR databaseRIPE 672 100% 67

AS-SET

AS211320 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 2 are in fix.csv.

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin195.77.119.0/24ROAs covering it name AS3352, not AS211320. If AS211320 should announce it, add a ROA for AS211320.3 of 673
Route object: none195.77.119.0/24No route object for it. Add a route object with origin AS211320 in the RIR database for the space.3 of 673

Route objects not announced

Every route object with origin AS211320 is announced.

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.