Network · data from 2026-11-12
AS16074 Capgemini_Outsourcing_NL Capgemini Nederland B.V.
Registry name: Capgemini_Outsourcing_NL Capgemini Nederland B.V., NL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS16074, 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.
| 62.145.32.0/22 | Valid | Nonecovered by 62.145.32.0/21 | 672 100% |
| 62.145.36.0/22 | Valid | Nonecovered by 62.145.32.0/21 | 672 100% |
| 62.112.160.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 62.112.176.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 62.145.32.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 192.113.128.0/17 | Valid | RIR databaseRIPE | 672 100% |
| 192.113.128.0/18 | Valid | RIR databaseRIPE | 672 100% |
| 192.113.192.0/18 | Valid | RIR databaseRIPE | 672 100% |
| 192.113.204.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a01:67c0::/41 | Valid | RIR databaseRIPE | 636 100% |
| 2a01:67c0:80::/41 | Valid | RIR databaseRIPE | 636 100% |
| 2a01:67c0::/40 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS16074 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 39 are in fix.csv.
- Route object: none2
- Route object: not announced37
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 62.145.32.0/22 | No route object for it. A route object for 62.145.32.0/21 with origin AS16074 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16074 in the RIR database for the space. |
| Route object: none | 62.145.36.0/22 | No route object for it. A route object for 62.145.32.0/21 with origin AS16074 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16074 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS16074 whose prefix no peer sees AS16074 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 62.112.160.0/19 | RIPE | Valid |
| 62.145.32.0/20 | RIPE | Valid |
| 62.145.32.0/24 | RIPE | Valid |
| 62.145.33.0/24 | RIPE | Valid |
| 62.145.36.0/24 | RIPE | Valid |
| 62.145.37.0/24 | RIPE | Valid |
| 62.145.38.0/24 | RIPE | Valid |
| 62.145.60.0/24 | RIPE | Valid |
| 145.77.32.0/22 | RIPE | Valid |
| 145.77.36.0/22 | RIPE | Valid |
| 145.77.42.0/23 | RIPE | Valid |
| 145.77.46.0/23 | RIPE | Valid |
| 145.77.48.0/23 | RIPE | Valid |
| 145.77.50.0/23 | RIPE | Valid |
| 145.77.52.0/22 | RIPE | Valid |
| 145.77.56.0/22 | RIPE | Valid |
| 145.77.60.0/22 | RIPE | Valid |
| 145.77.64.0/19 | RIPE | Valid |
| 145.77.96.0/20 | RIPE | Valid |
| 145.77.224.0/20 | RIPE | Valid |
| 192.113.0.0/16 | RIPE | Valid |
| 192.113.0.0/18 | RIPE | Valid |
| 192.113.0.0/19 | RIPE | Valid |
| 192.113.32.0/19 | RIPE | Valid |
| 192.113.80.0/20 | RIPE | Valid |
| 192.113.80.0/21 | RIPE | Valid |
| 192.113.88.0/21 | RIPE | Valid |
| 192.113.96.0/19 | RIPE | Valid |
| 192.113.96.0/20 | RIPE | Valid |
| 192.113.112.0/20 | RIPE | Valid |
| 194.14.77.0/24 | RIPE | No ROA |
| 217.115.224.0/20 | RIPE | No ROA |
| 217.115.224.0/21 | RIPE | No ROA |
| 217.115.232.0/21 | RIPE | No ROA |
| 2001:67c:2f04::/48 | RIPE | Valid |
| 2a01:67c0::/32 | RIPE | Valid |
| 2a01:67c0:400::/40 | RIPE | Valid |
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.