Network · data from 2026-11-12
AS61476 AS61476 - Universidad Nacional de La Pampa
Registry name: AS61476 - Universidad Nacional de La Pampa, AR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61476, 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.
| 190.104.95.0/24 | Invalid: maxLength | Nonecovered by 190.104.88.0/21 | 1 0%low visibility |
| 170.210.120.0/24 | Valid | Nonecovered by 170.210.120.0/21 | 8 1%low visibility |
| 170.210.121.0/24 | Valid | Nonecovered by 170.210.120.0/21 | 8 1%low visibility |
| 170.210.122.0/24 | Valid | Nonecovered by 170.210.120.0/21 | 8 1%low visibility |
| 170.210.123.0/24 | Valid | Nonecovered by 170.210.120.0/21 | 8 1%low visibility |
| 170.210.124.0/24 | Valid | Nonecovered by 170.210.120.0/21 | 8 1%low visibility |
| 170.210.125.0/24 | Valid | Nonecovered by 170.210.120.0/21 | 8 1%low visibility |
| 170.210.126.0/24 | Valid | Nonecovered by 170.210.120.0/21 | 8 1%low visibility |
| 170.210.127.0/24 | Valid | Nonecovered by 170.210.120.0/21 | 8 1%low visibility |
| 190.104.88.0/21 | Valid | RIR databaseLACNIC | 667 99% |
| 2801:18:8000::/48 | Valid | RIR databaseLACNIC | 629 99% |
| 170.210.120.0/21 | Valid | RIR databaseLACNIC | 106 16% |
AS-SET
AS61476 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 10 are in fix.csv.
- ROA: maxLength1
- Route object: none9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 190.104.95.0/24 | ROA 190.104.88.0/21 AS61476 has maxLength 21; the route is a /24. Raise the maxLength, or add a ROA for 190.104.95.0/24. |
| Route object: none | 190.104.95.0/24 | No route object for it. A route object for 190.104.88.0/21 with origin AS61476 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61476 in the RIR database for the space. |
| Route object: none | 170.210.120.0/24 | No route object for it. A route object for 170.210.120.0/21 with origin AS61476 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61476 in the RIR database for the space. |
| Route object: none | 170.210.121.0/24 | No route object for it. A route object for 170.210.120.0/21 with origin AS61476 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61476 in the RIR database for the space. |
| Route object: none | 170.210.122.0/24 | No route object for it. A route object for 170.210.120.0/21 with origin AS61476 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61476 in the RIR database for the space. |
| Route object: none | 170.210.123.0/24 | No route object for it. A route object for 170.210.120.0/21 with origin AS61476 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61476 in the RIR database for the space. |
| Route object: none | 170.210.124.0/24 | No route object for it. A route object for 170.210.120.0/21 with origin AS61476 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61476 in the RIR database for the space. |
| Route object: none | 170.210.125.0/24 | No route object for it. A route object for 170.210.120.0/21 with origin AS61476 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61476 in the RIR database for the space. |
| Route object: none | 170.210.126.0/24 | No route object for it. A route object for 170.210.120.0/21 with origin AS61476 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61476 in the RIR database for the space. |
| Route object: none | 170.210.127.0/24 | No route object for it. A route object for 170.210.120.0/21 with origin AS61476 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61476 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS61476 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.