Network · data from 2026-11-12
AS198018 trivago
Registry name: trivago-de trivago N.V., DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS198018, 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.
| 91.198.24.0/24 | No ROA | RIR databaseRADB, RIPE | 672 100% |
| 185.177.129.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 194.153.186.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 2a0b:1306:c::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a0b:1300::/34 | Valid | RIR databaseRADB, RIPE | 634 100% |
| 2a0b:1300:8000::/48 | Valid | RIR databaseRADB, RIPE | 634 100% |
| 2a0b:1306:4::/48 | Valid | RIR databaseRADB, RIPE | 634 100% |
| 2a0b:1306:6::/48 | Valid | RIR databaseRADB, RIPE | 634 100% |
| 2a0b:1306:400::/48 | Valid | RIR databaseRADB, RIPE | 634 100% |
AS-SET
AS198018's PeeringDB record names no 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 12 are in fix.csv.
- ROA: none1
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.198.24.0/24 | No ROA covers it. Add a ROA for AS198018, maxLength 24. |
Route objects not announced
Route objects with origin AS198018 whose prefix no peer sees AS198018 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 8.35.179.0/24 | NTTCOM | No ROA |
| 185.177.128.0/24 | RADB, RIPE | No ROA |
| 185.177.130.0/24 | RIPE | Invalid: origin |
| 185.177.131.0/24 | RIPE | Valid |
| 2a0b:1301::/34 | RADB, RIPE | Valid |
| 2a0b:1301:4000::/48 | RIPE | Invalid: maxLength |
| 2a0b:1306::/48 | RADB, RIPE | Valid |
| 2a0b:1306:1::/48 | RIPE | Valid |
| 2a0b:1306:2::/48 | RIPE | Valid |
| 2a0b:1306:7::/48 | RIPE | Valid |
| 2a0b:1306:8::/48 | RIPE | Valid |
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.