Network · data from 2026-11-12
AS57839 AS-FR-LIR-CELYA-2011-047 CARREFOUR SYSTEMES D'INFORMATION
Registry name: AS-FR-LIR-CELYA-2011-047 CARREFOUR SYSTEMES D'INFORMATION, FR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS57839, 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.
| 217.77.228.0/24 | No ROA | Nonecovered by 217.77.228.0/22 | 673 100% |
| 217.77.230.0/24 | No ROA | Nonecovered by 217.77.228.0/22 | 673 100% |
| 217.77.231.0/24 | No ROA | Nonecovered by 217.77.228.0/22 | 673 100% |
| 217.77.224.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 217.77.225.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 217.77.226.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 217.77.227.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 217.77.229.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 217.77.233.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 217.77.237.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 217.77.238.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 2001:67c:280c::/48 | No ROA | RIR databaseRIPE | 636 100% |
| 2001:67c:2a74::/48 | No ROA | RIR databaseRIPE | 636 100% |
AS-SET
AS57839 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 22 are in fix.csv.
- ROA: none13
- Route object: none3
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 217.77.228.0/24 | No ROA covers it. Add a ROA for AS57839, maxLength 24. |
| Route object: none | 217.77.228.0/24 | No route object for it. A route object for 217.77.228.0/22 with origin AS57839 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57839 in the RIR database for the space. |
| ROA: none | 217.77.230.0/24 | No ROA covers it. Add a ROA for AS57839, maxLength 24. |
| Route object: none | 217.77.230.0/24 | No route object for it. A route object for 217.77.228.0/22 with origin AS57839 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57839 in the RIR database for the space. |
| ROA: none | 217.77.231.0/24 | No ROA covers it. Add a ROA for AS57839, maxLength 24. |
| Route object: none | 217.77.231.0/24 | No route object for it. A route object for 217.77.228.0/22 with origin AS57839 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57839 in the RIR database for the space. |
| ROA: none | 217.77.224.0/24 | No ROA covers it. Add a ROA for AS57839, maxLength 24. |
| ROA: none | 217.77.225.0/24 | No ROA covers it. Add a ROA for AS57839, maxLength 24. |
| ROA: none | 217.77.226.0/24 | No ROA covers it. Add a ROA for AS57839, maxLength 24. |
| ROA: none | 217.77.227.0/24 | No ROA covers it. Add a ROA for AS57839, maxLength 24. |
| ROA: none | 217.77.229.0/24 | No ROA covers it. Add a ROA for AS57839, maxLength 24. |
| ROA: none | 217.77.233.0/24 | No ROA covers it. Add a ROA for AS57839, maxLength 24. |
| ROA: none | 217.77.237.0/24 | No ROA covers it. Add a ROA for AS57839, maxLength 24. |
| ROA: none | 217.77.238.0/24 | No ROA covers it. Add a ROA for AS57839, maxLength 24. |
| ROA: none | 2001:67c:280c::/48 | No ROA covers it. Add a ROA for AS57839, maxLength 48. |
| ROA: none | 2001:67c:2a74::/48 | No ROA covers it. Add a ROA for AS57839, maxLength 48. |
Route objects not announced
Route objects with origin AS57839 whose prefix no peer sees AS57839 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 217.77.228.0/22 | RIPE | No ROA |
| 217.77.232.0/24 | RIPE | No ROA |
| 217.77.234.0/24 | RIPE | No ROA |
| 217.77.235.0/24 | RIPE | No ROA |
| 217.77.236.0/24 | RIPE | No ROA |
| 217.77.239.0/24 | 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.