Network · data from 2026-11-12
AS27564 CAPGEMINI-CIS-AS1 - CAPGEMINI AMERICA, INC.
Registry name: CAPGEMINI-CIS-AS1 - CAPGEMINI AMERICA, INC., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS27564, 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.
| 198.199.238.0/24 | No ROA | None | 673 100% |
| 67.204.64.0/18 | No ROA | None | 670 100% |
| 67.204.73.0/24 | No ROA | None | 670 100% |
| 67.204.74.0/24 | No ROA | None | 670 100% |
| 67.204.75.0/24 | No ROA | None | 670 100% |
| 67.204.101.0/24 | No ROA | None | 670 100% |
| 67.204.105.0/24 | No ROA | None | 670 100% |
| 67.204.106.0/24 | No ROA | None | 670 100% |
| 67.204.108.0/24 | No ROA | None | 670 100% |
| 2606:4040::/32 | No ROA | RIR databaseARIN | 636 100% |
AS-SET
AS27564 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: none10
- Route object: none9
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 198.199.238.0/24 | No ROA covers it. Add a ROA for AS27564, maxLength 24. |
| Route object: none | 198.199.238.0/24 | No route object for it. Add a route object with origin AS27564 in the RIR database for the space. |
| ROA: none | 67.204.64.0/18 | No ROA covers it. Add a ROA for AS27564, maxLength 18. |
| Route object: none | 67.204.64.0/18 | No route object for it. Add a route object with origin AS27564 in the RIR database for the space. |
| ROA: none | 67.204.73.0/24 | No ROA covers it. Add a ROA for AS27564, maxLength 24. |
| Route object: none | 67.204.73.0/24 | No route object for it. Add a route object with origin AS27564 in the RIR database for the space. |
| ROA: none | 67.204.74.0/24 | No ROA covers it. Add a ROA for AS27564, maxLength 24. |
| Route object: none | 67.204.74.0/24 | No route object for it. Add a route object with origin AS27564 in the RIR database for the space. |
| ROA: none | 67.204.75.0/24 | No ROA covers it. Add a ROA for AS27564, maxLength 24. |
| Route object: none | 67.204.75.0/24 | No route object for it. Add a route object with origin AS27564 in the RIR database for the space. |
| ROA: none | 67.204.101.0/24 | No ROA covers it. Add a ROA for AS27564, maxLength 24. |
| Route object: none | 67.204.101.0/24 | No route object for it. Add a route object with origin AS27564 in the RIR database for the space. |
| ROA: none | 67.204.105.0/24 | No ROA covers it. Add a ROA for AS27564, maxLength 24. |
| Route object: none | 67.204.105.0/24 | No route object for it. Add a route object with origin AS27564 in the RIR database for the space. |
| ROA: none | 67.204.106.0/24 | No ROA covers it. Add a ROA for AS27564, maxLength 24. |
| Route object: none | 67.204.106.0/24 | No route object for it. Add a route object with origin AS27564 in the RIR database for the space. |
| ROA: none | 67.204.108.0/24 | No ROA covers it. Add a ROA for AS27564, maxLength 24. |
| Route object: none | 67.204.108.0/24 | No route object for it. Add a route object with origin AS27564 in the RIR database for the space. |
| ROA: none | 2606:4040::/32 | No ROA covers it. Add a ROA for AS27564, maxLength 32. |
Route objects not announced
Route objects with origin AS27564 whose prefix no peer sees AS27564 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 65.203.164.0/24 | NTTCOM | No ROA |
| 65.212.24.0/23 | NTTCOM | 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.