Network · data from 2026-11-12
AS10594 Cutting Edge Communications
Registry name: CEC - Cutting Edge Communications, Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS10594, 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.
| 64.85.8.0/21 | No ROA | Other IRR onlyRADB | 669 99% |
| 69.41.128.0/20 | No ROA | Other IRR onlyRADB | 669 99% |
| 69.41.144.0/20 | No ROA | Other IRR onlyRADB | 669 99% |
| 147.185.120.0/21 | No ROA | Other IRR onlyRADB | 669 99% |
| 173.225.80.0/20 | No ROA | Other IRR onlyRADB | 669 99% |
| 208.213.160.0/22 | No ROA | Other IRR onlyRADB | 667 99% |
AS-SET
PeeringDB's irr_as_set for AS10594: RADB::AS-CEC-TRANSIT. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS10594 isn't in the set, or no route object for AS10594 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS10594 in it | Not covered |
|---|---|---|---|---|---|
| RADB::AS-CEC-TRANSIT | RADB | 4 | 1 | No | 6 |
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 19 are in fix.csv.
- ROA: none6
- Route object: RIR6
- AS-SET: own ASN1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 64.85.8.0/21 | No ROA covers it. Add a ROA for AS10594, maxLength 21. |
| Route object: RIR | 64.85.8.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 69.41.128.0/20 | No ROA covers it. Add a ROA for AS10594, maxLength 20. |
| Route object: RIR | 69.41.128.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 69.41.144.0/20 | No ROA covers it. Add a ROA for AS10594, maxLength 20. |
| Route object: RIR | 69.41.144.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 147.185.120.0/21 | No ROA covers it. Add a ROA for AS10594, maxLength 21. |
| Route object: RIR | 147.185.120.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 173.225.80.0/20 | No ROA covers it. Add a ROA for AS10594, maxLength 20. |
| Route object: RIR | 173.225.80.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 208.213.160.0/22 | No ROA covers it. Add a ROA for AS10594, maxLength 22. |
| Route object: RIR | 208.213.160.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: own ASN | RADB::AS-CEC-TRANSIT | AS10594 isn't in AS-CEC-TRANSIT (RADB) once expanded. Add AS10594 to it. |
Route objects not announced
Route objects with origin AS10594 whose prefix no peer sees AS10594 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.85.16.0/21 | RADB | No ROA |
| 69.41.128.0/19 | RADB | No ROA |
| 204.238.153.0/24 | RADB | No ROA |
| 206.221.24.0/24 | RADB | No ROA |
| 206.221.28.0/23 | RADB | No ROA |
| 216.64.179.0/24 | 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.