To view uptime history for your instance of Canvas, click here.

Update - Canvas Data 2 and Beta should now be available for all customers. Canvas Test remains under maintenance.

As more information becomes available we will update here.

May 04, 2026 - 11:11 MDT
Update - Canvas Data 2 should now be available for all customers.

Canvas Beta & Test remain under maintenance.

As more information becomes available we will update here.

May 03, 2026 - 19:24 MDT
Update - Canvas Data 2 should now be available for all customers.

Canvas Beta & Test remain under maintenance.

As more information becomes available we will update here.

May 03, 2026 - 16:35 MDT
Update - Our team reissued certain application keys as a precautionary step, which requires end users to re-authorize access to those tools. Reissued application keys contain a timestamp in the name and will be visible to users during re-authorization. These are valid Instructure created keys and users should continue the authorization process. Please read the blog Application Key Timestamp Notice for more information. (https://community.instructure.com/en/discussion/665983/application-key-timestamp-notice)

We are continuing to review the issue and will provide updates here as more information becomes available.

Thank you for your patience.

May 02, 2026 - 12:53 MDT
Update - Our investigation continues and Canvas Data 2 and Canvas Beta & Test remain under maintenance.
As more information becomes available we will update here.

May 01, 2026 - 11:47 MDT
Update - Our investigation continues and Canvas Data 2 and Canvas Beta remain under maintenance.
As more information becomes available we will update here.

May 01, 2026 - 08:09 MDT
Investigating - Some customers may be experiencing limited disruption to tools relying on API keys. Our team is actively investigating and has taken precautionary steps to help maintain service stability while we work to restore full functionality.

We are continuing to review the issue and will provide updates here as more information becomes available.

Thank you for your patience.

Apr 30, 2026 - 17:06 MDT
Update - We are providing an update on the security incident we advised you of yesterday. While our investigation continues alongside our outside forensics experts, at this stage we believe the incident has been contained.

Here are the steps we have taken since we became aware of the incident. We have:
- Revoked privileged credentials and access tokens associated with affected systems
- Deployed patches to enhance system security
- Out of an abundance of caution, we rotated certain keys, even though there is no evidence they were misused
- Implemented increased monitoring across all platforms

While we continue actively investigating, thus far, indications are that the information involved consists of certain identifying information of users at affected institutions, such as names, email addresses, and student ID numbers, as well as messages among users. At this time, we have found no evidence that passwords, dates of birth, government identifiers, or financial information were involved. If that changes, we will notify any impacted institutions.

Thank you for your patience as we work to resolve this matter. We sincerely regret any inconvenience or concern this may cause. We will continue to keep you apprised as our investigation progresses. For up-to-date information on specific systems, please continue to visit our status page.

Steve Proud
Chief Information Security Officer

May 02, 2026 - 12:46 MDT
Investigating - Instructure recently experienced a cybersecurity incident perpetrated by a criminal threat actor. We are actively investigating this incident with the help of outside forensics experts. We are working quickly to understand the extent of the incident and actively taking steps to minimize its impact. Maintaining your trust is our highest priority, and we are committed to transparency throughout this process. We will provide new information as it is confirmed.

Steve Proud
Chief Information Security Officer

May 01, 2026 - 16:30 MDT
Instructure Operational
Canvas Operational
Canvas LMS Operational
Canvas Catalog Operational
Canvas Commons Operational
Canvas Credentials Operational
Canvas Data 2 Operational
Canvas Mobile Operational
Canvas Studio Operational
Canvas Portfolio Operational
Student ePortfolios Operational
Student Pathways Operational
SIS Platform Operational
90 days ago
100.0 % uptime
Today
SIStemic Operational
90 days ago
100.0 % uptime
Today
DataSync Operational
90 days ago
100.0 % uptime
Today
Elevate Operational
Elevate Data Quality Operational
Elevate Data Sync Operational
Elevate Standards Alignment Operational
Impact Operational
Learn Platform Operational
Mastery Operational
Mastery Connect Operational
Item Bank Operational
Online Testing Operational
Support Tools Operational
Support: Phones/Chat Operational
Support: Webform/email Operational
AWS Region Operational
ca-central-1 Operational
eu-central-1 Operational
eu-west-1 Operational
us-east-1 Operational
us-west-2 Operational
ap-southeast-1 Operational
ap-southeast-2 Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
May 5, 2026

No incidents reported today.

May 4, 2026
Resolved - This incident has been resolved.
May 4, 21:01 MDT
Investigating - We are currently investigating this issue.
May 4, 20:01 MDT
Resolved - This incident has been resolved. If you are still seeing page errors, please clear your browser cookies and cache.
May 4, 18:09 MDT
Investigating - We are currently investigating this issue.
May 4, 17:33 MDT
Resolved - This incident has been resolved.
May 4, 17:41 MDT
Monitoring - A fix has been implemented and we are monitoring the results.
May 4, 17:36 MDT
Investigating - We are currently investigating this issue.
May 4, 16:54 MDT
Resolved - This incident has been resolved.
May 4, 09:35 MDT
Monitoring - A fix has been implemented and we are monitoring the results.
May 4, 07:57 MDT
Investigating - We are currently investigating this issue.
May 4, 07:45 MDT
May 3, 2026
May 2, 2026

Unresolved incident: Confirmed Security Incident.

May 1, 2026
Apr 30, 2026
Apr 29, 2026

No incidents reported.

Apr 28, 2026
Resolved - This incident has been resolved. Our engineers are in the process of restoring the weblog data that was missed during the incident, but new weblogs are updating normally again.
Apr 28, 21:26 MDT
Identified - The issue has been identified and a fix is being implemented.
Apr 28, 20:54 MDT
Investigating - We are currently investigating this issue.
Apr 28, 20:14 MDT
Apr 27, 2026

No incidents reported.

Apr 26, 2026

No incidents reported.

Apr 25, 2026

No incidents reported.

Apr 24, 2026
Resolved - This incident has been resolved.
Apr 24, 07:26 MDT
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 24, 03:25 MDT
Identified - The issue has been identified and a fix is being implemented.
Apr 24, 03:03 MDT
Investigating - We are currently investigating this issue.
Apr 24, 01:33 MDT
Apr 23, 2026
Resolved - This incident has been resolved.
Apr 23, 00:17 MDT
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 23, 00:10 MDT
Update - We are continuing to work on a fix for this issue.
Apr 23, 00:07 MDT
Update - We are continuing to work on a fix for this issue.
Apr 22, 23:54 MDT
Update - We are continuing to work on a fix for this issue.
Apr 22, 23:41 MDT
Update - We are continuing to work on a fix for this issue.
Apr 22, 23:28 MDT
Update - We are continuing to work on a fix for this issue.
Apr 22, 23:15 MDT
Update - We are continuing to work on a fix for this issue.
Apr 22, 23:02 MDT
Update - We are continuing to work on a fix for this issue.
Apr 22, 22:52 MDT
Identified - The issue has been identified and a fix is being implemented.
Apr 22, 22:39 MDT
Investigating - We are currently investigating this issue.
Apr 22, 22:22 MDT
Apr 22, 2026
Resolved - This incident has been resolved.
Apr 22, 21:13 MDT
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 22, 21:07 MDT
Update - We are continuing to investigate this issue.
Apr 22, 20:59 MDT
Update - We are continuing to investigate this issue.
Apr 22, 20:32 MDT
Update - We are continuing to investigate this issue.
Apr 22, 19:39 MDT
Update - We are continuing to investigate this issue.
Apr 22, 19:15 MDT
Update - We are continuing to investigate this issue.
Apr 22, 18:48 MDT
Update - We are continuing to investigate this issue.
Apr 22, 18:14 MDT
Update - We are continuing to investigate this issue.
Apr 22, 17:45 MDT
Investigating - We are currently investigating this issue.
Apr 22, 17:22 MDT
Resolved - This incident has been resolved.
Apr 22, 08:46 MDT
Identified - The issue has been identified and a fix is being implemented.
Apr 22, 07:23 MDT
Investigating - We are currently investigating this issue.
Apr 22, 07:11 MDT
Apr 21, 2026
Resolved - This incident has been resolved. Users who are seeing these errors may see resolution by clearing cache and cookies.
Apr 21, 19:26 MDT
Monitoring - A fix has been implemented and we are monitoring the results. If users are still seeing these errors, clearing browser cache and cookies may resolve the behavior.
Apr 21, 19:22 MDT
Update - We are continuing to investigate this issue.
Apr 21, 19:05 MDT
Update - If you see these errors in a regular browser, clearing cache and cookies may resolve them.
Apr 21, 19:04 MDT
Investigating - We are currently investigating this issue, and have seen increased reports from users accessing via Respondus.
Apr 21, 17:42 MDT
Resolved - This incident has been resolved.
Apr 21, 11:33 MDT
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 21, 11:26 MDT
Update - We are continuing to work on a fix for this issue.
Apr 21, 11:12 MDT
Identified - The issue has been identified and a fix is being implemented.
Apr 21, 11:11 MDT