bgpreport

Network · data from 2026-11-12

AS270012 EDDAS HOLDING GROUP SOCIEDAD ANONIMA CERRADA

Registry name: AS270012 - EDDAS HOLDING GROUP SOCIEDAD ANONIMA CERRADA, PE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270012, 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.
200.39.148.0/24 Valid Nonecovered by 200.39.148.0/23 671 100% 66
200.39.149.0/24 Valid Nonecovered by 200.39.148.0/23 671 100% 66
2803:c9e0::/34 Valid Nonecovered by 2803:c9e0::/32 636 100% 67
2803:c9e0:4000::/34 Valid Nonecovered by 2803:c9e0::/32 636 100% 67
2803:c9e0:8000::/34 Valid Nonecovered by 2803:c9e0::/32 636 100% 67
2803:c9e0:c000::/34 Valid Nonecovered by 2803:c9e0::/32 636 100% 67
38.199.239.0/24 Valid RIR databaseARIN 671 100% 66
200.39.148.0/23 Valid RIR databaseLACNIC, RADB 671 100% 66
2803:c9e0::/32 Valid RIR databaseLACNIC, RADB 636 100% 67

AS-SET

AS270012's PeeringDB record names no 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.

  • Route object: none6
ChangePrefix or setDetailFull-table peers
Route object: none200.39.148.0/24No route object for it. A route object for 200.39.148.0/23 with origin AS270012 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270012 in the RIR database for the space.671 of 673
Route object: none200.39.149.0/24No route object for it. A route object for 200.39.148.0/23 with origin AS270012 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270012 in the RIR database for the space.671 of 673
Route object: none2803:c9e0::/34No route object for it. A route object for 2803:c9e0::/32 with origin AS270012 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270012 in the RIR database for the space.636 of 636
Route object: none2803:c9e0:4000::/34No route object for it. A route object for 2803:c9e0::/32 with origin AS270012 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270012 in the RIR database for the space.636 of 636
Route object: none2803:c9e0:8000::/34No route object for it. A route object for 2803:c9e0::/32 with origin AS270012 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270012 in the RIR database for the space.636 of 636
Route object: none2803:c9e0:c000::/34No route object for it. A route object for 2803:c9e0::/32 with origin AS270012 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270012 in the RIR database for the space.636 of 636

Route objects not announced

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