Learnosity driftsforstyrrelser

1. 26. oktober 2026 kl. 18.05 UTCinvestigating

   Fra 17: 50 UTC, vi oplever problemer påvirker element Pools i alle regioner. Learnosity Support og Systems Engineering teams er aktivt undersøge problemet, og vil følge videre med en opdatering og opløsning så hurtigt som muligt.

2. 26. oktober 2026 kl. 18.34 UTCinvestigating

   Fra 18: 30 UTC, vi er ved at undersøge forringet ydeevne, når du opretter og redigerer element Pools. Vi undersøger også en as- of- endnu ubekræftet tangential problem muligvis påvirker oprettelse og redigering af Local Device Assessment pakker. Alle andre API 'er i authoring, vurdering og analytics stakke fungerer normalt. Learnosity Support and Systems Engineering teams fortsætter aktivt med at undersøge problemet, og vil følge videre med en opdatering og opløsning så hurtigt som muligt.

3. 26. oktober 2026 kl. 19.01 UTCinvestigating

   Fra 19: 00 UTC, vi fortsætter med at undersøge forringet ydeevne, når du opretter eller redigerer element Pools orx Local Device Assessment pakker. Alle andre API 'er i authoring, vurdering og analytics stakke fungerer normalt. Learnosity Support and Systems Engineering teams fortsætter aktivt med at undersøge problemet, og vil følge videre med en opdatering og opløsning så hurtigt som muligt.

4. 26. oktober 2026 kl. 19.31 UTCmonitoring

   Fra 19: 30 UTC, Post Pool og Local Device Assessment har skabt normal gennemstrømning i ca. 30 minutter. Vi vil nu gå ind i en ekstra overvågningsperiode for at sikre stabilitet. Learnosity Support and Systems Engineering teams fortsætter aktivt med at undersøge problemet, og vil følge videre med en opdatering og opløsning så hurtigt som muligt.

5. 26. oktober 2026 kl. 20.10 UTCresolved

   Fra 20: 10 UTC, vi har set ingen yderligere problemer med element Pool eller Local Device Assessment pakke skabelse eller opdatering. Vi løser denne hændelse og vil fortsætte med at undersøge årsagen til den nedbrudte præstation. Learnosity Support and Systems Engineering teams vil følge op med en post mortem, når vi har afsluttet rod årsag analyse og færdiggjort næste trin eller forebyggende foranstaltninger kræves. Kontakt venligst, hvis du har spørgsmål eller bekymringer.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 20. oktober 2026 kl. 14.16 UTCinvestigating

   Fra 13: 20 UTC, vi begyndte at se scoring forsinkelser med vores Enhanced Math Scoring service i US- East-1 regionen. Der er ikke observeret tab af data, og alle sessioner er i sidste ende blevet scoret. Som en knock- on effekt, Data API Scoring endpoint oplever intermitterende tilgængelighed problemer. Ingen authoring eller vurdering levering er blevet påvirket. Learnosity Support og Systems Engineering teams er aktivt undersøge problemet, og vil følge videre med en opdatering og opløsning så hurtigt som muligt.

2. 20. oktober 2026 kl. 15.04 UTCinvestigating

   Fra 15: 00 UTC, er vi stadig undersøge kortlivede nedbrudte ydeevne af vores Enhanced Math Scoring service, men har ikke set væsentlige fejl eller forsinkelser i mere end en time. De forsinkelser af sessioner afventer scoring ryddet hurtigt, og indlæg fortsætter med at blive scoret normalt. Alle andre API 'er forbliver upåvirkede. Learnosity Support and Systems Engineering teams fortsætter aktivt med at undersøge problemet, og vil følge videre med en opdatering og opløsning så hurtigt som muligt.

