Cronologia delle interruzioni di Learnosity

1. 26 ottobre 2026 alle ore 18:05 UTCinvestigating

   A partire da 17:50 UTC, stiamo vivendo problemi che interessano i pool degli articoli in tutte le regioni. I team di Learnosity Support e Systems Engineering stanno attivamente indagando sul problema e seguiranno con un aggiornamento e una risoluzione il prima possibile.

2. 26 ottobre 2026 alle ore 18:34 UTCinvestigating

   A partire dalle 18:30 UTC, stiamo indagando sulle prestazioni degradate durante la creazione e la modifica dei pool di oggetti. Stiamo anche indagando su una questione tangenziale non confermata che potrebbe influenzare la creazione e la modifica dei pacchetti di valutazione dei dispositivi locali. Tutte le altre API negli stack di autore, valutazione e analisi funzionano normalmente. I team di Learnosity Support e Systems Engineering continuano a indagare attivamente il problema e seguiranno con un aggiornamento e una risoluzione il prima possibile.

3. 26 ottobre 2026 alle ore 19:01 UTCinvestigating

   A partire dalle 19:00 UTC, continuiamo a indagare sulle prestazioni degradate durante la creazione o la modifica dei pacchetti di valutazione dei dispositivi locali. Tutte le altre API negli stack di autore, valutazione e analisi funzionano normalmente. I team di Learnosity Support e Systems Engineering continuano a indagare attivamente il problema e seguiranno con un aggiornamento e una risoluzione il prima possibile.

4. 26 ottobre 2026 alle ore 19:31 UTCmonitoring

   A partire dalle 19:30 UTC, la creazione di Object Pool e Local Device Assessment ha visto un throughput normale per circa 30 minuti. Ora entreremo in un ulteriore periodo di monitoraggio per garantire la stabilità. I team di Learnosity Support e Systems Engineering continuano a indagare attivamente il problema e seguiranno con un aggiornamento e una risoluzione il prima possibile.

5. 26 ottobre 2026 alle ore 20:10 UTCresolved

   A partire da 20:10 UTC, non abbiamo visto ulteriori problemi con la creazione o l'aggiornamento del pacchetto di valutazione dei dispositivi locali o del pool dei prodotti. Stiamo risolvendo questo incidente e continueremo a indagare sulla causa principale delle prestazioni degradate. I team di Learningosity Support and Systems Engineering seguiranno con un post mortem una volta completata l'analisi delle cause di root e completano i prossimi passi o misure preventive richieste. Si prega di raggiungere se avete domande o dubbi.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 20 ottobre 2026 alle ore 14:16 UTCinvestigating

   A partire dalle 13:20 UTC, abbiamo iniziato a vedere i ritardi di punteggio con il nostro servizio Enhanced Math Scoring nella regione US-East-1. Non è stata osservata alcuna perdita di dati e tutte le sessioni sono state infine segnate. Come effetto knock-on, il Data API Scoring endpoint sta vivendo problemi di disponibilità intermittenti. Nessuna consegna di autorizzazione o valutazione è stata influenzata. I team di Learnosity Support e Systems Engineering stanno attivamente indagando sul problema e seguiranno con un aggiornamento e una risoluzione il prima possibile.

2. 20 ottobre 2026 alle ore 15:04 UTCinvestigating

   A partire dalle 15:00 UTC, stiamo ancora indagando sulle prestazioni degradate di breve durata del nostro servizio Enhanced Math Scoring, ma non hanno visto errori significativi o ritardi per più di un'ora. Il backlog delle sessioni in attesa di punteggio sgomberato rapidamente, e le presentazioni continuano a essere segnati normalmente. Tutte le altre API rimangono inalterate. I team di Learnosity Support e Systems Engineering continuano a indagare attivamente il problema e seguiranno con un aggiornamento e una risoluzione il prima possibile.

