Network · data from 2026-11-12
AS5777 RIBBON - Ribbon Communications Operating Company, Inc.
Registry name: RIBBON - Ribbon Communications Operating Company, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS5777, 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.
| 63.149.188.0/24 | No ROA | None | 673 100% |
| 64.129.37.0/24 | No ROA | None | 673 100% |
| 97.65.224.0/24 | No ROA | None | 673 100% |
| 216.110.2.0/24 | No ROA | None | 673 100% |
| 74.203.183.0/24 | No ROA | None | 672 100% |
| 173.227.240.0/24 | No ROA | None | 671 100% |
| 208.116.153.0/24 | No ROA | None | 2 0%low visibility |
| 147.234.184.0/24 | Valid | RIR databaseARIN | 673 100% |
| 147.234.170.0/24 | Valid | RIR databaseARIN | 672 100% |
| 147.234.175.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
AS-SET
AS5777 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 16 are in fix.csv.
- ROA: none7
- Route object: none7
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 63.149.188.0/24 | No ROA covers it. Add a ROA for AS5777, maxLength 24. |
| Route object: none | 63.149.188.0/24 | No route object for it. Add a route object with origin AS5777 in the RIR database for the space. |
| ROA: none | 64.129.37.0/24 | No ROA covers it. Add a ROA for AS5777, maxLength 24. |
| Route object: none | 64.129.37.0/24 | No route object for it. Add a route object with origin AS5777 in the RIR database for the space. |
| ROA: none | 97.65.224.0/24 | No ROA covers it. Add a ROA for AS5777, maxLength 24. |
| Route object: none | 97.65.224.0/24 | No route object for it. Add a route object with origin AS5777 in the RIR database for the space. |
| ROA: none | 216.110.2.0/24 | No ROA covers it. Add a ROA for AS5777, maxLength 24. |
| Route object: none | 216.110.2.0/24 | No route object for it. Add a route object with origin AS5777 in the RIR database for the space. |
| ROA: none | 74.203.183.0/24 | No ROA covers it. Add a ROA for AS5777, maxLength 24. |
| Route object: none | 74.203.183.0/24 | No route object for it. Add a route object with origin AS5777 in the RIR database for the space. |
| ROA: none | 173.227.240.0/24 | No ROA covers it. Add a ROA for AS5777, maxLength 24. |
| Route object: none | 173.227.240.0/24 | No route object for it. Add a route object with origin AS5777 in the RIR database for the space. |
| ROA: none | 208.116.153.0/24 | No ROA covers it. Add a ROA for AS5777, maxLength 24. |
| Route object: none | 208.116.153.0/24 | No route object for it. Add a route object with origin AS5777 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS5777 whose prefix no peer sees AS5777 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 147.234.160.0/24 | ARIN | Valid |
| 2620:131:2000::/40 | ARIN | 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.