3. 20. oktober 2026 kl. 15.51 UTCmonitoring

   Fra 15: 45 UTC har afbødende foranstaltninger med held holdt indsendelseskøen klar, og scoring har fortsat med at fungere normalt. Indlæg modtaget i perioden med forringet ydeevne blev registreret, og ingen data gik tabt. Alle andre API 'er forbliver operationelle. Vi fortsætter med at undersøge årsagen og vil dele en hændelse efter døden, når vores undersøgelse er afsluttet. I mellemtiden går vi ind i en ekstra overvågningsperiode for at bekræfte fortsat stabilitet, før vi afslutter hændelsen.

4. 20. oktober 2026 kl. 18.17 UTCresolved

   Fra 18: 00 UTC, efter en lang periode med yderligere overvågning uden yderligere problemer, er vi løst denne hændelse påvirker Enhanced Math Scoring i US- East-1. Learnosity Support and Systems Engineering teams vil følge op med en post mortem, når vi har afsluttet rod årsag analyse og færdiggjort næste trin eller forebyggende foranstaltninger kræves. Kontakt venligst, hvis du har spørgsmål eller bekymringer.

5. 27. oktober 2026 kl. 13.27 UTCpostmortem

   # Påvirkede systemer og regioner Den 20 oktober 2026, Learnosity oplevet scoring forsinkelser og intermitterende anmodning fejl påvirker Enhanced Math scoring i US- East-1. Kundepåvirkningen begyndte ca. 13: 06 UTC og sluttede kl. 13: 47 UTC, der varede ca. 41 minutter. Påvirkede scoring anmodninger oplevede længere end normale behandlingstider, og nogle direkte anmodninger til Data API scoring endpoint returnerede fejl. For sessioner gemt gennem Poster API, påvirkede scoring anmodninger blev i kø og forsøgte igen, hvilket resulterer i forsinket score tilgængelighed snarere end scoring fejl. Vurderingen uden matematiske spørgsmål og tjenesteydelser i andre regioner var upåvirket. Efterforskning Vores undersøgelse identificerede et specifikt mønster af scoring anmodninger, der resulterede i uventet høje behandlingstider. Dette reducerede kapaciteten til at behandle andre scoring anmodninger, forårsager forsinkelser og periodisk timeouts. Spørgsmålet var forbundet med, hvordan visse scoring input blev behandlet, snarere end en uventet stigning i den samlede efterspørgsel mængde. # Opløsning Scoring ydeevne returneres til normal ved 13: 47 UTC. Ved 15: 12 UTC, Learnosity ingeniører gennemført yderligere trafikisolering for at forhindre den berørte score arbejdsbyrde fra at påvirke scoring operationer for andre kunder. # Prevention Learnositeten har gennemført ændringer for at reducere unødvendigt ressourceforbrug og forbedre genopretningen af de berørte scoringsanmodninger. Yderligere forbedringer er undervejs for at styrke vurderingen af anmodninger, forbedre behandlingssikkerheden og forhindre, at individuelle scoringer af arbejdsbyrder påvirker den bredere service. Der vil fortsat være yderligere isolationsforanstaltninger på plads, mens disse forbedringer er afsluttet, og deres effektivitet kontrolleres.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 8. oktober 2026 kl. 13.40 UTCinvestigating

   Fra 13: 00 UTC, vi oplever problemer rekorting sunset API versioner v2024.1.LTS til de nyeste LTS-udgivelser i alle regioner. Dette påvirker kun et meget lille antal kunder, der stadig er bundet til v2024.1.LTS, som nåede slutningen af livet i marts 2026. Ingen andre API-versioner er påvirket. Learnosity Support og Systems Engineering teams er aktivt undersøge problemet, og vil følge videre med en opdatering og opløsning så hurtigt som muligt.

2. 8. oktober 2026 kl. 13.47 UTCinvestigating

   Fra 13: 40 > UTC, vi omdirigerer v2024.1.LTS versioner og Api 'er bliver tilgængelige som cache opdatering. Learnosity Support and Systems Engineering teams fortsætter aktivt med at undersøge problemet, og vil følge videre med en opdatering og opløsning så hurtigt som muligt.

