Network · data from 2026-11-12
AS11700 CA-CW-E - CW-E
Registry name: CA-CW-E - CW-E, CA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS11700, 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.
| 205.207.200.0/22 | No ROA | Other IRR onlyCANARIE, RADB | 672 100% |
| 207.219.101.0/24 | Valid | Other IRR onlyCANARIE, RADB | 672 100% |
| 209.202.75.0/24 | Valid | Other IRR onlyCANARIE, RADB | 672 100% |
| 137.207.0.0/16 | Valid | RIR databaseARIN, CANARIE, RADB | 672 100% |
| 199.71.12.0/24 | Valid | RIR databaseARIN, CANARIE, RADB | 672 100% |
| 199.71.141.0/24 | Valid | RIR databaseARIN, CANARIE, RADB | 672 100% |
| 205.207.190.0/23 | Valid | RIR databaseARIN, CANARIE, RADB | 672 100% |
| 205.207.192.0/21 | Valid | RIR databaseARIN, CANARIE, RADB | 672 100% |
| 205.207.203.0/24 | Valid | RIR databaseARIN, CANARIE | 672 100% |
| 204.225.7.0/24 | Valid | RIR databaseARIN, CANARIE, RADB | 670 100% |
| 205.207.189.0/24 | Valid | RIR databaseARIN, CANARIE, RADB | 670 100% |
| 205.207.202.0/24 | Valid | RIR databaseARIN, CANARIE | 670 100% |
| 205.211.88.0/23 | Valid | RIR databaseARIN, CANARIE, RADB | 670 100% |
| 205.211.90.0/24 | Valid | RIR databaseARIN, CANARIE, RADB | 670 100% |
AS-SET
AS11700 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: none1
- Route object: RIR3
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 205.207.200.0/22 | No ROA covers it. Add a ROA for AS11700, maxLength 22. |
| Route object: RIR | 205.207.200.0/22 | Route object only in CANARIE, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 207.219.101.0/24 | Route object only in CANARIE, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 209.202.75.0/24 | Route object only in CANARIE, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS11700 whose prefix no peer sees AS11700 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.139.208.0/24 | ARIN, CANARIE | Valid |
| 204.41.157.0/24 | CANARIE | No ROA |
| 204.41.158.0/24 | CANARIE | No ROA |
| 204.41.159.0/24 | CANARIE | No ROA |
| 204.41.160.0/24 | CANARIE | No ROA |
| 204.41.161.0/24 | CANARIE | No ROA |
| 205.207.198.0/24 | CANARIE | Invalid: maxLength |
| 205.207.199.0/24 | CANARIE | Invalid: maxLength |
| 205.207.200.0/23 | ARIN | Valid |
| 205.207.201.0/24 | CANARIE | Invalid: maxLength |
| 207.219.101.96/29 | CANARIE | Invalid: maxLength |
| 209.202.75.48/28 | CANARIE | Invalid: maxLength |
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.