Is Learnosity down?

As of 13:00 UTC, we are experiencing issues remapping sunset API versions v2024.1.LTS to the latest LTS releases in all regions. This only affects a very small number of customers who are still pinned to v2024.1.LTS, which reached End of Life in March 2026. No other API versions are affected. Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

As of 13:40> UTC, we are redirecting v2024.1.LTS versions and APIs are becoming accessible as caches update. 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.

As of 14:00 UTC, v2024.1.LTS is successfully remapping to the latest LTS version in AMER regions, including US-East-1 (VA) and US-West-2 (OR). All APIs should be accessible in these regions. We are currently remapping in EMEA and APAC regions. Direct access to active API versions remains operational. This issue is now only affecting version remapping for a microset of customers in the EMEA and APAC regions pinned to the sunsetted v2024.1.LTS API version, which reached EOL in March 2026. 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.

As of 15:00 UTC, v2024.1.LTS is successfully remapping in all regions. Using this EOL/sunset version string should access all APIs. Learnosity Support and Systems Engineering teams will follow up with a post mortem once we have completed root cause analysis and finalized any next steps or preventative measures required. Please reach out if you have any questions or concerns.

As of 16:45 UTC, we began experiencing very low numbers of scoring delays with our Enhanced Math Scoring service in the US-East-1 region. All sessions were scored, and no data loss occurred. No other APIs are affected. We're investigating ongoing delays limited to this service. Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

As of 18:30 UTC, we have identified a scaling issue for the Enhanced Math Scoring service and are working to resolve the problem. All sessions continue to be captured without data loss and all other API are operating normally. 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.

As of 19:00 UTC, we have not seen delays in the Enhanced Math Scoring service for some time and will now enter a monitoring phase. We will continue to monitor for 30 minutes before resolving the issue. 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.

As of 19:45 UTC, we have resolved the issue affecting Enhanced Math Scoring in the US-East-1 region. All APIs and services are functioning normally. Learnosity Support and Systems Engineering teams will follow up with a post mortem once we have completed root cause analysis and finalized any next steps or preventative measures required. Please reach out if you have any questions or concerns.

As of 17:00 UTC, we are currently investigating minor intermittent issues with scoring in the US-East-1 region. Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

As of 18:30 UTC, all APIs remain operational and we are monitoring scoring efficiency. 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.

As of 19:30 UTC, we've confirmed this to be a sporadic problem with scoring of three enhanced math question types only. These scoring attempts succeed on retry and no other APIs are affected. 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.

As of 20:45 UTC, we've improved the handling of initial EMS scoring requests and retries and will now enter a 60-minute monitoring phase. All APIs continue to function normally. 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.

As of 21:45 UTC, Enhanced Math Scoring question type responses are scoring normally in the US-East-1 region, all APIs are functioning normally, and we are closing this incident. Learnosity Support and Systems Engineering teams will follow up with a post mortem once we have completed root cause analysis and finalized any next steps or preventative measures required. Please reach out if you have any questions or concerns.

We are aware of an ongoing AWS issue affecting the US-West-2 (OR) region, which may cause intermittent connectivity issues when accessing the Learnosity Authoring environment. We are actively monitoring the situation and will provide updates as they become available. At this time, impact to Learnosity customers is brief and intermittent and limited to authoring. Assessments, and other APIs, are behaving normally. Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

As of 11:02 UTC, Learnosity started seeing monitor alerts of short-lived, intermittent timeouts when accessing the Learnosity author site. No other functionality was affected, and Learnosity alerts ceased at 11:11 UTC. At 11:40 UTC, AWS reported degraded service in US-West-2 (OR). At 11:56 UTC, AWS reported their systems were recovering. Learnosity Support and Systems Engineering teams are continuing to actively monitor the issue, and will follow on with an update and resolution as soon as possible.

At 12:30 UTC, AWS reported that they identified and corrected the issue, and that recovery is continuing. Learnosity Support and Systems Engineering teams will monitor the issue for a further 30 minutes, and will follow on with an update and resolution as soon as possible.

As of 13:00 UTC, we are calling this issue resolved. AWS systems are recovering and Learnosity authoring has been unaffected for 50 minutes. Learnosity Support and Systems Engineering teams will follow up with a post mortem once we have completed root cause analysis and finalized any next steps or preventative measures required. Please reach out if you have any questions or concerns.

### Affected Systems and Regions On 2026-07-24, Learnosity experienced brief intermittent timeouts affecting access to the Learnosity author site due to [a networking incident in the AWS US-West-2 \(OR\) region](https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-west-2::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_83A36_24C89B493A6). Learnosity customer impact began at approximately 11:02 UTC and ended at 11:11 UTC. AWS subsequently completed remediation and formally closed their regional incident at 12:12 UTC. The total duration of possible impact to Learnosity customers was approximately 9 minutes. ### Investigation Learnosity received an internal alert at 11:02 UTC that service in the OR region was affected and immediately began an investigation. Initial investigation found no evidence of a Learnosity service degradation. Further investigation identified intermittent timeouts affecting access to the Learnosity author site. Learnosity confirmed with AWS that an issue impacting their network infrastructure in the region had been identified and remediation had begun. ### Resolution Intermittent timeouts affecting the Learnosity author site ceased by 11:11 UTC, and AWS effectively resolved the issue by 11:15 UTC. AWS reported a brief reconvergence event that was resolved by 11:59 UTC, and officially closed the incident at 12:12 UTC. ### Prevention No Learnosity systems contributed to this incident. Internal monitoring and alerting behaved as expected.