3. 8. oktober 2026 kl. 14.20 UTCinvestigating

   Fra 14: 00 UTC, v2024.1.LTS er vellykket rekorting til den nyeste LTS version i AMER regioner, herunder US- East-1 (VA) og US- West-2 (OR). Alle API 'er bør være tilgængelige i disse regioner. Vi er i øjeblikket ved at rekortere i EMEA' s og APAC 's regioner. Direkte adgang til aktive API-versioner forbliver operationel. Dette spørgsmål påvirker nu kun version rekorting for et mikrosæt af kunder i EMEA 's og APAC' s regioner, der er fastgjort til den sunset v2024.1.LTS API version, som nåede EOL i marts 2026. Learnosity Support and Systems Engineering teams fortsætter aktivt med at undersøge problemet, og vil følge videre med en opdatering og opløsning så hurtigt som muligt.

4. 8. oktober 2026 kl. 15.15 UTCresolved

   Fra 15: 00 UTC, v2024.1.LTS er vellykket rekorting i alle regioner. Brug denne EOL / sunset version streng bør få adgang til alle API 'er. Learnosity Support and Systems Engineering teams vil følge op med en post mortem, når vi har afsluttet rod årsag analyse og færdiggjort næste trin eller forebyggende foranstaltninger kræves. Kontakt venligst, hvis du har spørgsmål eller bekymringer.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 2. oktober 2026 kl. 18.08 UTCinvestigating

   Fra 16: 45 UTC, vi begyndte at opleve meget lavt antal scoring forsinkelser med vores Enhanced Math Scoring service i US- East-1 regionen. Alle sessioner blev scoret, og der opstod ingen tab af data. Ingen andre API 'er er berørt. Vi undersøger forsinkelser begrænset til denne tjeneste. Learnosity Support og Systems Engineering teams er aktivt undersøge problemet, og vil følge videre med en opdatering og opløsning så hurtigt som muligt.

2. 2. oktober 2026 kl. 18.30 UTCidentified

   Fra 18: 30 UTC, vi har identificeret et skaleringsproblem for den forbedrede matematik Scoring service og arbejder på at løse problemet. Alle sessioner fortsætter med at blive fanget uden tab af data og alle andre API fungerer normalt. Learnosity Support and Systems Engineering teams fortsætter aktivt med at undersøge problemet, og vil følge videre med en opdatering og opløsning så hurtigt som muligt.

3. 2. oktober 2026 kl. 19.10 UTCmonitoring

   Fra 19: 00 UTC, vi har ikke set forsinkelser i den forbedrede matematik Scoring service i nogen tid og vil nu gå ind i en overvågningsfase. Vi vil fortsætte med at overvåge i 30 minutter, før vi løser problemet. Learnosity Support and Systems Engineering teams fortsætter aktivt med at undersøge problemet, og vil følge videre med en opdatering og opløsning så hurtigt som muligt.

4. 2. oktober 2026 kl. 19.52 UTCresolved

   Fra 19: 45 UTC, vi har løst problemet påvirker Enhanced Math Scoring i US- East-1 regionen. Alle API 'er og tjenester fungerer normalt. Learnosity Support and Systems Engineering teams vil følge op med en post mortem, når vi har afsluttet rod årsag analyse og færdiggjort næste trin eller forebyggende foranstaltninger kræves. Kontakt venligst, hvis du har spørgsmål eller bekymringer.

