Network · data from 2026-11-12
AS1342 Fujitsu Finland
Registry name: UNSPECIFIED - IDDQD-AS, EU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS1342, 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.192.0.0/16 | No ROA | RIR databaseRIPE | 672 100% |
| 185.231.144.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 193.105.160.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 213.138.128.0/19 | No ROA | RIR databaseRIPE | 672 100% |
| 213.214.128.0/18 | No ROA | RIR databaseRIPE | 672 100% |
| 2a02:2048::/32 | No ROA | RIR databaseRIPE | 634 100% |
| 193.163.4.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS1342's PeeringDB record names no 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: none6
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 141.192.0.0/16 | No ROA covers it. Add a ROA for AS1342, maxLength 16. |
| ROA: none | 185.231.144.0/22 | No ROA covers it. Add a ROA for AS1342, maxLength 22. |
| ROA: none | 193.105.160.0/24 | No ROA covers it. Add a ROA for AS1342, maxLength 24. |
| ROA: none | 213.138.128.0/19 | No ROA covers it. Add a ROA for AS1342, maxLength 19. |
| ROA: none | 213.214.128.0/18 | No ROA covers it. Add a ROA for AS1342, maxLength 18. |
| ROA: none | 2a02:2048::/32 | No ROA covers it. Add a ROA for AS1342, maxLength 32. |
Route objects not announced
Route objects with origin AS1342 whose prefix no peer sees AS1342 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.205.0.0/22 | RIPE | No ROA |
| 185.205.0.0/24 | RIPE | No ROA |
| 185.205.1.0/24 | RIPE | No ROA |
| 185.205.2.0/24 | RIPE | No ROA |
| 185.205.3.0/24 | RIPE | No 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.