bgpreport

Network · data from 2026-11-12

AS62969 ABCCOMM - TELUS Communications Inc.

Registry name: ABCCOMM - TELUS Communications Inc., CA · not in PeeringDB

9IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
10No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS62969, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS62969, 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.57.176.0/20 No ROA Other IRR onlyRADB 673 100% 67
23.163.192.0/24 No ROA Other IRR onlyRADB 671 100% 67
104.36.100.0/22 No ROA Other IRR onlyRADB 671 100% 67
172.83.68.0/22 No ROA Other IRR onlyRADB 671 100% 67
192.222.102.0/23 No ROA Other IRR onlyRADB 671 100% 67
198.55.228.0/22 No ROA Other IRR onlyRADB 671 100% 67
199.96.196.0/22 No ROA Other IRR onlyRADB 671 100% 67
204.239.167.0/24 No ROA Other IRR onlyRADB 671 100% 67
204.239.211.0/24 No ROA Other IRR onlyRADB 671 100% 67
2605:7e80::/32 No ROA Other IRR onlyRADB 634 100% 68

AS-SET

AS62969 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 20 are in fix.csv.

  • ROA: none10
  • Route object: RIR10
ChangePrefix or setDetailFull-table peers
ROA: none216.57.176.0/20No ROA covers it. Add a ROA for AS62969, maxLength 20.673 of 673
Route object: RIR216.57.176.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none23.163.192.0/24No ROA covers it. Add a ROA for AS62969, maxLength 24.671 of 673
Route object: RIR23.163.192.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none104.36.100.0/22No ROA covers it. Add a ROA for AS62969, maxLength 22.671 of 673
Route object: RIR104.36.100.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none172.83.68.0/22No ROA covers it. Add a ROA for AS62969, maxLength 22.671 of 673
Route object: RIR172.83.68.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none192.222.102.0/23No ROA covers it. Add a ROA for AS62969, maxLength 23.671 of 673
Route object: RIR192.222.102.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none198.55.228.0/22No ROA covers it. Add a ROA for AS62969, maxLength 22.671 of 673
Route object: RIR198.55.228.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.96.196.0/22No ROA covers it. Add a ROA for AS62969, maxLength 22.671 of 673
Route object: RIR199.96.196.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none204.239.167.0/24No ROA covers it. Add a ROA for AS62969, maxLength 24.671 of 673
Route object: RIR204.239.167.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none204.239.211.0/24No ROA covers it. Add a ROA for AS62969, maxLength 24.671 of 673
Route object: RIR204.239.211.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2605:7e80::/32No ROA covers it. Add a ROA for AS62969, maxLength 32.634 of 636
Route object: RIR2605:7e80::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

Every route object with origin AS62969 is announced.

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.