Resolved -
This incident has been resolved.
May 8, 12:46 EDT
Update -
We are continuing to monitor for any further issues.
May 8, 12:09 EDT
Monitoring -
A fix has been implemented, and Class services are now operating normally. We are continuing to monitor for any further issues.
May 8, 11:31 EDT
Update -
We are continuing to work closely with AWS to resolve the issue. We will provide more information when it is available. More details on the issue can be found on the AWS Health Dashboard: https://health.aws.amazon.com/health/status.
May 8, 10:50 EDT
Update -
We are continuing to work closely with AWS to resolve the issue. We will provide more information when it is available. More details on the issue can be found on the AWS Health Dashboard: https://health.aws.amazon.com/health/status.
May 8, 10:17 EDT
Identified -
We have identified that the service disruption is related to an AWS incident affecting multiple services in the N. Virginia region. Our engineering team is working with AWS to mitigate the issue and restore full service as quickly as possible.
We will provide more information when it is available. More details on the issue can be found on the AWS Health Dashboard: https://health.aws.amazon.com/health/status.
May 8, 09:54 EDT
Investigating -
At approximately 9:05 AM EDT on Friday, May 8, 2026, a subset of users in a single pod in the Class hosted environment started experiencing issues joining classes. The Class Engineering team is engaged and actively investigating.
May 8, 09:37 EDT