Network · data from 2026-11-12
AS53443 CITY-OF-WINNIPEG - City of Winnipeg
Registry name: CITY-OF-WINNIPEG - City of Winnipeg, CA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS53443, 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.
| 192.197.129.0/24 | No ROA | Other IRR onlyALTDB | 673 100% |
| 192.197.130.0/24 | No ROA | Other IRR onlyALTDB | 673 100% |
| 198.163.40.0/21 | No ROA | Other IRR onlyALTDB | 673 100% |
| 198.163.48.0/23 | No ROA | Other IRR onlyALTDB | 673 100% |
| 198.163.50.0/23 | No ROA | Other IRR onlyALTDB | 673 100% |
| 198.163.54.0/23 | No ROA | Other IRR onlyBELL | 673 100% |
| 198.163.56.0/21 | No ROA | Other IRR onlyALTDB | 673 100% |
| 192.197.131.0/24 | No ROA | Other IRR onlyALTDB | 671 100% |
| 192.197.132.0/24 | No ROA | Other IRR onlyALTDB | 671 100% |
| 198.163.52.0/23 | No ROA | Other IRR onlyBELL | 671 100% |
| 198.163.68.0/23 | No ROA | Other IRR onlyALTDB | 671 100% |
AS-SET
AS53443 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 24 are in fix.csv.
- ROA: none11
- Route object: RIR11
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.197.129.0/24 | No ROA covers it. Add a ROA for AS53443, maxLength 24. |
| Route object: RIR | 192.197.129.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 192.197.130.0/24 | No ROA covers it. Add a ROA for AS53443, maxLength 24. |
| Route object: RIR | 192.197.130.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 198.163.40.0/21 | No ROA covers it. Add a ROA for AS53443, maxLength 21. |
| Route object: RIR | 198.163.40.0/21 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 198.163.48.0/23 | No ROA covers it. Add a ROA for AS53443, maxLength 23. |
| Route object: RIR | 198.163.48.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 198.163.50.0/23 | No ROA covers it. Add a ROA for AS53443, maxLength 23. |
| Route object: RIR | 198.163.50.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 198.163.54.0/23 | No ROA covers it. Add a ROA for AS53443, maxLength 23. |
| Route object: RIR | 198.163.54.0/23 | Route object only in BELL. Add it in the RIR database for the space. |
| ROA: none | 198.163.56.0/21 | No ROA covers it. Add a ROA for AS53443, maxLength 21. |
| Route object: RIR | 198.163.56.0/21 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 192.197.131.0/24 | No ROA covers it. Add a ROA for AS53443, maxLength 24. |
| Route object: RIR | 192.197.131.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 192.197.132.0/24 | No ROA covers it. Add a ROA for AS53443, maxLength 24. |
| Route object: RIR | 192.197.132.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 198.163.52.0/23 | No ROA covers it. Add a ROA for AS53443, maxLength 23. |
| Route object: RIR | 198.163.52.0/23 | Route object only in BELL. Add it in the RIR database for the space. |
| ROA: none | 198.163.68.0/23 | No ROA covers it. Add a ROA for AS53443, maxLength 23. |
| Route object: RIR | 198.163.68.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS53443 whose prefix no peer sees AS53443 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 198.137.255.0/24 | RADB | No ROA |
| 198.163.64.0/22 | ALTDB | 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.