Network · data from 2026-11-12
AS29018 TRIVAGO-CAMPUS-AS trivago N.V.
Registry name: TRIVAGO-CAMPUS-AS trivago N.V., DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS29018, 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.
| 2a00:6480::/32 | No ROA | Other origin only | 618 97% |
| 2a00:6480:8748::/48 | No ROA | RIR databaseRIPE | 635 100% |
| 195.225.132.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a0b:1306:3::/48 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS29018 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: none2
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a00:6480::/32 | No ROA covers it. Add a ROA for AS29018, maxLength 32. |
| Route object: none | 2a00:6480::/32 | Route objects for it name AS35548. Add a route object with origin AS29018 in the RIR database for the space. |
| ROA: none | 2a00:6480:8748::/48 | No ROA covers it. Add a ROA for AS29018, maxLength 48. |
Route objects not announced
Route objects with origin AS29018 whose prefix no peer sees AS29018 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a0b:1300:8027::/48 | RIPE | No ROA |
| 2a0b:1306:5::/48 | 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.