Histórico de interrupções do Learnosity

1. 26 Here 2026 da 18:05 UTCinvestigating

   A partir das 17:50 UTC, estamos passando por problemas que afetam o Item Pools em todas as regiões. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas estão investigando ativamente o problema, e seguirão com uma atualização e resolução o mais rápido possível.

2. 26 Here 2026 da 18:34 UTCinvestigating

   A partir das 18:30 UTC, estamos investigando desempenho degradado ao criar e editar o Item Pools. Também estamos investigando uma questão tangencial ainda não confirmada, possivelmente afetando a criação e edição de pacotes de avaliação de dispositivos locais. Todas as outras APIs nas pilhas de criação, avaliação e análise estão funcionando normalmente. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas continuam a investigar ativamente o problema, e seguirão com uma atualização e resolução o mais rápido possível.

3. 26 Here 2026 da 19:01 UTCinvestigating

   A partir das 19:00 UTC, continuamos a investigar o desempenho degradado ao criar ou editar pacotes de avaliação de dispositivos locais do Item Pools orx. Todas as outras APIs nas pilhas de criação, avaliação e análise estão funcionando normalmente. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas continuam a investigar ativamente o problema, e seguirão com uma atualização e resolução o mais rápido possível.

4. 26 Here 2026 da 19:31 UTCmonitoring

   A partir das 19:30 UTC, a criação do Item Pool e da Avaliação Local de Dispositivos tem observado um rendimento normal por aproximadamente 30 minutos. Entraremos agora num período adicional de monitorização para garantir a estabilidade. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas continuam a investigar ativamente o problema, e seguirão com uma atualização e resolução o mais rápido possível.

5. 26 Here 2026 da 20:10 UTCresolved

   A partir de 20:10 UTC, não vimos mais problemas com a criação ou atualização de pacotes de avaliação de dispositivos locais. Estamos a resolver este incidente e vamos continuar a investigar a causa raiz do desempenho degradado. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas seguirão com uma post mortem, uma vez que tenhamos concluído a análise da causa raiz e finalizado os próximos passos ou medidas preventivas necessárias. Por favor, contacte se tiver dúvidas ou preocupações.

Traduzido automaticamente da atualização oficial do incidente.

1. 20 Here 2026 da 14:16 UTCinvestigating

   A partir das 13:20 UTC, começamos a ver atrasos de pontuação com nosso serviço de pontuação matemática aprimorada na região EUA-Leste-1. Nenhuma perda de dados foi observada e todas as sessões foram pontuadas. Como efeito knock-on, o endpoint de pontuação da API de dados está tendo problemas de disponibilidade intermitentes. Não foi afectada a produção de autoria ou avaliação. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas estão investigando ativamente o problema, e seguirão com uma atualização e resolução o mais rápido possível.

2. 20 Here 2026 da 15:04 UTCinvestigating

   A partir das 15:00 UTC, ainda estamos investigando o desempenho degradado de curta duração do nosso serviço de pontuação matemática aprimorada, mas não temos visto erros ou atrasos significativos por mais de uma hora. O backlog das sessões que aguardam a pontuação foi limpo rapidamente, e as submissões continuam a ser pontuadas normalmente. Todas as outras APIs permanecem não afetadas. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas continuam a investigar ativamente o problema, e seguirão com uma atualização e resolução o mais rápido possível.

3. 20 Here 2026 da 15:51 UTCmonitoring

   A partir das 15:45 UTC, as medidas de mitigação mantiveram a fila de submissão livre e a pontuação continuou a funcionar normalmente. As submissões recebidas durante o período de desempenho degradado foram captadas e nenhum dado foi perdido. Todas as outras APIs permanecem operacionais. Continuamos a investigar a causa raiz e vamos partilhar um incidente após a morte quando a nossa investigação estiver concluída. Entretanto, estamos a entrar num período de monitorização adicional para confirmar a estabilidade contínua antes de encerrar o incidente.

