Network · data from 2026-11-12
AS264774 UGALDE JUAN IGNACIO
Registry name: AS264774 - UGALDE JUAN IGNACIO, AR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS264774, 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.
| 2803:8c0:cafe::/48 | Invalid: maxLength | Nonecovered by 2803:8c0::/32 | 3 0%low visibility |
| 45.164.231.0/24 | Valid | RIR databaseLACNIC | 668 99% |
| 168.197.200.0/22 | Valid | RIR databaseLACNIC | 668 99% |
| 2803:8c0::/32 | Valid | RIR databaseLACNIC | 632 99% |
| 168.197.200.0/24 | Valid | RIR databaseLACNIC | 100 15% |
| 168.197.201.0/24 | Valid | RIR databaseLACNIC | 100 15% |
| 168.197.202.0/24 | Valid | RIR databaseLACNIC | 100 15% |
| 168.197.203.0/24 | Valid | RIR databaseLACNIC | 100 15% |
AS-SET
AS264774'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 2 are in fix.csv.
- ROA: maxLength1
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 2803:8c0:cafe::/48 | ROA 2803:8c0::/32 AS264774 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2803:8c0:cafe::/48. |
| Route object: none | 2803:8c0:cafe::/48 | No route object for it. A route object for 2803:8c0::/32 with origin AS264774 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264774 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS264774 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.