Amplify incident

Login and Navigation Service Disruption

Critical Resolved View vendor source →

Amplify experienced a critical incident on January 12, 2026 affecting Amplify CKLA and Amplify ELA and 1 more component, lasting 22d 4h. The incident has been resolved; the full update timeline is below.

Started
Jan 12, 2026, 07:20 PM UTC
Resolved
Feb 03, 2026, 11:50 PM UTC
Duration
22d 4h
Detected by Pingoru
Jan 12, 2026, 07:20 PM UTC

Affected components

Amplify CKLAAmplify ELABoost ReadingAmplify ScienceAmplify MathDesmos ClassroommCLASS AssessmentmCLASS InterventionDesmos Classroom

Update timeline

  1. investigating Jan 12, 2026, 07:20 PM UTC

    We are aware of and investigating an issue disrupting login services and navigation across all products right now. Our Engineering team is working to identify the root cause of and implement a fix for this issue as we speak. We apologize for this inconvenience and will update this page as efforts towards resolution progress. Thank you for your patience!

  2. investigating Jan 12, 2026, 07:25 PM UTC

    Login issues have recovered but users are still experiencing general slowness in the system. We are continuing to narrow down the root cause.

  3. investigating Jan 12, 2026, 07:44 PM UTC

    Login services and navigational load times have recovered. Administrator Reports pages may still be experiencing long load times right now.

  4. monitoring Jan 12, 2026, 08:10 PM UTC

    All services have recovered. We are continuing to monitor. Thank you again for your patience!

  5. investigating Jan 13, 2026, 03:44 PM UTC

    We are aware of and investigating an issue disrupting login services and navigation across all products right now. Our Engineering team is working to identify the root cause of and implement a fix for this issue as we speak. Thank you for your patience!

  6. monitoring Jan 14, 2026, 04:59 PM UTC

    A fix has been implemented and we are monitoring the results.

  7. monitoring Jan 21, 2026, 08:48 PM UTC

    This issue was officially resolved the evening of Sunday 1/18. Thank you for your patience!

  8. resolved Feb 03, 2026, 11:50 PM UTC

    This incident has been resolved.