Is Learnosity Down Right Now? Check if there is a current outage ongoing.

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

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

As of 16:05 UTC, We are have resolved the issue affecting live progress reports in VA (us-east-1). As the recovery remains stable, we are now resolving the incident that was affecting live progress reports. 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.

As of 15:35 UTC, the Systems Engineering team has deployed a fix, the errors have stopped, and currently all systems are functional. We will continue to monitor for a time before resolving the incident but we are currently seeing no errors. We will follow on with an update and resolution as soon as possible.

As of 15:20 UTC, the Systems Engineering team has identified the cause for the slower than normal delivery of events and is proceeding with mitigation steps. 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, we are currently investigating an issue affecting the event delivery that powers the live progress report (live-activitystatus-by-user) 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.

As of 16:00 UTC, after monitoring and confirming the stable state of the fixes put into place, we have resolved the Events API events delivery issue affecting proctored assessments in us-east-1 (VA). 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.

As of 15:30 UTC, events are flowing normally once again and all systems are operational. We will continue to monitor for some time before we resolve the issue fully to ensure we have a stable recovery.

As of 15:00 UTC, the Learnosity Systems Engineering team has identified the issue preventing the assessment events from being delivered and are working on the implementation of remediation steps. Learnosity Support and Systems Engineering teams are continuing to work on the issue, and will follow on with an update and resolution as soon as possible.

As of 15:00 UTC, the Learnosity Systems Engineering team has identified the issue preventing the assessment events from being delivered and are working on the implementation of remediation steps. Learnosity Support and Systems Engineering teams are continuing to work on the issue, and will follow on with an update and resolution as soon as possible.

As of 14:30 UTC, We are investigating a potential issue affecting the delivery of some Events API events (used in the live proctoring / live-activitystatus-by-user report) in us-east-1 (VA). Assessments are otherwise proceeding normally and can be saved and submitted without any issue. This issue if confirmed would only affect the delivery of Events API events. 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 19:40 UTC, we believe we've identified content to be the root cause of this tiny number of sessions not passing through scoring and triggering a Firehose event. We've reached out to customer proactively and will help address this issue directly. We are now calling this issue resolved and apologize for any distractions. Please reach out if you have any questions or concerns.

As of 19:00 UTC, we have been unable to find any systemic problems, while the number of potentially impacted sessions remains at one hundredth of one percent ( 0.01%) of total submissions over the period investigated, likely due to a content issue. Learnosity Support and Systems Engineering teams will continue to monitor for 30 minutes and expect to close this investigation at that time.

As of 18:45 UTC, Learnosity Support and Systems Engineering teams are continuing to investigate an unconfirmed issue, examining less than 500 potentially affected sessions out of 4.93 million submitted over the same period. We will follow on with an update as soon as possible.

As of 18:30 UTC, Learnosity Support and Systems Engineering teams are continuing to investigate this unconfirmed issue and will follow on with an update as soon as possible.

As of 18:10 UTC, we are trying to determine if an issue exists causing a very small number of adaptive sessions to not trigger a Firehose event after scoring in US-East-1. This is just an internal investigation at present, without confirmation, and we have no evidence that any impact outside the described implementation is 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.

On 2024-04-30, Learnosity suffered a service interruption in the AMER \(US East-1\) region that affected a subset of customers. The incident began at 12:52 UTC and was resolved at 14:18 UTC, lasting 1 hour and 26 minutes.  We apologize for the impact that this had on our valued customers and learners.  We have learned, and will continue to learn, from this incident and have taken steps to ensure this issue doesn’t repeat. **Details of Incident** Performance issues were initially detected by our Site Reliability Engineering team, who executed our escalation process in raising Tier1 and subsequently Tier2 in short order. While assessment and authoring load were typical, we saw a massive spike in Data API activity from a single client. This was limited to the **get\_/itembank** endpoints set typically used for authoring. The single client had never used these Data API endpoints before, went from zero to equal to all other clients combined in a short period of time. This is a particularly laborious query necessary for authoring use. Calling this at such a high volume and frequency created a hotspot and contention on the cluster of four itembank delivery databases, which handle a subset of customers. When we’re under high volume of typical traffic we operate on about 30% peak database load. The atypical traffic outlined above put the databases at full capacity. While all of our assessment critical systems auto scale, the itembank delivery databases are over provisioned to have significant headroom, and as such don’t auto scale. Auto scaling of database instances can introduce a risk if anything goes wrong while scaling, and as such when designing the system our team determined manual scaling of these itembank delivery databases was the more reliable option. This atypical activity led to resource starvation of the Data API, with knock-on effects to the assessments stack. Data API impacts included limiting access to authoring and session data, as well as slowing down session scoring and follow-on dispatching of scoring events via Learnosity Firehose. During the incident, we experienced degraded performance with up to 30% of requests not succeeding. Assessment impacts included cases where the Data API was used in assessment delivery, and in some cases limited new initializations \(i.e. starting a test\). For the avoidance of doubt, all save and submit calls were successful without data loss. **Resolution** Once the atypical traffic was identified, temporary request rate limits were put in place to allow our remediation efforts to quickly scale to support the increased level of activity and process backlog. Once all services were again operating at optimal levels, the temporary request limits were removed. **Additional Analysis and Prevention** We are making the following changes as a result of this operational event, to prevent this from happening again. * We identified that the baseline rate limit configured for the itembank endpoints was not appropriate - and have reviewed and configured this appropriately. * We are reviewing improvements and resource allocations of the Data API to handle atypical usage patterns and increase resilience. * We are continuing to perform analysis to determine what other preventative measures are appropriate to implement.

As of 15:00 UTC, we are closing this incident as resolved. The availability and performance of the Data API and downstream systems in US-East-1 has been restored and operating correctly for 30 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.

As of 14:30 UTC, we have addressed an issue primarily affecting Data API use. Error rate has reduced to zero, all newly submitted sessions are scoring immediately, and the backlog of sessions awaiting scoring is cleared. The Firehose service queue is clearing quickly dispatching information about recently scored 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.

As of 13:45 UTC, we are investigating an issue with the availability of authoring and assessment content in the US-East-1 region. This issue is also impacting analytics, with degraded performance of Reports and select Data API endpoints that require content, such as the Session Detail by Item report and Data API item bank and scoring endpoints. We will continue to update this incident as we learn more. 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.

We are currently experiencing an issue affecting the availability of newly authored and edited content. This is also having a ripple effect on assessments dynamically retrieving content, such as adaptive and on-the-fly assessments. We are investigating and will update this record as soon as we learn more.

As of 21:56 UTC, all jobs continue to be processed at a normal rate and all services are operational. We are marking the issue affecting the processing of item pool and offline package jobs in US-West-2 as resolved. 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.

As of 21:26 UTC, the jobs processing performance has returned to normal and all job queues are empty. Everything is currently performing as expected, we will continue to monitor for a time to ensure a full recovery before fully resolving the incident.

