Network · data from 2026-11-12
AS31389 ATOMIDATA-AS Atomidata Oy
Registry name: ATOMIDATA-AS Atomidata Oy, FI · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS31389, 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.
| 5.61.92.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 164.5.224.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 45.14.201.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 78.108.118.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 2a13:82c0::/29 | No ROA | RIR databaseRIPE | 633 100% |
AS-SET
AS31389 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 5 are in fix.csv.
- ROA: none5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 5.61.92.0/24 | No ROA covers it. Add a ROA for AS31389, maxLength 24. |
| ROA: none | 164.5.224.0/21 | No ROA covers it. Add a ROA for AS31389, maxLength 21. |
| ROA: none | 45.14.201.0/24 | No ROA covers it. Add a ROA for AS31389, maxLength 24. |
| ROA: none | 78.108.118.0/24 | No ROA covers it. Add a ROA for AS31389, maxLength 24. |
| ROA: none | 2a13:82c0::/29 | No ROA covers it. Add a ROA for AS31389, maxLength 29. |
Route objects not announced
Every route object with origin AS31389 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.