Network · data from 2026-11-12
AS273170 LATENCIA 0
Registry name: AS273170 - LATENCIA 0 SA, AR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS273170, 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.59.193.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 200.59.63.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 209.61.1.0/24 | Valid | RIR databaseALTDB, ARIN, RADB | 673 100% |
| 209.61.3.0/24 | Valid | RIR databaseALTDB, ARIN, RADB | 673 100% |
| 38.211.245.0/24 | Valid | RIR databaseALTDB, ARIN, RADB | 672 100% |
| 209.61.2.0/24 | Valid | RIR databaseALTDB, ARIN | 670 100% |
| 206.85.20.0/24 | Valid | RIR databaseALTDB, ARIN | 668 99% |
AS-SET
AS273170'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 3 are in fix.csv.
- Route object: RIR2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 200.59.193.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.59.63.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS273170 whose prefix no peer sees AS273170 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2803:b250::/32 | RADB | 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.