Network · data from 2026-11-12
AS19720 CABLEVISION-CORP - Cablevision Systems Corp.
Registry name: CABLEVISION-CORP - Cablevision Systems Corp., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS19720, 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.
| 216.255.107.0/24 | Invalid: origin | None | 48 7%low visibility |
| 167.206.119.0/24 | No ROA | None | 670 100% |
| 167.206.120.0/24 | No ROA | None | 670 100% |
| 167.206.122.0/24 | No ROA | None | 670 100% |
| 167.206.123.0/24 | No ROA | None | 670 100% |
| 65.51.29.0/24 | Valid | None | 673 100% |
| 65.51.31.0/24 | Valid | None | 673 100% |
| 216.2.193.0/24 | Valid | RIR databaseARIN | 673 100% |
| 216.2.194.0/24 | Valid | RIR databaseARIN | 673 100% |
| 216.2.195.0/24 | Valid | RIR databaseARIN | 673 100% |
AS-SET
AS19720 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 15 are in fix.csv.
- ROA: origin1
- ROA: none4
- Route object: none7
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 216.255.107.0/24 | ROAs covering it name AS6128, not AS19720. If AS19720 should announce it, add a ROA for AS19720. |
| Route object: none | 216.255.107.0/24 | No route object for it. Add a route object with origin AS19720 in the RIR database for the space. |
| ROA: none | 167.206.119.0/24 | No ROA covers it. Add a ROA for AS19720, maxLength 24. |
| Route object: none | 167.206.119.0/24 | No route object for it. Add a route object with origin AS19720 in the RIR database for the space. |
| ROA: none | 167.206.120.0/24 | No ROA covers it. Add a ROA for AS19720, maxLength 24. |
| Route object: none | 167.206.120.0/24 | No route object for it. Add a route object with origin AS19720 in the RIR database for the space. |
| ROA: none | 167.206.122.0/24 | No ROA covers it. Add a ROA for AS19720, maxLength 24. |
| Route object: none | 167.206.122.0/24 | No route object for it. Add a route object with origin AS19720 in the RIR database for the space. |
| ROA: none | 167.206.123.0/24 | No ROA covers it. Add a ROA for AS19720, maxLength 24. |
| Route object: none | 167.206.123.0/24 | No route object for it. Add a route object with origin AS19720 in the RIR database for the space. |
| Route object: none | 65.51.29.0/24 | No route object for it. Add a route object with origin AS19720 in the RIR database for the space. |
| Route object: none | 65.51.31.0/24 | No route object for it. Add a route object with origin AS19720 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS19720 whose prefix no peer sees AS19720 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 148.77.63.0/24 | ARIN | Valid |
| 216.2.192.0/22 | ARIN | Valid |
| 216.2.192.0/24 | 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.