3. 20 ottobre 2026 alle ore 15:51 UTCmonitoring

   A partire da 15:45 UTC, le misure di mitigazione hanno mantenuto con successo la coda di presentazione chiaro, e il punteggio ha continuato a funzionare normalmente. Le sottomissioni ricevute durante il periodo delle prestazioni degradate sono state catturate, e nessun dato è stato perso. Tutte le altre API rimangono operative. Stiamo continuando a indagare la causa principale e condivideremo un postmortem incidente una volta che la nostra indagine è completa. Nel frattempo, stiamo entrando in un periodo di monitoraggio aggiuntivo per confermare la stabilità continua prima di chiudere l'incidente.

4. 20 ottobre 2026 alle ore 18:17 UTCresolved

   A partire dalle 18:00 UTC, dopo un lungo periodo di monitoraggio aggiuntivo senza ulteriori problemi, siamo risolti questo incidente che colpisce Enhanced Math Scoring negli Stati Uniti-Est-1. I team di Learningosity Support and Systems Engineering seguiranno con un post mortem una volta completata l'analisi delle cause di root e completano i prossimi passi o misure preventive richieste. Si prega di raggiungere se avete domande o dubbi.

5. 27 ottobre 2026 alle ore 13:27 UTCpostmortem

   ## Sistemi e Regioni interessati Il 20 ottobre 2026, Learnosity ha sperimentato ritardi di punteggio e errori di richiesta intermittente che interessano il punteggio di matematica potenziato negli Stati Uniti-Est-1. L'impatto del cliente è iniziato a circa 13:06 UTC e si è concluso alle 13:47 UTC, della durata di circa 41 minuti. Interessate richieste di punteggio sperimentate più di normali tempi di elaborazione, e alcune richieste dirette all'API di dati che segnano errori di endpoint restituiti. Per le sessioni salvate tramite l'API Elementi, le richieste di punteggio interessate sono state in coda e riattivate, con conseguente ritardo nella disponibilità dei punteggi piuttosto che nel punteggio dei guasti. Le valutazioni senza domande di matematica e servizi in altre regioni non sono state influenzate. ## Indagine La nostra indagine ha identificato uno schema specifico di richieste di punteggio che ha portato a tempi di elaborazione inaspettatamente elevati. Ciò ha ridotto la capacità disponibile per elaborare altre richieste di punteggio, causando ritardi e timeout intermittenti. Il problema è stato associato a come determinati input di punteggio sono stati elaborati, piuttosto che un aumento inaspettato del volume di richiesta generale. ## Risoluzione Le prestazioni di punteggio tornarono alla normalità entro 13:47 UTC. A 15:12 UTC, gli ingegneri di Learnosity hanno implementato un ulteriore isolamento del traffico per evitare che il carico di lavoro di punteggio interessato urti operazioni di punteggio per altri clienti. # Prevenzione Learnosity ha implementato modifiche per ridurre il consumo di risorse inutili e migliorare il recupero delle richieste di punteggio interessate. Ulteriori miglioramenti sono in corso per rafforzare la validazione delle richieste di punteggio, migliorare le garanzie di elaborazione e impedire ai singoli carichi di lavoro di punteggio di influenzare il servizio più ampio. Ulteriori misure di isolamento resteranno in vigore mentre questi miglioramenti sono completati e la loro efficacia è verificata.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 8 ottobre 2026 alle ore 13:40 UTCinvestigating

   A partire dalle 13:00 UTC, stiamo vivendo problemi di remapping tramonti API versioni v2024.1.LTS alle ultime versioni LTS in tutte le regioni. Ciò colpisce solo un numero molto piccolo di clienti che sono ancora inclini a v2024.1.LTS, che ha raggiunto la fine della vita nel marzo 2026. Non sono interessate altre versioni API. I team di Learnosity Support e Systems Engineering stanno attivamente indagando sul problema e seguiranno con un aggiornamento e una risoluzione il prima possibile.

2. 8 ottobre 2026 alle ore 13:47 UTCinvestigating

   A partire da 13:40> UTC, stiamo reindirizzando le versioni v2024.1.LTS e le API stanno diventando accessibili come aggiornamento cache. I team di Learnosity Support e Systems Engineering continuano a indagare attivamente il problema e seguiranno con un aggiornamento e una risoluzione il prima possibile.

