Learnosity incident

Issue affecting availability of recent session data for a minority of customers in the US-East-1 region.

Notice Resolved View vendor source →

Learnosity experienced a notice incident on January 12, 2026 affecting Loading and rendering of reports and Availability of session information and 1 more component, lasting 2h 4m. The incident has been resolved; the full update timeline is below.

Started
Jan 12, 2026, 05:06 PM UTC
Resolved
Jan 12, 2026, 07:10 PM UTC
Duration
2h 4m
Detected by Pingoru
Jan 12, 2026, 05:06 PM UTC

Affected components

Loading and rendering of reportsAvailability of session informationUpdating session response scoresFirehose

Update timeline

  1. investigating Jan 12, 2026, 05:06 PM UTC

    As of 4:30 UTC, we are currently investigating an issue that may result in temporary session unavailability for a small number of US-only customers. We can confirm that no session data has been lost, and we are working to restore the affected sessions as quickly as possible. Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

  2. identified Jan 12, 2026, 05:52 PM UTC

    As of 5:30 UTC, we've identified and corrected a load balancing configuration affecting database reads and writes for a very small number of US-only customers with consumers in the US-East-1 region. - All new sessions will behave as expected. - Read requests seeking data on sessions created prior to 23:00 UTC yesterday will also now behave correctly. - We are working on restoring sessions recently affected While all APIs continue to function normally, this update identifies service areas that may temporarily have limited access to recently saved or submitted sessions. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

  3. resolved Jan 12, 2026, 07:10 PM UTC

    As of 7:00 UTC, we've concluded our monitoring and confirmed that all new requests are behaving as expected. We are closing this record and will continue to work with affected customers directly to confirm that all recent sessions are accessible. Please reach out if you have any questions or concerns.