Network · data from 2026-11-12
AS33745 ATOS-BLYTHEWOOD - Atos IT Solutions and Services Inc
Registry name: ATOS-BLYTHEWOOD - Atos IT Solutions and Services Inc, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS33745, 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.
| 64.132.136.0/23 | No ROA | Other origin only | 673 100% |
| 66.193.2.0/23 | No ROA | Other origin only | 673 100% |
| 66.194.30.0/24 | No ROA | Other origin only | 673 100% |
| 138.69.182.0/24 | No ROA | Other origin only | 673 100% |
| 198.182.130.0/24 | No ROA | Other origin only | 673 100% |
| 198.182.131.0/24 | No ROA | Other origin only | 673 100% |
| 138.69.202.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 138.69.225.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 138.69.227.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 138.69.228.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 167.82.144.0/20 | No ROA | RIR databaseARIN | 673 100% |
| 167.82.176.0/20 | No ROA | RIR databaseARIN | 673 100% |
| 167.82.192.0/19 | No ROA | RIR databaseARIN | 673 100% |
| 167.82.240.0/20 | No ROA | RIR databaseARIN | 673 100% |
AS-SET
AS33745 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 21 are in fix.csv.
- ROA: none14
- Route object: none6
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 64.132.136.0/23 | No ROA covers it. Add a ROA for AS33745, maxLength 23. |
| Route object: none | 64.132.136.0/23 | Route objects for it name AS198949. Add a route object with origin AS33745 in the RIR database for the space. |
| ROA: none | 66.193.2.0/23 | No ROA covers it. Add a ROA for AS33745, maxLength 23. |
| Route object: none | 66.193.2.0/23 | Route objects for it name AS198949. Add a route object with origin AS33745 in the RIR database for the space. |
| ROA: none | 66.194.30.0/24 | No ROA covers it. Add a ROA for AS33745, maxLength 24. |
| Route object: none | 66.194.30.0/24 | Route objects for it name AS198949. Add a route object with origin AS33745 in the RIR database for the space. |
| ROA: none | 138.69.182.0/24 | No ROA covers it. Add a ROA for AS33745, maxLength 24. |
| Route object: none | 138.69.182.0/24 | Route objects for it name AS198949. Add a route object with origin AS33745 in the RIR database for the space. |
| ROA: none | 198.182.130.0/24 | No ROA covers it. Add a ROA for AS33745, maxLength 24. |
| Route object: none | 198.182.130.0/24 | Route objects for it name AS198949. Add a route object with origin AS33745 in the RIR database for the space. |
| ROA: none | 198.182.131.0/24 | No ROA covers it. Add a ROA for AS33745, maxLength 24. |
| Route object: none | 198.182.131.0/24 | Route objects for it name AS198949. Add a route object with origin AS33745 in the RIR database for the space. |
| ROA: none | 138.69.202.0/24 | No ROA covers it. Add a ROA for AS33745, maxLength 24. |
| ROA: none | 138.69.225.0/24 | No ROA covers it. Add a ROA for AS33745, maxLength 24. |
| ROA: none | 138.69.227.0/24 | No ROA covers it. Add a ROA for AS33745, maxLength 24. |
| ROA: none | 138.69.228.0/24 | No ROA covers it. Add a ROA for AS33745, maxLength 24. |
| ROA: none | 167.82.144.0/20 | No ROA covers it. Add a ROA for AS33745, maxLength 20. |
| ROA: none | 167.82.176.0/20 | No ROA covers it. Add a ROA for AS33745, maxLength 20. |
| ROA: none | 167.82.192.0/19 | No ROA covers it. Add a ROA for AS33745, maxLength 19. |
| ROA: none | 167.82.240.0/20 | No ROA covers it. Add a ROA for AS33745, maxLength 20. |
Route objects not announced
Route objects with origin AS33745 whose prefix no peer sees AS33745 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 138.69.192.0/24 | 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.