Network · data from 2026-11-12
AS375 TIETOTIE-AS Tieto Oyj
Registry name: TIETOTIE-AS Tieto Oyj, FI · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS375, 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.207.0.0/17 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.0.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.10.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.13.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.19.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.20.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.22.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.33.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.36.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.40.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.48.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.52.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.55.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.56.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.64.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.68.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.70.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.72.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.72.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 192.49.78.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.81.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.86.0/23 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 192.49.88.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.91.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.92.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.96.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.112.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.117.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.119.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.120.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.124.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.126.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.128.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.133.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.134.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.136.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.139.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.140.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.142.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.144.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.146.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.148.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.152.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.160.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.168.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.170.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.173.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.174.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.176.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.192.0/18 | Valid | RIR databaseRIPE | 672 100% |
| 192.163.145.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.49.9.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2a03:9b80::/34 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS375 isn't in PeeringDB, where networks name their AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS375 is announced.
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.