4. 20 Here 2026 da 18:17 UTCresolved

   A partir das 18:00 UTC, após um longo período de monitoramento adicional sem mais problemas, estamos resolvidos este incidente que afeta pontuação matemática aprimorada em EUA-Leste-1. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas seguirão com uma post mortem, uma vez que tenhamos concluído a análise da causa raiz e finalizado os próximos passos ou medidas preventivas necessárias. Por favor, contacte se tiver dúvidas ou preocupações.

5. 27 Here 2026 da 13:27 UTCpostmortem

   # Sistemas e Regiões Afetados Em 20 de outubro de 2026, a Learnosity experimentou atrasos de pontuação e falhas intermitentes de solicitação afetando a pontuação de matemática aprimorada em US-East-1. O impacto do cliente começou em aproximadamente 13:06 UTC e terminou em 13:47 UTC, com duração de aproximadamente 41 minutos. As solicitações de pontuação afetadas experimentaram mais tempo do que os tempos normais de processamento, e algumas solicitações diretas para o endpoint de pontuação da API de dados retornaram erros. Para as sessões salvas através da API dos Itens, as solicitações de pontuação afetadas foram em fila de espera e repetidas, resultando em disponibilidade de pontuação atrasada em vez de falhas de pontuação. Avaliações sem questões e serviços de matemática em outras regiões não foram afetadas. Investigação Nossa investigação identificou um padrão específico de solicitações de pontuação que resultou em tempos de processamento inesperadamente elevados. Isso reduziu a capacidade disponível para processar outras solicitações de pontuação, causando atrasos e intervalos intermitentes. A questão foi associada à forma como determinadas entradas de pontuação foram processadas, em vez de um aumento inesperado no volume de solicitação global. # # Resolução A pontuação voltou ao normal às 13:47 UTC. Em 15:12 UTC, engenheiros de Learnosity implementaram isolamento de tráfego adicional para evitar que a carga de trabalho de pontuação afetada impactasse as operações de pontuação para outros clientes. # # Prevenção A aprendizagem implementou mudanças para reduzir o consumo desnecessário de recursos e melhorar a recuperação de pedidos de pontuação afetados. Estão em curso novas melhorias para reforçar a validação de pedidos de pontuação, melhorar as salvaguardas de processamento e impedir que cargas de trabalho de pontuação individuais afetem o serviço em geral. As medidas adicionais de isolamento permanecerão em vigor enquanto estas melhorias forem concluídas e a sua eficácia verificada.

Traduzido automaticamente da atualização oficial do incidente.

1. 8 Here 2026 da 13:40 UTCinvestigating

   A partir das 13:00 UTC, estamos experimentando problemas remapping sunset API versões v2024.1.LTS para as últimas versões LTS em todas as regiões. Isso só afeta um número muito pequeno de clientes que ainda estão presos ao v2024.1.LTS, que chegou ao fim da vida em março de 2026. Nenhuma outra versão da API é afetada. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas estão investigando ativamente o problema, e seguirão com uma atualização e resolução o mais rápido possível.

2. 8 Here 2026 da 13:47 UTCinvestigating

   A partir de 13:40> UTC, estamos redirecionando versões v2024.1.LTS e APIs estão se tornando acessíveis como atualização de caches. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas continuam a investigar ativamente o problema, e seguirão com uma atualização e resolução o mais rápido possível.

3. 8 Here 2026 da 14:20 UTCinvestigating

   A partir das 14:00 UTC, v2024.1.LTS está remapping com sucesso para a última versão LTS em regiões AMER, incluindo US-East-1 (VA) e US-West-2 (OR). Todas as APIs devem ser acessíveis nessas regiões. Estamos atualmente remapping nas regiões da EMEA e APAC. O acesso direto às versões da API ativa permanece operacional. Este problema está agora apenas afetando a versão remapping para um microset de clientes nas regiões EMEA e APAC preso à versão de API do sunsetted v2024.1.LTS, que chegou à EOL em março de 2026. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas continuam a investigar ativamente o problema, e seguirão com uma atualização e resolução o mais rápido possível.

4. 8 Here 2026 da 15:15 UTCresolved

   A partir das 15:00 UTC, v2024.1.LTS está remapping com sucesso em todas as regiões. Usando este texto de versão EOL/sunset deve acessar todas as APIs. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas seguirão com uma post mortem, uma vez que tenhamos concluído a análise da causa raiz e finalizado os próximos passos ou medidas preventivas necessárias. Por favor, contacte se tiver dúvidas ou preocupações.

