bgpreport

Network · data from 2026-11-12

AS265679 COOPERATIVA DE PROVISION DE SERVICIOS EVOLUCION

Registry name: AS265679 - COOPERATIVA DE PROVISION DE SERVICIOS EVOLUCION LTDA., AR · PeeringDB

8IPv4 routes 100.0% RPKI valid · 0.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
4Route objects not announced registered with origin AS265679, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS265679, 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.236.64.0/24 Valid Nonecovered by 38.236.64.0/22 671 100% 66
38.236.65.0/24 Valid Nonecovered by 38.236.64.0/22 671 100% 66
38.236.66.0/24 Valid Nonecovered by 38.236.64.0/22 671 100% 66
38.236.67.0/24 Valid Nonecovered by 38.236.64.0/22 671 100% 66
45.4.216.0/24 Valid Nonecovered by 45.4.216.0/22 671 100% 66
45.4.217.0/24 Valid Nonecovered by 45.4.216.0/22 671 100% 66
45.4.218.0/24 Valid Nonecovered by 45.4.216.0/22 671 100% 66
45.4.219.0/24 Valid Nonecovered by 45.4.216.0/22 671 100% 66

AS-SET

PeeringDB's irr_as_set for AS265679: LACNIC::AS265679. 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 (AS265679 isn't in the set, or no route object for AS265679 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 objectsAS265679 in itNot covered
LACNIC::AS265679 A single AS number, not a set: AS265679 (this network), 4 route objects.

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

  • Route object: none8
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none38.236.64.0/24No route object for it. A route object for 38.236.64.0/22 with origin AS265679 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265679 in the RIR database for the space.671 of 673
Route object: none38.236.65.0/24No route object for it. A route object for 38.236.64.0/22 with origin AS265679 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265679 in the RIR database for the space.671 of 673
Route object: none38.236.66.0/24No route object for it. A route object for 38.236.64.0/22 with origin AS265679 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265679 in the RIR database for the space.671 of 673
Route object: none38.236.67.0/24No route object for it. A route object for 38.236.64.0/22 with origin AS265679 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265679 in the RIR database for the space.671 of 673
Route object: none45.4.216.0/24No route object for it. A route object for 45.4.216.0/22 with origin AS265679 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265679 in the RIR database for the space.671 of 673
Route object: none45.4.217.0/24No route object for it. A route object for 45.4.216.0/22 with origin AS265679 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265679 in the RIR database for the space.671 of 673
Route object: none45.4.218.0/24No route object for it. A route object for 45.4.216.0/22 with origin AS265679 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265679 in the RIR database for the space.671 of 673
Route object: none45.4.219.0/24No route object for it. A route object for 45.4.216.0/22 with origin AS265679 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265679 in the RIR database for the space.671 of 673

Route objects not announced

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

38.236.64.0/22ARINValid
45.4.216.0/22LACNICValid
181.209.74.208/30LACNICValid
2803:c1c0::/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.