Canvas System Status

Some users may be receiving a 500 error messages or general Canvas slowness when attempting to access Canvas if they are hosted in our PDX region.

Dec 14, 04:32 MST
Identified - We are receiving some additional reports about page errors. We are currently investigating this issue.

Dec 14, 04:19 MST
Monitoring - A fix has been implemented and we are monitoring the results.

Dec 14, 04:13 MST
Identified - The issue has been identified and a fix is being implemented.

Dec 14, 04:06 MST
Investigating - We are currently investigating this issue.

Amazon Web Services (AWS) is currently experiencing an outage that is affecting some Canvas users hosted in the IAD (North American) region.

Dec 7, 10:23 MST
Update - We are continuing to work on a fix for this issue.

Dec 7, 10:03 MST
Update - We are actively working towards recovery.

Dec 7, 09:47 MST
Update - We are actively working towards recovery.

Dec 7, 09:37 MST
Update - We are continuing to work on a fix for this issue.

Dec 7, 09:32 MST
Update - We are continuing to work on a fix for this issue.

Dec 7, 09:30 MST
Update - We are actively working towards recovery.

Dec 7, 09:17 MST
Identified - The issue has been identified.

Dec 7, 09:06 MST
Update - We are continuing to investigate this issue.

Dec 7, 09:06 MST
Investigating - We are currently investigating this issue.

Customers hosted in the IAD region were seeing slow requests.

Nov 22, 14:22 MST
Resolved - Between 2:22 PM and 2:32 PM MST users may have encountered slow load times and possible page errors. Our DevOps team was able to correct this and load times have returned to normal.

Page errors when accessing Canvas.

Oct 30, 18:13 MDT
Resolved - This incident has been resolved.

Oct 30, 18:03 MDT
Monitoring - A fix has been implemented and we are monitoring the results.

Oct 30, 17:47 MDT
Investigating - Our team is investigating an issue that is causing a small number of users to experience request timeout errors when accessing Canvas.

Canvas Page Errors

Oct 25, 08:19 MDT
Resolved - This incident has been resolved.

Oct 25, 08:14 MDT
Monitoring - A fix has been implemented and we are monitoring the results.

Oct 25, 07:58 MDT
Identified - The issue has been identified and a fix is being implemented.

Oct 25, 07:53 MDT
Update - We are continuing to investigate this issue.

Oct 25, 07:52 MDT
Investigating - We are currently investigating page errors that some users hosted in the PDX region may receive when accessing their Canvas instance.

Canvas Page Errors

Oct 24, 22:27 MDT
Monitoring - A fix has been implemented and we are monitoring the results.

Oct 24, 22:26 MDT
Identified - Our team has identified an issue that is causing a small amount of users hosted in our Singapore region to encounter page errors or slow load times when accessing Canvas. They are actively working to correct this issue.

Some users may be receiving a 500 error messages or general Canvas slowness when attempting to access Canvas if they are hosted in our IAD (North American) region.

Oct 21, 11:27 MDT
Resolved - This incident has been resolved.

Oct 21, 11:18 MDT
Investigating - We are currently investigating this issue.

Some users may be receiving a 500 errors when access Canvas.

Oct 21, 07:22 MDT
Identified - The issue has been identified and a fix is being implemented.

Live Events were delayed or may not have posted for some users

Oct 18, 08:00 MDT
Resolved - Live Events using the http method were impacted between 8am-8pm MT. Originality scores sent through the Plagiarism Platform may have been slow to post to Canvas, or may not have posted at all. Our team has since corrected the issue and are investigating the cause, as well as how to best re-run any of these that may have not processed during the affected time period.

Some users are experiencing long load times or error messages when accessing New Quizzes.

Oct 14, 07:09 MDT
Resolved - This incident has been resolved.

Oct 14, 07:04 MDT
Monitoring - A fix has been implemented and we are monitoring the results.

Oct 14, 07:01 MDT
Investigating - We are currently investigating this issue.

You are here

Pages