3. 8 ottobre 2026 alle ore 14:20 UTCinvestigating

   A partire dalle 14:00 UTC, v2024.1.LTS sta rimapping con successo all'ultima versione LTS nelle regioni AMER, tra cui US-East-1 (VA) e US-West-2 (OR). Tutte le API dovrebbero essere accessibili in queste regioni. Attualmente stiamo remapping nelle regioni EMEA e APAC. L'accesso diretto alle versioni API attive rimane operativo. Questo problema riguarda ora solo la remapping versione per un microset di clienti nelle regioni EMEA e APAC pinned alla versione v2024.1.LTS API al tramonto, che ha raggiunto EOL nel marzo 2026. I team di Learnosity Support e Systems Engineering continuano a indagare attivamente il problema e seguiranno con un aggiornamento e una risoluzione il prima possibile.

4. 8 ottobre 2026 alle ore 15:15 UTCresolved

   A partire dalle 15:00 UTC, v2024.1.LTS sta rimapping con successo in tutte le regioni. Utilizzando questa stringa di versione EOL/sunset dovrebbe accedere a tutte le API. I team di Learningosity Support and Systems Engineering seguiranno con un post mortem una volta completata l'analisi delle cause di root e completano i prossimi passi o misure preventive richieste. Si prega di raggiungere se avete domande o dubbi.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 2 ottobre 2026 alle ore 18:08 UTCinvestigating

   A partire dalle 16:45 UTC, abbiamo iniziato a sperimentare un numero molto basso di ritardi di punteggio con il nostro servizio di punteggio matematica avanzata nella regione US-East-1. Tutte le sessioni sono state segnate e non si è verificata alcuna perdita di dati. Non sono interessate altre API. Stiamo indagando su ritardi in corso limitati a questo servizio. I team di Learnosity Support e Systems Engineering stanno attivamente indagando sul problema e seguiranno con un aggiornamento e una risoluzione il prima possibile.

2. 2 ottobre 2026 alle ore 18:30 UTCidentified

   A partire dalle 18:30 UTC, abbiamo identificato un problema di scaling per il servizio Enhanced Math Scoring e stiamo lavorando per risolvere il problema. Tutte le sessioni continuano a essere catturate senza perdita di dati e tutte le altre API sono operative normalmente. I team di Learnosity Support e Systems Engineering continuano a indagare attivamente il problema e seguiranno con un aggiornamento e una risoluzione il prima possibile.

3. 2 ottobre 2026 alle ore 19:10 UTCmonitoring

   A partire dalle 19:00 UTC, non abbiamo visto ritardi nel servizio Enhanced Math Scoring per un certo tempo e ora entrerà in una fase di monitoraggio. Continueremo a monitorare per 30 minuti prima di risolvere il problema. I team di Learnosity Support e Systems Engineering continuano a indagare attivamente il problema e seguiranno con un aggiornamento e una risoluzione il prima possibile.

4. 2 ottobre 2026 alle ore 19:52 UTCresolved

   A partire da 19:45 UTC, abbiamo risolto il problema che interessa Enhanced Math Scoring nella regione US-East-1. Tutte le API e i servizi funzionano normalmente. I team di Learningosity Support and Systems Engineering seguiranno con un post mortem una volta completata l'analisi delle cause di root e completano i prossimi passi o misure preventive richieste. Si prega di raggiungere se avete domande o dubbi.