As of 21:15 UTC, the Learnosity Systems Engineering team has identified the issue and is making adjustments to restore normal jobs performance. Learnosity Support and Systems Engineering teams are continuing to work on the issue, and will follow on with an update and resolution as soon as possible.

As of 20:30 UTC, we are investigating a possible issue affecting the processing of item pool and offline package jobs in the US-West-2 region and causing slower than normal processing times. 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 17:00 UTC, we've identified the problem affecting tag hierarchies and it is not an infrastructure/services issue. We've determined that an application-level bug limited to saving a newly edited hierarchy is the root cause and have raised a ticket for processing. All other API and backend functionality, including the use of existing tag hierarchies, remains operational. We are closing this incident and moving the focus to the software team. If you experience any issues with saving hierarchies please don't hesitate to raise a ticket with the Learnosity Support team and we will provide additional updates. Thank you.

As of 16:00 UTC, we are continuing to investigate an issue preventing updates to Tag Hierarchies. This issue is limited to the creation and editing of tag hierarchies. Only a small subset of reports that make use of this feature may be affected, and only when a change to a tag hierarchy is required. All other APIs, including reports that don't rely on hierarchy updates, remain operational. 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:30 UTC, we are investigating an issue preventing tag hierarchies from being created or updated in the US-East-1 Region. This only appears to affect new changes to tag hierarchies, so this should only impact the use of select reports that rely on this feature, and only when a newly created or updated hierarchy is required. Routine authoring and assessments are unaffected, as are reports and Data API use that don't rely on newly edited hierarchies. We're including tag-related reports in this update for visibility, but the Reports API remains operational and only a small subset of reports use tag heirarchies. Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

