Network · data from 2026-11-12

AS5411 Tieto Oyj

Registry name: Tieto Oyj, FI · not in PeeringDB

56IPv4 routes 94.6% RPKI valid · 100.0% with a route object

6IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

3No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

7Route objects not announced registered with origin AS5411, seen from no peer

Announced routes

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


145.251.0.0/17	No ROA	RIR databaseRIPE	672 100%	66
145.251.128.0/17	No ROA	RIR databaseRIPE	672 100%	66
145.251.0.0/16	No ROA	RIR databaseRIPE	670 100%	67
82.196.160.0/20	Valid	RIR databaseRIPE	672 100%	66
82.196.176.0/20	Valid	RIR databaseRIPE	672 100%	66
93.190.195.0/24	Valid	RIR databaseRIPE	672 100%	66
93.190.198.0/24	Valid	RIR databaseRIPE	672 100%	66
93.190.199.0/24	Valid	RIR databaseRIPE	672 100%	66
192.36.44.0/24	Valid	RIR databaseRIPE	672 100%	66
192.36.45.0/24	Valid	RIR databaseRIPE	672 100%	66
192.71.132.0/24	Valid	RIR databaseRIPE	672 100%	66
192.71.133.0/24	Valid	RIR databaseRIPE	672 100%	66
192.71.134.0/24	Valid	RIR databaseRIPE	672 100%	66
192.71.135.0/24	Valid	RIR databaseRIPE	672 100%	66
192.165.101.0/24	Valid	RIR databaseRIPE	672 100%	66
192.165.117.0/24	Valid	RIR databaseRIPE	672 100%	66
192.165.118.0/24	Valid	RIR databaseRIPE	672 100%	66
192.176.2.0/24	Valid	RIR databaseRIPE	672 100%	66
192.176.132.0/24	Valid	RIR databaseRIPE	672 100%	66
192.176.133.0/24	Valid	RIR databaseRIPE	672 100%	66
192.176.148.0/24	Valid	RIR databaseRIPE	672 100%	66
192.176.149.0/24	Valid	RIR databaseRIPE	672 100%	66
192.176.162.0/24	Valid	RIR databaseRIPE	672 100%	66
192.176.163.0/24	Valid	RIR databaseRIPE	672 100%	66
193.8.32.0/23	Valid	RIR databaseRIPE	672 100%	66
193.8.34.0/23	Valid	RIR databaseRIPE	672 100%	66
193.41.168.0/24	Valid	RIR databaseRIPE	672 100%	66
193.41.169.0/24	Valid	RIR databaseRIPE	672 100%	66
193.44.76.0/23	Valid	RIR databaseRIPE	672 100%	66
193.44.78.0/23	Valid	RIR databaseRIPE	672 100%	66
193.44.172.0/23	Valid	RIR databaseRIPE	672 100%	66
193.44.174.0/23	Valid	RIR databaseRIPE	672 100%	66
194.14.63.0/24	Valid	RIR databaseRIPE	672 100%	66
194.14.66.0/24	Valid	RIR databaseRIPE	672 100%	66
194.14.67.0/24	Valid	RIR databaseRIPE	672 100%	66
194.14.70.0/24	Valid	RIR databaseRIPE	672 100%	66
194.14.71.0/24	Valid	RIR databaseRIPE	672 100%	66
194.132.39.0/24	Valid	RIR databaseRIPE	672 100%	66
213.153.96.0/20	Valid	RIR databaseRIPE	672 100%	66
213.153.112.0/20	Valid	RIR databaseRIPE	672 100%	66
192.176.131.0/24	Valid	RIR databaseRIPE	671 100%	66
82.196.160.0/19	Valid	RIR databaseRIPE	670 100%	67
93.190.198.0/23	Valid	RIR databaseRIPE	670 100%	67
192.36.44.0/23	Valid	RIR databaseRIPE	670 100%	67
192.71.132.0/23	Valid	RIR databaseRIPE	670 100%	67
192.71.134.0/23	Valid	RIR databaseRIPE	670 100%	67
192.176.132.0/23	Valid	RIR databaseRADB, RIPE	670 100%	67
192.176.148.0/23	Valid	RIR databaseRADB, RIPE	670 100%	67
192.176.162.0/23	Valid	RIR databaseRADB, RIPE	670 100%	67
193.8.32.0/22	Valid	RIR databaseRIPE	670 100%	67
193.41.168.0/23	Valid	RIR databaseRIPE	670 100%	67
193.44.76.0/22	Valid	RIR databaseRIPE	670 100%	67
193.44.172.0/22	Valid	RIR databaseRIPE	670 100%	67
194.14.66.0/23	Valid	RIR databaseRIPE	670 100%	67
194.14.70.0/23	Valid	RIR databaseRIPE	670 100%	67
213.153.96.0/19	Valid	RIR databaseRIPE	670 100%	67
2a01:6d00::/32	Valid	RIR databaseRIPE	635 100%	67
2a01:6d00::/33	Valid	RIR databaseRIPE	635 100%	68
2a01:6d00:8000::/33	Valid	RIR databaseRIPE	635 100%	68
2a03:9b80:4000::/34	Valid	RIR databaseRADB, RIPE	635 100%	67
2a03:9b80:4000::/35	Valid	RIR databaseRIPE	635 100%	68
2a03:9b80:6000::/35	Valid	RIR databaseRIPE	635 100%	68

AS-SET

AS5411 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 10 are in fix.csv.

ROA: none3
Route object: not announced7

Change	Prefix or set	Detail	Full-table peers
ROA: none	145.251.0.0/17	No ROA covers it. Add a ROA for AS5411, maxLength 17.	672 of 673
ROA: none	145.251.128.0/17	No ROA covers it. Add a ROA for AS5411, maxLength 17.	672 of 673
ROA: none	145.251.0.0/16	No ROA covers it. Add a ROA for AS5411, maxLength 16.	670 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

145.251.0.0/17

No ROA covers it. Add a ROA for AS5411, maxLength 17.

672 of 673

ROA: none

145.251.128.0/17

No ROA covers it. Add a ROA for AS5411, maxLength 17.

672 of 673

ROA: none

145.251.0.0/16

No ROA covers it. Add a ROA for AS5411, maxLength 16.

670 of 673

Route objects not announced

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


185.222.176.0/22	RIPE	Valid
185.222.176.0/23	RIPE	Valid
185.222.178.0/23	RIPE	Valid
192.71.131.0/24	RIPE	No ROA
192.71.178.0/23	RIPE	Valid
192.71.178.0/24	RIPE	Valid
192.71.179.0/24	RIPE	Valid

185.222.176.0/22

RIPE

Valid

185.222.176.0/23

RIPE

Valid

185.222.178.0/23

RIPE

Valid

192.71.131.0/24

RIPE

No ROA

192.71.178.0/23

RIPE

Valid

192.71.178.0/24

RIPE

Valid

192.71.179.0/24

RIPE

Valid

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.