bgpreport

Network · data from 2026-11-12

AS21856 NOKIA-ASN - Nokia of America Corporation

Registry name: NOKIA-ASN - Nokia of America Corporation, US · not in PeeringDB

5IPv4 routes 0.0% RPKI valid · 40.0% with a route object
2IPv6 routes 0.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
7No ROA 5 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
14Route objects not announced registered with origin AS21856, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS21856, 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.207.0/24 No ROA Other origin only 673 100% 67
93.183.14.0/24 No ROA Other origin only 673 100% 67
93.183.18.0/24 No ROA Other origin only 673 100% 67
2a00:8a05::/44 No ROA None 636 100% 67
2a03:5345::/44 No ROA None 636 100% 67
131.228.96.0/24 No ROA RIR databaseRIPE 673 100% 67
131.228.96.0/23 No ROA RIR databaseRIPE 672 100% 67

AS-SET

AS21856 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 26 are in fix.csv.

  • ROA: none7
  • Route object: none5
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none87.254.207.0/24No ROA covers it. Add a ROA for AS21856, maxLength 24.673 of 673
Route object: none87.254.207.0/24Route objects for it name AS4847. Add a route object with origin AS21856 in the RIR database for the space.673 of 673
ROA: none93.183.14.0/24No ROA covers it. Add a ROA for AS21856, maxLength 24.673 of 673
Route object: none93.183.14.0/24Route objects for it name AS4847. Add a route object with origin AS21856 in the RIR database for the space.673 of 673
ROA: none93.183.18.0/24No ROA covers it. Add a ROA for AS21856, maxLength 24.673 of 673
Route object: none93.183.18.0/24Route objects for it name AS4847. Add a route object with origin AS21856 in the RIR database for the space.673 of 673
ROA: none2a00:8a05::/44No ROA covers it. Add a ROA for AS21856, maxLength 44.636 of 636
Route object: none2a00:8a05::/44No route object for it. Add a route object with origin AS21856 in the RIR database for the space.636 of 636
ROA: none2a03:5345::/44No ROA covers it. Add a ROA for AS21856, maxLength 44.636 of 636
Route object: none2a03:5345::/44No route object for it. Add a route object with origin AS21856 in the RIR database for the space.636 of 636
ROA: none131.228.96.0/24No ROA covers it. Add a ROA for AS21856, maxLength 24.673 of 673
ROA: none131.228.96.0/23No ROA covers it. Add a ROA for AS21856, maxLength 23.672 of 673

Route objects not announced

Route objects with origin AS21856 whose prefix no peer sees AS21856 announce. Many are kept on purpose (backup routes, space announced only in some places).

93.183.0.0/21RIPENo ROA
93.183.8.0/22RIPENo ROA
131.228.97.0/24RIPENo ROA
131.228.104.0/23RIPENo ROA
131.228.104.0/24NTTCOM, RADB, RIPENo ROA
135.245.115.0/24NTTCOM, RADBNo ROA
135.245.117.0/24NTTCOM, RADBNo ROA
135.245.118.0/23RADBNo ROA
135.245.121.0/24NTTCOM, RADBNo ROA
135.245.122.0/24NTTCOM, RADBNo ROA
135.252.9.0/24RADBNo ROA
192.100.102.0/23RIPENo ROA
192.100.132.0/23RIPEInvalid: origin
194.149.238.0/23RIPENo 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.