Network · data from 2026-11-12
AS18666 NOKIA-ASN - Nokia of America Corporation
Registry name: NOKIA-ASN - Nokia of America Corporation, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18666, 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.
| 87.254.200.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 93.183.8.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 131.228.48.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 2a00:8a00:2000::/35 | No ROA | RIR databaseRIPE | 636 100% |
| 2a00:8a01:10::/44 | No ROA | RIR databaseRIPE | 636 100% |
| 2a00:8a01:190::/44 | No ROA | RIR databaseRIPE | 636 100% |
| 2a00:8a01:8010::/44 | No ROA | RIR databaseRIPE | 636 100% |
| 2a03:5341:10::/44 | No ROA | RIR databaseRIPE | 636 100% |
AS-SET
AS18666 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 15 are in fix.csv.
- ROA: none8
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 87.254.200.0/22 | No ROA covers it. Add a ROA for AS18666, maxLength 22. |
| ROA: none | 93.183.8.0/23 | No ROA covers it. Add a ROA for AS18666, maxLength 23. |
| ROA: none | 131.228.48.0/24 | No ROA covers it. Add a ROA for AS18666, maxLength 24. |
| ROA: none | 2a00:8a00:2000::/35 | No ROA covers it. Add a ROA for AS18666, maxLength 35. |
| ROA: none | 2a00:8a01:10::/44 | No ROA covers it. Add a ROA for AS18666, maxLength 44. |
| ROA: none | 2a00:8a01:190::/44 | No ROA covers it. Add a ROA for AS18666, maxLength 44. |
| ROA: none | 2a00:8a01:8010::/44 | No ROA covers it. Add a ROA for AS18666, maxLength 44. |
| ROA: none | 2a03:5341:10::/44 | No ROA covers it. Add a ROA for AS18666, maxLength 44. |
Route objects not announced
Route objects with origin AS18666 whose prefix no peer sees AS18666 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 93.183.8.0/22 | RIPE | No ROA |
| 93.183.10.0/23 | RIPE | No ROA |
| 131.228.56.0/22 | RIPE | No ROA |
| 131.228.56.0/24 | RIPE | No ROA |
| 135.245.160.0/19 | RADB | No ROA |
| 2001:490:c000::/35 | RIPE-NONAUTH | No ROA |
| 2a00:1c68:6::/48 | RIPE | Invalid: origin |
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.