Network · data from 2026-11-12
AS21150 InacDE-Atos Atos Information Technology GmbH
Registry name: InacDE-Atos Atos Information Technology GmbH, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS21150, 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.
| 194.8.100.0/28 | Invalid: maxLength | None | 1 0%low visibility |
| 91.207.162.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 129.185.160.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 185.60.36.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 192.54.66.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.26.126.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.138.113.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.55.108.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 217.115.64.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 217.115.72.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 194.8.100.0/24 | Valid | None | 673 100% |
| 155.45.160.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 155.45.176.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 155.45.208.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 155.45.240.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 155.45.255.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a01:8180:1000::/36 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS21150 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 34 are in fix.csv.
- ROA: maxLength1
- ROA: none9
- Route object: none2
- Route object: not announced22
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 194.8.100.0/28 | ROA 194.8.100.0/24 AS21150 has maxLength 24; the route is a /28. Raise the maxLength, or add a ROA for 194.8.100.0/28. |
| Route object: none | 194.8.100.0/28 | No route object for it. Add a route object with origin AS21150 in the RIR database for the space. |
| ROA: none | 91.207.162.0/23 | No ROA covers it. Add a ROA for AS21150, maxLength 23. |
| ROA: none | 129.185.160.0/19 | No ROA covers it. Add a ROA for AS21150, maxLength 19. |
| ROA: none | 185.60.36.0/22 | No ROA covers it. Add a ROA for AS21150, maxLength 22. |
| ROA: none | 192.54.66.0/24 | No ROA covers it. Add a ROA for AS21150, maxLength 24. |
| ROA: none | 193.26.126.0/24 | No ROA covers it. Add a ROA for AS21150, maxLength 24. |
| ROA: none | 193.138.113.0/24 | No ROA covers it. Add a ROA for AS21150, maxLength 24. |
| ROA: none | 194.55.108.0/22 | No ROA covers it. Add a ROA for AS21150, maxLength 22. |
| ROA: none | 217.115.64.0/21 | No ROA covers it. Add a ROA for AS21150, maxLength 21. |
| ROA: none | 217.115.72.0/21 | No ROA covers it. Add a ROA for AS21150, maxLength 21. |
| Route object: none | 194.8.100.0/24 | No route object for it. Add a route object with origin AS21150 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS21150 whose prefix no peer sees AS21150 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 143.99.146.0/24 | RIPE | No ROA |
| 143.99.147.0/24 | RIPE | No ROA |
| 143.99.208.0/22 | RIPE | No ROA |
| 193.187.16.0/20 | RIPE | Invalid: origin |
| 193.187.33.0/24 | RIPE | Invalid: origin |
| 193.187.36.0/22 | RIPE | Invalid: origin |
| 193.187.40.0/22 | RIPE | Invalid: origin |
| 193.221.87.0/24 | RIPE | No ROA |
| 193.221.89.0/24 | RIPE | No ROA |
| 193.221.90.0/24 | RIPE | No ROA |
| 217.115.64.0/20 | RIPE | No ROA |
| 217.115.64.0/24 | RIPE | No ROA |
| 217.115.65.0/24 | RIPE | No ROA |
| 217.115.66.0/24 | RIPE | No ROA |
| 217.115.67.0/24 | RIPE | No ROA |
| 217.115.68.0/24 | RIPE | No ROA |
| 217.115.70.0/24 | RIPE | No ROA |
| 217.115.72.0/24 | RIPE | No ROA |
| 217.115.73.0/24 | RIPE | No ROA |
| 217.115.74.0/24 | RIPE | No ROA |
| 217.115.75.0/24 | RIPE | No ROA |
| 217.115.76.0/25 | 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.