Network · data from 2026-11-12
AS27979 Stel Chile
Registry name: AS27979 - Stel Chile S.A., CL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS27979, 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.
| 200.73.208.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 200.73.209.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 200.73.210.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 200.73.211.0/24 | Valid | Other IRR onlyRADB | 671 100% |
AS-SET
AS27979'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 11 are in fix.csv.
- Route object: RIR4
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 200.73.208.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.73.209.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.73.210.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.73.211.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS27979 whose prefix no peer sees AS27979 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 190.93.224.0/20 | NTTCOM, RADB | No ROA |
| 190.93.232.0/22 | LACNIC | Valid |
| 190.93.232.0/23 | RADB | Valid |
| 190.93.234.0/23 | RADB | Valid |
| 190.93.235.0/24 | RADB | Valid |
| 190.93.236.0/22 | LACNIC, RADB | Valid |
| 200.73.208.0/21 | LACNIC, NTTCOM, 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.