Is Learnosity down?

As of 17:50 UTC, we are experiencing issues affecting Item Pools in all regions. 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 are investigating degraded performance when creating and editing Item Pools. We're also investigating an as-of-yet unconfirmed tangential issue possibly affecting creation and editing of Local Device Assessment packages. All other APIs in the authoring, assessment, and analytics stacks are functioning 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 are continuing to investigate degraded performance when creating or editing Item Pools orx Local Device Assessment packages. All other APIs in the authoring, assessment, and analytics stacks are functioning 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:30 UTC, Item Pool and Local Device Assessment creation has seen normal throughput for approximately 30 minutes. We will now enter an additional period of monitoring to ensure stability. 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:10 UTC, we have seen no further issues with Item Pool or Local Device Assessment package creation or update. We're resolving this incident and will continue to investigate the root cause of the degraded performance. 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 13:20 UTC, we started seeing scoring delays with our Enhanced Math Scoring service in the US-East-1 region. No data loss has been observed and all sessions have ultimately been scored. As a knock-on effect, the Data API Scoring endpoint is experiencing intermittent availability issues. No authoring or assessment delivery has been 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 15:00 UTC, we are still investigating the short-lived degraded performance of our Enhanced Math Scoring service, but have not seen significant errors or delays for more than an hour. The backlog of sessions awaiting scoring cleared quickly, and submissions continue to be scored normally. All other APIs remain unaffected. 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:45 UTC, mitigation measures have successfully kept the submission queue clear, and scoring has continued to operate normally. Submissions received during the period of degraded performance were captured, and no data was lost. All other APIs remain operational. We are continuing to investigate the root cause and will share an incident postmortem once our investigation is complete. In the meantime, we are entering an additional monitoring period to confirm continued stability before closing the incident.

As of 18:00 UTC, after a long period of additional monitoring without further issue, we are resolved this incident affecting Enhanced Math Scoring in US-East-1. 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 20 October 2026, Learnosity experienced scoring delays and intermittent request failures affecting Enhanced Math scoring in US-East-1. Customer impact began at approximately 13:06 UTC and ended at 13:47 UTC, lasting approximately 41 minutes. Affected scoring requests experienced longer than normal processing times, and some direct requests to the Data API scoring endpoint returned errors. For sessions saved through the Items API, affected scoring requests were queued and retried, resulting in delayed score availability rather than scoring failures. Assessments without math questions and services in other regions were unaffected. ## Investigation Our investigation identified a specific pattern of scoring requests that resulted in unexpectedly high processing times. This reduced the capacity available to process other scoring requests, causing delays and intermittent timeouts. The issue was associated with how certain scoring inputs were processed, rather than an unexpected increase in overall request volume. ## Resolution Scoring performance returned to normal by 13:47 UTC. At 15:12 UTC, Learnosity engineers implemented additional traffic isolation to prevent the affected scoring workload from impacting scoring operations for other customers. ## Prevention Learnosity has implemented changes to reduce unnecessary resource consumption and improve the recovery of affected scoring requests. Further improvements are underway to strengthen scoring request validation, improve processing safeguards and prevent individual scoring workloads from affecting the wider service. Additional isolation measures will remain in place while these improvements are completed and their effectiveness is verified.

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.

