Minor incident

Learnosity: Issue affecting LTS Remapping of Sunset version v2024.1.LTS

Affected: LTS Remapping of Sunset Versions

Current status of Learnosity: Operational — live Learnosity status

Timeline

1. Oct 8, 2026, 13:40 UTC
   investigating
   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.
2. Oct 8, 2026, 13:47 UTC
   investigating
   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.
3. Oct 8, 2026, 14:20 UTC
   investigating
   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.
4. Oct 8, 2026, 15:15 UTC
   resolved
   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.
5. Oct 28, 2026, 22:14 UTC
   postmortem
   ### 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.

Updates as published by Learnosity (original).