Learnosity Outage History

Started Oct 20, 2026, 02:16 PM UTC· resolved Oct 20, 2026, 06:17 PM UTC

1. investigating Oct 20, 2026, 02:16 PM UTC

   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.

2. investigating Oct 20, 2026, 03:04 PM UTC

   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.

3. monitoring Oct 20, 2026, 03:51 PM UTC

   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.

4. resolved Oct 20, 2026, 06:17 PM UTC

   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.

Read the full incident report →

Started Oct 08, 2026, 01:40 PM UTC· resolved Oct 08, 2026, 03:15 PM UTC

1. investigating Oct 08, 2026, 01:40 PM UTC

   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. investigating Oct 08, 2026, 01:47 PM UTC

   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. investigating Oct 08, 2026, 02:20 PM UTC

   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. resolved Oct 08, 2026, 03:15 PM UTC

   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.

Read the full incident report →

Started Oct 02, 2026, 06:08 PM UTC· resolved Oct 02, 2026, 07:52 PM UTC

1. investigating Oct 02, 2026, 06:08 PM UTC

   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.

2. identified Oct 02, 2026, 06:30 PM UTC

   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.

3. monitoring Oct 02, 2026, 07:10 PM UTC

   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.

4. resolved Oct 02, 2026, 07:52 PM UTC

   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.

Read the full incident report →

Started Sep 11, 2026, 06:19 PM UTC· resolved Sep 11, 2026, 09:44 PM UTC

1. investigating Sep 11, 2026, 06:19 PM UTC

   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.

2. investigating Sep 11, 2026, 06:30 PM UTC

   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.

3. identified Sep 11, 2026, 07:42 PM UTC

   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.

4. monitoring Sep 11, 2026, 08:53 PM UTC

   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.

5. resolved Sep 11, 2026, 09:44 PM UTC

   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.

Read the full incident report →

Started Jul 24, 2026, 12:16 PM UTC· resolved Jul 24, 2026, 01:02 PM UTC

1. investigating Jul 24, 2026, 12:16 PM UTC

   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.

2. monitoring Jul 24, 2026, 12:28 PM UTC

   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.

3. monitoring Jul 24, 2026, 12:35 PM UTC

   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.

4. resolved Jul 24, 2026, 01:02 PM UTC

   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.

5. postmortem Jul 24, 2026, 01:03 PM UTC

   ### 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.

Read the full incident report →

Started Apr 17, 2026, 04:06 PM UTC· resolved Apr 17, 2026, 04:55 PM UTC

1. investigating Apr 17, 2026, 04:06 PM UTC

   As of 16:00 UTC, we are currently experiencing a slowdown in availability of newly submitted submitted session results in the us-east-1 region. There is no data loss, all saves and submissions are being queued as designed, and the assessments stack remains operational. Delays may currently be experienced using the Data API to fetch session results, and the Reports API to display results. Other workflows that rely on the synchronous use of Data API results may also be 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. identified Apr 17, 2026, 04:21 PM UTC

   As of 16:20 UTC, Learnosity has increased database performance and we are processing queued sessions rapidly. 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. monitoring Apr 17, 2026, 04:28 PM UTC

   As of 16:25 UTC, we have resolved the slowdown in processing session results and all sessions are being scored normally. We will continue to monitor for a further 30 minutes before closing this incident report. 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. resolved Apr 17, 2026, 05:58 PM UTC

   As of 16:55 UTC, we are have resolved the degraded performance issue affecting availability of session data 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.

5. postmortem May 04, 2026, 05:23 PM UTC

   ### Affected Systems and Regions On 2026-04-17, Learnosity experienced a service degradation impacting availability of newly submitted session results for a small subset of customers in US-East-1. The issue began at approximately 13:54 UTC and was resolved at 16:24 UTC. The total duration of customer impact was approximately 2.5 hours. ### Investigation Service degradation was detected following the accumulation of submitted sessions in the async scoring queue, This was caused by elevated CPU utilization when heavy load coincided with a background data migration task that had been running for several days on the affected EC2 instance. This reduced message processing throughput, leading to queueing of sessions. ### Resolution Learnosity CloudOps engineers responded by scaling session processing node EC2 instances, and corresponding database proxies, to maximum allowable capacity. The migration task was also stopped, which further reduced CPU pressure and allowed message processing throughput to recover. The session scoring backlog was fully cleared by 16:24 UTC. ### Prevention Learnosity is implementing the following measures to mitigate: * Pre-flight health checks and safeguards are being introduced to prevent migration tasks from running during busy periods of production usage. * Enhanced monitoring is being applied to detect backlog growth and database contention, and apply remedial action more quickly

