Network · data from 2026-11-12
AS12888 Amadeus GmbH
Registry name: Amadeus GmbH, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS12888, 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.
| 171.17.170.0/24 | No ROA | Nonecovered by 171.17.128.0/18 | 3 0%low visibility |
| 82.150.224.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 171.17.128.0/18 | No ROA | RIR databaseRIPE | 672 100% |
| 171.17.255.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 185.165.8.0/23 | No ROA | RIR databaseRIPE | 672 100% |
| 193.23.186.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 193.24.37.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 213.70.140.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 168.153.3.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 168.153.4.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 168.153.6.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 168.153.7.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 168.153.8.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 168.153.32.0/22 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 168.153.40.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 168.153.96.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 168.153.106.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 168.153.109.0/24 | Valid | RIR databaseAPNIC, RADB, RIPE-NONAUTH | 672 100% |
| 168.153.110.0/24 | Valid | RIR databaseAPNIC, RADB, RIPE-NONAUTH | 672 100% |
| 168.153.111.0/24 | Valid | RIR databaseAPNIC, RADB, RIPE-NONAUTH | 672 100% |
| 168.153.144.0/22 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 168.153.160.0/22 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 195.27.162.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 168.153.9.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 168.153.5.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 168.153.64.0/22 | Valid | RIR databaseAPNIC | 670 100% |
AS-SET
AS12888 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 13 are in fix.csv.
- ROA: none8
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 171.17.170.0/24 | No ROA covers it. Add a ROA for AS12888, maxLength 24. |
| Route object: none | 171.17.170.0/24 | No route object for it. A route object for 171.17.128.0/18 with origin AS12888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12888 in the RIR database for the space. |
| ROA: none | 82.150.224.0/21 | No ROA covers it. Add a ROA for AS12888, maxLength 21. |
| ROA: none | 171.17.128.0/18 | No ROA covers it. Add a ROA for AS12888, maxLength 18. |
| ROA: none | 171.17.255.0/24 | No ROA covers it. Add a ROA for AS12888, maxLength 24. |
| ROA: none | 185.165.8.0/23 | No ROA covers it. Add a ROA for AS12888, maxLength 23. |
| ROA: none | 193.23.186.0/24 | No ROA covers it. Add a ROA for AS12888, maxLength 24. |
| ROA: none | 193.24.37.0/24 | No ROA covers it. Add a ROA for AS12888, maxLength 24. |
| ROA: none | 213.70.140.0/24 | No ROA covers it. Add a ROA for AS12888, maxLength 24. |
Route objects not announced
Route objects with origin AS12888 whose prefix no peer sees AS12888 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 168.153.107.0/24 | APNIC, RADB | Valid |
| 168.153.108.0/24 | APNIC, RADB | Valid |
| 2001:1a78::/32 | RIPE | No ROA |
| 2001:1a78:8000::/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.