Network · data from 2026-11-12
AS7861 TELUS-7861 - TELUS Communications Inc.
Registry name: TELUS-7861 - TELUS Communications Inc., CA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS7861, 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.
| 66.203.206.0/24 | Invalid: origin | None | 41 6%low visibility |
| 209.29.245.0/24 | Valid | Nonecovered by 209.29.244.0/23 | 669 99% |
| 64.114.189.0/24 | Valid | RIR databaseARIN | 669 99% |
| 154.11.131.0/24 | Valid | RIR databaseARIN | 669 99% |
| 204.191.2.0/24 | Valid | RIR databaseARIN | 669 99% |
| 204.191.4.0/23 | Valid | RIR databaseARIN | 669 99% |
| 204.191.175.0/24 | Valid | RIR databaseARIN | 669 99% |
| 207.34.120.0/24 | Valid | RIR databaseARIN | 669 99% |
| 207.34.206.0/24 | Valid | RIR databaseARIN | 669 99% |
| 207.167.232.0/24 | Valid | RIR databaseARIN | 669 99% |
| 207.229.36.0/24 | Valid | RIR databaseARIN, RADB | 669 99% |
| 209.20.32.0/24 | Valid | RIR databaseARIN | 669 99% |
| 209.20.33.0/24 | Valid | RIR databaseARIN | 669 99% |
| 209.20.38.0/23 | Valid | RIR databaseARIN | 669 99% |
| 209.29.141.0/24 | Valid | RIR databaseARIN | 669 99% |
| 209.29.160.0/24 | Valid | RIR databaseARIN | 669 99% |
| 209.29.161.0/24 | Valid | RIR databaseARIN | 669 99% |
| 209.29.162.0/24 | Valid | RIR databaseARIN | 669 99% |
| 209.29.163.0/24 | Valid | RIR databaseARIN | 669 99% |
| 209.29.216.0/22 | Valid | RIR databaseARIN | 669 99% |
| 209.29.222.0/23 | Valid | RIR databaseARIN | 669 99% |
| 209.29.226.0/23 | Valid | RIR databaseARIN | 669 99% |
| 209.29.242.0/23 | Valid | RIR databaseARIN | 669 99% |
| 209.89.78.0/24 | Valid | RIR databaseARIN, RADB | 669 99% |
| 209.91.75.0/24 | Valid | RIR databaseARIN | 669 99% |
| 209.91.88.0/23 | Valid | RIR databaseARIN | 669 99% |
| 209.91.90.0/24 | Valid | RIR databaseARIN | 669 99% |
| 209.91.95.0/24 | Valid | RIR databaseARIN | 669 99% |
| 209.91.108.0/24 | Valid | RIR databaseARIN | 669 99% |
| 209.91.115.0/24 | Valid | RIR databaseARIN | 669 99% |
| 209.91.116.0/24 | Valid | RIR databaseARIN | 669 99% |
| 209.91.117.0/24 | Valid | RIR databaseARIN | 669 99% |
| 209.91.119.0/24 | Valid | RIR databaseARIN | 669 99% |
| 209.115.158.0/23 | Valid | RIR databaseARIN | 669 99% |
| 209.121.167.0/24 | Valid | RIR databaseARIN | 669 99% |
| 209.91.77.0/24 | Valid | RIR databaseARIN | 668 99% |
AS-SET
AS7861 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 15 are in fix.csv.
- ROA: origin1
- Route object: none2
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 66.203.206.0/24 | ROAs covering it name AS852, not AS7861. If AS7861 should announce it, add a ROA for AS7861. |
| Route object: none | 66.203.206.0/24 | No route object for it. Add a route object with origin AS7861 in the RIR database for the space. |
| Route object: none | 209.29.245.0/24 | No route object for it. A route object for 209.29.244.0/23 with origin AS7861 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7861 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS7861 whose prefix no peer sees AS7861 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 209.20.31.0/24 | ARIN | Valid |
| 209.29.227.0/24 | ARIN | Valid |
| 209.29.244.0/23 | ARIN | Valid |
| 209.53.1.0/24 | ARIN | Valid |
| 2001:568:800::/40 | ARIN | Valid |
| 2001:56a:e::/48 | ARIN | Valid |
| 2001:56a:f::/48 | ARIN | Valid |
| 2001:56a:8f00::/40 | ARIN | Valid |
| 2001:56b:e::/48 | ARIN | Valid |
| 2001:56b:f::/48 | ARIN | Valid |
| 2001:56b:e00::/40 | ARIN | Valid |
| 2001:56b:f00::/40 | ARIN | 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.