Network · data from 2026-11-12
AS20053 AIRCLIC - The Descartes Systems Group Inc
Registry name: AIRCLIC - The Descartes Systems Group Inc, CA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS20053, 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.
| 8.14.166.0/24 | No ROA | None | 672 100% |
| 64.157.238.0/24 | No ROA | None | 672 100% |
| 216.241.112.0/24 | No ROA | Nonecovered by 216.241.112.0/23 | 672 100% |
| 216.241.113.0/24 | No ROA | Nonecovered by 216.241.112.0/23 | 672 100% |
| 216.241.114.0/24 | No ROA | Nonecovered by 216.241.114.0/23 | 672 100% |
| 216.241.115.0/24 | No ROA | Nonecovered by 216.241.114.0/23 | 672 100% |
| 38.98.238.0/24 | No ROA | None | 671 100% |
| 216.241.112.0/23 | No ROA | RIR databaseARIN | 673 100% |
| 216.241.114.0/23 | No ROA | RIR databaseARIN | 673 100% |
| 216.241.124.0/23 | No ROA | RIR databaseARIN | 672 100% |
AS-SET
AS20053 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 20 are in fix.csv.
- ROA: none10
- Route object: none7
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 8.14.166.0/24 | No ROA covers it. Add a ROA for AS20053, maxLength 24. |
| Route object: none | 8.14.166.0/24 | No route object for it. Add a route object with origin AS20053 in the RIR database for the space. |
| ROA: none | 64.157.238.0/24 | No ROA covers it. Add a ROA for AS20053, maxLength 24. |
| Route object: none | 64.157.238.0/24 | No route object for it. Add a route object with origin AS20053 in the RIR database for the space. |
| ROA: none | 216.241.112.0/24 | No ROA covers it. Add a ROA for AS20053, maxLength 24. |
| Route object: none | 216.241.112.0/24 | No route object for it. A route object for 216.241.112.0/23 with origin AS20053 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20053 in the RIR database for the space. |
| ROA: none | 216.241.113.0/24 | No ROA covers it. Add a ROA for AS20053, maxLength 24. |
| Route object: none | 216.241.113.0/24 | No route object for it. A route object for 216.241.112.0/23 with origin AS20053 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20053 in the RIR database for the space. |
| ROA: none | 216.241.114.0/24 | No ROA covers it. Add a ROA for AS20053, maxLength 24. |
| Route object: none | 216.241.114.0/24 | No route object for it. A route object for 216.241.114.0/23 with origin AS20053 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20053 in the RIR database for the space. |
| ROA: none | 216.241.115.0/24 | No ROA covers it. Add a ROA for AS20053, maxLength 24. |
| Route object: none | 216.241.115.0/24 | No route object for it. A route object for 216.241.114.0/23 with origin AS20053 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20053 in the RIR database for the space. |
| ROA: none | 38.98.238.0/24 | No ROA covers it. Add a ROA for AS20053, maxLength 24. |
| Route object: none | 38.98.238.0/24 | No route object for it. Add a route object with origin AS20053 in the RIR database for the space. |
| ROA: none | 216.241.112.0/23 | No ROA covers it. Add a ROA for AS20053, maxLength 23. |
| ROA: none | 216.241.114.0/23 | No ROA covers it. Add a ROA for AS20053, maxLength 23. |
| ROA: none | 216.241.124.0/23 | No ROA covers it. Add a ROA for AS20053, maxLength 23. |
Route objects not announced
Route objects with origin AS20053 whose prefix no peer sees AS20053 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 216.241.112.0/20 | RADB | No ROA |
| 216.241.116.0/23 | ARIN | No ROA |
| 216.241.122.0/23 | ARIN | 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.