Historial de interrupciones de Learnosity

1. 26 de octubre de 2026 a las 18:05 UTCinvestigating

   A partir de las 17:50 UTC, estamos experimentando problemas que afectan a los grupos de artículos en todas las regiones. Los equipos de Apoyo a la Aprendizaje e Ingeniería de Sistemas están investigando activamente la cuestión y seguirán con una actualización y resolución lo antes posible.

2. 26 de octubre de 2026 a las 18:34 UTCinvestigating

   A partir de las 18:30 UTC, estamos investigando el rendimiento degradado al crear y editar Grupos de artículos. También estamos investigando un tema tangencial sin confirmar que podría afectar la creación y edición de paquetes de Evaluación de Dispositivos Locales. Todas las demás API en las pilas de autoría, evaluación y análisis funcionan normalmente. Los equipos de Apoyo a la Aprendizaje e Ingeniería de Sistemas continúan investigando activamente la cuestión y seguirán con una actualización y resolución lo antes posible.

3. 26 de octubre de 2026 a las 19:01 UTCinvestigating

   A partir de las 19:00 UTC, continuamos investigando el rendimiento degradado al crear o editar paquetes Item Pools orx Local Device Assessment. Todas las demás API en las pilas de autoría, evaluación y análisis funcionan normalmente. Los equipos de Apoyo a la Aprendizaje e Ingeniería de Sistemas continúan investigando activamente la cuestión y seguirán con una actualización y resolución lo antes posible.

4. 26 de octubre de 2026 a las 19:31 UTCmonitoring

   A partir de las 19:30 UTC, Piscina de Artículos y Evaluación de Dispositivos Locales ha visto un rendimiento normal durante aproximadamente 30 minutos. Entraremos ahora en un período adicional de vigilancia para garantizar la estabilidad. Los equipos de Apoyo a la Aprendizaje e Ingeniería de Sistemas continúan investigando activamente la cuestión y seguirán con una actualización y resolución lo antes posible.

5. 26 de octubre de 2026 a las 20:10 UTCresolved

   A partir de 20:10 UTC, no hemos visto más problemas con la creación o actualización del paquete de Evaluación de Dispositivos Locales o Piscina de Artículos. Estamos resolviendo este incidente y seguiremos investigando la causa raíz de la actuación degradada. Los equipos de soporte de aprendizaje y ingeniería de sistemas seguirán con un post mortem una vez que hayamos completado el análisis de causas profundas y hayamos finalizado los próximos pasos o las medidas preventivas necesarias. Por favor contacte si tiene alguna pregunta o preocupación.

Traducido automáticamente desde la actualización oficial del incidente.

1. 20 de octubre de 2026 a las 14:16 UTCinvestigating

   A partir de las 13:20 UTC, comenzamos a ver retrasos de puntuación con nuestro servicio de Enhanced Math Scoring en la región estadounidense-este-1. No se ha observado ninguna pérdida de datos y todas las sesiones se han marcado en última instancia. Como efecto de golpe, el punto final de conexión de Data API está experimentando problemas de disponibilidad intermitente. No se ha afectado la entrega de la autorización ni la evaluación. Los equipos de Apoyo a la Aprendizaje e Ingeniería de Sistemas están investigando activamente la cuestión y seguirán con una actualización y resolución lo antes posible.

2. 20 de octubre de 2026 a las 15:04 UTCinvestigating

   A partir de las 15:00 UTC, todavía estamos investigando el rendimiento degradado de corta duración de nuestro servicio de Enhanced Math Scoring, pero no han visto errores o retrasos significativos durante más de una hora. El atraso de las sesiones en espera de la puntuación se despejó rápidamente, y las presentaciones siguen siendo anotadas normalmente. Todas las demás API siguen sin ser afectadas. Los equipos de Apoyo a la Aprendizaje e Ingeniería de Sistemas continúan investigando activamente la cuestión y seguirán con una actualización y resolución lo antes posible.

3. 20 de octubre de 2026 a las 15:51 UTCmonitoring

   A partir de las 15:45 UTC, las medidas de mitigación han mantenido claramente la cola de presentación, y la puntuación ha seguido funcionando normalmente. Las comunicaciones recibidas durante el período de ejecución degradada fueron capturadas y no se perdieron datos. Todas las demás API siguen funcionando. Continuamos investigando la causa raíz y compartiremos un incidente postmortem una vez que nuestra investigación esté completa. Mientras tanto, estamos entrando en un período adicional de vigilancia para confirmar la estabilidad continua antes de cerrar el incidente.