Traduzido automaticamente da atualização oficial do incidente.

1. 2 Here 2026 da 18:08 UTCinvestigating

   A partir das 16:45 UTC, começamos a experimentar um número muito baixo de atrasos de pontuação com nosso serviço de pontuação matemática aprimorada na região EUA-Leste-1. Todas as sessões foram pontuadas e nenhuma perda de dados ocorreu. Nenhuma outra API é afetada. Estamos a investigar atrasos em curso limitados a este serviço. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas estão investigando ativamente o problema, e seguirão com uma atualização e resolução o mais rápido possível.

2. 2 Here 2026 da 18:30 UTCidentified

   A partir das 18:30 UTC, identificamos um problema de escala para o serviço de pontuação matemática aprimorada e estamos trabalhando para resolver o problema. Todas as sessões continuam a ser capturadas sem perda de dados e todas as outras APIs estão funcionando normalmente. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas continuam a investigar ativamente o problema, e seguirão com uma atualização e resolução o mais rápido possível.

3. 2 Here 2026 da 19:10 UTCmonitoring

   A partir das 19:00 UTC, não vimos atrasos no serviço de pontuação matemática aprimorada há algum tempo e agora entraremos em uma fase de monitoramento. Vamos continuar a monitorar por 30 minutos antes de resolver o problema. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas continuam a investigar ativamente o problema, e seguirão com uma atualização e resolução o mais rápido possível.

4. 2 Here 2026 da 19:52 UTCresolved

   A partir das 19:45 UTC, resolvemos o problema que afeta a pontuação matemática melhorada na região EUA-Leste-1. Todas as APIs e serviços estão funcionando normalmente. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas seguirão com uma post mortem, uma vez que tenhamos concluído a análise da causa raiz e finalizado os próximos passos ou medidas preventivas necessárias. Por favor, contacte se tiver dúvidas ou preocupações.

5. 27 Here 2026 da 01:24 UTCpostmortem

   ** ** Sistemas e Regiões Afetados Em 2 de outubro de 2026, Learnosity experimentou erros intermitentes de pontuação e timeouts afetando tipos de perguntas matemáticas em US-East-1. O impacto do cliente começou em aproximadamente 16:34 UTC e terminou em 18:47 UTC, com duração de aproximadamente 2 horas e 13 minutos. Pedidos afetados podem sofrer atrasos de até 40 segundos antes de falhar. Outras regiões não foram afetadas. ## **Investigação# O incidente ocorreu quando a demanda no serviço de pontuação matemática ultrapassou a capacidade disponível. Embora as melhorias de capacidade e de escala tivessem sido introduzidas na sequência de um incidente anterior, o serviço encontrou um limite adicional na sua configuração de rede que impediu que outras instâncias fossem providas. O impacto foi agravado por cálculos lentos que ocuparam instâncias mais tempo do que o previsto, uma vez que os prazos de cálculo não foram aplicados de forma fiável sob carga pesada. Em conjunto, essas condições impediram o serviço de escalar o suficiente para lidar com a demanda. **Resolução** Engenheiros de aprendizagem restauraram o serviço movendo o serviço de pontuação para uma configuração de rede com capacidade de escala adicional e aumentando os recursos de computação alocados a cada instância. Essas mudanças permitiram que o serviço se recuperasse, com erros de pontuação limpando por 18:47 UTC. * * Prevenção * A learnosity atualizou o mecanismo de aplicação do limite de tempo de cálculo para terminar de forma confiável cálculos lentos sob carga pesada. Os controlos sanitários também foram separados do processamento de cálculo para evitar a substituição desnecessária de instâncias. O serviço agora opera com computação adicional e capacidade de rede. Outras melhorias arquitetônicas estão em andamento para impedir que a capacidade de rede limite a escala futura, e estamos avaliando prazos de cálculo mais curtos para reduzir o impacto de cálculos anormalmente lentos.

Traduzido automaticamente da atualização oficial do incidente.

