Network · data from 2026-11-12
AS14663 TELUS-MOBILITY - TELUS Communications Inc.
Registry name: TELUS-MOBILITY - TELUS Communications Inc., CA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS14663, 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.198.128.0/20 | Valid | Other IRR onlyBELL, RADB | 2 0%low visibility |
| 216.198.144.0/20 | Valid | Other IRR onlyBELL, RADB | 2 0%low visibility |
AS-SET
AS14663 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 7 are in fix.csv.
- Route object: RIR2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 216.198.128.0/20 | Route object only in BELL, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 216.198.144.0/20 | Route object only in BELL, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS14663 whose prefix no peer sees AS14663 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 68.182.0.0/18 | RADB | No ROA |
| 68.182.64.0/18 | RADB | No ROA |
| 68.182.192.0/18 | RADB | No ROA |
| 161.184.88.0/24 | RADB | Valid |
| 216.198.158.0/23 | RADB | 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.