5. 27. oktober 2026 kl. 01.24 UTCpostmortem

   # # * * Berørte systemer og regioner * * Den 2 oktober 2026, Learnosity oplevede intermitterende scoring fejl og timeouts påvirker matematik spørgsmål typer i US- East-1. Kundepåvirkningen begyndte ca. 16: 34 UTC og sluttede kl. 18: 47 UTC, der varede ca. 2 timer og 13 minutter. Berørte anmodninger kunne opleve forsinkelser på op til 40 sekunder før fiasko. Andre regioner blev ikke berørt. # * * Undersøgelse * * Hændelsen opstod, da efterspørgslen på matematik scoring service oversteg den tilgængelige kapacitet. Selv om kapaciteten og skaleringen forbedringer var blevet indført efter en tidligere hændelse, tjenesten stødte på en ekstra grænse i sin netværkskonfiguration, der forhindrede yderligere tilfælde i at blive leveret. Virkningen blev yderligere forstærket af langsomme beregninger, der besatte tilfælde længere end planlagt, fordi beregningsfristerne ikke blev håndhævet pålideligt under tung belastning. Tilsammen forhindrede disse betingelser tjenesten i at skalere tilstrækkeligt til at håndtere efterspørgslen. # * * Opløsning * * Learnosity ingeniører restaureret service ved at flytte scoring service til et netværk konfiguration med yderligere skalering kapacitet og øge de computerressourcer, der er tildelt til hver instans. Disse ændringer gjorde det muligt for tjenesten at komme sig, med scoring fejl rydde af 18: 47 UTC. # * * Prevention * * Learnositeten har opdateret beregningstidsbegrænsningsmekanismen for pålideligt at afslutte langsomme beregninger under tung belastning. Helbredskontrol er også blevet adskilt fra beregning behandling for at forhindre unødvendige instans udskiftning. Tjenesten fungerer nu med ekstra computer- og netværkskapacitet. Yderligere arkitektoniske forbedringer er undervejs for at forhindre netkapaciteten i at begrænse den fremtidige skalering, og vi er ved at evaluere kortere beregningsfrister for at reducere virkningen af usædvanligt langsomme beregninger.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 11. september 2026 kl. 18.19 UTCinvestigating

   Fra kl. 17: 00 UTC undersøger vi i øjeblikket mindre periodiske problemer med scoring i US- East-1-regionen. Learnosity Support og Systems Engineering teams er aktivt undersøge problemet, og vil følge videre med en opdatering og opløsning så hurtigt som muligt.

2. 11. september 2026 kl. 18.30 UTCinvestigating

   Fra 18: 30 UTC, alle API 'er forbliver operationelle, og vi overvåger scoring effektivitet. Learnosity Support and Systems Engineering teams fortsætter aktivt med at undersøge problemet, og vil følge videre med en opdatering og opløsning så hurtigt som muligt.

3. 11. september 2026 kl. 19.42 UTCidentified

   Fra 19: 30 UTC, vi har bekræftet dette at være et sporadisk problem med scoring af tre forbedrede matematik spørgsmål typer kun. Disse scoring forsøg lykkes på at prøve igen og ingen andre Api 'er er påvirket. Learnosity Support and Systems Engineering teams fortsætter aktivt med at undersøge problemet, og vil følge videre med en opdatering og opløsning så hurtigt som muligt.

4. 11. september 2026 kl. 20.53 UTCmonitoring

   Fra 20: 45 UTC, vi har forbedret håndteringen af oprindelige EMS scoring anmodninger og forsøg og vil nu gå ind i en 60-minutters overvågning fase. Alle API 'er fungerer fortsat normalt. Learnosity Support and Systems Engineering teams fortsætter aktivt med at undersøge problemet, og vil følge videre med en opdatering og opløsning så hurtigt som muligt.

5. 11. september 2026 kl. 21.44 UTCresolved

   Fra 21: 45 UTC, Enhanced Math Scoring spørgsmål type svar scorer normalt i US- East-1 regionen, alle API 'er fungerer normalt, og vi er ved at lukke denne hændelse. Learnosity Support and Systems Engineering teams vil følge op med en post mortem, når vi har afsluttet rod årsag analyse og færdiggjort næste trin eller forebyggende foranstaltninger kræves. Kontakt venligst, hvis du har spørgsmål eller bekymringer.