1. 11 Gwengolo 2026 da 18:19 UTCinvestigating

   A partir das 17:00 UTC, estamos atualmente investigando questões intermitentes menores com pontuação na região EUA-Leste-1. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas estão investigando ativamente o problema, e seguirão com uma atualização e resolução o mais rápido possível.

2. 11 Gwengolo 2026 da 18:30 UTCinvestigating

   A partir das 18:30 UTC, todas as APIs permanecem operacionais e estamos monitorando a eficiência de pontuação. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas continuam a investigar ativamente o problema, e seguirão com uma atualização e resolução o mais rápido possível.

3. 11 Gwengolo 2026 da 19:42 UTCidentified

   A partir das 19:30 UTC, confirmamos que este é um problema esporádico com pontuação de três tipos de perguntas matemáticas aprimoradas apenas. Essas tentativas de pontuação têm sucesso em tentar novamente e nenhuma outra API é afetada. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas continuam a investigar ativamente o problema, e seguirão com uma atualização e resolução o mais rápido possível.

4. 11 Gwengolo 2026 da 20:53 UTCmonitoring

   A partir das 20:45 UTC, melhoramos o tratamento dos pedidos iniciais de pontuação de EMS e repetições e agora entraremos em uma fase de monitoramento de 60 minutos. Todas as APIs continuam a funcionar normalmente. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas continuam a investigar ativamente o problema, e seguirão com uma atualização e resolução o mais rápido possível.

5. 11 Gwengolo 2026 da 21:44 UTCresolved

   A partir das 21:45 UTC, respostas de tipo de pergunta de pontuação matemática aprimorada estão marcando normalmente na região EUA-East-1, todas as APIs estão funcionando normalmente, e estamos fechando este incidente. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas seguirão com uma post mortem, uma vez que tenhamos concluído a análise da causa raiz e finalizado os próximos passos ou medidas preventivas necessárias. Por favor, contacte se tiver dúvidas ou preocupações.

6. 27 Here 2026 da 01:23 UTCpostmortem

   ** ** Sistemas e Regiões Afetados Em 11 de setembro de 2026, Learnosity experimentou erros intermitentes de pontuação e timeouts afetando tipos de questões matemáticas em US-East-1. O impacto do cliente começou aproximadamente às 17:00 UTC e terminou às 21:45 UTC, com duração aproximada de 4 horas e 45 minutos. Outros tipos de perguntas continuaram a marcar normalmente, e outras regiões não foram afetadas. A maioria dos pedidos falhou ao tentar novamente. ## **Investigação# O incidente foi causado pela capacidade insuficiente no serviço de pontuação matemática após um aumento da demanda nas semanas anteriores. O serviço alcançou o número máximo de instâncias configurado e não conseguiu escalar mais para acomodar a carga. Isto foi agravado por recursos de computação limitados por instância e cálculos lentos que ocuparam instâncias mais tempo do que o pretendido. Sob carga pesada, o prazo de cálculo não foi aplicado de forma confiável, e instâncias ocupadas poderiam falhar em exames de saúde e ser substituídas, reduzindo ainda mais a capacidade disponível. **Resolução** Engenheiros de aprendizado restauraram o serviço aumentando o número de instâncias em execução e aumentando o limite máximo de instância. As operações de pontuação normal foram retomadas por 21:45 UTC, e todos os pedidos restantes de pontuação em fila foram processados por 23:17 UTC. Em 14 de setembro, mudanças adicionais de configuração foram implantadas para aumentar os recursos de computação, melhorar o escalonamento automático e reduzir a substituição de instância desnecessária. * * Prevenção * A aprendizagem aumentou a capacidade de pontuação, aumentou os limites de instância e melhorou a escala automática com base na utilização do processador. Os controlos de saúde foram separados do processamento de cálculo para evitar que as instâncias ocupadas fossem incorretamente identificadas como não saudáveis. Nós também melhoramos o tempo de cálculo limite de execução e monitoramento expandido e alerta para utilização de recursos, tempos de resposta e erros de pontuação. Estão em curso outros trabalhos para reforçar a capacidade de escala da rede e avaliar prazos de cálculo mais curtos.

