Network · data from 2026-11-12
AS12291 DPAG-AS DHL AG
Registry name: DPAG-AS DHL AG, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS12291, 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.
| 149.239.0.0/17 | No ROA | RIR databaseRIPE | 672 100% |
| 149.239.128.0/17 | No ROA | RIR databaseRIPE | 672 100% |
| 160.54.0.0/16 | No ROA | RIR databaseRIPE | 672 100% |
| 160.55.0.0/16 | No ROA | RIR databaseRIPE | 672 100% |
| 160.56.0.0/16 | No ROA | RIR databaseRIPE | 672 100% |
| 160.57.0.0/16 | No ROA | RIR databaseRIPE | 672 100% |
| 160.58.0.0/17 | No ROA | RIR databaseRIPE | 672 100% |
| 160.58.128.0/17 | No ROA | RIR databaseRIPE | 672 100% |
| 192.109.50.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 149.239.0.0/16 | No ROA | RIR databaseRIPE | 671 100% |
| 160.54.0.0/15 | No ROA | RIR databaseRIPE | 671 100% |
| 160.56.0.0/15 | No ROA | RIR databaseRIPE | 671 100% |
| 160.58.0.0/16 | No ROA | RIR databaseRIPE | 671 100% |
| 192.109.50.0/23 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS12291 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 16 are in fix.csv.
- ROA: none14
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 149.239.0.0/17 | No ROA covers it. Add a ROA for AS12291, maxLength 17. |
| ROA: none | 149.239.128.0/17 | No ROA covers it. Add a ROA for AS12291, maxLength 17. |
| ROA: none | 160.54.0.0/16 | No ROA covers it. Add a ROA for AS12291, maxLength 16. |
| ROA: none | 160.55.0.0/16 | No ROA covers it. Add a ROA for AS12291, maxLength 16. |
| ROA: none | 160.56.0.0/16 | No ROA covers it. Add a ROA for AS12291, maxLength 16. |
| ROA: none | 160.57.0.0/16 | No ROA covers it. Add a ROA for AS12291, maxLength 16. |
| ROA: none | 160.58.0.0/17 | No ROA covers it. Add a ROA for AS12291, maxLength 17. |
| ROA: none | 160.58.128.0/17 | No ROA covers it. Add a ROA for AS12291, maxLength 17. |
| ROA: none | 192.109.50.0/24 | No ROA covers it. Add a ROA for AS12291, maxLength 24. |
| ROA: none | 149.239.0.0/16 | No ROA covers it. Add a ROA for AS12291, maxLength 16. |
| ROA: none | 160.54.0.0/15 | No ROA covers it. Add a ROA for AS12291, maxLength 15. |
| ROA: none | 160.56.0.0/15 | No ROA covers it. Add a ROA for AS12291, maxLength 15. |
| ROA: none | 160.58.0.0/16 | No ROA covers it. Add a ROA for AS12291, maxLength 16. |
| ROA: none | 192.109.50.0/23 | No ROA covers it. Add a ROA for AS12291, maxLength 23. |
Route objects not announced
Route objects with origin AS12291 whose prefix no peer sees AS12291 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.109.49.0/24 | RIPE | No ROA |
| 192.109.51.0/24 | 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.