Network · data from 2026-11-12
AS16378 Otto
Registry name: OTTO-NET Otto GmbH & Co. KGaA, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS16378, 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.
| 80.85.192.0/20 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 80.85.192.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 80.85.193.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 80.85.194.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 80.85.195.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 80.85.196.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 80.85.197.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 80.85.198.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 80.85.199.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 80.85.200.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 80.85.201.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 80.85.202.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 80.85.203.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 80.85.204.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 80.85.205.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 80.85.206.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 80.85.207.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 2a02:d700::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:d700::/33 | Valid | RIR databaseRADB, RIPE | 633 100% |
| 2a02:d700:8000::/33 | Valid | RIR databaseRADB, RIPE | 633 100% |
AS-SET
AS16378's PeeringDB record names no 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 AS16378 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.