Network · data from 2026-11-12
AS17001 UMANITOBA - University of Manitoba
Registry name: UMANITOBA - University of Manitoba, CA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17001, 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.
| 140.193.0.0/18 | Valid | Other origin onlycovered by 140.193.0.0/16 | 670 100% |
| 130.179.0.0/16 | Valid | RIR databaseARIN, CANARIE | 671 100% |
| 140.193.0.0/16 | Valid | RIR databaseARIN, CANARIE | 671 100% |
| 192.139.114.0/24 | Valid | RIR databaseARIN, CANARIE | 671 100% |
AS-SET
AS17001 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 5 are in fix.csv.
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 140.193.0.0/18 | Route objects for it name AS10965. A route object for 140.193.0.0/16 with origin AS17001 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17001 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS17001 whose prefix no peer sees AS17001 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 142.233.0.0/16 | CANARIE | No ROA |
| 192.139.25.0/24 | CANARIE | No ROA |
| 206.12.27.0/24 | CANARIE | Invalid: origin |
| 2620:0:bd0::/48 | CANARIE | 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.