4. 20 de octubre de 2026 a las 18:17 UTCresolved

   A partir de las 18:00 UTC, después de un largo período de seguimiento adicional sin más problema, estamos resueltos este incidente que afecta a la ampliación de la gama de Matemáticas en el US-Este-1. Los equipos de soporte de aprendizaje y ingeniería de sistemas seguirán con un post mortem una vez que hayamos completado el análisis de causas profundas y hayamos finalizado los próximos pasos o las medidas preventivas necesarias. Por favor contacte si tiene alguna pregunta o preocupación.

Traducido automáticamente desde la actualización oficial del incidente.

1. 8 de octubre de 2026 a las 13:40 UTCinvestigating

   A las 13:00 UTC, estamos experimentando problemas remapping puesta de sol API versiones v2024.1.LTS a las últimas versiones de LTS en todas las regiones. Esto sólo afecta a un número muy pequeño de clientes que todavía están conectados a v2024.1.LTS, que llegó a End of Life en marzo de 2026. Ninguna otra versión de API se ve afectada. Los equipos de Apoyo a la Aprendizaje e Ingeniería de Sistemas están investigando activamente la cuestión y seguirán con una actualización y resolución lo antes posible.

2. 8 de octubre de 2026 a las 13:47 UTCinvestigating

   A partir de 13:40 confía UTC, estamos redireccionando versiones v2024.1.LTS y APIs se están haciendo accesibles como actualización de caches. Los equipos de Apoyo a la Aprendizaje e Ingeniería de Sistemas continúan investigando activamente la cuestión y seguirán con una actualización y resolución lo antes posible.

3. 8 de octubre de 2026 a las 14:20 UTCinvestigating

   A las 14:00 UTC, v2024.1.LTS vuelve a aparecer con éxito a la última versión de LTS en las regiones de AMER, incluyendo US-Este-1 (VA) y US-West-2 (OR). Todas las API deben ser accesibles en estas regiones. Actualmente estamos remapping en las regiones EMEA y APAC. El acceso directo a las versiones de API activas sigue siendo operacional. Este problema ahora sólo está afectando la versión de remapping para un microset de clientes en las regiones EMEA y APAC clavados a la versión de API V2024.1.LTS, que alcanzó EOL en marzo de 2026. Los equipos de Apoyo a la Aprendizaje e Ingeniería de Sistemas continúan investigando activamente la cuestión y seguirán con una actualización y resolución lo antes posible.

4. 8 de octubre de 2026 a las 15:15 UTCresolved

   A partir de las 15.00 horas, la UTC, v2024.1.LTS, está recortando con éxito en todas las regiones. Utilizando esta cadena de versión EOL/sunset debe acceder a todas las API. Los equipos de soporte de aprendizaje y ingeniería de sistemas seguirán con un post mortem una vez que hayamos completado el análisis de causas profundas y hayamos finalizado los próximos pasos o las medidas preventivas necesarias. Por favor contacte si tiene alguna pregunta o preocupación.

Traducido automáticamente desde la actualización oficial del incidente.

1. 2 de octubre de 2026 a las 18:08 UTCinvestigating

   A partir de las 16:45 UTC, comenzamos a experimentar un número muy bajo de retrasos de puntuación con nuestro servicio de Scoring de Matemáticas mejorado en la región estadounidense-este-1. Todas las sesiones fueron anotadas, y no se produjo ninguna pérdida de datos. Ninguna otra API está afectada. Estamos investigando retrasos continuos limitados a este servicio. Los equipos de Apoyo a la Aprendizaje e Ingeniería de Sistemas están investigando activamente la cuestión y seguirán con una actualización y resolución lo antes posible.

2. 2 de octubre de 2026 a las 18:30 UTCidentified

   A partir de las 18:30 UTC, hemos identificado un problema de escalado para el servicio Enhanced Math Scoring y estamos trabajando para resolver el problema. Todas las sesiones siguen siendo capturadas sin pérdida de datos y todas las demás API están operando normalmente. Los equipos de Apoyo a la Aprendizaje e Ingeniería de Sistemas continúan investigando activamente la cuestión y seguirán con una actualización y resolución lo antes posible.

3. 2 de octubre de 2026 a las 19:10 UTCmonitoring

   A partir de las 19:00 UTC, no hemos visto retrasos en el servicio de Enhanced Math Scoring por algún tiempo y ahora entrará en una fase de monitoreo. Seguiremos monitoreando durante 30 minutos antes de resolver el problema. Los equipos de Apoyo a la Aprendizaje e Ingeniería de Sistemas continúan investigando activamente la cuestión y seguirán con una actualización y resolución lo antes posible.