### Affected Systems and Regions On 8 October 2026, Learnosity experienced intermittent API errors only affecting requests that specified the retired API version `v2024.1.LTS` in the US Virginia, US Oregon, Australia, and Ireland regions. This version reached End of Life in March of 2026 After sunset, affected requests should have been automatically redirected to the latest long-term-support \(LTS\) release. Instead, some returned server errors. Customer impact began at approximately 00:14 UTC and continued intermittently until 15:08 UTC, varying by region. Only a portion of production servers were affected, so not all requests specifying this version failed. ### Investigation The incident was caused by an incomplete configuration update during the October 8 platform release, which retired `v2024.1.LTS`. Although the updated version mapping was correct in staging, a required release step to update production configuration servers was not completed. Consequently, some production servers retained an outdated mapping that directed requests to API versions that had been removed. Our existing release validation verified that deployed API versions were available but did not verify that retired versions redirected correctly in each production region. As a result, the configuration inconsistency was not detected during deployment. ### Resolution Learnosity engineers identified the outdated version mapping and restored service by regenerating configuration on affected production servers, region by region. By 15:08 UTC, verification confirmed that the correct version mapping was in place across all checked regions and requests were being handled correctly. The incident was formally resolved at 15:48 UTC. ### Prevention Learnosity is implementing improvements to its release and validation procedures to prevent similar configuration inconsistencies. These include automated verification that all production configuration servers are running the correct release version, integrating configuration updates directly into the deployment process so they cannot be inadvertently skipped, and expanding release validation to confirm that retired API versions redirect correctly in every region. We are also improving alerting to detect this specific class of error earlier and developing tooling to identify and refresh servers retaining outdated configurations. These measures are intended to ensure consistent deployments across regions, detect configuration discrepancies before they affect customers, and accelerate recovery should similar issues occur.

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.

## **Affected Systems and Regions** On 2 October 2026, Learnosity experienced intermittent scoring errors and timeouts affecting math question types in US-East-1. Customer impact began at approximately 16:34 UTC and ended at 18:47 UTC, lasting approximately 2 hours and 13 minutes. Affected requests could experience delays of up to 40 seconds before failing. Other regions were unaffected. ## **Investigation** The incident occurred when demand on the math scoring service exceeded available capacity. Although capacity and scaling improvements had been introduced following an earlier incident, the service encountered an additional limit in its network configuration that prevented further instances from being provisioned. The impact was compounded by slow calculations that occupied instances longer than intended because calculation time limits were not reliably enforced under heavy load. Together, these conditions prevented the service from scaling sufficiently to handle demand. ## **Resolution** Learnosity engineers restored service by moving the scoring service to a network configuration with additional scaling capacity and increasing the compute resources allocated to each instance. These changes allowed the service to recover, with scoring errors clearing by 18:47 UTC. ## **Prevention** Learnosity has updated the calculation time limit enforcement mechanism to reliably terminate slow calculations under heavy load. Health checks have also been separated from calculation processing to prevent unnecessary instance replacement. The service now operates with additional compute and network capacity. Further architectural improvements are underway to prevent network capacity from limiting future scaling, and we are evaluating shorter calculation time limits to reduce the impact of unusually slow calculations.

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.

## **Affected Systems and Regions** On 11 September 2026, Learnosity experienced intermittent scoring errors and timeouts affecting math question types in US-East-1. Customer impact began at approximately 17:00 UTC and ended at 21:45 UTC, lasting approximately 4 hours and 45 minutes. Other question types continued to score normally, and other regions were unaffected. Most failed requests succeeded when retried. ## **Investigation** The incident was caused by insufficient capacity in the math scoring service following an increase in demand over the preceding weeks. The service reached its configured maximum number of instances and could not scale further to accommodate the load. This was compounded by limited compute resources per instance and slow calculations that occupied instances longer than intended. Under heavy load, the calculation time limit was not reliably enforced, and busy instances could fail health checks and be replaced, further reducing available capacity. ## **Resolution** Learnosity engineers restored service by increasing the number of running instances and raising the maximum instance limit. Normal scoring operations resumed by 21:45 UTC, and all remaining queued scoring requests were processed by 23:17 UTC. On 14 September, additional configuration changes were deployed to increase compute resources, improve automatic scaling, and reduce unnecessary instance replacement. ## **Prevention** Learnosity has increased scoring capacity, raised instance limits, and improved automatic scaling based on processor utilization. Health checks have been separated from calculation processing to prevent busy instances from being incorrectly identified as unhealthy. We have also improved calculation time limit enforcement and expanded monitoring and alerting for resource utilization, response times, and scoring errors. Further work is underway to strengthen network scaling capacity and evaluate shorter calculation time limits.