Traduzido automaticamente da atualização oficial do incidente.

1. 24 Gouere 2026 da 12:16 UTCinvestigating

   Estamos cientes de um problema AWS em curso que afeta a região US-West-2 (OR), que pode causar problemas de conectividade intermitentes ao acessar o ambiente de Criação de Aprendizagem. Estamos monitorando ativamente a situação e forneceremos atualizações à medida que estiverem disponíveis. Neste momento, o impacto para os clientes de Learnosity é breve e intermitente e limitado à autoria. Avaliações, e outras APIs, estão se comportando normalmente. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas estão investigando ativamente o problema, e seguirão com uma atualização e resolução o mais rápido possível.

2. 24 Gouere 2026 da 12:28 UTCmonitoring

   A partir das 11:02 UTC, a Learnosity começou a ver alertas de monitor de curto prazo intermitentes ao acessar o site do autor da Learnosity. Nenhuma outra funcionalidade foi afetada, e os alertas de Learnosity cessaram às 11:11 UTC. Às 11:40 UTC, AWS relatou serviço degradado em US-West-2 (OR). Às 11:56 UTC, a AWS relatou que seus sistemas estavam se recuperando. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas continuam a monitorar ativamente o problema, e seguirão com uma atualização e resolução o mais rápido possível.

3. 24 Gouere 2026 da 12:35 UTCmonitoring

   Às 12:30 UTC, a AWS relatou que identificou e corrigiu o problema, e que a recuperação continua. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas monitorarão o problema por mais 30 minutos e seguirão com uma atualização e resolução o mais breve possível.

4. 24 Gouere 2026 da 13:02 UTCresolved

   A partir das 13:00 UTC, estamos chamando esta questão resolvido. Os sistemas AWS estão a recuperar e a autoria da Learnosity não foi afectada durante 50 minutos. As equipes de Suporte de Aprendizagem e Engenharia de Sistemas seguirão com uma post mortem, uma vez que tenhamos concluído a análise da causa raiz e finalizado os próximos passos ou medidas preventivas necessárias. Por favor, contacte se tiver dúvidas ou preocupações.

5. 24 Gouere 2026 da 13:03 UTCpostmortem

   Sistemas e Regiões Afetados Em 2026-07-24, a Learnosity experimentou curtos períodos de tempo intermitentes que afetaram o acesso ao site do autor da Learnosity devido a [um incidente de rede na região AWS US-West-2 \(OR\)](https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-west-2::event/MULTIPLE SERVICES/AWS MULTIPLE SERVICES OPERATIONAL ISSUE/AWS MULTIPLE SERVICES OPERATIONAL ISSUE 83A36 24C89B493A6). O impacto do cliente no aprendizado começou em aproximadamente 11:02 UTC e terminou em 11:11 UTC. A AWS posteriormente completou a reparação e formalmente encerrou seu incidente regional em 12:12 UTC. A duração total do possível impacto para os clientes da Learnosity foi de aproximadamente 9 minutos. Investigação A aprendizagem recebeu um alerta interno às 11:02 UTC que o serviço na região de OR foi afetado e imediatamente iniciou uma investigação. A investigação inicial não encontrou evidência de degradação de um serviço de aprendizagem. Outras investigações identificaram intervalos intermitentes que afetam o acesso ao site do autor da Learnosity. A aprendizagem confirmou com a AWS que havia sido identificado e iniciado um problema que afectava a sua infra-estrutura de rede na região. Resolução Tempos intermitentes que afetaram o site do autor da Learnosity cessaram até 11:11 UTC, e o AWS efetivamente resolveu o problema até 11:15 UTC. AWS relatou um breve evento de reconvergência que foi resolvido por 11:59 UTC, e oficialmente fechou o incidente em 12:12 UTC. Prevenção Nenhum sistema de aprendizagem contribuiu para este incidente. A monitorização e o alerta internos comportaram-se como esperado.

Traduzido automaticamente da atualização oficial do incidente.