5. 27 ottobre 2026 alle ore 01:24 UTCpostmortem

   Revisione: Il 2 ottobre 2026, Learnosity ha sperimentato errori di punteggio intermittente e timeout che interessano i tipi di domande di matematica negli Stati Uniti-Est-1. L'impatto del cliente è iniziato a circa 16:34 UTC e si è concluso a 18:47 UTC, della durata di circa 2 ore e 13 minuti. Le richieste colpite potrebbero verificarsi ritardi fino a 40 secondi prima di fallire. Altre regioni non sono state colpite. # Investigazione # L'incidente si è verificato quando la domanda sul servizio di punteggio di matematica ha superato la capacità disponibile. Anche se sono stati introdotti miglioramenti di capacità e scalabilità a seguito di un precedente incidente, il servizio ha incontrato un limite aggiuntivo nella sua configurazione di rete che ha impedito ulteriori istanze di essere fornito. L'impatto è stato composto da calcoli lenti che hanno occupato le istanze più lunghe di quanto previsto perché i limiti di tempo di calcolo non sono stati rispettati in modo affidabile sotto carico pesante. Insieme, queste condizioni hanno impedito al servizio di scalare sufficientemente per gestire la domanda. Traduzione: Gli ingegneri di Learnosity hanno ripristinato il servizio spostando il servizio di punteggio a una configurazione di rete con capacità di scaling aggiuntive e aumentando le risorse di calcolo assegnate ad ogni istanza. Questi cambiamenti hanno permesso al servizio di recuperare, con errori di punteggio di compensazione di 18:47 UTC. # Prevenzione # Learnosity ha aggiornato il meccanismo di applicazione del limite di tempo di calcolo per terminare in modo affidabile calcoli lenti sotto carico pesante. I controlli sanitari sono stati anche separati dall'elaborazione del calcolo per evitare inutili sostituzioni di istanze. Il servizio opera ora con capacità di elaborazione e rete aggiuntive. Ulteriori miglioramenti architettonici sono in corso per evitare che la capacità di rete limiti la scalabilità futura, e stiamo valutando i limiti di tempo di calcolo più brevi per ridurre l'impatto di calcoli insolitamente lenti.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 11 settembre 2026 alle ore 18:19 UTCinvestigating

   A partire dalle 17:00 UTC, stiamo attualmente indagando su minori problemi intermittenti con il punteggio nella regione US-East-1. I team di Learnosity Support e Systems Engineering stanno attivamente indagando sul problema e seguiranno con un aggiornamento e una risoluzione il prima possibile.

2. 11 settembre 2026 alle ore 18:30 UTCinvestigating

   A partire dalle 18:30 UTC, tutte le API rimangono operative e stiamo monitorando l'efficienza di punteggio. I team di Learnosity Support e Systems Engineering continuano a indagare attivamente il problema e seguiranno con un aggiornamento e una risoluzione il prima possibile.

3. 11 settembre 2026 alle ore 19:42 UTCidentified

   A partire dalle 19:30 UTC, abbiamo confermato che questo è un problema sporadico con il punteggio di tre tipi di domande di matematica potenziati solo. Questi tentativi di punteggio riescono a riprovare e nessun'altra API sono interessati. I team di Learnosity Support e Systems Engineering continuano a indagare attivamente il problema e seguiranno con un aggiornamento e una risoluzione il prima possibile.

4. 11 settembre 2026 alle ore 20:53 UTCmonitoring

   A partire dalle 20:45 UTC, abbiamo migliorato la gestione delle richieste di punteggio e dei retries iniziali dello SME e ora entreremo in una fase di monitoraggio di 60 minuti. Tutte le API continuano a funzionare normalmente. I team di Learnosity Support e Systems Engineering continuano a indagare attivamente il problema e seguiranno con un aggiornamento e una risoluzione il prima possibile.

5. 11 settembre 2026 alle ore 21:44 UTCresolved

   A partire da 21:45 UTC, Enhanced Math Scoring risposte tipo di domanda stanno segnando normalmente nella regione US-East-1, tutte le API funzionano normalmente, e stiamo chiudendo questo incidente. I team di Learningosity Support and Systems Engineering seguiranno con un post mortem una volta completata l'analisi delle cause di root e completano i prossimi passi o misure preventive richieste. Si prega di raggiungere se avete domande o dubbi.