4. 2 de octubre de 2026 a las 19:52 UTCresolved

   A partir de las 19:45 UTC, hemos resuelto el problema que afecta a la ampliación de la gama de matemáticas en la región de Estados Unidos-Este-1. Todas las API y los servicios funcionan normalmente. Los equipos de soporte de aprendizaje y ingeniería de sistemas seguirán con un post mortem una vez que hayamos completado el análisis de causas profundas y hayamos finalizado los próximos pasos o las medidas preventivas necesarias. Por favor contacte si tiene alguna pregunta o preocupación.

Traducido automáticamente desde la actualización oficial del incidente.

1. 11 de septiembre de 2026 a las 18:19 UTCinvestigating

   A partir de las 17:00 UTC, estamos investigando cuestiones intermitentes menores con puntuación en la región de Estados Unidos-Este. Los equipos de Apoyo a la Aprendizaje e Ingeniería de Sistemas están investigando activamente la cuestión y seguirán con una actualización y resolución lo antes posible.

2. 11 de septiembre de 2026 a las 18:30 UTCinvestigating

   A partir de las 18:30 UTC, todas las API siguen funcionando y estamos monitoreando la eficiencia de puntuación. Los equipos de Apoyo a la Aprendizaje e Ingeniería de Sistemas continúan investigando activamente la cuestión y seguirán con una actualización y resolución lo antes posible.

3. 11 de septiembre de 2026 a las 19:42 UTCidentified

   A partir de las 19:30 UTC, hemos confirmado que este es un problema esporádico con la puntuación de tres tipos mejorados de preguntas matemáticas solamente. Estos intentos de puntuación tienen éxito en la reingresación y ninguna otra API se ve afectada. Los equipos de Apoyo a la Aprendizaje e Ingeniería de Sistemas continúan investigando activamente la cuestión y seguirán con una actualización y resolución lo antes posible.

4. 11 de septiembre de 2026 a las 20:53 UTCmonitoring

   A partir de las 20:45 UTC, hemos mejorado el manejo de las solicitudes iniciales de puntuación de EMS y los registros y ahora entraremos en una fase de monitoreo de 60 minutos. Todas las API siguen funcionando normalmente. Los equipos de Apoyo a la Aprendizaje e Ingeniería de Sistemas continúan investigando activamente la cuestión y seguirán con una actualización y resolución lo antes posible.

5. 11 de septiembre de 2026 a las 21:44 UTCresolved

   A partir de las 21:45 UTC, las respuestas de tipo de preguntas mejoradas de Matemáticas están anotando normalmente en la región US-Este-1, todas las API funcionan normalmente, y estamos cerrando este incidente. Los equipos de soporte de aprendizaje y ingeniería de sistemas seguirán con un post mortem una vez que hayamos completado el análisis de causas profundas y hayamos finalizado los próximos pasos o las medidas preventivas necesarias. Por favor contacte si tiene alguna pregunta o preocupación.

Traducido automáticamente desde la actualización oficial del incidente.

1. 24 de julio de 2026 a las 12:16 UTCinvestigating

   Somos conscientes de un problema AWS en curso que afecta a la región US-West-2 (OR), que puede causar problemas de conectividad intermitente al acceder al entorno de Autorización de la Aprendiz. Estamos monitoreando activamente la situación y proporcionaremos actualizaciones cuando estén disponibles. En este momento, el impacto a los clientes de la Aprendiz es breve e intermitente y limitado a la autorización. Las evaluaciones y otras API se comportan normalmente. Los equipos de Apoyo a la Aprendizaje e Ingeniería de Sistemas están investigando activamente la cuestión y seguirán con una actualización y resolución lo antes posible.

2. 24 de julio de 2026 a las 12:28 UTCmonitoring

   A partir de las 11:02 UTC, Learnosity comenzó a ver alertas de monitor de corto plazos intermitentes al acceder al sitio de autor de la Learnosity. Ninguna otra funcionalidad fue afectada, y las alertas de la apreosidad cesaron en el 11:11 UTC. At 11:40 UTC, AWS reported degraded service in US-West-2 (OR). A las 11:56 UTC, AWS informó que sus sistemas se estaban recuperando. Los equipos de Apoyo a la Aprendizaje e Ingeniería de Sistemas siguen monitoreando activamente la cuestión y seguirán con una actualización y resolución lo antes posible.

3. 24 de julio de 2026 a las 12:35 UTCmonitoring

   At 12:30 UTC, AWS reported that they identified and corrected the issue, and that recovery is continuing. Los equipos de Apoyo a la Aprendiz e Ingeniería de Sistemas supervisarán la cuestión durante 30 minutos más, y seguirán con una actualización y resolución lo antes posible.