6. 27. oktober 2026 kl. 01.23 UTCpostmortem

   # # * * Berørte systemer og regioner * * Den 11 september 2026, Learnosity oplevede intermitterende scoring fejl og timeouts påvirker matematik spørgsmål typer i US- East-1. Kundesammenstødet begyndte ca. 17: 00 UTC og sluttede kl. 21: 45 UTC, der varede ca. 4 timer og 45 minutter. Andre spørgsmålstyper fortsatte med at score normalt, og andre regioner blev ikke påvirket. De fleste mislykkede anmodninger lykkedes, da de blev genprøvet. # * * Undersøgelse * * Hændelsen skyldtes utilstrækkelig kapacitet i matematik scoring service efter en stigning i efterspørgslen i de foregående uger. Tjenesten nåede sit konfigurerede maksimale antal tilfælde og kunne ikke skalere yderligere for at imødekomme belastningen. Dette blev forstærket af begrænsede computerressourcer per eksempel og langsomme beregninger, der besatte tilfælde længere end planlagt. Under tung belastning blev beregningsfristen ikke håndhævet pålideligt, og travle tilfælde kunne fejle sundhedstjek og blive erstattet, hvilket yderligere reducerede den tilgængelige kapacitet. # * * Opløsning * * Learnosity ingeniører genoprettet service ved at øge antallet af kørende tilfælde og hæve den maksimale instans grænse. Normal scoring operationer genoptaget med 21: 45 UTC, og alle resterende queued scoring anmodninger blev behandlet med 23: 17 UTC. Den 14. september blev der foretaget yderligere konfigurationsændringer for at øge computerressourcer, forbedre automatisk skalering og reducere unødvendig udskiftning af instans. # * * Prevention * * Learnositeten har øget scoringkapaciteten, forhøjede instansgrænser og forbedret automatisk skalering baseret på processorudnyttelse. Helbredskontrol er blevet adskilt fra beregning behandling for at forhindre travle tilfælde i at blive ukorrekt identificeret som usund. Vi har også forbedret beregningen tidsbegrænsning håndhævelse og udvidet overvågning og advarsel om ressourceudnyttelse, responstid, og scoring fejl. Der arbejdes videre på at styrke netskaleringskapaciteten og evaluere kortere beregningsfrister.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 24. juli 2026 kl. 12.16 UTCinvestigating

   Vi er klar over et igangværende AWS problem, der påvirker US- West-2 (OR) regionen, som kan forårsage intermitterende konnektivitet problemer, når adgang til Learnosity Authoring miljø. Vi overvåger situationen aktivt og vil levere opdateringer, efterhånden som de bliver tilgængelige. På dette tidspunkt er virkningen for Learnosity kunder kort og intermitterende og begrænset til authoring. Bedømmelser og andre Api 'er opfører sig normalt. Learnosity Support og Systems Engineering teams er aktivt undersøge problemet, og vil følge videre med en opdatering og opløsning så hurtigt som muligt.

2. 24. juli 2026 kl. 12.28 UTCmonitoring

   Fra 11: 02 UTC, Learnosity begyndte at se overvågning indberetninger af kortvarig, intermitterende timeouts, når adgang til Learnosity forfatter websted. Ingen andre funktioner blev påvirket, og Learnosity indberetninger ophørte kl 11: 11 UTC. Ved 11: 40 UTC rapporterede AWS om forringet service i US- West-2 (OR). Kl. 11: 56 UTC rapporterede AWS, at deres systemer var ved at komme sig. Learnosity Support and Systems Engineering teams fortsætter med aktivt at overvåge problemet, og vil følge videre med en opdatering og opløsning så hurtigt som muligt.

3. 24. juli 2026 kl. 12.35 UTCmonitoring

   Kl. 12.30 UTC rapporterede AWS, at de identificerede og rettede problemet, og at genopretningen fortsætter. Learnosity Support and Systems Engineering teams vil overvåge spørgsmålet i yderligere 30 minutter, og vil følge videre med en opdatering og opløsning så hurtigt som muligt.

