bgpreport

Network · data from 2026-11-12

AS34414 NOKIA-APAC Nokia Oyj

Registry name: NOKIA-APAC Nokia Oyj, FI · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS34414, 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.

131.228.104.0/24 No ROA RIR databaseRADB, RIPE 673 100% 67
131.228.108.0/24 No ROA RIR databaseRIPE 673 100% 67
131.228.110.0/24 No ROA RIR databaseRADB, RIPE 673 100% 67
135.245.115.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
135.245.117.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
135.245.121.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
135.245.128.0/22 No ROA RIR databaseARIN 673 100% 67
135.245.190.0/23 No ROA RIR databaseARIN 673 100% 67
203.17.66.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 67
203.62.196.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 67
2a00:8a04::/44 No ROA RIR databaseRIPE 634 100% 69
2a00:8a04:8000::/44 No ROA RIR databaseRIPE 634 100% 69
2a03:5344::/44 No ROA RIR databaseRIPE 634 100% 69
2a03:5344:40::/44 No ROA RIR databaseRIPE 634 100% 69

AS-SET

AS34414 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 20 are in fix.csv.

  • ROA: none14
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none131.228.104.0/24No ROA covers it. Add a ROA for AS34414, maxLength 24.673 of 673
ROA: none131.228.108.0/24No ROA covers it. Add a ROA for AS34414, maxLength 24.673 of 673
ROA: none131.228.110.0/24No ROA covers it. Add a ROA for AS34414, maxLength 24.673 of 673
ROA: none135.245.115.0/24No ROA covers it. Add a ROA for AS34414, maxLength 24.673 of 673
ROA: none135.245.117.0/24No ROA covers it. Add a ROA for AS34414, maxLength 24.673 of 673
ROA: none135.245.121.0/24No ROA covers it. Add a ROA for AS34414, maxLength 24.673 of 673
ROA: none135.245.128.0/22No ROA covers it. Add a ROA for AS34414, maxLength 22.673 of 673
ROA: none135.245.190.0/23No ROA covers it. Add a ROA for AS34414, maxLength 23.673 of 673
ROA: none203.17.66.0/24No ROA covers it. Add a ROA for AS34414, maxLength 24.673 of 673
ROA: none203.62.196.0/24No ROA covers it. Add a ROA for AS34414, maxLength 24.673 of 673
ROA: none2a00:8a04::/44No ROA covers it. Add a ROA for AS34414, maxLength 44.634 of 636
ROA: none2a00:8a04:8000::/44No ROA covers it. Add a ROA for AS34414, maxLength 44.634 of 636
ROA: none2a03:5344::/44No ROA covers it. Add a ROA for AS34414, maxLength 44.634 of 636
ROA: none2a03:5344:40::/44No ROA covers it. Add a ROA for AS34414, maxLength 44.634 of 636

Route objects not announced

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

131.228.104.0/23RADB, RIPENo ROA
135.245.122.0/24RADBNo ROA
192.11.145.0/24ARINNo ROA
2a00:1c68:3::/48RIPEInvalid: origin
2a00:8a04:40::/44RIPENo ROA
2a00:8a04:8040::/44RIPENo 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.