Read the full incident report →

Started Apr 16, 2026, 02:08 PM UTC· resolved Apr 16, 2026, 03:23 PM UTC

1. investigating Apr 16, 2026, 02:08 PM UTC

   As of 13:30 UTC, we are currently experiencing slow downs affecting the Live Progress report in the us-east-1 region. Atypical use of eventbus may also be affected, such as custom reports/implementations. 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. resolved Apr 16, 2026, 03:23 PM UTC

   As of 14:30 UTC, the Live Progress report event degradation issue in the us-east-1 region has been resolved. Additional capacity processed the event load and these systems are operating normally. Brief additional latency during this scaling may have been introduced for users of Learnosity's premium Firehose feature, but we've seen no evidence that this affected customers. This, too, was resolved once scaling was complete. 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.

3. postmortem May 04, 2026, 02:39 PM UTC

   ### Affected Systems and Regions On 2026-04-16, Learnosity experienced a service degradation impacting the Live Progress report. The issue began at approximately 13:12 UTC and was resolved at 14:40 UTC. The total duration of customer impact was approximately 88 minutes. ### Investigation The issue was detected following elevated error rates on the load balancer serving the eventbus service. Investigation determined that an unhealthy condition within the EC2 instances led to elevated CPU utilization and memory pressure within the Auto Scaling Group, resulting in application instability and repeated service restarts. Inconsistent recovery caused traffic to concentrate on a subset of hosts, further elevating error rates. A secondary effect of the instability was increased request pressure on downstream dependencies. ### Resolution Service was restored by stabilizing the affected EC2 instance and restoring consistent application availability across the Auto Scaling Group. Load distribution normalized once all instances returned to a healthy state. ### Prevention Learnosity is implementing the following measures to mitigate: * Improve service startup and dependency handling to ensure consistent recovery behavior * Review resource thresholds to reduce the likelihood of similar instability * Enhance monitoring to detect and respond more quickly to similar conditions

Read the full incident report →

Started Feb 04, 2026, 06:34 PM UTC· resolved Feb 04, 2026, 07:15 PM UTC

1. identified Feb 04, 2026, 06:34 PM UTC

   As of 18:30 UTC, we are currently experiencing an issue affecting assessment delivery in VA (us-east-1). 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. monitoring Feb 04, 2026, 06:55 PM UTC

   As of 18:52 UTC, the Learnosity System Engineering team has put a fix in place. We will continue to monitor for some time to ensure a stable recovery, but all services are operational again. Learnosity Support and Systems Engineering teams will continue to actively monitor the issue, and will follow on with an update and resolution as soon as possible.