6. 27 ottobre 2026 alle ore 01:23 UTCpostmortem

   Revisione: L'11 settembre 2026, Learnosity ha sperimentato errori di punteggio intermittente e timeout che interessano i tipi di domande di matematica negli Stati Uniti-Est-1. L'impatto del cliente è iniziato a circa 17:00 UTC e si è concluso alle 21:45 UTC, della durata di circa 4 ore e 45 minuti. Altri tipi di domande hanno continuato a segnare normalmente, e altre regioni non sono state colpite. La maggior parte delle richieste fallite è riuscita quando si è tentato. # Investigazione # L'incidente è stato causato da una capacità insufficiente nel servizio di punteggio di matematica a seguito di un aumento della domanda nelle settimane precedenti. Il servizio ha raggiunto il suo numero massimo configurato di istanze e non ha potuto scalare ulteriormente per ospitare il carico. Questo è stato composto da risorse di calcolo limitate per caso e calcoli lenti che hanno occupato le istanze più lunghe di previsto. Sotto carico pesante, il limite di tempo di calcolo non è stato applicato in modo affidabile, e le istanze occupate potrebbero fallire i controlli sanitari e essere sostituiti, riducendo ulteriormente la capacità disponibile. Traduzione: Gli ingegneri di Learnosity hanno ripristinato il servizio aumentando il numero di istanze in esecuzione e aumentando il limite massimo di istanza. Operazioni di punteggio normali riprese da 21:45 UTC, e tutte le richieste di punteggio in coda rimanenti sono state elaborate da 23:17 UTC. Il 14 settembre sono state implementate ulteriori modifiche di configurazione per aumentare le risorse di calcolo, migliorare la scalabilità automatica e ridurre la sostituzione delle istanze inutili. # Prevenzione # L'apprendimento ha aumentato la capacità di punteggio, ha aumentato i limiti di istanza e ha migliorato la scalatura automatica in base all'utilizzo del processore. I controlli sanitari sono stati separati dall'elaborazione del calcolo per evitare che le istanze occupate vengano identificate in modo errato come malsano. Abbiamo anche migliorato l'applicazione dei limiti di tempo di calcolo e ampliato il monitoraggio e l'avviso per l'utilizzo delle risorse, i tempi di risposta e gli errori di punteggio. Ulteriori lavori sono in corso per rafforzare la capacità di scaling della rete e valutare i limiti di tempo di calcolo più brevi.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 24 luglio 2026 alle ore 12:16 UTCinvestigating

   Siamo a conoscenza di un problema AWS in corso che riguarda la regione US-West-2 (OR), che può causare problemi di connettività intermittente durante l'accesso all'ambiente di apprendimento. Stiamo monitorando attivamente la situazione e fornirà aggiornamenti come diventano disponibili. In questo momento, l'impatto ai clienti di Learnosity è breve e intermittente e limitato all'autore. Le valutazioni e altre API si stanno comportando normalmente. I team di Learnosity Support e Systems Engineering stanno attivamente indagando sul problema e seguiranno con un aggiornamento e una risoluzione il prima possibile.

2. 24 luglio 2026 alle ore 12:28 UTCmonitoring

   A partire dalle 11:02 UTC, Learnosity ha iniziato a vedere avvisi di monitor di breve durata, timeout intermittenti quando si accede al sito dell'autore Learnosity. Nessun'altra funzionalità è stata influenzata e gli avvisi di Learnosity sono cessati alle 11:11 UTC. Alle 11:40 UTC, AWS ha riferito il servizio degradato in US-West-2 (OR). Alle 11:56 UTC, AWS ha riferito che i loro sistemi stavano recuperando. I team di Learningosity Support e Systems Engineering continuano a monitorare attivamente il problema e seguiranno con un aggiornamento e una risoluzione il prima possibile.

3. 24 luglio 2026 alle ore 12:35 UTCmonitoring

   Alle 12:30 UTC, AWS ha riferito che hanno identificato e corretto il problema, e che il recupero continua. I team di Learnosity Support and Systems Engineering monitoreranno il problema per altri 30 minuti e seguiranno il più presto possibile con un aggiornamento e una risoluzione.