On 2023-12-13, Learnosity suffered a major outage that began at 13:22 UTC and was resolved at 18:29 UTC, lasting 5 hours and 7 minutes. Its primary impact was on the assessment stack in the AMER region, with partial impact to authoring and select analytics APIs due to the use of assessment functionality in some preview features. Initially, we thought this incident was a scaling issue because errors were linked to the creation of new virtual servers to meet daily traffic. However, we ultimately discovered that the problem was unrelated to scaling. The root cause was actually a faulty configuration management client, `salt v3006.5`. A [bug in the most recent version of Salt-stack](https://github.com/saltstack/salt/issues/65691), released at 2023-12-12 at 21:38, caused a failure in our `cloudinit` process when spawning new EC2 instances. From 13:05 PM UTC, as new instances were launched, the `salt` bug caused the new machines to fail a health check and fall into a loop of retried launches. **Resolution** Immediately after this discovery, we were able to hard code to a prior version of `salt`, removing the regression. New EC2 instances were successfully  provisioned and scaled to comfortably handle all traffic. All APIs returned to normal operations soon after. **Additional Analysis and Prevention** Upon further investigation, it was discovered that our system became vulnerable to the `salt` regression due to error handling dependencies. To facilitate fast and reliable scale up, our image build process is designed so that dependencies are pre-installed at build time, with only minor applicable config changes required at instantiation. Further investigation discovered that a prior fix for a build dependency issue inadvertently moved the installation of the affected `salt` package from _image build_ time to _instance launch_ time. This meant that the creation of new instances no longer relied on the original image version of `salt`, instead the newest `salt` version was installed during the scaling process.  We are making the following changes as a result of this operational event, to prevent this from happening again. * We are conducting a full review of the launch process to ensure there are no other unknown launch-time dependencies. * We are adding additional guard rails in the build process to catch any dependency regression at the imaging phase before production use.

As of 19:40 UTC, we've concluded one hour of active monitoring without additional issues. We will continue to keep an eye on everything but are now ready to call this incident 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.

As of 18:36 UTC, we've now recovered fully and all stacks are operational. We will continue to monitor for a period before resolving the incident. 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 18:20 UTC, we've verified a cause of the current incident and recovery is already partially complete. We have restored part of the assessment stack and are working on full restoration now, with the remaining stacks to follow. We will provide additional updates soon, including a possible ETA as soon as a reasonably accurate estimate has been determined. 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.

We've now identified a possible cause for the current incident and are working to resolve the issue. We will add additional information as soon as it becomes available. We've also added EMEA authoring and APAC authoring to affected regions for users of the hosted author site, which operates in the AMER region. Learnosity Support and Systems Engineering teams are continuing to actively investigate the current issue, and will follow on with an update and resolution as soon as possible.

Correction: The authoring and analytics stacks are also begin impacted intermittently in workflows where the assessment stack is in play. (E.g. editing views where the assessment stack is used for previews.) Errors in the AMER region continue to reduce. 502 errors have cleared and 504 timeout errors are now being investigated. Elevating classifications to include all stacks and partial outage. 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:15 UTC, the assessment stack returned to normal operating metrics in the EMEA and APAC regions. As of 14:30 and 14:45 UTC, the NA region error count dropped by approximately 15% each period, and error counts are continuing to reduce as of 15:00 UTC. Intermittent errors continue to occur in the assessment stack in AMER. Authoring and Analytics 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 14:15 UTC, we've identified that the AWS Auto Scaling Groups failed to create additional EC2 instances causing an elevated number of 502 errors in the assessment 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.

As of 14:00 UTC, We are seeing intermittent issues with loading demo assessment content and are investigating out of an abundance of caution. 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 17:55 UTC, we identified an adaptive Redis cache that was intermittently refusing a small percentage of connections. Self-hosted adaptive makes extensive use of this cache due to the need to store more state information supplied by the self-hosted client. We replaced the cache database, routed all traffic to the new instance, and saw an immediate, dramatic reduction of refused connections. We've monitored for approximately 90 minutes and all activity indicates normal operation of all APIs. We are resolving this issue and will continue to monitor customer comms. 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:25 UTC, we are investigating a possible issue affecting Self-Hosted Adaptive testing in the US-East-1 region. Due to the very small number of customers affected, we've not yet confirmed if this is something related to Learnosity APIs or the self-hosted algorithm portion of the solution. Most customers using this feature appear to be unaffected, but we're raising this alert out of an abundance of caution. 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 16:45 UTC, we are have resolved the issue affecting scoring delays in the US-East-1 region. All sessions are scoring as expected, with no backlog or delays. No data was lost during this incident, the authoring and assessment stacks were unaffected, and analytics have been restored. 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:10 UTC, incoming submissions are now being scored with expected turnaround, and the queue of previously submitted sessions awaiting scoring has been cleared. Session results, access to the Data API sessions/responses endpoint, and analytics via the Reports API for affected sessions, should all function normally. All APIs are fully operational. 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.

As of 15:40 UTC, we are addressing an issue with scoring delays in the US-East-1 region. Session results, access to the Data API sessions/responses endpoint, and analytics via the Reports API for affected sessions, are showing delays. Submissions are continuing to be accepted with no data loss, and we are processing the backlog of submissions awaiting scoring. 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 14:20 UTC, We are currently experiencing an issue affecting learner session data retrieval in VA (us-east-1). Learnosity Support and Systems Engineering teams have identified the issue and are working to address it, and will follow on with an update and resolution as soon as possible.

As of 14:53 UTC, We are have resolved the delay affecting authoring in all regions. 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 14:00 UTC, normal authoring performance has been restored in the remaining regions and all systems are now operating as expected across all regions. Clients should no longer be experiencing any delays in being able to access newly created or edited content in any Learnosity region. We will continue to monitor for some time to ensure that all systems continue to operate normally before fully resolving this issue.

As of 13:20 UTC, the delay in availability of newly authored or edited content has resolved for the AU region. Our engineers continue to work on the resolution for the rest of the regions and we will provide an update as soon as those have also recovered. 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 07:33 UTC, We are currently experiencing a delay in the availability of newly authored or edited of content in all regions. New or edited content may be delayed in appearing in the authoring interface and in being available to be used in assessments. Existing content is unaffected and will be available to assessments as usual. Learnosity Support and Systems Engineering teams have identified the cause of the issue and are actively working on it, and will follow on with an update and resolution as soon as possible.

As of 16:55 UTC, after two hours of monitoring, all scoring queues remain empty as sessions are being scored promptly. We are resolving this issue. 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 14:55 UTC, all queued sessions have completed scoring and new sessions are moving through the scoring process smoothly. Analytical data and Firehose messages should be available for all sessions. No authoring or assessment flows were affected, all submissions were successfully saved without data loss, and the small subset of customers in the VA region that were affected should again be fully operational. Learnosity Support and Systems Engineering teams will continuing to monitor the issue, and will follow on with an update and resolution as soon as possible.

As of 14:30 UTC, we identified and corrected the issue. Our engineers are now monitoring the queue which is diminishing quickly. Learnosity Support and Systems Engineering teams are monitoring the issue, and will follow on with an update and resolution as soon as possible.

As of 14:00 UTC, we are investigating an issue with asynchronous scoring delays affecting our US-East-1 region. Note: Submissions are not affected, resulting in no data loss, and no other APIs are affected. Sessions are being successfully stored and submitted for scoring, going into a temporary backlog queue. This slows down availability of analytics, including notification delays in the otherwise fully functional Firehose 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 17:45 UTC, we are no longer experiencing issues with Support tickets loading, and are calling this third-party issue resolved.

As of 14:30 UTC, we are currently seeing a partial outage in our third-party ticketing system. Zendesk status doesn't currently reflect an issue, but the ability to load or create support tickets may be affected. Learnosity Support is actively monitoring the issue, and will follow on with an update and resolution as soon as possible.

As of 19:20 UTC, our third-party support vendor states that no issues are affecting Learnosity Support. (One incident remains active but is not thought to affect the Learnosity Support ticketing system.) We are resolving this incident but will reopen if we are affected. Please reach out if you have any questions or concerns.

As of 19:00 UTC, our ticketing system vendor is reporting an ongoing incident affecting performance of the Learnosity Help ticketing system. We will continue to monitor and report progress as we become aware of changes.

As of 13:40 UTC, we have resolved the issue affecting assessments in VA (us-east-1). All systems continue to operate normally, so we're closing off this incident. Please reach out if you have any questions or concerns.

As of 13:10 UTC, the Systems Engineering team has identified the cause of the errors and has taken steps to address it. Due to the Questions API built-in retry logic, clients should not have experienced any visible failures and all sessions would have been processed with only a slight delay. All systems are currently back to fully operational status. We will continue to monitor for a time to confirm continued normal operations before we fully close this incident.

As of 12:46 UTC, we are investigating elevated error rates below 3% affecting assessments in the VA region (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.

Zendesk has closed their incident affecting ticketing and guided help in Brazil.

As of 17 August 13:15 UTC, Zendesk is continuing to address the issue affecting our ticketing system and help guides in Brazil. From Zendesk: "We started to roll out a temporary fix for the network connectivity issues, which appear to be have been caused by some Zendesk IPs being blocked by an ISP provider in Brazil. We also encourage you to please clear your cache and cookies a few times before trying to connect again as the rollout continues across all Pods. More information as we have them."

As of 18:00 UTC, Learnosity continues to monitor this ongoing incident with Zendesk that impact customers in Brazil. Performance of support tickets, and Help and Authorguide knowledgebase articles, continues to be degraded.

For those wishing to monitor Zendesk's comms on the issue, you can do so here: https://status.zendesk.com/

Zendesk, our support ticketing system vendor has reported an active incident that may affect the ability for customers in Brazil to create support tickets. Learnosity will do our best to monitor this situation and update our own status page to help pass information on. This affects tickets and knowledge base documentation resources help.learnosity.com, and authorguide.learnosity.com. The Reference site (API language resource) is unaffected. Zendesk currently says this only affects customers in Brazil.

As of 20:00 UTC, availability of newly authored/updated content is back to normal and this issue has been resolved. We will continue to monitor this a further period, looking for recurrences. 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 19:45 UTC, delays in availability of newly created/updated content have abated. We will continue to monitor for before downgrading the alert status. 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:18 UTC, we've confirmed minor delays in availability of newly created or updated authoring content in the us-east-1 region. 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 currently investigating possible delays in newly created and updated authoring content 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 4:00 UTC, after extensive monitoring, we have resolved the issue affecting timely creation of item pools in the us-west-1 region. 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 2:15 UTC, item pools are being processed as expected and we are monitoring their creation and throughput. 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 12:12 UTC: As part of our ongoing investigation and remediation of issues affecting the timely creation of item pools, we've detected an issue creating and updating index values that may be linked to creating large batches of small item pools. We are working to correct the issue. 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 16:50 UTC, after extended monitoring with no further delays, we're resolving this incident. We will continue to monitor for 30 more minutes to watch for any further issues. 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 15:00 UTC, we confirmed delays accessing newly authored content. All content has been successfully writing and then delays occurred making the content available in the VA region. The delay dramatically diminished and we are continuing to monitor. 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:30 UTC, we are investigating possible delays with newly created content being available to assessments in the us-east-1 region. If confirmed, this will only affect content recently created. Availability of existing content is unaffected, and all other APIs are operating 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 03:00 UTC, we have observed all system to be performing as expected and are resolving this issue. We will continue to monitor our systems for a period of hours following resolution, should anything related occur. 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.

As of 00:50 UTC, newly created/updated content is fully available worldwide. Learnosity Support and Systems Engineering teams are continuing to monitor the issue to ensure it has completely stabilised.

As of 22:30 UTC, newly created/updated content is almost fully available worldwide. AWS regions us-west-2 (AMER OR), us-east-1 (AMER VA), and eu-west-1 (EMEA IE) are current. The ap-southeast-2 (APAC AU) region is still a somewhat behind and recovering. Learnosity Support and Systems Engineering teams are continuing to work on the issue, and will follow on with an update and resolution as soon as possible.

As of 21:00 UTC, we are continuing to work on this issue and will update this alert as new information becomes available.

As of 19:50 UTC, authoring of new content has been restored. A brief period will now follow during which any content newly authored since 19:50 UTC will gradually become available to all regions. We will update this alert again when all regions are updated. Learnosity Support and Systems Engineering teams will follow on with further updates and a resolution as soon as possible.

As of 19:25 UTC, Learnosity has begun its unplanned outage of authoring new content. We will update this alert when authoring creation/editing becomes available again. Existing content will continue to be available to assessments and analytics, with no other APIs affected. Learnosity Support and Systems Engineering teams will follow on with further updates and a resolution as soon as possible.

Within an estimated thirty minutes, Learnosity will begin an unplanned outage of authoring new content as part of restoring the ability to create new item pools. Existing content and item pools are now, and will continue to remain, available to assessments and analytics. This unplanned outage is expected to last less than sixty minutes and will only affect the creation and updating of new content. Once authoring of new content is restored, a brief span of degraded performance will follow during which new content will gradually become available to all regions. No other APIs are affected. Learnosity Support and Systems Engineering teams will follow up with further updates and a resolution as soon as possible.

As of 01:00 UTC, all item pool creation is working as expected so we are resolving this incident. 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.

As of 22;30 UTC, item pool creation has been stable for some time. We will monitor the issue for a short while longer to be sure no remaining issues arise.

As of 18:30 UTC, we have determined that restoring item pool creation requires an unplanned outage of new content authoring, followed by a short period of recovery while newly authored content is made available to all regions. We will create a new incident for the unplanned authoring maintenance, and continue to update this incident for further information related to item pool creation. Use of existing item pools remain unchanged, and no other APIs are affected.

As of 17:30 UTC, we are continuing to work on the issue affecting creation of item pools, and will follow on with an update and resolution as soon as possible.

As of 15:40 UTC, we've likely identified the cause of the halted item pools and are working on a resolution. 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, we are investigating an issue preventing the creation of item pools in the us-east-1 region. Pool creation requests are successful and the pool is halted. No other APIs 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 17:20 UTC, after an hour of monitoring, we've seen no further delays with creating or updating content in any region. 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.

[Update status to monitoring.] 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 16:20 UTC, authoring queues have cleared and no further impact is detected. Learnosity Support and Systems Engineering teams will continue to monitor the issue, and will follow on with an update as soon as possible.

As of 16:10 UTC, we are investigating possible delays in creating and updating content in the us-east-1 and eu-west-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 19:30 UTC, all authoring queues remain empty so we are resolving this issue. We will continue to monitor our systems for a period of hours following resolution, should anything related occur. 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.

As of 19:05 UTC, all remaining authoring backlog queues in eu-west-1 have cleared and no delays remain for availability of authored content in any region Learnosity Support and Systems Engineering teams will continue to monitor the issue, and will follow on with an update and resolution as soon as possible.

As of 19:00 UTC, we continue to work to address the delay of authored content in us-west-1. As of this update, delays have been reduced by two-thirds with only approximately 30% of customers actively authoring in us-west-1 are seeing delays. Other IE/EMEA customers, and all other regions appear to be 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 17:45 UTC, we're still investigating delayed availability of authored content in the eu-west-1 region (IE/EMEA) No other regions seem to be affected at this time and our engineering team is working to identify a possible cause for the delay in IE. 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 17:00 UTC, we are investigating possible delays in creation of authoring content in the eu-west-1 region (IE/EMEA). 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 22:42 UTC, the vendor issue affecting scoring delays in us-east-1 has been resolved. AWS has marked the incident as resolved in their own status page, and we haven't experienced any delays in scoring since 20:39 UTC, therefore we are marking this incident as resolved. Please reach out if you have any questions or concerns.

As of 21:55 UTC, we continue to operate normally and with no scoring backlog. We are continuing to monitor the status of the AWS service incident, which AWS current expects to have fully resolved in the next hour, but there is currently no impact on Learnosity's operations and all API and services 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 20:43 UTC, Learnosity has taken measures to bypass Lambda functions for scoring until AWS recovers. Scoring backlog has cleared and we will continue to monitor the status of the AWS service degradation until AWS fully recovers. 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:40 UTC, Learnosity is working on mitigation efforts in parallel with work by AWS on the issue. We will also continue to monitor the AWS performance degradation and update this incident when we learn more. 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:20 UTC, AWS has reported a degradation of performance of Lambda functions used for scoring. Learnosity is working with AWS to try to resolve the situation as quickly as we can. 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 16:50 UTC, we believe any intermittent issues affecting availability of new content to assessments have been resolved and we're closing this incident. We know most of you were unaffected and appreciate your patience as we strive to be proactive and transparent. Please reach out if you have any questions or concerns.

As of 16:20 UTC, we have been unable to confirm that any issue exists. We will move this incident to monitoring and continue to monitor for a short period. Learnosity Support and Systems Engineering teams will continue to monitor the issue, and will follow on with an update as soon as possible.

As of 15:40 UTC, We are currently investigating possible delays in accessing newly created assessment content. As a followup to yesterday's issue, we are investigating minor delays in one previously unaffected system. At present, all APIs are operational. One report has been logged, however, showing intermittent delays in delivering assessments, so we are determining if proactive measures are required. We will update this post as soon as we have additional information. 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 if 22:45 UTC, we are still seeing all systems continue to operate normally, and we will therefore close this issue.

As of 22:15 UTC, all systems are operating normally and users should not be experiencing any delays in new content becoming available. We will keep to monitor to confirm the continued normal operation of all systems.

As of 22:00 UTC, we are investigating a possible delay in the availability of newly created content in US-East-1 (VA) for some users. During this period, affected users may experience a delay in newly created content becoming available for use in Items API assessments, being displayed in the Item or Activity lists in Author API, or in being returned by Data API's /itembank/* endpoints. 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 21:14 UTC, the backlog of messages affecting the availability of sessions in the US-East-1 (VA) region has been processed and all function are operating normally. 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.

As of 18:30 UTC, we have a correction of the earlier message, the Systems Engineering team is still working on backfilling some of the messages from sessions submitted during this incident. Some data may not yet be available as the backfilling process continues but all data is safely stored and awaiting processing, and there will not be any data loss resulting from this event. Sessions currently submitted are being processed normally and will be available shortly after submission.

As of 17:00 UTC, the scoring backlog has resolved and all sessions should be available via Data API and Reports API as normal. Learnosity Support and Systems Engineering teams will continue to monitor the scoring queue for a time to ensure normal operations continue.

As of 16:30 UTC, the scoring backlog is continuing to decrease. Learnosity Support and Systems Engineering teams are continuing to actively work on this issue, and will follow on with an update and resolution as soon as possible.

As of 16:00 UTC, the Systems Engineering team continues to work on remediation to allow the backlog to decrease as quickly as possible. Learnosity Support and Systems Engineering teams are continuing to actively work on this issue, and will follow on with an update and resolution as soon as possible.

As of 15:30 UTC, we're seeing a reduction in the scoring backlog, our Systems Engineering team is taking further steps to speed up the recovery process. Learnosity Support and Systems Engineering teams are continuing to actively work on this issue, and will follow on with an update and resolution as soon as possible.

As of 15:00 UTC, the Systems Engineering team has identified the source of the resource starvation at the bottom of this issue and has began remediation steps. Learnosity Support and Systems Engineering teams are continuing to actively work on this issue, and will follow on with an update and resolution as soon as possible.

As of 14:30 UTC, we are still investigating scoring delays of submitted assessments for some customers, causing session data to take longer than normal to become available in Data API and Reports API . 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 13:50 UTC, we are investigating possible scoring delays of submitted assessments in the US-East-1 region. Authoring and assessment functionality remains largely unaffected, and no data loss is evident. If confirmed, impact will be on availability of submitted sessions via the Data API and Reports API. 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:15 am EDT, 3:15 pm UTC, the issue causing delayed availability of a small subset of submitted sessions in us-east-1 has been 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.

As of 10:45 am EDT, 2:45 pm UTC, the scoring backlog is now fully recovered and we have moved to monitoring. This update is mainly to note that our support ticket system, by our vendor Zendesk, is experiencing unrelated issues with loading tickets. Errors appear small in number and intermittent, but note that we have responded to all tickets received, including the two related to this incident. 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 10:20 am EDT, 2:20 pm UTC, we are still investigating possible scoring delays of submitted assessments and have confirmed that a small number of customers are experiencing delays in availability of session information. One of several scoring queues is suffering degraded performance and is recovering, and sessions are moving through other queues, with backlog reducing at a substantial rate. All other APIs remain operational, there is no known data loss, and only a small subset of customers have been 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 10:00 am EDT, 2:00 pm UTC, we are still investigating possible scoring delays of submitted assessments and have not confirmed any direct customer impact. As a precautionary measure, we will continue to show degraded performance for availability of session information until we're certain no possibility for delays exists. 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 9:00 am EDT, 1:00 pm UTC, we are investigating possible scoring delays of submitted assessments in the US-East-1 region. Authoring and assessment functionality remains largely unaffected, and no data loss is evident. If confirmed, impact will be on availability of submitted sessions via the Data API, and possibly adaptive testing due to the need for per-item scoring 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 4:45 pm / 16:45 UTC, We are have resolved the issue affecting Data API sets in the eu-west-1 region. All APIs in all regions should be 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.

As of 4:30 pm / 16:30 UTC, we have addressed the issue and are monitoring performance. Users of the data-ie.learnosity.com regional endpoint should now be able to set questions/items/activities without issue. No other API was affected, and users of other regional endpoints--including EMEA clients using data-or.learnosity.com--were not affected. Learnosity Support and Systems Engineering teams are continuing to actively monitor the issue, and will follow on with an update once the issue is resolved.

As of 3:00 pm UTC, we are experiencing failures creating authored content via the Data API in the IE (eu-west-1) region only. The Learnosity-hosted author site is unaffected, and no other APIs or geographical regions are impacted. Users in EMEA areas can use the data-or.learnosity.com endpoint as described in the following knowledge base article. https://help.learnosity.com/hc/en-us/articles/360000754798-What-Regions-and-Endpoints-Should-I-Use- Learnosity Support and Systems Engineering teams are actively working on the issue, and will follow on with an update and resolution as soon as possible.

On November 1, 2022, one of the four databases that persist student responses became unable to write an ID that ordered questions/responses in review and report modes only. The analytics features were potentially impacted by a maximum 25% of submitted sessions during the 2 hour and 9 minute duration of the incident and, because only a subset of those sessions used contributing features, only an estimated 1% to 3% of sessions were actually affected. No data was lost and only the order of displayed questions were temporarily changed. Immediately after discovery, we began testing remediation options and the safest and quickest way to address the issue was to reset the impacted ID, as it played no other role in processing the data. This was theoretically unable to affect a typical assessment because questions and responses are captured upon initialization within milliseconds. However, a very small number of sessions using deferred loading features \(such as sections and, in some cases, lazy loading or dynamically adding items via public method\) were impacted--only if the ID was reset both _after_ an initial batch of items were loaded and before a following batch of items were loaded. In this case, the sequential ids in the later batch were set to values lower than those in the earlier section batch, due to the reset. \(Using sections as an example, this caused section two to appear before section one in a report.\) To summarize, this issue was relevant only when all of the following applied: * customer was among a subset of customers using the US-East-1 region * sessions were among the 25% or less captured to the single affected shard * sessions were initialized for the first time during the incident window * sessions contained more than one section or deferred loading mechanism Additional long-term adjustments were made to prevent this issue from occurring again in the future. In addition to the immediate fix of resetting the ID, the review/reporting logic was improved to no longer require the ID for ordering questions/responses. As a result, all affected sessions were thereafter automatically displayed correctly without any need for rescoring or other alterations to the data.

As of 18:59 UTC, we have corrected the issue affecting the capture and persistence of some student responses. A single database was affected and our sharding process limited impact to 25% or less of active sessions only, for a subset of customers, in the US-East-1 region. Learnosity Support and Systems Engineering teams will continue to monitor the situation for a further period to be sure errors no longer occur. We will further 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.

As of 17:55 UTC, we have identified an issue with saving student responses in active sessions only, affecting a single shard in region US-East-1. We have elevated this to Partial outage for affected customers and are working to correct the issue. We are returning the 'Availability of existing session information' status to Operational and will continue to monitor results. 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 17:30 UTC, we've detected an increase in errors in persisting student responses for some customers in the US-East-1 region. This currently appears to be affecting a minority of active sessions only. Authoring and Analytics remain unaffected. <ANY ADDITIONAL INFORMATION REQUIRED>. 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 17:10 UTC, we are currently investigating a possible issue with saving student responses in region 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.

On November 29th 2022, our systems detected delays in available analytics data affecting the Live Activity Events API, Data API, and Reports API in the US-East-1 region. Investigation began immediately upon detection, leading to the discovery of a resource starvation in our api-events system. Requests to `events/lastevents` \(used internally by our Live Progress by Activity by User report\) encountered a function that ran for an extended period of time, leading to the exhaustion of select workers. This in turn led to starvation of api-data and api-reports resources. This siloed issue did not trigger autoscaling, but Learnosity manually scaled relevant EC2 instances to temporarily add workers, limiting the incident to 1 hour and 19 minutes from detection to remediation. Steps were taken to reduce the impact of extraneous calls to `events/lastevents` that result from malformed customer initializations, such as when enabling the Events API in assessment initialization requests when those assessments are not part of a Live Progress by Activity by User report. This errant use indiscriminately publishes live events even when the Live Progress by Activity by User report is not in use to receive them. As a further safeguard, a "wait for subscribe" feature is in testing to reduce extraneous events that fire in this edge case.

As of 3:10 UTC, a further 30 minutes of monitoring has confirmed that all delays affecting the availability of session data in the US-East-1 (VA) region have been eliminated and all functions are operating normally. 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.

As of 2:40 UTC, availability of session data is fully restored, the message backlog has been eliminated, and load balancing is performing normally. Data API, Reports API, and Firehose streams all operating as expected. No impact was seen in authoring or assessment data flows, and persisting of learner data was also unaffected. 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 approximately 2:10 UTC, Learnosity engineers identified an apparent scaling issue and have manually scaled available server instances, to immediately impact message backlog. Queues are steadily reducing and we are actively monitoring. 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.

2:05 UTC. We are continuing to investigate possible delays affecting the availability of session data in the US-East-1 (VA) region. Firehose messages and Data API queries started showing slower than normal response times at approximately 1:20 UTC. Learner submissions, persisting data, and scoring remain unaffected, as do all authoring and assessment APIs which continue to operate normally. Learnosity Support and Systems Engineering teams will follow on with an update and resolution as soon as possible.

As of 1:40 UTC, we are investigating possible delays affecting the availability of session data in the US-East-1 (VA) region. Scoring is not affected, nor are any authoring or assessment APIs.. 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 16:32 UTC, Scanii resolved their issue and the Learnosity media queue is again empty. Consistent with Scanii's report of some requests generating errors, a small number of files failed and have been requeued. All new files are moving through the queue. We will continue to monitor for approximately 30 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.

As of 16:15 UTC, Scanii is working through the media scanning backlog and the queue has diminished substantially. Current estimates are that the queue will be empty in approximately 15 to 20 minutes. 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:30 UTC, we are seeing delays in the review/resume availability of recorded audio files due to a Scanii outage. Audio files are scanned for viruses and Scanii's outage delayed post-processing. No data loss occurred. Scanii's issue appears to have been resolved and the scanning cue is working through it's backlog. 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, after a post-resolution monitoring period, we have seen no additional issues with newly authored content becoming available in preview or assessment settings. We are resolving this issue but will continue to monitor for a brief follow-on period. 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 18:00 UTC, preview/availability of newly authored content is functioning correctly, and the US-East-1 (VA) server has been restored. We will continue to monitor for a short period and then begin transitioning the replication load back to the restored VA server. Some latency may still be apparent until the load has been fully transitioned to VA. 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 17:45 UTC, we've routed the content replication backlog to the US-West-1 (CA) region while we await additional assistance from AWS to restore the unresponsive server in US-East-1 (VA). Content continues to save without data loss, and continues to preview successfully in all regions worldwide, other than VA. Further, the backlog has already reduced by two-thirds and is still dropping. 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 17:15 UTC, we have identified an issue with content replication in US-East-1 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 16:45 UTC, we are seeing delays in availability of newly authored questions/items in the US-East-1 region. Content is being created and persisted without issue, and is being successfully replicated to the CA, OR, IE and AUS regions. There is no data loss, but authoring previews are delayed in the VA 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.

An underlying storage system corruption, linked to a single row in the database table where _scoring errors_ are saved, caused delays in the asynchronous scoring queue. Prior to correction, queries run against this table could take anywhere from a partial second up to several seconds to complete, and this impact was compounded by an unusually high number of sessions scoring errors submitted at one time. Because this issue only surfaced when rare scoring errors were logged, it was not immediately detected. Originally, the number and size of RDS instances were increased to work through the scoring backlog but the queue cleared before this process could be completed. This led us to the fact that delays only occurred when errors were persisted, and led to the discovery, and deletion, of the problem table row. Additional measures have been put in place to monitor the write speed of errors, as well as session data, and the issue has not resurfaced since then.

As of 16:53 UTC, we have resolved the issue affecting scoring delays in the US East 1 (VA) region. 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:22 UTC, the scoring queue is empty, with sessions scoring too quickly to create a backlog. Learnosity Support and Systems Engineering teams will continue to monitor for 30 more minutes and then, in the absence of any further delays, mark this issue resolved.

As of 16:00 UTC, scoring throughput remains to normal. The backlog in the queues is continuing to reduce. Learnosity Support and Systems Engineering teams are continuing to monitor the issue, and will follow on with an update and resolution as soon as possible.

As of 15:46 UTC, scoring throughput has returned to normal. We are still seeing a backlog in some scoring queues but it is rapidly reducing. Learnosity Support and Systems Engineering teams are continuing to monitor the issue, and will follow on with an update and resolution as soon as possible.

As of 15:00 UTC, the Learnosity Systems Engineering team is working on mitigating the delays affecting the availability of newly scored session data in US East 1. 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:30 UTC, we are continuing to investigate an uptick in scoring delays that are affecting the US East 1 (VA) region. 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, we are currently experiencing minor delays in scoring of submitted sessions affecting the US East 1 region (VA). Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

AWS experienced an outage in one Availability Zone in US-East-1 due to a power failure. Initially unaffected, Learnosity experienced some knock-on effects s few hours later. AWS has resolved the power issue and things quickly returned to normal.

As of 16:00 UTC, we are still seeing no lingering effects from this mornings AWS outage and are resolving this issue. 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.

Looking like AWS have resolved the issue on their end, our systems are starting to stabilise and looking to be in good health again. We will continue to monitor the situation and updated as needed. The error rates have dropped again to zero and all systems are looking green again.

AWS have experienced an outage in one Availability Zone and it's affecting the systems running in that AZ. Most of Learnosity systems are still operational but this AWS outage is having a knock-on effect that is impacting other AWS systems.

As of 04:35 AM PST AWS has been experiencing problems that are trickling down to Learnosity. It appears that some areas of the U.S. are having trouble accessing some data and some assessments may be affected. Learnosity systems are running impaired and we will update this status as more information becomes available.

As of 17:20 UTC, the AWS incident has been marked resolved for over an hour. All Learnosity services continue to operate normally, so we will consider this incident resolved. Please reach out if you have any questions or concerns.

AWS has marked the incidents affecting the US-West-1 and US-West-2 regions as resolved. We will continue to monitor for a further 30 minutes before calling this resolved as well.

As of 15:30 UTC, AWS has been experiencing problems that are trickling down to Learnosity. It appears that some areas of the U.S. are having trouble logging into author.learnosity.com and reference.learnosity.com. At the moment we suspect this is affecting CDN usage. All Learnosity systems are functioning properly, and we've seen reports from a minority of customers, so we will maintain Operational status. However, we will try to keep our customers up to date with the AWS outage, even if short-lived. Please note that this issue is also affecting our ability to access our StatusPage service, so updates may be sporadic.

On November 9, 2021, asynchronous scoring delays affected a small subset of customers for 3.25 hours. \(94.24%, or 49.16 million, of scoring messages were processed in less than a second on November 9.\) This was caused by temporary database locks due to inefficient queries that processed unexpectedly large database operations \(joins and index creations\). Immediate resolution was achieved by increasing the number of database sync workers and AWS Relational Database Service instances to work through the scoring backlog. Ongoing work is continuing, as we analyze and improve database queries in the affected areas.

As of 23:30 UTC, we are have resolved the delays in availability of scored sessions 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.

As of 22:45 UTC, we've seen no delays for more than 30 minutes. We will continue to monitor for a further 30 minutes before calling this resolved. Thanks to AWS Support for additional help. 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 22:00 UTC, we've made significant improvements in our async scoring queue, reducing delays by over 90% for the small subset of affected customers, and are actively working with AWS to resolve the issue. We will continue with our degraded performance status until the queue is clear but, as previously stated, if your team is unaffected, please ignore this 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 21:00 UTC, we are actively investigating delays affecting asynchronous scoring in the US East 1 region. This issue is affecting a very small number of customers, so if you are not seeing delays you can disregard this notice. 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:15 UTC, we are continuing to investigate scoring delays in our US East 1 region. Our investigation to date seems to indicate that this is affecting a very small number of customers, so it's expected that most are not seeing delays and can disregard this notice. 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 17:45 UTC, we are now seeing delays affecting scoring of some submitted sessions in the US East 1 region, which remains in degraded performance status. 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 17:45 UTC, we are continuing to investigate delays affecting scoring of some submitted sessions in the US East 1 region and are reclassifying as degraded performance 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 17:15 UTC, we are seeing a slight build-up in asynchronous scoring queue messages in US East 1. No known ill-effects have been detected so far, but we will keep this incident active until our investigation is complete. 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:30 UTC, we have resolved the issue affecting scoring delays in the US East 1 (VA) region. 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 15:00 UTC, the scoring queue continues to be stable at (for all intents and purposes) zero, with sessions scoring too quickly to create a backlog. Learnosity Support and Systems Engineering teams will continue to monitor for 30 more minutes and then, in the absence of any further delays, mark this issue resolved.

As of 14:45 UTC, scoring throughput has returned to normal. Learnosity Support and Systems Engineering teams are continuing to monitor the issue, and will follow on with an update and resolution as soon as possible.

As of 14:30 UTC, we are continuing to investigate an uptick in scoring delays that are affecting the US East 1 (VA) region. 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, we are currently experiencing minor delays in scoring of submitted sessions affecting the US East 1 region (VA). Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

**All Learnosity APIs currently operational** As of 1:30AM UTC, We are have resolved the AWS issue causing degraded performance or slowdown of a small percentage of requests (circa 5%) in our APIs in Virginia region. As of around 1:00AM UTC, AWS have experienced network connectivity issues in the Virginia region affecting our APIs. Root cause was a power issue on AWS side. We'll continue to monitor this on our side. Please reach out if you have any questions or concerns.

As of 22:30 UTC, AWS's resolution seems to have addressed all knock on effects to our authoring site. Everything is functioning normally again.

As of 21:40 UTC, the currently running AWS outage is affecting performance of the Learnosity authoring site. When available throughout this AWS outage, ALL LEARNOSITY APIs ARE FULLY FUNCTIONAL. However, AWS is currently trying to resolve connectivity and Elastic Load Balancing issues. Because authors can't reach our authoring site, we have chosen to mark authoring as degraded performance *as a visual cue for our StatusPage subscribers.* However, this only seems to be affecting authoring (the AWS incident is in US-WEST-2, for context), and Learnosity APIs are otherwise healthy. Learnosity Support and Systems Engineering teams are continuing to monitor the AWS outage the issue, and will follow on with an update and resolution as soon as possible

As of 20:20 UTC, the currently running AWS outage is affecting performance of the Learnosity authoring site. When available through the AWS outage, ALL LEARNOSITY APIs ARE FULLY FUNCTIONAL. However, we have chosen to mark authoring as degraded performance as a visual cue for our StatusPage subscribers. At present, this only seems to be affecting authoring, as the AWS incident is in US-WEST-2. Learnosity Support and Systems Engineering teams are continuing to monitor the AWS outage the issue, and will follow on with an update and resolution as soon as possible.

**All Learnosity APIs currently operational** We are seeing slight knock-on effects due to a currently ongoing AWS issue: 31 Aug 2021 11:25 PDT https://status.aws.amazon.com/ We're experiencing occasional, seemingly momentary latency and will continue to monitor the situation.

As of 4:15 UTC, we have seen session creation in the IE region operating at normal levels without delay and are closing this issue. 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.

As of 4:00 UTC, increased scale for session creation has reduced delays in the IE region and we will continue to monitor the situation. 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 3:45 UTC, we are continuing to investigate delays creating session records via Data API in the IE region. All other services continue to function normally. Learnosity Support and Systems Engineering teams are continuing to investigate the issue, and will follow on with an update and resolution as soon as possible.

As of 2:45 UTC, we are experiencing delays creating session records via the Data API in the IE region. This affects session creation via Data API only and no other services appear to 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.

As of 8:15 UTC, we are no longer seeing any affected assessment sessions in the IE region and will close this issue.. 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 7:45 UTC, we're no longer seeing affected sessions, but are continuing to monitor the situation. Learnosity Support and Systems Engineering teams will follow on with further updates as soon as possible.

As of 7:00 UTC, we are only seeing very occasional delays in assessment or session availability. 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 6:10 UTC, we are seeing intermittent failures in our internal monitoring when initializing assessments, and possibly delays retrieving existing session information, affecting the IE region. This appears to be very intermittent, so this may not affect end-users 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:00 UTC, we are have resolved the issues affecting the availability of session information in US East 1. Learnosity's asynchronous scoring mechanism ensured there was no data loss, and all sessions waiting to be scored were scored more than an hour ago. In the subsequent monitoring phase, there have been no further delays and everything is operating 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:15 UTC, session availability continues to be performant. We will monitor the situation for a short period before resolving the incident 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 17:00 UTC, session availability has returned to normal in US East 1. 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:30 UTC, we are continuing to investigating possible delays affecting the availability of newly scored session data in US East 1. We are escalating to Degraded Performance status and continuing to investigate. 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:15 UTC, We are currently investigating possible delays affecting the availability of newly scored session data in US East 1>. At the moment, this is a proactive alert. This may affect the Data API and/or Reports API and does not appear to be affecting customers. 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 00:45 UTC, we are closing this proactive status update, having felt no effect from AWS Network Load Balancing issues. Thanks for your attention, and sorry for any concerns this may have raised. Please reach out if you have any questions or concerns.

As of 21:29 UTC, We are tracking a notice from Amazon Web Services regarding issues with network load balancers in 3 of 11 availability zones in the us-east-1 region. At this time, we have seen no impact on Learnosity but are raising the issue for transparency. We will continue to monitor both our own services and updates from AWS. https://status.aws.amazon.com/ 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 23:10 UTC, we have resolved the delays affecting authoring and availability of session information (Reports and Data API). We have been monitoring for an additional 30 minutes and all remains at pre-delay levels. Learnosity Support and Systems Engineering teams will follow up with a post mortem once we have completed root cause analysis and finalizsed any next steps or preventative measures required. Please reach out if you have any questions or concerns.

As of 22:25 UTC, all services appear to be returning to normal, and we are continuing to investigate and monitor. 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 22:00 UTC, we are continuing to investigate delays affecting authoring in all regions. Reports API and Data API delays may also be occurring for some customers. 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, we are experiencing issues affecting authoring in all regions. The author site and Author API are experiencing delays loading items. 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 20:00 UTC, all APIs continue to behave normally and we are closing this incident report. 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 19:50 UTC, we've seen no authoring save delays of any note. We will move to monitoring mode for 10 minutes, after which we'll close this incident barring any evidence to indicate otherwise. 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:40 UTC, we’ve replaced an authoring slave db replica instance that was exhibiting intermittent delays, as a precautionary measure. 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:05 UTC, we are seeing intermittent delays when trying to save authored content. This appears to be isolated in scope and, thus far, having no significant effect on authors. Nevertheless, we are escalating the status of this issue and will update when we know more. 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 18:40 UTC, we're seeing no further instances of the intermittent delays in saving items. All APIs remain operational. We will continue to monitor the situation for a period and either update or close this status incident soon. 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 18:30 UTC, we are currently monitoring possible degraded performance affecting the saving of authoring content in all regions. At the moment, we are merely monitoring for a potential issue and will update this status report as we learn more. 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 21:00 UTC, Learnosity identified and corrected an issue causing intermittent latency affecting next-item selection during adaptive testing in us-east-1. Learnosity isolated and restricted database optimization tasks that were causing intermittent degraded performance affecting adaptive endpoints. Elevated connections to the DB were reduced to normal operating levels, eliminating the unexpected latencies. This issue has been resolved and a fix identified to prevent this from occurring again. Please contact Support if you have any additional questions.

As of 21:00 UTC, we are have resolved the intermittent latency issue affecting next-item selection during adaptive testing in us-east-1. Adaptive services continue to operate 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 20:43 UTC, we have implemented optimizations to eliminate the previously observed latency when selecting items during adaptive testing in us-east-1. Learnosity Support and Systems Engineering teams will continuing to actively monitor the issue, and will follow on with an update and resolution as soon as possible.

As of 20:31 UTC, we are testing an optimization that is addressing today's intermittent latency experienced today during adaptive assessment. Adaptive item selection is currently operating at optimal levels. 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 investigating Intermittent latency affecting next-item selection during adaptive testing in us-east-1. At present, only select configurations are affected, but we are continuing to test widely. 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 21:06 UTC, we are have resolved the issue affecting dispatch of Firehose messages in us-east-1. All services should be fully operational now. 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 20:54 UTC, all systems are operational with minimal to no delays in session results for affected custoemrs. Learnosity Support and Systems Engineering teams are continuing to monitor the issue, and will follow on with an update and resolution as soon as possible.

As of 18:52 UTC, Firehose appears to be functioning normally. We are continuing to investigate possible scoring delays affecting a small number of customers. 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 still investigating delays affecting Firehose messages, slower response times for the Data and Reports APIs, affecting a small number of customers. 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 18:00 UTC, we are investigating delays affecting Firehose Submission Responses messages affecting a small number of customers 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.

As of 07:50 PST, AWS have updated that they have restored all kinesis traffic and resolved error rates, with immediate actions in place to prevent reoccurrence. As a result, Learnosity will mark this issue as resolved, and will update with any further information or postmortem should any subsequent information from AWS shed light on route causes, or mitigation strategies.

We are continuing to monitor for any further issues.

As of 06:00am UTC, AWS have reported resolution for the service outage affecting the Kinesis stream, EventBridge and other related services though recovery efforts on their part remain ongoing. * Events API - Available * Firehose Service - Available * Live Progress reporting - Available Learnosity systems are now fully operational though our Support and Engineering teams will continue to monitor for further issues, many thanks for your patience and understanding.

As of 12:50 am UTC, Learnosity continues to monitor steady improvements with the AWS service outage affecting the Kinesis stream and EventBridge, as well as other related services. We are delaying calling this resolved until Kinesis has recovered, though only the following Learnosity services are impacted to varying degrees: * Events API - Unavailable * Firehose Service - Unavailable * Live Progress reporting - Unavailable The following systems continue to work reliably: * Authoring - Available * Assessment - Delivery and capture of student assessments - Available * Analytics - Reporting - Available (except live progress and firehose) Learnosity Support and Systems Engineering teams are diligently monitoring the issue, and will follow on with an update and resolution as soon as possible. Thank you for your patience and understanding.

As of 10:50 pm UTC, we continue to monitor the AWS outages. Services with knock on effects impacting Learnosity, such as EvenBridge and Kinesis, have started to recover, and we've thus far seen no significant impact from other services. Our infrastructure team has successfully managed scaling when required, and we've had no reports of CloudFront failures. Because Firehose and the Events API (including Live Progress reporting) may still experience delays until the AWS issues are resolved, we will continue to monitor. Learnosity Support and Systems Engineering teams are continuing to be vigilant, and will follow on with an update and resolution as soon as possible.

As of 8:28 UTC, we are continuing to monitor the AWS Kinesis incident that is ongoing. Our current status is as follows. Affected areas: * Events API - Unavailable * Firehose Service - Unavailable * Live Progress reporting - Unavailable The following systems are all working reliably - though we are observing reduced traffic as many of our customers are also affected by the AWS issue. Unaffected areas: * Authoring - Available * Assessment - Delivery and capture of student assessments - Available * Analytics - Reporting - Available (except live progress and firehose) 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. Full details available here also: https://status.learnosity.com/

As of 6:52 UTC, Learnosity continues to monitor the widespread AWS service degradation. Note that, while CloudFront has been added to the list of affected AWS services, only customer reporting is affected, not content delivery. Similarly, our infrastructure team is personally monitoring traffic to mitigate any affect on autoscaling. Only Learnosity's Firehose and the Events API have been affected this far, and all other APIs and services are operating normally. 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. (Retriggered to send notifications.)

As of 6:52 UTC, Learnosity continues to monitor the widespread AWS service degradation. Note that, while CloudFront has been added to the list of affected AWS services, only customer reporting is affected, not content delivery. Similarly, our infrastructure team is personally monitoring traffic to mitigate any affect on autoscaling. Only Learnosity's Firehose and the Events API have been affected this far, and all other APIs and services are operating normally. 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.

As of 4:06 UTC, AWS issues with Kinesis continue, but effects appear to be limited to Learnosity's Firehose and Event Bus services. Basic events, scoring, and availability of session data is functioning normally, as are all other Learnosity services such as authoring, and delivery of assessments. We are again revising our degraded performance status to apply only to Firehose and Event Bus use. Learnosity Support and Systems Engineering teams are continuing to monitor the issue, and will follow on with an update and resolution as soon as possible.

As of 3:13 UTC, continuing AWS issues may start to cause delays in availability of session information for all, not just those using Firehose. 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 2:58 UTC, AWS is reporting increased error rates in Kinesis Data Streams APIs in the US-EAST-1 Region. Learnosity expects this to have an effect on Learnosity Firehose, and possibly Events API, users, so we're moving proactively to alert for degraded performance in these areas. Note that the listed availability of Session Information is currently limited to Firehose users. No other functionality is expected to be affected at the moment. All other authoring, assessment, and analytics services 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 2:45 UTC, we are currently looking at possible impact of reported degradation of AWS Kinesis performance. As of this posting, all Learnosity services are fully operational. We are looking for possible delays in Firehose messages that may be caused by this AWS issue. Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.