Network · data from 2026-11-12
AS273837 AS273837 - NAVEGANTE NETWORK, C.A.
Registry name: AS273837 - NAVEGANTE NETWORK, C.A., VE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS273837, 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.
| 38.58.191.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 38.147.74.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 38.147.75.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 38.58.232.0/24 | No ROA | Other IRR onlyRADB | 669 99% |
| 200.36.152.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 200.36.153.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 200.36.154.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 200.36.155.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 2803:6950:300::/40 | Valid | RIR databaseLACNIC, RADB | 632 99% |
AS-SET
AS273837 isn't in PeeringDB, where networks name their 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 13 are in fix.csv.
- ROA: none4
- Route object: RIR4
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.58.191.0/24 | No ROA covers it. Add a ROA for AS273837, maxLength 24. |
| Route object: RIR | 38.58.191.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.147.74.0/24 | No ROA covers it. Add a ROA for AS273837, maxLength 24. |
| Route object: RIR | 38.147.74.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.147.75.0/24 | No ROA covers it. Add a ROA for AS273837, maxLength 24. |
| Route object: RIR | 38.147.75.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.58.232.0/24 | No ROA covers it. Add a ROA for AS273837, maxLength 24. |
| Route object: RIR | 38.58.232.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS273837 whose prefix no peer sees AS273837 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 200.36.152.0/22 | LACNIC | Valid |
| 2803:6950:100::/40 | LACNIC | Valid |
| 2803:6950:200::/40 | LACNIC | Valid |
| 2803:6950:400::/40 | LACNIC | Valid |
| 2803:6950:500::/40 | LACNIC | 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.