bgpreport

Network · data from 2026-11-12

AS61487 Cooperativa Electrica de Saladillo

Registry name: AS61487 - COOPERATIVA ELECTRICA DE SALADILLO, AR · PeeringDB

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

Announced routes

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

131.108.1.0/24 Valid Nonecovered by 131.108.0.0/22 672 100% 66
170.244.48.0/24 Valid Nonecovered by 170.244.48.0/22 672 100% 66
170.244.50.0/24 Valid Nonecovered by 170.244.48.0/22 672 100% 66
131.108.0.0/24 Valid Nonecovered by 131.108.0.0/22 670 100% 67
131.108.2.0/24 Valid Nonecovered by 131.108.0.0/22 670 100% 67
131.108.3.0/24 Valid Nonecovered by 131.108.0.0/22 670 100% 67
170.244.49.0/24 Valid Nonecovered by 170.244.48.0/22 670 100% 67
170.244.51.0/24 Valid Nonecovered by 170.244.48.0/22 670 100% 67
131.108.0.0/22 Valid RIR databaseLACNIC 671 100% 66
170.244.48.0/22 Valid RIR databaseLACNIC 671 100% 66

AS-SET

PeeringDB's irr_as_set for AS61487: AS61487:AS-COOPSAL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS61487 isn't in the set, or no route object for AS61487 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS61487 in itNot covered
AS61487:AS-COOPSAL LACNIC 51310 No 10

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

  • Route object: none8
  • AS-SET: own ASN1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none131.108.1.0/24No route object for it. A route object for 131.108.0.0/22 with origin AS61487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61487 in the RIR database for the space.672 of 673
Route object: none170.244.48.0/24No route object for it. A route object for 170.244.48.0/22 with origin AS61487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61487 in the RIR database for the space.672 of 673
Route object: none170.244.50.0/24No route object for it. A route object for 170.244.48.0/22 with origin AS61487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61487 in the RIR database for the space.672 of 673
Route object: none131.108.0.0/24No route object for it. A route object for 131.108.0.0/22 with origin AS61487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61487 in the RIR database for the space.670 of 673
Route object: none131.108.2.0/24No route object for it. A route object for 131.108.0.0/22 with origin AS61487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61487 in the RIR database for the space.670 of 673
Route object: none131.108.3.0/24No route object for it. A route object for 131.108.0.0/22 with origin AS61487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61487 in the RIR database for the space.670 of 673
Route object: none170.244.49.0/24No route object for it. A route object for 170.244.48.0/22 with origin AS61487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61487 in the RIR database for the space.670 of 673
Route object: none170.244.51.0/24No route object for it. A route object for 170.244.48.0/22 with origin AS61487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61487 in the RIR database for the space.670 of 673
AS-SET: own ASNAS61487:AS-COOPSALAS61487 isn't in AS61487:AS-COOPSAL (LACNIC) once expanded. Add AS61487 to it.

Route objects not announced

Route objects with origin AS61487 whose prefix no peer sees AS61487 announce. Many are kept on purpose (backup routes, space announced only in some places).

2803:3d80::/32LACNICValid

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.