bgpreport

Network · data from 2026-11-12

AS263186 AS263186 - Universidad Nacional de General Sarmiento

Registry name: AS263186 - Universidad Nacional de General Sarmiento, AR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263186, 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.
179.0.144.0/23 No ROA None 670 100% 67
2801:18:c000::/48 No ROA None 631 99% 67
170.210.52.0/23 Valid Nonecovered by 170.210.52.0/22 8 1%low visibility 6
170.210.52.0/24 Valid Nonecovered by 170.210.52.0/22 8 1%low visibility 6
170.210.53.0/24 Valid Nonecovered by 170.210.52.0/22 8 1%low visibility 6
170.210.54.0/24 Valid Nonecovered by 170.210.52.0/22 8 1%low visibility 6
170.210.55.0/24 Valid Nonecovered by 170.210.52.0/22 8 1%low visibility 6
170.210.52.0/22 Valid RIR databaseLACNIC 104 15% 41

AS-SET

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

  • ROA: none2
  • Route object: none7
ChangePrefix or setDetailFull-table peers
ROA: none179.0.144.0/23No ROA covers it. Add a ROA for AS263186, maxLength 23.670 of 673
Route object: none179.0.144.0/23No route object for it. Add a route object with origin AS263186 in the RIR database for the space.670 of 673
ROA: none2801:18:c000::/48No ROA covers it. Add a ROA for AS263186, maxLength 48.631 of 636
Route object: none2801:18:c000::/48No route object for it. Add a route object with origin AS263186 in the RIR database for the space.631 of 636
Route object: none170.210.52.0/23No route object for it. A route object for 170.210.52.0/22 with origin AS263186 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263186 in the RIR database for the space.8 of 673
Route object: none170.210.52.0/24No route object for it. A route object for 170.210.52.0/22 with origin AS263186 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263186 in the RIR database for the space.8 of 673
Route object: none170.210.53.0/24No route object for it. A route object for 170.210.52.0/22 with origin AS263186 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263186 in the RIR database for the space.8 of 673
Route object: none170.210.54.0/24No route object for it. A route object for 170.210.52.0/22 with origin AS263186 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263186 in the RIR database for the space.8 of 673
Route object: none170.210.55.0/24No route object for it. A route object for 170.210.52.0/22 with origin AS263186 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263186 in the RIR database for the space.8 of 673

Route objects not announced

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