1. 17 Ebrel 2026 da 16:06 UTCinvestigating

   As of 16:00 UTC, we are currently experiencing a slowdown in availability of newly submitted submitted session results in the us-east-1 region. There is no data loss, all saves and submissions are being queued as designed, and the assessments stack remains operational. Delays may currently be experienced using the Data API to fetch session results, and the Reports API to display results. Other workflows that rely on the synchronous use of Data API results may also be affected. Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

2. 17 Ebrel 2026 da 16:21 UTCidentified

   As of 16:20 UTC, Learnosity has increased database performance and we are processing queued sessions rapidly. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

3. 17 Ebrel 2026 da 16:28 UTCmonitoring

   As of 16:25 UTC, we have resolved the slowdown in processing session results and all sessions are being scored normally. We will continue to monitor for a further 30 minutes before closing this incident report. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

4. 17 Ebrel 2026 da 17:58 UTCresolved

   As of 16:55 UTC, we are have resolved the degraded performance issue affecting availability of session data in us-east-1. Learnosity Support and Systems Engineering teams will follow up with a post mortem once we have completed root cause analysis and finalized any next steps or preventative measures required. Please reach out if you have any questions or concerns.

5. 4 Mae 2026 da 17:23 UTCpostmortem

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

1. 16 Ebrel 2026 da 14:08 UTCinvestigating

   As of 13:30 UTC, we are currently experiencing slow downs affecting the Live Progress report in the us-east-1 region. Atypical use of eventbus may also be affected, such as custom reports/implementations. Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

2. 16 Ebrel 2026 da 15:23 UTCresolved

   As of 14:30 UTC, the Live Progress report event degradation issue in the us-east-1 region has been resolved. Additional capacity processed the event load and these systems are operating normally. Brief additional latency during this scaling may have been introduced for users of Learnosity's premium Firehose feature, but we've seen no evidence that this affected customers. This, too, was resolved once scaling was complete. Learnosity Support and Systems Engineering teams will follow up with a post mortem once we have completed root cause analysis and finalized any next steps or preventative measures required. Please reach out if you have any questions or concerns.

3. 4 Mae 2026 da 14:39 UTCpostmortem

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

1. 4 Cʼhwevrer 2026 da 18:34 UTCidentified

   As of 18:30 UTC, we are currently experiencing an issue affecting assessment delivery in VA (us-east-1). Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

2. 4 Cʼhwevrer 2026 da 18:55 UTCmonitoring

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

3. 4 Cʼhwevrer 2026 da 19:15 UTCresolved

   As of 19:12 UTC, traffic has returned to normal and everything remains stable. We have resolved the incident affecting assessments in VA (us-east-1). Learnosity Support and Systems Engineering teams will follow up with a post mortem once we have completed root cause analysis and finalized any next steps or preventative measures required. Please reach out if you have any questions or concerns.

4. 10 Cʼhwevrer 2026 da 17:08 UTCpostmortem

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

1. 12 Genver 2026 da 17:06 UTCinvestigating

   As of 4:30 UTC, we are currently investigating an issue that may result in temporary session unavailability for a small number of US-only customers. We can confirm that no session data has been lost, and we are working to restore the affected sessions as quickly as possible. Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

2. 12 Genver 2026 da 17:52 UTCidentified

   As of 5:30 UTC, we've identified and corrected a load balancing configuration affecting database reads and writes for a very small number of US-only customers with consumers in the US-East-1 region. - All new sessions will behave as expected. - Read requests seeking data on sessions created prior to 23:00 UTC yesterday will also now behave correctly. - We are working on restoring sessions recently affected While all APIs continue to function normally, this update identifies service areas that may temporarily have limited access to recently saved or submitted sessions. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

3. 12 Genver 2026 da 19:10 UTCresolved

   As of 7:00 UTC, we've concluded our monitoring and confirmed that all new requests are behaving as expected. We are closing this record and will continue to work with affected customers directly to confirm that all recent sessions are accessible. Please reach out if you have any questions or concerns.

1. 20 Here 2025 da 14:53 UTCmonitoring

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

2. 20 Here 2025 da 15:30 UTCinvestigating

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

3. 20 Here 2025 da 18:13 UTCmonitoring

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

4. 20 Here 2025 da 19:02 UTCmonitoring

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

