bgpreport

Network · data from 2026-11-12

AS207136 AUREA AUREA ENERGIA Y TELECOMUNICACIONES S.L.

Registry name: AUREA AUREA ENERGIA Y TELECOMUNICACIONES S.L., ES · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS207136, 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.

38.7.158.0/23 No ROA Other IRR onlyRADB 673 100% 67
38.172.32.0/22 No ROA Other IRR onlyRADB 673 100% 67
185.164.116.0/22 No ROA RIR databaseRIPE 673 100% 67
2a09:f40::/29 No ROA RIR databaseRIPE 604 95% 67
94.198.44.0/24 Valid RIR databaseRIPE 673 100% 67
45.137.138.0/24 Valid RIR databaseRIPE 672 100% 67

AS-SET

AS207136 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 6 are in fix.csv.

  • ROA: none4
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none38.7.158.0/23No ROA covers it. Add a ROA for AS207136, maxLength 23.673 of 673
Route object: RIR38.7.158.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.172.32.0/22No ROA covers it. Add a ROA for AS207136, maxLength 22.673 of 673
Route object: RIR38.172.32.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none185.164.116.0/22No ROA covers it. Add a ROA for AS207136, maxLength 22.673 of 673
ROA: none2a09:f40::/29No ROA covers it. Add a ROA for AS207136, maxLength 29.604 of 636

Route objects not announced

Every route object with origin AS207136 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.