Network · data from 2026-11-12
AS39838 as-peering_latam
Registry name: as-peering_latam Valor Information Technologies, S.L., ES · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS39838, 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.
| 141.136.56.0/21 | No ROA | Other IRR onlyRADB | 672 100% |
| 45.145.135.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 2a0a:e9c3::/32 | Valid | RIR databaseRADB, RIPE | 635 100% |
AS-SET
AS39838'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 7 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 141.136.56.0/21 | No ROA covers it. Add a ROA for AS39838, maxLength 21. |
| Route object: RIR | 141.136.56.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS39838 whose prefix no peer sees AS39838 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.42.112.0/23 | RADB | Valid |
| 176.57.202.0/24 | RADB, RIPE | Valid |
| 201.77.54.0/24 | RADB | Valid |
| 217.26.188.0/22 | RADB | Valid |
| 217.76.247.0/24 | 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.