Amplify incident

Admin Reports Accessibility Issue

Notice Resolved View vendor source →

Amplify experienced a notice incident on March 19, 2025 affecting Amplify CKLA and Amplify ELA and 1 more component, lasting 21h 19m. The incident has been resolved; the full update timeline is below.

Started
Mar 19, 2025, 04:39 PM UTC
Resolved
Mar 20, 2025, 01:58 PM UTC
Duration
21h 19m
Detected by Pingoru
Mar 19, 2025, 04:39 PM UTC

Affected components

Amplify CKLAAmplify ELABoost ReadingAmplify ScienceAmplify Math

Update timeline

  1. identified Mar 19, 2025, 04:39 PM UTC

    Some users may be unable to access Admin Reports and Boost Usage Dashboards due to a performance issue from our third party data warehouse provider. Per communication from our data warehouse provider: "We've identified the source of the issue, and we're developing and implementing a fix to restore service." We understand this frustration a disruption like this can cause, and we greatly appreciate your patience while our data warehouse provider works towards resolving these performance issues.

  2. identified Mar 19, 2025, 05:36 PM UTC

    We are continuing to work on a fix for this issue.

  3. identified Mar 19, 2025, 08:41 PM UTC

    Admin Report services are now back up and running in production. Users should be seeing relief now! If you are still experiencing an error when attempting to open Admin Reports, please report this issue to our Support teams via chat, email ([email protected]), or phone (800-823-1969). Please note: While the Admin Report services have been restored, some users may experience a delay in data. We are working on restoring this data and will continue updating this page until the issue has been fully resolved. Thank you again for your patience!

  4. monitoring Mar 20, 2025, 12:10 AM UTC

    Admin Reports and Boost Usage functionality has returned to normal and all data is up-to-date. Our Data and Engineering teams will continue to monitor data pipelines throughout the nightly runs.

  5. resolved Mar 20, 2025, 01:58 PM UTC

    This incident has been resolved.