bgpreport

Network · data from 2026-11-12

AS29601 UPM-KYMMENE-AS UPM-Kymmene Oyj

Registry name: UPM-KYMMENE-AS UPM-Kymmene Oyj, FI · not in PeeringDB

13IPv4 routes 92.3% RPKI valid · 84.6% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS29601, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS29601, 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.
141.172.0.0/16 No ROA RIR databaseRIPE 673 100% 67
193.24.67.0/24 Valid None 673 100% 67
193.24.71.0/24 Valid None 673 100% 67
139.123.224.0/24 Valid RIR databaseRIPE 673 100% 67
192.130.31.0/24 Valid RIR databaseRIPE 673 100% 67
192.130.157.0/24 Valid RIR databaseRIPE 673 100% 67
192.194.132.0/22 Valid RIR databaseRIPE 673 100% 67
192.194.136.0/21 Valid RIR databaseRIPE 673 100% 67
192.194.144.0/20 Valid RIR databaseRIPE 673 100% 67
192.194.160.0/24 Valid RIR databaseRIPE 673 100% 67
193.24.64.0/24 Valid RIR databaseRIPE 673 100% 67
193.24.70.0/24 Valid RIR databaseRIPE 673 100% 67
194.252.225.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

AS29601 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 11 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none141.172.0.0/16No ROA covers it. Add a ROA for AS29601, maxLength 16.673 of 673
Route object: none193.24.67.0/24No route object for it. Add a route object with origin AS29601 in the RIR database for the space.673 of 673
Route object: none193.24.71.0/24No route object for it. Add a route object with origin AS29601 in the RIR database for the space.673 of 673

Route objects not announced

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

139.123.224.0/19RIPENo ROA
192.194.132.0/24RIPEInvalid: maxLength
192.194.134.0/23RIPEInvalid: maxLength
192.194.144.0/21RIPEValid
192.194.152.0/23RIPEValid
192.194.154.0/24RIPEValid
192.194.155.0/24RIPEValid
192.194.156.0/22RIPEValid

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.