Canvas System Status

Oct 25, 15:38 MDT
Monitoring - Our DevOps team was able to deploy a fix, and it appears that users are experiencing normal load times. We'll continue to monitor the situation and provide and update in a few minutes.

Oct 25, 15:30 MDT
Identified - Our DevOps team has identified the cause of the issue, and are working towards a solution. We apologize for any inconvenience caused.

Oct 25, 15:17 MDT
Update - Our DevOps team is continuing to investigate the cause of this behavior. We apologize for any inconvenience caused.

Oct 25, 14:47 MDT
Investigating - Some Canvas users are seeing long load times while trying to access Canvas. We're currently investigating these issues and will post an update shortly. We sincerely apologize for the inconvenience and appreciate your patience.

Oct 25, 06:13 MDT
Resolved - Our engineers have identified the issue and resolved the issue. Access to Canvas is working as expected.

Oct 25, 06:07 MDT
Identified - Our engineers have identified what caused the issue. They are currently working on a fix, we will continue to update as more information becomes available.

Oct 25, 05:49 MDT
Investigating - Some Canvas users are receiving a page error while trying to access Canvas. We're currently investigating these issues and will post an update shortly. We sincerely apologize for the inconvenience and appreciate your patience.

Oct 24, 17:38 MDT
Identified - Some users in Canvas are seeing various page errors while accessing Canvas. Our engineers have identified the issue and are working towards a resolution. We will post any updates as soon as possible.

Oct 24, 17:18 MDT
Investigating - Some Canvas users are receiving a page error while trying to access certain functions of Canvas. We're currently investigating these issues and will post an update shortly. We sincerely apologize for the inconvenience and appreciate your patience.

Oct 17, 12:21 MDT
Resolved - Between 11:38 AM and 11:45 AM MDT a small number of US-based users were unable to access Canvas. Our DevOps team was able to implement a solution to this behavior. Access should now be restored, we apologize for any inconvenience this may have caused.