Network · data from 2026-11-12
AS20855 AIRDATA-AS Airdata AG
Registry name: AIRDATA-AS Airdata AG, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS20855, 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.
| 213.220.163.0/24 | No ROA | Nonecovered by 213.220.160.0/19 | 673 100% |
| 212.107.160.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 212.107.168.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 213.220.160.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 213.220.161.0/24 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS20855 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 10 are in fix.csv.
- ROA: none5
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 213.220.163.0/24 | No ROA covers it. Add a ROA for AS20855, maxLength 24. |
| Route object: none | 213.220.163.0/24 | No route object for it. A route object for 213.220.160.0/19 with origin AS20855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20855 in the RIR database for the space. |
| ROA: none | 212.107.160.0/19 | No ROA covers it. Add a ROA for AS20855, maxLength 19. |
| ROA: none | 212.107.168.0/24 | No ROA covers it. Add a ROA for AS20855, maxLength 24. |
| ROA: none | 213.220.160.0/19 | No ROA covers it. Add a ROA for AS20855, maxLength 19. |
| ROA: none | 213.220.161.0/24 | No ROA covers it. Add a ROA for AS20855, maxLength 24. |
Route objects not announced
Route objects with origin AS20855 whose prefix no peer sees AS20855 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 213.220.128.0/18 | RADB | No ROA |
| 213.220.128.0/22 | RIPE | No ROA |
| 213.220.132.0/22 | RIPE | No ROA |
| 213.220.136.0/21 | 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.