4. 24. juli 2026 kl. 13.02 UTCresolved

   Fra kl. 13: 00 UTC kalder vi dette spørgsmål løst. AWS systemer er ved at komme sig og Learnosity authoring har været upåvirket i 50 minutter. Learnosity Support and Systems Engineering teams vil følge op med en post mortem, når vi har afsluttet rod årsag analyse og færdiggjort næste trin eller forebyggende foranstaltninger kræves. Kontakt venligst, hvis du har spørgsmål eller bekymringer.

5. 24. juli 2026 kl. 13.03 UTCpostmortem

   Berørte systemer og regioner Den 2026- 07- 24, Learnosity oplevet korte intermitterende timeout påvirker adgangen til Learnosity forfatter websted på grund af [en netværkshændelse i AWS US- West-2\ (OR\) regionen] (https: / / health.aws.amazon.com / health / status? eventID = arn: aws: health: us- west-2::: event / MULTIPLE _ Services / AWS _ MULTIPLE _ Services _ OPERATIONAL _ issue / AWS _ MULTIPLE _ Services _ OPERATIONAL _ ISSE _ 83A36 _ 24C89B493A6). Learnosity kunde kollision begyndte omkring 11: 02 UTC og sluttede på 11: 11 UTC. AWS efterfølgende afsluttet oprydning og formelt lukket deres regionale hændelse på 12: 12 UTC. Den samlede varighed af mulige konsekvenser for Learnosity kunder var omkring 9 minutter. Efterforskning Learnosity modtaget en intern alarm på 11: 02 UTC, at tjenesten i OR regionen blev påvirket og straks indledt en undersøgelse. Den første undersøgelse viste ingen tegn på nedbrydning af Learnosity Service. Yderligere undersøgelse identificerede intermitterende timeouts påvirker adgangen til Learnosity forfatter site. Learnositeten bekræftede med AWS, at et problem, der påvirker deres netværk infrastruktur i regionen var blevet identificeret, og oprensning var begyndt. # # # Resolution Intermitterende timeouts påvirker Learnosity forfatter websted ophørte med 11: 11 UTC, og AWS effektivt løst problemet med 11: 15 UTC. AWS rapporterede en kort reconvergence begivenhed, der blev løst ved 11: 59 UTC, og officielt lukket hændelsen på 12: 12 UTC. # # Forebyggelse Ingen Learnosity systemer bidraget til denne hændelse. Intern overvågning og alarmering opførte sig som forventet.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 17. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. maj 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. maj 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. oktober 2025 kl. 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. oktober 2025 kl. 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. oktober 2025 kl. 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. oktober 2025 kl. 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. oktober 2025 kl. 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. oktober 2025 kl. 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. oktober 2025 kl. 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. oktober 2025 kl. 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. oktober 2025 kl. 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. oktober 2025 kl. 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. oktober 2025 kl. 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. oktober 2025 kl. 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. august 2025 kl. 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. august 2025 kl. 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. august 2025 kl. 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. august 2025 kl. 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. august 2025 kl. 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. august 2025 kl. 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. august 2025 kl. 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. august 2025 kl. 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. september 2025 kl. 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. august 2025 kl. 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. august 2025 kl. 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. august 2025 kl. 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. august 2025 kl. 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. marts 2025 kl. 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. marts 2025 kl. 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. marts 2025 kl. 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. marts 2025 kl. 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. marts 2025 kl. 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. marts 2025 kl. 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. januar 2025 kl. 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. januar 2025 kl. 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. januar 2025 kl. 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. januar 2025 kl. 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. januar 2025 kl. 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. oktober 2024 kl. 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. oktober 2024 kl. 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. oktober 2024 kl. 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. oktober 2024 kl. 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. september 2024 kl. 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. september 2024 kl. 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. september 2024 kl. 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. september 2024 kl. 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. maj 2024 kl. 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. maj 2024 kl. 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. maj 2024 kl. 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. maj 2024 kl. 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. maj 2024 kl. 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.