Network · data from 2026-11-12
AS28317 Boomerang Wireless
Registry name: AS28317 - NAVEGALO S.A., CR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS28317, 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.
| 138.121.140.0/24 | Valid | Other IRR onlyRADB | 663 99% |
| 138.121.141.0/24 | Valid | Other IRR onlyRADB | 663 99% |
| 138.121.142.0/24 | Valid | Other IRR onlyRADB | 663 99% |
| 138.121.143.0/24 | Valid | Other IRR onlyRADB | 663 99% |
| 170.81.32.0/24 | Valid | Other IRR onlyRADB | 663 99% |
| 170.81.33.0/24 | Valid | Other IRR onlyRADB | 663 99% |
| 170.81.34.0/24 | Valid | Other IRR onlyRADB | 663 99% |
| 170.81.35.0/24 | Valid | Other IRR onlyRADB | 663 99% |
| 191.102.56.0/24 | Valid | Other IRR onlyRADB | 663 99% |
| 191.102.57.0/24 | Valid | Other IRR onlyRADB | 663 99% |
| 191.102.58.0/24 | Valid | Other IRR onlyRADB | 663 99% |
| 191.102.59.0/24 | Valid | Other IRR onlyRADB | 663 99% |
| 209.51.185.0/24 | Valid | RIR databaseARIN, RADB | 668 99% |
| 138.122.247.0/24 | Valid | RIR databaseLACNIC, RADB | 663 99% |
AS-SET
AS28317'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 19 are in fix.csv.
- Route object: RIR12
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 138.121.140.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.121.141.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.121.142.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.121.143.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.81.32.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.81.33.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.81.34.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.81.35.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 191.102.56.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 191.102.57.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 191.102.58.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 191.102.59.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS28317 whose prefix no peer sees AS28317 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 138.121.140.0/22 | LACNIC, NTTCOM, RADB | Valid |
| 138.122.244.0/22 | RADB | No ROA |
| 138.122.244.0/24 | LACNIC, RADB | Valid |
| 170.81.32.0/22 | LACNIC, RADB | Valid |
| 191.102.56.0/22 | LACNIC, NTTCOM, RADB | Valid |
| 2606:f180:1::/48 | ARIN | No ROA |
| 2803:1a80:10::/48 | 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.