Network · data from 2026-11-12
AS23140 Universidad de Chile
Registry name: AS23140 - Universidad de Chile, CL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS23140, 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.
| 146.83.248.32/27 | Invalid: origin | None | 2 0%low visibility |
| 192.80.24.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 200.9.97.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 671 100% |
| 200.9.98.0/23 | No ROA | Other IRR onlyNTTCOM, RADB | 671 100% |
| 200.9.100.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 146.83.2.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 146.83.2.0/23 | Valid | RIR databaseLACNIC, NTTCOM, RADB | 672 100% |
| 146.83.4.0/22 | Valid | RIR databaseLACNIC, NTTCOM, RADB | 672 100% |
| 146.83.8.0/21 | Valid | RIR databaseLACNIC, NTTCOM, RADB | 672 100% |
| 146.83.16.0/20 | Valid | RIR databaseLACNIC, NTTCOM, RADB | 672 100% |
| 146.83.32.0/19 | Valid | RIR databaseLACNIC, NTTCOM, RADB | 672 100% |
| 200.89.64.0/20 | Valid | RIR databaseLACNIC, NTTCOM, RADB | 670 100% |
| 2803:7ce0::/32 | Valid | RIR databaseLACNIC | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS23140: AS23140:AS-UCHILE. 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 (AS23140 isn't in the set, or no route object for AS23140 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 | AS23140 in it | Not covered |
|---|---|---|---|---|---|
| AS23140:AS-UCHILE | LACNIC | 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 12 are in fix.csv.
- ROA: origin1
- ROA: none4
- Route object: none1
- Route object: RIR5
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 146.83.248.32/27 | ROAs covering it name AS11340, not AS23140. If AS23140 should announce it, add a ROA for AS23140. |
| Route object: none | 146.83.248.32/27 | No route object for it. Add a route object with origin AS23140 in the RIR database for the space. |
| ROA: none | 192.80.24.0/24 | No ROA covers it. Add a ROA for AS23140, maxLength 24. |
| Route object: RIR | 192.80.24.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 200.9.97.0/24 | No ROA covers it. Add a ROA for AS23140, maxLength 24. |
| Route object: RIR | 200.9.97.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 200.9.98.0/23 | No ROA covers it. Add a ROA for AS23140, maxLength 23. |
| Route object: RIR | 200.9.98.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 200.9.100.0/24 | No ROA covers it. Add a ROA for AS23140, maxLength 24. |
| Route object: RIR | 200.9.100.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 146.83.2.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS23140 whose prefix no peer sees AS23140 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 200.9.98.0/24 | NTTCOM | No 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.