bgpreport

Network · data from 2026-11-12

AS265793 COOPENET AMERICA

Registry name: AS265793 - COOP PROV SERV. ELECT. OB .Y SERV. PUB. SERV. SOC. Y CR. VIV. Y CONS. RIVADAVIA LTDA, AR · PeeringDB

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

Announced routes

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

201.182.16.0/24 Valid Nonecovered by 201.182.16.0/22 673 100% 67
201.182.17.0/24 Valid Nonecovered by 201.182.16.0/22 673 100% 67
201.182.19.0/24 Valid Nonecovered by 201.182.16.0/22 673 100% 67
201.182.16.0/22 Valid RIR databaseLACNIC, RADB 672 100% 66

AS-SET

PeeringDB's irr_as_set for AS265793: AS265793:AS-COOPENETRIV. 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 (AS265793 isn't in the set, or no route object for AS265793 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 objectsAS265793 in itNot covered
AS265793:AS-COOPENETRIV LACNIC 41345 No 4

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

  • Route object: none3
  • AS-SET: own ASN1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none201.182.16.0/24No route object for it. A route object for 201.182.16.0/22 with origin AS265793 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265793 in the RIR database for the space.673 of 673
Route object: none201.182.17.0/24No route object for it. A route object for 201.182.16.0/22 with origin AS265793 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265793 in the RIR database for the space.673 of 673
Route object: none201.182.19.0/24No route object for it. A route object for 201.182.16.0/22 with origin AS265793 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265793 in the RIR database for the space.673 of 673
AS-SET: own ASNAS265793:AS-COOPENETRIVAS265793 isn't in AS265793:AS-COOPENETRIV (LACNIC) once expanded. Add AS265793 to it.

Route objects not announced

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

2803:a020::/32LACNIC, RADBValid

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.