3. resolved Feb 04, 2026, 07:15 PM UTC

   As of 19:12 UTC, traffic has returned to normal and everything remains stable. We have resolved the incident affecting assessments in VA (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.

4. postmortem Feb 10, 2026, 05:08 PM UTC

   ### **Affected Systems and Regions** On 2026-02-04, Learnosity experienced an availability incident impacting Questions API access for customers in the AMER region. The issue began at approximately 18:02 UTC and was formally declared resolved at 18:51 UTC. The total duration of customer impact was approximately 49 minutes. ### **Investigation** The issue was first detected when the Items API attempted to initialize the dependent Questions API. The incident was traced to a misconfiguration within the content delivery network servicing the AMER region, causing a SSL certificate error.. During a certificate management task, the distribution responsible for serving [_questions.learnosity.com_](http://questions.learnosity.com) was configured with an SSL certificate that did not match the _\*.learnosity.com_ domain nomenclature. This caused browsers and client systems to reject connections to the affected subdomain. ### **Resolution** Once the issue was identified, the response team updated the affected distribution to use the correct SSL certificate. Service was fully restored after the change was completed. ### **Prevention** Learnosity is strengthening certificate deployment and validation processes to ensure that domain mappings are verified prior to rollout. Additional safeguards have been added to prevent cross-domain certificate assignments and to improve monitoring for sudden traffic drops that may indicate certificate-related failures.

Read the full incident report →

Started Jan 12, 2026, 05:06 PM UTC· resolved Jan 12, 2026, 07:10 PM UTC

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.

Read the full incident report →

Started Oct 20, 2025, 02:53 PM UTC· resolved Oct 20, 2025, 09:35 PM UTC

1. monitoring Oct 20, 2025, 02:53 PM UTC

   Learnosity services in VA are continuing to be partially impacted by the major AWS outage. AWS first reported the incident at 7:11 UTC As of 14:50 UTC they are continuing to work on its full resolution, but have again set their impact level to "Degraded". The AWS Health Status dashboard where updates are being posted by the AWS team can be found here: https://health.aws.amazon.com/health/status Overall, the error rate has fallen and has stayed below what we saw earlier in the day and we have been successful in slowly scaling up the infrastructure, but we're still seeing some issues stemming from the the ongoing AWS outage as we attempt to bring online some new instances, and we have begun to see an uptick in errors. These have included errors associated with Data API, Feedback Aide, and the delivery of adaptive assessments, delays in scoring and video encoding, as well as other smaller spikes across different systems. While the overall error rate remains low, Learnosity Support and Systems Engineering teams are actively monitoring the outage and manually intervening where possible to mitigate the issues we're facing. In spite of our best efforts it is likely that the APIs may not be fully operational in VA until AWS's service is fully restored to normal operation, but we are taking every step within our power to try to minimize the disruption to our services.

2. investigating Oct 20, 2025, 03:30 PM UTC

   As of 15:25 UTC, we are seeing increasing error rates. Data API is the most affected service at the moment and we are seeing an increase in scoring delays, but we are continuing to score incoming messages to the best rate our current capacity allows. AWS is still reporting a severity of "Degraded", but now with an increased count of 81 affected services. Learnosity Support and Systems Engineering teams are continuing to monitor the issue, and will continue our mitigation efforts wherever possible.

3. monitoring Oct 20, 2025, 06:13 PM UTC

   As of 19:10 UTC, we are beginning to see errors rates diminish and some Learnosity services are beginning to scale again. AWS is still reporting a severity of "Degraded" with problems to 104 of their services in us-east-1. Learnosity Support and Systems Engineering teams are continuing to monitor and manually intervene when possible to mitigate the effects of the outage.

4. monitoring Oct 20, 2025, 07:02 PM UTC

   As of 20:00 UTC, the error rate has continued to drop, systems remain scaled and the backlogs of scoring messages continues to drop. AWS is still reporting 109 impacted services and a severity of "Degraded" Learnosity Support and Systems Engineering teams are continuing to monitor the issue and are manually adjusting the infrastructure where needed to ensure stability.

5. monitoring Oct 20, 2025, 07:32 PM UTC

   As of 19:30 UTC, the error rate has fallen to 0.1% and continues to fall, we continue to steadily process the backlog of scoring messages. As of their latest update AWS has downgraded the severity of outage to "Impacted" but still list 109 services as affected. 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.

6. monitoring Oct 20, 2025, 08:44 PM UTC

   As of 20:40 UTC, the error rate remains low, the infrastructure is scaled to meet demand, and the scoring queues are empty and new submissions are being processed as they come in. All services are operational and we are processing the remaining backlog of messages from the incident. AWS still lists 93 affected services and a severity of "Impacted". Learnosity Support and Systems Engineering teams are continuing to monitor the issue, but at the moment all systems are fully operational.

7. resolved Oct 20, 2025, 09:35 PM UTC

   As of 21:30 UTC, all systems keep operating normally, so we are resolving the status page about the AWS outage affecting Learnosity Services in the VA (us-east-1) region. Learnosity Support and Systems Engineering teams will continue to monitor the systems closely while AWS continues to work on the issues on their side. Please reach out if you have any questions or concerns.

Read the full incident report →

Started Oct 20, 2025, 10:11 AM UTC· resolved Oct 20, 2025, 11:23 AM UTC

1. monitoring Oct 20, 2025, 10:11 AM UTC

   AWS is going through late-stage recovery of a major outage in US-East-1 bringing down most of their services. Learnosity APIs were stable and unaffected in isolation, but some impact cascaded to Learnosity (such as availability of assets from CloudFront). The full extent of the incident is unknown at this time. NOTE: Up until the time of this writing (10:05 UTC), this included impact to sign-in services that prevented us from accessing our StatusPage. We immediately posted banner notifications in our Support Portal, and those banners will remain visible until we've been able to verify that service has been restored for sufficient time. Incident History: As of 7:00 UTC, AWS experienced a major outage. While Learnosity APIs were fully operational, some Learnosity services use AWS and were affected. These included access to our Support ticketing system (the Learnosity-hosted Help guides were unaffected), and availability of CloudFront-hosted assets, but other systems may have been impacted as well. As of 10:00 UTC, AWS has restored services and access to Learnosity-adjacent features is becoming available relatively quickly. Learnosity Support will monitor AWS for a further 30 minutes before calling this issue resolved. We will follow on with an update and resolution at that time, or sooner.

2. resolved Oct 20, 2025, 11:23 AM UTC

   As of 11:20 UTC, AWS services appear to have been stable for approximately an hour. Learnosity APIs--including services affected by the AWS outage (such as CloudFront)--appear to be fully operational. At this time we are labeling this issue resolved. Learnosity Support and Systems Engineering teams will continue to investigate impact from this incident and follow up with a post mortem once we hear from AWS. Please reach out if you have any questions or concerns.

Read the full incident report →

Started Oct 02, 2025, 09:34 PM UTC· resolved Oct 02, 2025, 10:43 PM UTC

1. investigating Oct 02, 2025, 09:34 PM UTC

   As of 21:15 UTC, Learnosity APIs are being impacted by a temporary outage from our Math partner, Desmos. Authoring or Editing content with Desmos questions or features, or initializing assessments that contain Desmos questions or features, can prevent the Author API or Items API from initializing. Specific reports that display question content, such as the Session Detail by Item report, can also fail to initialize Learnosity APIs are not otherwise impacted, so content that does not include Desmos features are not affected. Until we learn more, we will list APIs that may experience knock-on effects from this temporary Desmos outage. However, as most customers will not experience any issues, we will not list these APIs as down. Desmos and 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. monitoring Oct 02, 2025, 10:14 PM UTC

   As of 22:12 UTC, Desmos services have been restored and Learnosity APIs are initializing without issue. Desmos and Learnosity Support and Systems Engineering teams will continue to monitor for a further 30 minutes before declaring this issue resolved. We will follow on with an update and resolution as soon as possible.

3. resolved Oct 02, 2025, 10:43 PM UTC

   As of 22:42 UTC, all Learnosity APIs are continuing to function as expected in all regions, and we are declaring this issue resolved. 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.

Read the full incident report →

Started Aug 19, 2025, 04:11 PM UTC· resolved Aug 19, 2025, 09:31 PM UTC

1. investigating Aug 19, 2025, 04:11 PM UTC

   As of 3:40 UTC, we are experiencing degraded performance in our analytics stack affecting the availability of session data in US-East-1 for a subset of customers. This is affecting the Reports API and Data API. Neither authoring nor assessment stacks are affected, and there is no data loss. Submitted sessions are queueing for processing. 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. investigating Aug 19, 2025, 04:35 PM UTC

   As of 4:30 UTC, we are continuing to investigate degraded performance in our Data and Reports APIs. Only availability of recently submitted session data is affected. Historic session data, as well as all other API stacks, remain unaffected. New submissions are persisting correctly with no data loss and these submission are being queued for scoring. 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. identified Aug 19, 2025, 05:34 PM UTC

   (Note: We're correcting cited UTC times to the 24 hr format and will include both forms in this update only.) As of 5:30pm/17:30 UTC, we've identified a possible contributing cause for the degraded performance in our analytics stack. 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. identified Aug 19, 2025, 06:42 PM UTC

   As of 18:30 UTC, initial remediation efforts have tripled the rate of queued session processing and we are continuing to work toward a full resolution. Access to recently submitted session results via the Data API and Reports API remains the only affected part of the Learnosity ecosystem. New submissions continue to be safely queued for scoring while the degraded performance remains. 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.

5. identified Aug 19, 2025, 07:56 PM UTC

   As of 19:30 UTC, we are now processing queued sessions rapidly and more than half of the backlog has already cleared.. 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.

6. identified Aug 19, 2025, 08:35 PM UTC

   As of 20:30 UTC, the scoring queue backlog is almost empty and new sessions will soon be processed without delay. 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.

7. monitoring Aug 19, 2025, 09:05 PM UTC

   As of 21:00 UTC, all sessions have been cleared from the scoring backlog queue and all submissions are being processed normally. Learnosity Support and Systems Engineering teams will monitor this situation for a further 30 minutes before calling it resolved.

8. resolved Aug 19, 2025, 09:31 PM UTC

   As of 21:30 UTC, we are have resolved the issue affecting availability of session data 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.

9. postmortem Sep 19, 2025, 07:14 PM UTC

   ### Affected Systems and Regions On 19 August 2025, Learnosity experienced degraded performance in our analytics stack, affecting session data availability in US-East-1 for a subset of customers. This affected the Reports API and Data API, with no other stacks affected, and no data loss. ### Investigation Monitoring detected a rapid increase in unprocessed and retried messages, along with elevated lock contention in the sessions database. The root cause was traced to a customer implementation issue generating an extraordinarily high number of submissions. This drove excessive retries, magnifying actual traffic volume. The use of time-ordered v7 UUIDs for session IDs, normally handled without issue, became problematic under this contention. Uniqueness checks on each session ID required more resources and triggered a succession of temporary deadlocks. These deadlocks would usually self-resolve, but the amplified traffic prevented recovery, turning a minor issue into a sustained queue blockage. ### Resolution Once the issue was identified, Learnosity moved the customer to a dedicated, isolated sync queue, preventing cross‑tenant impact while we investigated. We applied targeted rate limits for the isolated service to protect the database, and drained the backlog. Where safe, long‑running queries were terminated to free locks and allow forward progress. To support faster diagnosis, Learnosity enabled detailed deadlock logging and expanded metrics around message retries, abandonment, and per‑session activity. Learnosity also worked with the customer to adjust implementation settings, reducing combined saves and submits by two orders of magnitude. Session IDs were also switched to v4 UUIDs which simplified uniqueness checks further preventing deadlocks. Immediately after these changes were put into use, queues began to rapidly recover, and normal processing resumed. Most sessions for the subset of affected customers saw short delays, while the most significantly delayed session took ~6 hours before final persistence. Throughout, we identified no data loss. ### Prevention To prevent recurrence, we are: * Implementing targeted load tests and contention simulations to replicate high-parallelism patterns. * Reviewing customer identifier schemes for session IDs and auditing usage across all customers \(initial checks confirm none of our Top 50 customers currently use v7 UUIDs\). * Analyzing adoption of per-tenant fair-use queues \(or equivalent fair-share policies\) to cap burst throughput from a single tenant and protect shared infrastructure.

Read the full incident report →

Started Aug 08, 2025, 01:55 PM UTC· resolved Aug 08, 2025, 02:19 PM UTC

1. investigating Aug 08, 2025, 01:55 PM UTC

   As of 13:40 UTC, we began investigating a possible issue affecting manual update jobs to session response scores, sessions statuses, and session metadata in the US-East-1 (VA) region. We saw a brief buildup in the queue for these jobs, the queue processed as expected, and is now empty. However, we're investigating further, out of an abundance of caution, to see if there are any unexpected causes for the short queue buildup. 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. investigating Aug 08, 2025, 01:57 PM UTC

   As of 13:55 UTC, all manual update jobs have been executed and the jobs queue is empty. Requests to manually update session response scores, session statuses, and session metadata should execute as expected. We are still investigating possible reasons for the blip. 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 Aug 08, 2025, 02:19 PM UTC

   As of 14:10 UTC, we've found no negative behavior in the manual update processes and attribute the short burst of jobs to uncharacteristic testing of the new manual grading workflow. The jobs queue functioned as expected, ensuring no loss of requests, and the jobs were processed in a timely fashion. Learnosity will continue to monitor this activity for a further 60 minutes, but we are calling this resolved at this time. We apologize for the unwarranted alert. Please reach out if you have any questions or concerns.

4. postmortem Aug 08, 2025, 02:19 PM UTC

   At 13:40 UTC on 8 August 2025, we noticed a brief backup of asynchronous jobs affecting manual session updates in the US-East-1 \(VA\) region. Possible jobs including manual updates to response scores, session statuses, and session metadata. The queue mechanism worked as expected, and all requests were processed in short order. Out of an abundance of caution, we raised an alert while systems remained operational, but found nothing of concern during our investigation. We hope the unwarranted alert was not a significant distraction.

Read the full incident report →

Started Mar 03, 2025, 01:48 PM UTC· resolved Mar 03, 2025, 03:54 PM UTC

1. investigating Mar 03, 2025, 01:48 PM UTC

   As of 13:45 UTC, we are experiencing delays in availability of session information in US-East-1 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. investigating Mar 03, 2025, 02:00 PM UTC

   As of 14:00 UTC, we are still investigating an issue affecting the availability of session information in US-East-1. Both Data API and Reports API are experiencing extended delays and intermittent failures in returning session results. Authoring and Assessment APIs appear to be unaffected at this time and all session submissions are being successfully queued. 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. investigating Mar 03, 2025, 03:06 PM UTC

   As of 15:00 UTC, we are continuing to investigate the issue. Data and Reports API are still impacted. Assessment and Authoring APIs remain unaffected. Assessment submissions are being queued and will be processed as the system works through any backlog queue. Note that if the Data API or Reports API is used in a preliminary/synchronous assessment delivery workflow, this will likely have a knock-on affect when initializing assessments. Initializing any assessment API directly is unaffected at present. 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. monitoring Mar 03, 2025, 03:20 PM UTC

   As of 15:15 UTC, all services have been restored. All queued messages have been processed and session information should now be available. Users of the Learnosity Firehose service will still see slight delays as messages are sent out for recently processed events. 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.

5. resolved Mar 03, 2025, 03:54 PM UTC

   As of 15:45 UTC, after a further 30 minutes of monitoring, we are resolving this issue. All services remain fully operational. Learnosity Support and Systems Engineering teams will follow up with a post mortem once we have completed root cause analysis and finalised any next steps or preventative measures required. Please reach out if you have any questions or concerns.

6. postmortem Mar 14, 2025, 04:31 PM UTC

   ### Affected Systems and Regions On March 3, 2025, we experienced a temporary service slowdown impacting the availability of session information in the US-East-1 region. The issue began at 13:19 UTC and was resolved by 15:15 UTC. The Data API and Reports API experienced delays and intermittent failures when returning session results. Authoring and Assessment APIs were unaffected with no data loss. ### Investigation We identified a recently introduced inefficient database query was causing unnecessary strain when handling extremely large data sets. This led to delayed responses to the Data API sessions endpoints. This further led to delays or unavailability in select reports via the Reports API. Additionally, some timeouts and safeguards that should have triggered earlier did not activate as expected. ### Resolution To quickly restore performance: * We optimized the affected queries, improving efficiency and reducing database load. * We scaled up the impacted systems to immediately process the backlog. * We fine-tuned system timeouts and connection limits to prevent similar issues in the future. Following these fixes, all services resumed normal operations. ### Prevention To prevent future occurrences: * We have permanently updated our database handling methods to ensure more efficient query execution. * We are enhancing automated monitoring to detect and respond to database slowdowns before they impact customers. We appreciate your patience and remain committed to delivering a seamless experience.

Read the full incident report →

Started Jan 09, 2025, 01:33 PM UTC· resolved Jan 09, 2025, 02:50 PM UTC

1. investigating Jan 09, 2025, 01:33 PM UTC

   As of 13:30 UTC, We are currently investigating a possible performance degradation affecting Reports API and Data API results in US-East-1. 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. investigating Jan 09, 2025, 02:02 PM UTC

   As of 14:00 UTC, Learnosity is working on identifying the cause of degraded performance in our Analytics APIs, Reports and Data. Authoring and Assessment stacks 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.

3. monitoring Jan 09, 2025, 02:13 PM UTC

   As of 14:10 UTC, Learnosity has restored full service for all new requests to all Analytics APIs. We are monitoring stability and analyzing all queued requests. 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. resolved Jan 09, 2025, 02:50 PM UTC

   As of 14:50 UTC, after a further 60 minutes of issue-free monitoring, we are resolving this issue affecting availability of session information via our Analytics stack. Reports API and Data API are fully operational. 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. postmortem Jan 14, 2025, 05:25 PM UTC

   **Affected Systems and Regions** On 2025-01-09, Learnosity experienced a brief partial outage affecting our analytics stacks, specifically the Reports API and Data API in the AMER region. The issue began at 13:30 UTC and was resolved at 14:06 UTC, lasting 36 minutes. All other API's were unaffected and there was no loss of data. **Investigation** We discovered that a large number of atypical, inefficient Data API queries requested by customers were taking too long to complete. This prevented other queries from running in a timely manner, creating a backlog. It was determined that an additional database index would significantly improve the response times of these types of queries. **Resolution** Immediately upon discovering this issue, the impacted database instances were successfully scaled up to ease the backlog of requests. The additional index was implemented and all remaining queries were processed quickly. Affected APIs returned to normal operations, and further monitoring ensured the issue was fully resolved. **Prevention** Following further testing, the new index is working well and has become a permanent part of the system. We are also adding new automated monitoring and regression testing to ensure similar requests perform as expected.

Read the full incident report →