5. 20 Here 2025 da 19:32 UTCmonitoring

   As of 19:30 UTC, the error rate has fallen to 0.1% and continues to fall, we continue to steadily process the backlog of scoring messages. As of their latest update AWS has downgraded the severity of outage to "Impacted" but still list 109 services as affected. Learnosity Support and Systems Engineering teams are continuing to actively monitor the issue, and will follow on with an update and resolution as soon as possible.

6. 20 Here 2025 da 20:44 UTCmonitoring

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

7. 20 Here 2025 da 21:35 UTCresolved

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

1. 20 Here 2025 da 10:11 UTCmonitoring

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

2. 20 Here 2025 da 11:23 UTCresolved

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

1. 2 Here 2025 da 21:34 UTCinvestigating

   As of 21:15 UTC, Learnosity APIs are being impacted by a temporary outage from our Math partner, Desmos. Authoring or Editing content with Desmos questions or features, or initializing assessments that contain Desmos questions or features, can prevent the Author API or Items API from initializing. Specific reports that display question content, such as the Session Detail by Item report, can also fail to initialize Learnosity APIs are not otherwise impacted, so content that does not include Desmos features are not affected. Until we learn more, we will list APIs that may experience knock-on effects from this temporary Desmos outage. However, as most customers will not experience any issues, we will not list these APIs as down. Desmos and Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

2. 2 Here 2025 da 22:14 UTCmonitoring

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

3. 2 Here 2025 da 22:43 UTCresolved

   As of 22:42 UTC, all Learnosity APIs are continuing to function as expected in all regions, and we are declaring this issue resolved. Learnosity Support and Systems Engineering teams will follow up with a post mortem once we have completed root cause analysis and finalized any next steps or preventative measures required. Please reach out if you have any questions or concerns.

1. 19 Eost 2025 da 16:11 UTCinvestigating

   As of 3:40 UTC, we are experiencing degraded performance in our analytics stack affecting the availability of session data in US-East-1 for a subset of customers. This is affecting the Reports API and Data API. Neither authoring nor assessment stacks are affected, and there is no data loss. Submitted sessions are queueing for processing. Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

2. 19 Eost 2025 da 16:35 UTCinvestigating

   As of 4:30 UTC, we are continuing to investigate degraded performance in our Data and Reports APIs. Only availability of recently submitted session data is affected. Historic session data, as well as all other API stacks, remain unaffected. New submissions are persisting correctly with no data loss and these submission are being queued for scoring. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

