bgpreport

Network · data from 2026-11-12

AS264790 AS264790 - COOPERATIVA DE PROVISION DE SERVICIO ELECTRICO Y OTROS SERV DE PIGUE

Registry name: AS264790 - COOPERATIVA DE PROVISION DE SERVICIO ELECTRICO Y OTROS SERV DE PIGUE, AR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264790, 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.251.119.0/24 Invalid: origin None 1 0%low visibility 2
170.79.16.0/24 Valid Nonecovered by 170.79.16.0/22 672 100% 66
170.79.17.0/24 Valid Nonecovered by 170.79.16.0/22 672 100% 66
170.79.18.0/24 Valid Nonecovered by 170.79.16.0/22 668 99% 66
170.79.19.0/24 Valid Nonecovered by 170.79.16.0/22 668 99% 66
181.189.164.0/24 Valid Nonecovered by 181.189.164.0/22 668 99% 66
181.189.165.0/24 Valid Nonecovered by 181.189.164.0/22 668 99% 66
181.189.166.0/24 Valid Nonecovered by 181.189.164.0/22 668 99% 66
181.189.167.0/24 Valid Nonecovered by 181.189.164.0/22 668 99% 66
190.103.196.0/24 Valid Nonecovered by 190.103.196.0/23 667 99% 66
190.103.197.0/24 Valid Nonecovered by 190.103.196.0/23 667 99% 66
2803:b8c0::/48 Valid Nonecovered by 2803:b8c0::/32 635 100% 67
2803:b8c0:1::/48 Valid Nonecovered by 2803:b8c0::/32 635 100% 67
2803:b8c0:2::/48 Valid Nonecovered by 2803:b8c0::/32 635 100% 67
2803:b8c0:3::/48 Valid Nonecovered by 2803:b8c0::/32 635 100% 67
2803:b8c0:4::/48 Valid Nonecovered by 2803:b8c0::/32 635 100% 67
2803:b8c0:5::/48 Valid Nonecovered by 2803:b8c0::/32 635 100% 67
2803:b8c0:6::/48 Valid Nonecovered by 2803:b8c0::/32 635 100% 67
2803:b8c0:7::/48 Valid Nonecovered by 2803:b8c0::/32 635 100% 67
2803:b8c0:8::/48 Valid Nonecovered by 2803:b8c0::/32 635 100% 67
170.79.16.0/22 Valid RIR databaseLACNIC 670 100% 66
190.103.205.0/24 Valid RIR databaseLACNIC 667 99% 66
190.103.206.0/24 Valid RIR databaseLACNIC 667 99% 66

AS-SET

AS264790 isn't in PeeringDB, where networks name their 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 25 are in fix.csv.

  • ROA: origin1
  • Route object: none20
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin201.251.119.0/24ROAs covering it name AS22927, not AS264790. If AS264790 should announce it, add a ROA for AS264790.1 of 673
Route object: none201.251.119.0/24No route object for it. Add a route object with origin AS264790 in the RIR database for the space.1 of 673
Route object: none170.79.16.0/24No route object for it. A route object for 170.79.16.0/22 with origin AS264790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264790 in the RIR database for the space.672 of 673
Route object: none170.79.17.0/24No route object for it. A route object for 170.79.16.0/22 with origin AS264790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264790 in the RIR database for the space.672 of 673
Route object: none170.79.18.0/24No route object for it. A route object for 170.79.16.0/22 with origin AS264790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264790 in the RIR database for the space.668 of 673
Route object: none170.79.19.0/24No route object for it. A route object for 170.79.16.0/22 with origin AS264790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264790 in the RIR database for the space.668 of 673
Route object: none181.189.164.0/24No route object for it. A route object for 181.189.164.0/22 with origin AS264790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264790 in the RIR database for the space.668 of 673
Route object: none181.189.165.0/24No route object for it. A route object for 181.189.164.0/22 with origin AS264790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264790 in the RIR database for the space.668 of 673
Route object: none181.189.166.0/24No route object for it. A route object for 181.189.164.0/22 with origin AS264790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264790 in the RIR database for the space.668 of 673
Route object: none181.189.167.0/24No route object for it. A route object for 181.189.164.0/22 with origin AS264790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264790 in the RIR database for the space.668 of 673
Route object: none190.103.196.0/24No route object for it. A route object for 190.103.196.0/23 with origin AS264790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264790 in the RIR database for the space.667 of 673
Route object: none190.103.197.0/24No route object for it. A route object for 190.103.196.0/23 with origin AS264790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264790 in the RIR database for the space.667 of 673
Route object: none2803:b8c0::/48No route object for it. A route object for 2803:b8c0::/32 with origin AS264790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264790 in the RIR database for the space.635 of 636
Route object: none2803:b8c0:1::/48No route object for it. A route object for 2803:b8c0::/32 with origin AS264790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264790 in the RIR database for the space.635 of 636
Route object: none2803:b8c0:2::/48No route object for it. A route object for 2803:b8c0::/32 with origin AS264790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264790 in the RIR database for the space.635 of 636
Route object: none2803:b8c0:3::/48No route object for it. A route object for 2803:b8c0::/32 with origin AS264790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264790 in the RIR database for the space.635 of 636
Route object: none2803:b8c0:4::/48No route object for it. A route object for 2803:b8c0::/32 with origin AS264790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264790 in the RIR database for the space.635 of 636
Route object: none2803:b8c0:5::/48No route object for it. A route object for 2803:b8c0::/32 with origin AS264790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264790 in the RIR database for the space.635 of 636
Route object: none2803:b8c0:6::/48No route object for it. A route object for 2803:b8c0::/32 with origin AS264790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264790 in the RIR database for the space.635 of 636
Route object: none2803:b8c0:7::/48No route object for it. A route object for 2803:b8c0::/32 with origin AS264790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264790 in the RIR database for the space.635 of 636
Route object: none2803:b8c0:8::/48No route object for it. A route object for 2803:b8c0::/32 with origin AS264790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264790 in the RIR database for the space.635 of 636

Route objects not announced

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

181.189.164.0/22LACNICValid
181.209.74.240/30LACNICValid
190.103.196.0/23LACNICValid
2803:b8c0::/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.