Network · data from 2026-11-12
AS3278 ASSEW SEW-EURODRIVE GmbH & Co KG
Registry name: ASSEW SEW-EURODRIVE GmbH & Co KG, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS3278, 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.
| 194.180.2.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.180.3.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.180.4.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 194.180.4.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.180.5.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.180.0.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 194.180.0.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.180.1.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS3278 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 AS3278 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.