4. 24 de julio de 2026 a las 13:02 UTCresolved

   A las 13:00 UTC, estamos llamando a este tema resuelto. Los sistemas AWS están recuperando y la autorización de la apreosidad no ha sido afectada durante 50 minutos. Los equipos de soporte de aprendizaje y ingeniería de sistemas seguirán con un post mortem una vez que hayamos completado el análisis de causas profundas y hayamos finalizado los próximos pasos o las medidas preventivas necesarias. Por favor contacte si tiene alguna pregunta o preocupación.

5. 24 de julio de 2026 a las 13:03 UTCpostmortem

   ## Sistemas afectados y regiones On 2026-07-24, Learnosity experienced brief intermittent timeouts affecting access to the Learnosity author site due to [a networking incident in the AWS US-West-2 \(OR\) region](https://health.aws.amazon.com/health/status?eventID=arn:SER:health:us-west-2:::event/MULTIPLE SERVIIPLE El impacto del cliente de la aprendiz comenzó a aproximadamente 11:02 UTC y terminó en 11:11 UTC. Posteriormente, el AWS concluyó su rehabilitación y cerró formalmente su incidente regional a las 12:12 UTC. La duración total del posible impacto para los clientes de la Aprendiz fue de aproximadamente 9 minutos. ### Investigation Learnosity recibió una alerta interna a las 11:02 UTC que el servicio en la región OR fue afectado e inmediatamente comenzó una investigación. La investigación inicial no encontró pruebas de la degradación del servicio de la Aprendiz. Further investigation identified intermittent timeouts affecting access to the Learnosity author site. La aprendiz confirmó con AWS que se había identificado un problema que afectaba a su infraestructura de red en la región y se había iniciado la rehabilitación. Resolución Los timeouts intermitentes que afectan al sitio del autor de la Aprensión cesaron por 11:11 UTC, y AWS resolvió efectivamente el tema por 11:15 UTC. AWS informó de un breve evento de reconocimiento que fue resuelto por 11:59 UTC, y cerró oficialmente el incidente a las 12:12 UTC. ### Prevention Ningún sistema de aprendices contribuyó a este incidente. La vigilancia interna y la alerta se comportaron como se esperaba.

Traducido automáticamente desde la actualización oficial del incidente.

1. 17 de abril de 2026 a las 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 de abril de 2026 a las 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 de abril de 2026 a las 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 de abril de 2026 a las 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 de mayo de 2026 a las 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 de abril de 2026 a las 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 de abril de 2026 a las 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 de mayo de 2026 a las 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 de febrero de 2026 a las 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 de febrero de 2026 a las 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 de febrero de 2026 a las 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 de febrero de 2026 a las 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 de enero de 2026 a las 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 de enero de 2026 a las 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 de enero de 2026 a las 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 de octubre de 2025 a las 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 de octubre de 2025 a las 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 de octubre de 2025 a las 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 de octubre de 2025 a las 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 de octubre de 2025 a las 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 de octubre de 2025 a las 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 de octubre de 2025 a las 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 de octubre de 2025 a las 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 de octubre de 2025 a las 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 de octubre de 2025 a las 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 de octubre de 2025 a las 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 de octubre de 2025 a las 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 de agosto de 2025 a las 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 de agosto de 2025 a las 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 de agosto de 2025 a las 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 de agosto de 2025 a las 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 de agosto de 2025 a las 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 de agosto de 2025 a las 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 de agosto de 2025 a las 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 de agosto de 2025 a las 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 de septiembre de 2025 a las 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 de agosto de 2025 a las 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 de agosto de 2025 a las 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 de agosto de 2025 a las 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 de agosto de 2025 a las 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 de marzo de 2025 a las 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 de marzo de 2025 a las 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 de marzo de 2025 a las 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 de marzo de 2025 a las 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 de marzo de 2025 a las 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 de marzo de 2025 a las 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 de enero de 2025 a las 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 de enero de 2025 a las 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 de enero de 2025 a las 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 de enero de 2025 a las 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 de enero de 2025 a las 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 de octubre de 2024 a las 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 de octubre de 2024 a las 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 de octubre de 2024 a las 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 de octubre de 2024 a las 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 de septiembre de 2024 a las 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 de septiembre de 2024 a las 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 de septiembre de 2024 a las 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 de septiembre de 2024 a las 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 de mayo de 2024 a las 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 de mayo de 2024 a las 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 de mayo de 2024 a las 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 de mayo de 2024 a las 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 de mayo de 2024 a las 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.