bgpreport

Network · data from 2026-11-12

AS267882 AGENCIA DE CIENCIA, TECNOLOGIA Y SOCIEDAD SAN LUIS

Registry name: AS267882 - AGENCIA DE CIENCIA, TECNOLOGIA Y SOCIEDAD SAN LUIS, AR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267882, 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.
45.178.0.0/24 No ROA Nonecovered by 45.178.0.0/22 672 100% 67
45.178.1.0/24 No ROA Nonecovered by 45.178.0.0/22 670 100% 67
45.178.2.0/24 No ROA Nonecovered by 45.178.0.0/22 670 100% 67
45.178.3.0/24 No ROA Nonecovered by 45.178.0.0/22 670 100% 67
2803:aa60::/32 No ROA None 636 100% 67

AS-SET

AS267882's PeeringDB record names no 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 12 are in fix.csv.

  • ROA: none5
  • Route object: none5
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none45.178.0.0/24No ROA covers it. Add a ROA for AS267882, maxLength 24.672 of 673
Route object: none45.178.0.0/24No route object for it. A route object for 45.178.0.0/22 with origin AS267882 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267882 in the RIR database for the space.672 of 673
ROA: none45.178.1.0/24No ROA covers it. Add a ROA for AS267882, maxLength 24.670 of 673
Route object: none45.178.1.0/24No route object for it. A route object for 45.178.0.0/22 with origin AS267882 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267882 in the RIR database for the space.670 of 673
ROA: none45.178.2.0/24No ROA covers it. Add a ROA for AS267882, maxLength 24.670 of 673
Route object: none45.178.2.0/24No route object for it. A route object for 45.178.0.0/22 with origin AS267882 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267882 in the RIR database for the space.670 of 673
ROA: none45.178.3.0/24No ROA covers it. Add a ROA for AS267882, maxLength 24.670 of 673
Route object: none45.178.3.0/24No route object for it. A route object for 45.178.0.0/22 with origin AS267882 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267882 in the RIR database for the space.670 of 673
ROA: none2803:aa60::/32No ROA covers it. Add a ROA for AS267882, maxLength 32.636 of 636
Route object: none2803:aa60::/32No route object for it. Add a route object with origin AS267882 in the RIR database for the space.636 of 636

Route objects not announced

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

45.178.0.0/22RADBNo ROA
201.222.56.0/22RADBNo ROA

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.