bgpreport

Network · data from 2026-11-12

AS27996 Cooperativa Electrica de Colon

Registry name: AS27996 - Cooperativa Electrica de Colon (BA) LTDA, AR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS27996, 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.71.93.0/24 Valid Nonecovered by 200.71.88.0/21 671 100% 66
190.114.232.0/22 Valid Nonecovered by 190.114.232.0/21 670 100% 67
190.114.232.0/24 Valid Nonecovered by 190.114.232.0/21 670 100% 67
190.114.233.0/24 Valid Nonecovered by 190.114.232.0/21 670 100% 67
190.114.234.0/24 Valid Nonecovered by 190.114.232.0/21 670 100% 67
190.114.235.0/24 Valid Nonecovered by 190.114.232.0/21 670 100% 67
190.114.236.0/24 Valid Nonecovered by 190.114.232.0/21 670 100% 67
190.114.237.0/24 Valid Nonecovered by 190.114.232.0/21 670 100% 67
190.114.238.0/24 Valid Nonecovered by 190.114.232.0/21 670 100% 67
190.114.239.0/24 Valid Nonecovered by 190.114.232.0/21 670 100% 67
200.71.88.0/22 Valid Nonecovered by 200.71.88.0/21 670 100% 67
200.71.88.0/24 Valid Nonecovered by 200.71.88.0/21 670 100% 67
200.71.89.0/24 Valid Nonecovered by 200.71.88.0/21 670 100% 67
200.71.90.0/24 Valid Nonecovered by 200.71.88.0/21 670 100% 67
200.71.91.0/24 Valid Nonecovered by 200.71.88.0/21 670 100% 67
200.71.92.0/22 Valid Nonecovered by 200.71.88.0/21 670 100% 67
200.71.92.0/24 Valid Nonecovered by 200.71.88.0/21 670 100% 67
200.71.94.0/24 Valid Nonecovered by 200.71.88.0/21 670 100% 67
200.71.95.0/24 Valid Nonecovered by 200.71.88.0/21 670 100% 67
190.114.232.0/21 Valid RIR databaseLACNIC, RADB 671 100% 66
200.71.88.0/21 Valid RIR databaseLACNIC, RADB 671 100% 66

AS-SET

PeeringDB's irr_as_set for AS27996: AS27996:AS-COOPENETCOLON. 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 (AS27996 isn't in the set, or no route object for AS27996 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 objectsAS27996 in itNot covered
AS27996:AS-COOPENETCOLON LACNIC 31137 No 21

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

  • Route object: none19
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
Route object: none200.71.93.0/24No route object for it. A route object for 200.71.88.0/21 with origin AS27996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27996 in the RIR database for the space.671 of 673
Route object: none190.114.232.0/22No route object for it. A route object for 190.114.232.0/21 with origin AS27996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27996 in the RIR database for the space.670 of 673
Route object: none190.114.232.0/24No route object for it. A route object for 190.114.232.0/21 with origin AS27996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27996 in the RIR database for the space.670 of 673
Route object: none190.114.233.0/24No route object for it. A route object for 190.114.232.0/21 with origin AS27996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27996 in the RIR database for the space.670 of 673
Route object: none190.114.234.0/24No route object for it. A route object for 190.114.232.0/21 with origin AS27996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27996 in the RIR database for the space.670 of 673
Route object: none190.114.235.0/24No route object for it. A route object for 190.114.232.0/21 with origin AS27996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27996 in the RIR database for the space.670 of 673
Route object: none190.114.236.0/24No route object for it. A route object for 190.114.232.0/21 with origin AS27996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27996 in the RIR database for the space.670 of 673
Route object: none190.114.237.0/24No route object for it. A route object for 190.114.232.0/21 with origin AS27996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27996 in the RIR database for the space.670 of 673
Route object: none190.114.238.0/24No route object for it. A route object for 190.114.232.0/21 with origin AS27996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27996 in the RIR database for the space.670 of 673
Route object: none190.114.239.0/24No route object for it. A route object for 190.114.232.0/21 with origin AS27996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27996 in the RIR database for the space.670 of 673
Route object: none200.71.88.0/22No route object for it. A route object for 200.71.88.0/21 with origin AS27996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27996 in the RIR database for the space.670 of 673
Route object: none200.71.88.0/24No route object for it. A route object for 200.71.88.0/21 with origin AS27996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27996 in the RIR database for the space.670 of 673
Route object: none200.71.89.0/24No route object for it. A route object for 200.71.88.0/21 with origin AS27996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27996 in the RIR database for the space.670 of 673
Route object: none200.71.90.0/24No route object for it. A route object for 200.71.88.0/21 with origin AS27996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27996 in the RIR database for the space.670 of 673
Route object: none200.71.91.0/24No route object for it. A route object for 200.71.88.0/21 with origin AS27996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27996 in the RIR database for the space.670 of 673
Route object: none200.71.92.0/22No route object for it. A route object for 200.71.88.0/21 with origin AS27996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27996 in the RIR database for the space.670 of 673
Route object: none200.71.92.0/24No route object for it. A route object for 200.71.88.0/21 with origin AS27996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27996 in the RIR database for the space.670 of 673
Route object: none200.71.94.0/24No route object for it. A route object for 200.71.88.0/21 with origin AS27996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27996 in the RIR database for the space.670 of 673
Route object: none200.71.95.0/24No route object for it. A route object for 200.71.88.0/21 with origin AS27996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27996 in the RIR database for the space.670 of 673
AS-SET: own ASNAS27996:AS-COOPENETCOLONAS27996 isn't in AS27996:AS-COOPENETCOLON (LACNIC) once expanded. Add AS27996 to it.

Route objects not announced

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