3. 19 Eost 2025 da 17:34 UTCidentified

   (Note: We're correcting cited UTC times to the 24 hr format and will include both forms in this update only.) As of 5:30pm/17:30 UTC, we've identified a possible contributing cause for the degraded performance in our analytics stack. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

4. 19 Eost 2025 da 18:42 UTCidentified

   As of 18:30 UTC, initial remediation efforts have tripled the rate of queued session processing and we are continuing to work toward a full resolution. Access to recently submitted session results via the Data API and Reports API remains the only affected part of the Learnosity ecosystem. New submissions continue to be safely queued for scoring while the degraded performance remains. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

5. 19 Eost 2025 da 19:56 UTCidentified

   As of 19:30 UTC, we are now processing queued sessions rapidly and more than half of the backlog has already cleared.. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

6. 19 Eost 2025 da 20:35 UTCidentified

   As of 20:30 UTC, the scoring queue backlog is almost empty and new sessions will soon be processed without delay. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

7. 19 Eost 2025 da 21:05 UTCmonitoring

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

8. 19 Eost 2025 da 21:31 UTCresolved

   As of 21:30 UTC, we are have resolved the issue affecting availability of session data in US-East-1. Learnosity Support and Systems Engineering teams will follow up with a post mortem once we have completed root cause analysis and finalized any next steps or preventative measures required. Please reach out if you have any questions or concerns.

9. 19 Gwengolo 2025 da 19:14 UTCpostmortem

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

1. 8 Eost 2025 da 13:55 UTCinvestigating

   As of 13:40 UTC, we began investigating a possible issue affecting manual update jobs to session response scores, sessions statuses, and session metadata in the US-East-1 (VA) region. We saw a brief buildup in the queue for these jobs, the queue processed as expected, and is now empty. However, we're investigating further, out of an abundance of caution, to see if there are any unexpected causes for the short queue buildup. Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

2. 8 Eost 2025 da 13:57 UTCinvestigating

   As of 13:55 UTC, all manual update jobs have been executed and the jobs queue is empty. Requests to manually update session response scores, session statuses, and session metadata should execute as expected. We are still investigating possible reasons for the blip. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

3. 8 Eost 2025 da 14:19 UTCresolved

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

4. 8 Eost 2025 da 14:19 UTCpostmortem

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

1. 3 Meurzh 2025 da 13:48 UTCinvestigating

   As of 13:45 UTC, we are experiencing delays in availability of session information in US-East-1 Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

2. 3 Meurzh 2025 da 14:00 UTCinvestigating

   As of 14:00 UTC, we are still investigating an issue affecting the availability of session information in US-East-1. Both Data API and Reports API are experiencing extended delays and intermittent failures in returning session results. Authoring and Assessment APIs appear to be unaffected at this time and all session submissions are being successfully queued. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

3. 3 Meurzh 2025 da 15:06 UTCinvestigating

   As of 15:00 UTC, we are continuing to investigate the issue. Data and Reports API are still impacted. Assessment and Authoring APIs remain unaffected. Assessment submissions are being queued and will be processed as the system works through any backlog queue. Note that if the Data API or Reports API is used in a preliminary/synchronous assessment delivery workflow, this will likely have a knock-on affect when initializing assessments. Initializing any assessment API directly is unaffected at present. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

4. 3 Meurzh 2025 da 15:20 UTCmonitoring

   As of 15:15 UTC, all services have been restored. All queued messages have been processed and session information should now be available. Users of the Learnosity Firehose service will still see slight delays as messages are sent out for recently processed events. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

5. 3 Meurzh 2025 da 15:54 UTCresolved

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

6. 14 Meurzh 2025 da 16:31 UTCpostmortem

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

1. 9 Genver 2025 da 13:33 UTCinvestigating

   As of 13:30 UTC, We are currently investigating a possible performance degradation affecting Reports API and Data API results in US-East-1. Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

2. 9 Genver 2025 da 14:02 UTCinvestigating

   As of 14:00 UTC, Learnosity is working on identifying the cause of degraded performance in our Analytics APIs, Reports and Data. Authoring and Assessment stacks remain unaffected Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

3. 9 Genver 2025 da 14:13 UTCmonitoring

   As of 14:10 UTC, Learnosity has restored full service for all new requests to all Analytics APIs. We are monitoring stability and analyzing all queued requests. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

4. 9 Genver 2025 da 14:50 UTCresolved

   As of 14:50 UTC, after a further 60 minutes of issue-free monitoring, we are resolving this issue affecting availability of session information via our Analytics stack. Reports API and Data API are fully operational. Learnosity Support and Systems Engineering teams will follow up with a post mortem once we have completed root cause analysis and finalized any next steps or preventative measures required. Please reach out if you have any questions or concerns.

5. 14 Genver 2025 da 17:25 UTCpostmortem

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

1. 1 Here 2024 da 15:09 UTCinvestigating

   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.

2. 1 Here 2024 da 15:25 UTCidentified

   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.

3. 1 Here 2024 da 15:40 UTCmonitoring

   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.

4. 1 Here 2024 da 16:07 UTCresolved

   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.

1. 13 Gwengolo 2024 da 14:35 UTCinvestigating

   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.

2. 13 Gwengolo 2024 da 15:09 UTCidentified

   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.

3. 13 Gwengolo 2024 da 15:34 UTCmonitoring

   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.

4. 13 Gwengolo 2024 da 16:03 UTCresolved

   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.

1. 22 Mae 2024 da 18:27 UTCinvestigating

   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.

2. 22 Mae 2024 da 18:33 UTCinvestigating

   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.

3. 22 Mae 2024 da 18:47 UTCinvestigating

   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.

4. 22 Mae 2024 da 19:01 UTCmonitoring

   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.

5. 22 Mae 2024 da 19:42 UTCresolved

   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.