Network · data from 2026-11-12
AS51401 arvato-systems-AS Arvato Systems GmbH
Registry name: arvato-systems-AS Arvato Systems GmbH, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS51401, 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.
| 83.137.32.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 83.137.36.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 185.91.104.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 185.91.106.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 2a01:be80::/32 | No ROA | RIR databaseRIPE | 636 100% |
| 83.137.32.0/21 | No ROA | RIR databaseRIPE | 2 0%low visibility |
| 185.91.104.0/22 | No ROA | RIR databaseRIPE | 2 0%low visibility |
| 193.28.78.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.28.79.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.28.78.0/23 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS51401 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 7 are in fix.csv.
- ROA: none7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 83.137.32.0/22 | No ROA covers it. Add a ROA for AS51401, maxLength 22. |
| ROA: none | 83.137.36.0/22 | No ROA covers it. Add a ROA for AS51401, maxLength 22. |
| ROA: none | 185.91.104.0/23 | No ROA covers it. Add a ROA for AS51401, maxLength 23. |
| ROA: none | 185.91.106.0/23 | No ROA covers it. Add a ROA for AS51401, maxLength 23. |
| ROA: none | 2a01:be80::/32 | No ROA covers it. Add a ROA for AS51401, maxLength 32. |
| ROA: none | 83.137.32.0/21 | No ROA covers it. Add a ROA for AS51401, maxLength 21. |
| ROA: none | 185.91.104.0/22 | No ROA covers it. Add a ROA for AS51401, maxLength 22. |
Route objects not announced
Every route object with origin AS51401 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.