Network · data from 2026-11-12
AS52411 Universidad del Desarrollo
Registry name: AS52411 - Universidad del Desarrollo, CL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52411, 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.
| 216.241.10.0/24 | Invalid: origin | Other origin only | 42 6%low visibility |
| 179.189.216.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 179.189.217.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 201.221.123.0/24 | Valid | RIR databaseLACNIC, NTTCOM, RADB | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS52411: AS52411:AS-ALL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS52411 isn't in the set, or no route object for AS52411 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS52411 in it | Not covered |
|---|---|---|---|---|---|
| AS52411:AS-ALL | RADB | 1 | 1 | Yes | 1 |
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 6 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: RIR2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 216.241.10.0/24 | ROAs covering it name AS18747, not AS52411. If AS52411 should announce it, add a ROA for AS52411. |
| Route object: none | 216.241.10.0/24 | Route objects for it name AS18747. Add a route object with origin AS52411 in the RIR database for the space. |
| Route object: RIR | 179.189.216.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 179.189.217.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS52411 whose prefix no peer sees AS52411 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 179.189.216.0/23 | LACNIC, RADB | Valid |
| 2801:0:400::/48 | LACNIC, RADB | Valid |
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.