Network · data from 2026-11-12
AS201868 PROSOLUCE SAS
Registry name: PROSOLUCE Prosoluce SAS, FR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS201868, 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.
| 185.61.117.0/24 | No ROA | Nonecovered by 185.61.116.0/22 | 673 100% |
| 185.61.118.0/24 | No ROA | Nonecovered by 185.61.116.0/22 | 673 100% |
| 185.61.119.0/24 | No ROA | Nonecovered by 185.61.116.0/22 | 673 100% |
| 185.131.40.0/24 | No ROA | Nonecovered by 185.131.40.0/23 | 673 100% |
| 185.131.41.0/24 | No ROA | Nonecovered by 185.131.40.0/23 | 673 100% |
| 185.131.42.0/24 | No ROA | Nonecovered by 185.131.42.0/23 | 673 100% |
| 185.61.116.0/24 | No ROA | Nonecovered by 185.61.116.0/22 | 672 100% |
| 185.176.233.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 45.147.20.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 45.147.21.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 45.147.22.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 45.147.23.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 185.53.26.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 2a02:7920::/48 | No ROA | RIR databaseRIPE | 632 99% |
AS-SET
AS201868's PeeringDB record names no 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 24 are in fix.csv.
- ROA: none14
- Route object: none7
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.61.117.0/24 | No ROA covers it. Add a ROA for AS201868, maxLength 24. |
| Route object: none | 185.61.117.0/24 | No route object for it. A route object for 185.61.116.0/22 with origin AS201868 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201868 in the RIR database for the space. |
| ROA: none | 185.61.118.0/24 | No ROA covers it. Add a ROA for AS201868, maxLength 24. |
| Route object: none | 185.61.118.0/24 | No route object for it. A route object for 185.61.116.0/22 with origin AS201868 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201868 in the RIR database for the space. |
| ROA: none | 185.61.119.0/24 | No ROA covers it. Add a ROA for AS201868, maxLength 24. |
| Route object: none | 185.61.119.0/24 | No route object for it. A route object for 185.61.116.0/22 with origin AS201868 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201868 in the RIR database for the space. |
| ROA: none | 185.131.40.0/24 | No ROA covers it. Add a ROA for AS201868, maxLength 24. |
| Route object: none | 185.131.40.0/24 | No route object for it. A route object for 185.131.40.0/23 with origin AS201868 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201868 in the RIR database for the space. |
| ROA: none | 185.131.41.0/24 | No ROA covers it. Add a ROA for AS201868, maxLength 24. |
| Route object: none | 185.131.41.0/24 | No route object for it. A route object for 185.131.40.0/23 with origin AS201868 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201868 in the RIR database for the space. |
| ROA: none | 185.131.42.0/24 | No ROA covers it. Add a ROA for AS201868, maxLength 24. |
| Route object: none | 185.131.42.0/24 | No route object for it. A route object for 185.131.42.0/23 with origin AS201868 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201868 in the RIR database for the space. |
| ROA: none | 185.61.116.0/24 | No ROA covers it. Add a ROA for AS201868, maxLength 24. |
| Route object: none | 185.61.116.0/24 | No route object for it. A route object for 185.61.116.0/22 with origin AS201868 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201868 in the RIR database for the space. |
| ROA: none | 185.176.233.0/24 | No ROA covers it. Add a ROA for AS201868, maxLength 24. |
| ROA: none | 45.147.20.0/24 | No ROA covers it. Add a ROA for AS201868, maxLength 24. |
| ROA: none | 45.147.21.0/24 | No ROA covers it. Add a ROA for AS201868, maxLength 24. |
| ROA: none | 45.147.22.0/24 | No ROA covers it. Add a ROA for AS201868, maxLength 24. |
| ROA: none | 45.147.23.0/24 | No ROA covers it. Add a ROA for AS201868, maxLength 24. |
| ROA: none | 185.53.26.0/24 | No ROA covers it. Add a ROA for AS201868, maxLength 24. |
| ROA: none | 2a02:7920::/48 | No ROA covers it. Add a ROA for AS201868, maxLength 48. |
Route objects not announced
Route objects with origin AS201868 whose prefix no peer sees AS201868 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.61.116.0/22 | RIPE | No ROA |
| 185.131.40.0/23 | RIPE | No ROA |
| 185.131.42.0/23 | 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.