Network · data from 2026-11-12
AS14487 WIND-RIVER-INTENET - Wind River Internet
Registry name: WIND-RIVER-INTENET - Wind River Internet, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS14487, 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.50.168.0/22 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 67.133.76.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 74.81.176.0/22 | No ROA | RIR databaseARIN | 673 100% |
| 72.36.4.0/24 | No ROA | RIR databaseARIN | 672 100% |
| 72.164.134.0/24 | No ROA | RIR databaseARIN | 672 100% |
| 2607:2280::/32 | No ROA | RIR databaseARIN | 636 100% |
AS-SET
AS14487 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 8 are in fix.csv.
- ROA: none6
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.50.168.0/22 | No ROA covers it. Add a ROA for AS14487, maxLength 22. |
| ROA: none | 67.133.76.0/24 | No ROA covers it. Add a ROA for AS14487, maxLength 24. |
| ROA: none | 74.81.176.0/22 | No ROA covers it. Add a ROA for AS14487, maxLength 22. |
| ROA: none | 72.36.4.0/24 | No ROA covers it. Add a ROA for AS14487, maxLength 24. |
| ROA: none | 72.164.134.0/24 | No ROA covers it. Add a ROA for AS14487, maxLength 24. |
| ROA: none | 2607:2280::/32 | No ROA covers it. Add a ROA for AS14487, maxLength 32. |
Route objects not announced
Route objects with origin AS14487 whose prefix no peer sees AS14487 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 12.37.211.0/24 | RADB | No ROA |
| 209.118.74.0/24 | 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.