Network · data from 2026-11-12
AS54781 Sysco Corporation
Registry name: SYSCO-AS - Sysco Corporation, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS54781, 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.
| 80.252.82.68/30 | Invalid: origin | None | 1 0%low visibility |
| 213.168.225.72/30 | Invalid: origin | None | 1 0%low visibility |
| 69.94.16.0/22 | No ROA | Nonecovered by 69.94.16.0/20 | 673 100% |
| 69.94.16.0/23 | No ROA | Nonecovered by 69.94.16.0/20 | 672 100% |
| 69.94.18.0/23 | No ROA | Nonecovered by 69.94.16.0/20 | 672 100% |
| 69.94.20.0/24 | No ROA | Nonecovered by 69.94.16.0/20 | 672 100% |
| 69.94.21.0/24 | No ROA | Nonecovered by 69.94.16.0/20 | 672 100% |
| 65.125.90.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS54781'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 18 are in fix.csv.
- ROA: origin2
- ROA: none6
- Route object: none7
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 80.252.82.68/30 | ROAs covering it name AS15830, not AS54781. If AS54781 should announce it, add a ROA for AS54781. |
| Route object: none | 80.252.82.68/30 | No route object for it. Add a route object with origin AS54781 in the RIR database for the space. |
| ROA: origin | 213.168.225.72/30 | ROAs covering it name AS15830, not AS54781. If AS54781 should announce it, add a ROA for AS54781. |
| Route object: none | 213.168.225.72/30 | No route object for it. Add a route object with origin AS54781 in the RIR database for the space. |
| ROA: none | 69.94.16.0/22 | No ROA covers it. Add a ROA for AS54781, maxLength 22. |
| Route object: none | 69.94.16.0/22 | No route object for it. A route object for 69.94.16.0/20 with origin AS54781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54781 in the RIR database for the space. |
| ROA: none | 69.94.16.0/23 | No ROA covers it. Add a ROA for AS54781, maxLength 23. |
| Route object: none | 69.94.16.0/23 | No route object for it. A route object for 69.94.16.0/20 with origin AS54781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54781 in the RIR database for the space. |
| ROA: none | 69.94.18.0/23 | No ROA covers it. Add a ROA for AS54781, maxLength 23. |
| Route object: none | 69.94.18.0/23 | No route object for it. A route object for 69.94.16.0/20 with origin AS54781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54781 in the RIR database for the space. |
| ROA: none | 69.94.20.0/24 | No ROA covers it. Add a ROA for AS54781, maxLength 24. |
| Route object: none | 69.94.20.0/24 | No route object for it. A route object for 69.94.16.0/20 with origin AS54781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54781 in the RIR database for the space. |
| ROA: none | 69.94.21.0/24 | No ROA covers it. Add a ROA for AS54781, maxLength 24. |
| Route object: none | 69.94.21.0/24 | No route object for it. A route object for 69.94.16.0/20 with origin AS54781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54781 in the RIR database for the space. |
| ROA: none | 65.125.90.0/24 | No ROA covers it. Add a ROA for AS54781, maxLength 24. |
| Route object: RIR | 65.125.90.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS54781 whose prefix no peer sees AS54781 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 67.216.22.0/24 | RADB | No ROA |
| 69.94.16.0/20 | RADB | 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.