Network · data from 2026-11-12
AS41935 DASSAULTSYSTEMES-AS Dassault Systemes SE
Registry name: DASSAULTSYSTEMES-AS Dassault Systemes SE, FR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS41935, 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.
| 2a00:4b00:20d::/48 | No ROA | Nonecovered by 2a00:4b00:200::/40 | 635 100% |
| 91.103.43.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.103.40.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 91.103.41.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 91.103.42.0/24 | No ROA | RIR databaseRADB, RIPE | 672 100% |
| 91.103.45.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 91.103.47.0/24 | No ROA | RIR databaseRADB, RIPE | 672 100% |
| 160.231.64.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 160.231.68.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 178.255.208.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 178.255.215.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 2a00:4b00:100::/40 | No ROA | RIR databaseRIPE | 633 100% |
| 2a00:4b00:200::/40 | No ROA | RIR databaseRIPE | 632 99% |
| 160.231.132.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 160.231.136.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 2a00:4b00:13d::/48 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
AS41935 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 30 are in fix.csv.
- ROA: none13
- Route object: none1
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a00:4b00:20d::/48 | No ROA covers it. Add a ROA for AS41935, maxLength 48. |
| Route object: none | 2a00:4b00:20d::/48 | No route object for it. A route object for 2a00:4b00:200::/40 with origin AS41935 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41935 in the RIR database for the space. |
| ROA: none | 91.103.43.0/24 | No ROA covers it. Add a ROA for AS41935, maxLength 24. |
| ROA: none | 91.103.40.0/24 | No ROA covers it. Add a ROA for AS41935, maxLength 24. |
| ROA: none | 91.103.41.0/24 | No ROA covers it. Add a ROA for AS41935, maxLength 24. |
| ROA: none | 91.103.42.0/24 | No ROA covers it. Add a ROA for AS41935, maxLength 24. |
| ROA: none | 91.103.45.0/24 | No ROA covers it. Add a ROA for AS41935, maxLength 24. |
| ROA: none | 91.103.47.0/24 | No ROA covers it. Add a ROA for AS41935, maxLength 24. |
| ROA: none | 160.231.64.0/22 | No ROA covers it. Add a ROA for AS41935, maxLength 22. |
| ROA: none | 160.231.68.0/22 | No ROA covers it. Add a ROA for AS41935, maxLength 22. |
| ROA: none | 178.255.208.0/22 | No ROA covers it. Add a ROA for AS41935, maxLength 22. |
| ROA: none | 178.255.215.0/24 | No ROA covers it. Add a ROA for AS41935, maxLength 24. |
| ROA: none | 2a00:4b00:100::/40 | No ROA covers it. Add a ROA for AS41935, maxLength 40. |
| ROA: none | 2a00:4b00:200::/40 | No ROA covers it. Add a ROA for AS41935, maxLength 40. |
Route objects not announced
Route objects with origin AS41935 whose prefix no peer sees AS41935 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.103.40.0/21 | RIPE | No ROA |
| 91.103.46.0/24 | RIPE | No ROA |
| 160.231.64.0/23 | RIPE | No ROA |
| 160.231.96.0/20 | RIPE | No ROA |
| 160.231.99.0/24 | RIPE | No ROA |
| 178.255.208.0/21 | RIPE | No ROA |
| 178.255.208.0/23 | RIPE | No ROA |
| 178.255.208.0/24 | RIPE | No ROA |
| 178.255.209.0/24 | RIPE | No ROA |
| 178.255.210.0/24 | RIPE | No ROA |
| 178.255.211.0/24 | RIPE | No ROA |
| 193.47.80.0/24 | RIPE | No ROA |
| 2a00:4b00::/32 | RIPE | No ROA |
| 2a00:4b00:10c::/48 | RIPE | No ROA |
| 2a00:4b00:12d::/48 | RIPE | No ROA |
| 2a00:4b00:130::/48 | 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.