4. 24 luglio 2026 alle ore 13:02 UTCresolved

   A partire dalle 13:00 UTC, stiamo chiamando questo problema risolto. I sistemi AWS stanno recuperando e l'autore di Learnosity non è stato colpito per 50 minuti. I team di Learningosity Support and Systems Engineering seguiranno con un post mortem una volta completata l'analisi delle cause di root e completano i prossimi passi o misure preventive richieste. Si prega di raggiungere se avete domande o dubbi.

5. 24 luglio 2026 alle ore 13:03 UTCpostmortem

   ### Sistemi e Regioni interessati Su 2026-07-24, Learnosity ha sperimentato brevi timeout intermittenti che interessano l'accesso al sito dell'autore di Learnosity a causa di [un incidente di rete nella regione AWS US-West-2 \(OR\)](https://health.aws.amazon.com/health/status?eventID=arn:aws:us-west-2::event/MULTIPLE L'impatto del cliente di Learnosity è iniziato a circa 11:02 UTC e si è concluso a 11:11 UTC. AWS successivamente completato la bonifica e formalmente chiuso il loro incidente regionale a 12:12 UTC. La durata totale del possibile impatto per i clienti di Learnosity è stata di circa 9 minuti. ### Investigation Learnosity ha ricevuto un avviso interno alle 11:02 UTC che il servizio nella regione OR è stato colpito e subito ha iniziato un'indagine. L'indagine iniziale non ha trovato alcuna prova di un degrado del servizio di Learnosity. Ulteriori indagini hanno identificato timeout intermittenti che interessano l'accesso al sito dell'autore di Learnosity. L'apprendimento ha confermato con AWS che un problema che influenza la loro infrastruttura di rete nella regione era stato identificato e la bonifica era iniziata. ## Risoluzione Intermittent timeouts che interessano il sito dell'autore di Learnosity ha cessato di 11:11 UTC, e AWS efficacemente risolto il problema di 11:15 UTC. AWS ha riferito un breve evento di riconvergenza che è stato risolto da 11:59 UTC, e ufficialmente chiuso l'incidente a 12:12 UTC. ## Prevenzione Nessun sistema di Learnosity ha contribuito a questo incidente. Il monitoraggio interno e l'avviso si sono comportati come previsto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 17 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 maggio 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 maggio 2026 alle ore 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 febbraio 2026 alle ore 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 febbraio 2026 alle ore 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 febbraio 2026 alle ore 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 febbraio 2026 alle ore 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 gennaio 2026 alle ore 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 gennaio 2026 alle ore 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 gennaio 2026 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 agosto 2025 alle ore 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 agosto 2025 alle ore 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 agosto 2025 alle ore 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 agosto 2025 alle ore 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 agosto 2025 alle ore 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 agosto 2025 alle ore 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 agosto 2025 alle ore 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 agosto 2025 alle ore 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 settembre 2025 alle ore 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 agosto 2025 alle ore 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 agosto 2025 alle ore 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 agosto 2025 alle ore 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 agosto 2025 alle ore 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 marzo 2025 alle ore 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 marzo 2025 alle ore 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 marzo 2025 alle ore 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 marzo 2025 alle ore 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 marzo 2025 alle ore 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 marzo 2025 alle ore 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 gennaio 2025 alle ore 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 gennaio 2025 alle ore 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 gennaio 2025 alle ore 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 gennaio 2025 alle ore 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 gennaio 2025 alle ore 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 ottobre 2024 alle ore 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 ottobre 2024 alle ore 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 ottobre 2024 alle ore 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 ottobre 2024 alle ore 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 settembre 2024 alle ore 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 settembre 2024 alle ore 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 settembre 2024 alle ore 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 settembre 2024 alle ore 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 maggio 2024 alle ore 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 maggio 2024 alle ore 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 maggio 2024 alle ore 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 maggio 2024 alle ore 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 maggio 2024 alle ore 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.