Istoricul incidentelor Learnosity

1. 26 octombrie 2026 la 18:05 UTCinvestigating

   De la 17:50 UTC, ne confruntăm cu probleme care afectează pool-urile de articole din toate regiunile. Echipele de suport pentru învățare și inginerie sisteme investighează în mod activ problema și vor continua cu o actualizare și rezoluție cât mai curând posibil.

2. 26 octombrie 2026 la 18:34 UTCinvestigating

   Din 18:30 UTC, investigăm performanţele degradate atunci când creăm şi edităm Pool-uri de articole. Investigăm, de asemenea, o problemă tangentă neconfirmată care poate afecta crearea și editarea pachetelor de evaluare a dispozitivelor locale. Toate celelalte API-uri din stivele de autor, evaluare și analiză funcționează în mod normal. Echipele de Inginerie a Învățământului și Sistemelor continuă să investigheze activ problema și vor continua cu o actualizare și rezoluție cât mai curând posibil.

3. 26 octombrie 2026 la 19:01 UTCinvestigating

   Începând cu ora 19:00 UTC, continuăm să investigăm performanţele degradate atunci când creăm sau edităm pachete de evaluare a dispozitivelor locale Pools orx. Toate celelalte API-uri din stivele de autor, evaluare și analiză funcționează în mod normal. Echipele de Inginerie a Învățământului și Sistemelor continuă să investigheze activ problema și vor continua cu o actualizare și rezoluție cât mai curând posibil.

4. 26 octombrie 2026 la 19:31 UTCmonitoring

   De la 19:30 UTC, Pool element și crearea de evaluare a dispozitivelor locale a văzut o trecere normală timp de aproximativ 30 de minute. Vom introduce acum o perioadă suplimentară de monitorizare pentru a asigura stabilitatea. Echipele de Inginerie a Învățământului și Sistemelor continuă să investigheze activ problema și vor continua cu o actualizare și rezoluție cât mai curând posibil.

5. 26 octombrie 2026 la 20:10 UTCresolved

   De la 20:10 UTC, nu am mai văzut alte probleme cu crearea sau actualizarea pachetului de evaluare a dispozitivelor locale. Rezolvăm acest incident şi vom continua să investigăm cauza principală a performanţei degradate. Echipele de Inginerie a Învățarii și Suportului Sistemelor vor continua cu o autopsie după ce am finalizat analiza cauzelor profunde și am finalizat orice pași sau măsuri preventive necesare. Vă rugăm să ajungeţi dacă aveţi întrebări sau preocupări.

Traducere automată din actualizarea oficială a incidentului.

1. 20 octombrie 2026 la 14:16 UTCinvestigating

   Începând cu 13:20 UTC, am început să vedem întârzieri notate cu serviciul nostru îmbunătăţit de evaluare matematică în regiunea SUA-Est-1. Nu au fost observate pierderi de date și toate sesiunile au fost în cele din urmă marcate. Ca efect knock-on, data API Scoring final se confruntă cu probleme intermitente de disponibilitate. Nu a fost afectată nicio livrare de autorizare sau evaluare. Echipele de suport pentru învățare și inginerie sisteme investighează în mod activ problema și vor continua cu o actualizare și rezoluție cât mai curând posibil.

2. 20 octombrie 2026 la 15:04 UTCinvestigating

   Începând cu ora 15:00 UTC, încă investigăm performanţele de scurtă durată degradate ale serviciului nostru îmbunătăţit de evaluare matematică, dar nu am văzut erori sau întârzieri semnificative de mai mult de o oră. Reflectarea sesiunilor în așteptare punctaj șterse rapid, și transmiterile continuă să fie marcate în mod normal. Toate celelalte API rămân neafectate. Echipele de Inginerie a Învățământului și Sistemelor continuă să investigheze activ problema și vor continua cu o actualizare și rezoluție cât mai curând posibil.

3. 20 octombrie 2026 la 15:51 UTCmonitoring

   Începând cu ora 15:45 UTC, măsurile de atenuare au menținut cu succes coada de depunere clară, iar notarea a continuat să funcționeze în mod normal. În cursul perioadei de performanță degradată au fost captate declarațiile primite și nu s-au pierdut date. Toate celelalte API rămân operaționale. Continuăm să investigăm cauza principală şi vom împărţi un incident postmortem odată ce investigaţia noastră este completă. Între timp, intrăm într-o perioadă de monitorizare suplimentară pentru a confirma stabilitatea continuă înainte de a închide incidentul.

4. 20 octombrie 2026 la 18:17 UTCresolved

   Începând cu ora 18:00 UTC, după o lungă perioadă de monitorizare suplimentară, fără alte probleme, am rezolvat acest incident care afectează îmbunătățirea scorului matematic în SUA-Est-1. Echipele de Inginerie a Învățarii și Suportului Sistemelor vor continua cu o autopsie după ce am finalizat analiza cauzelor profunde și am finalizat orice pași sau măsuri preventive necesare. Vă rugăm să ajungeţi dacă aveţi întrebări sau preocupări.

5. 27 octombrie 2026 la 13:27 UTCpostmortem

   ## Afected Systems and Regiunis La 20 octombrie 2026, Learnozitatea a experimentat întârzieri de notare și eșecuri intermitente ale cererii care afectează îmbunătățirea scorului matematic în SUA-Est-1. Impactul asupra clienților a început la aproximativ 13:06 UTC și s-a încheiat la 13:47 UTC, cu durata de aproximativ 41 de minute. Cererile de notare afectate s-au confruntat cu perioade de procesare mai lungi decât cele normale, iar unele cereri directe către criteriul de evaluare a datelor API au returnat erori. Pentru sesiuni salvate prin intermediul API elemente, cererile de notare afectate au fost coadă și rejudecată, ceea ce a dus la disponibilitatea scor întârziat, mai degrabă decât înscrie eșecuri. Evaluările fără întrebări și servicii matematice în alte regiuni nu au fost afectate. ## Investigation Ancheta noastră a identificat un model specific de cereri de notare care a dus la vremuri neașteptat de mari de procesare. Aceasta a redus capacitatea disponibilă pentru a procesa alte cereri de notare, cauzând întârzieri și întârzieri intermitente. Problema a fost asociată cu modul în care anumite intrări de notare au fost prelucrate, mai degrabă decât o creștere neașteptată a volumului global al cererii. ## Resolution Performanță scoring revenit la normal de 13:47 UTC. La 15:12 UTC, inginerii Learnosity au implementat izolarea traficului pentru a împiedica volumul de muncă afectat de punctaj să afecteze operațiunile de notare pentru alți clienți. ## Prevention Learnozitatea a implementat schimbări pentru a reduce consumul inutil de resurse și pentru a îmbunătăți recuperarea cererilor de notare afectate. Mai multe îmbunătățiri sunt în curs de desfășurare pentru a consolida validarea cererilor de punctaj, a îmbunătăți garanțiile de prelucrare și a împiedica ca volumul de muncă înregistrat individual să afecteze serviciul mai larg. Măsurile de izolare suplimentare vor rămâne în vigoare în timp ce aceste îmbunătățiri sunt finalizate și eficacitatea lor este verificată.

Traducere automată din actualizarea oficială a incidentului.

1. 8 octombrie 2026 la 13:40 UTCinvestigating

   Ca de 13:00 UTC, ne confruntăm cu probleme remapping Sunset API versiuni v2024.1.LTS la cele mai recente LTS versiuni în toate regiunile. Acest lucru afectează doar un număr foarte mic de clienți care sunt încă fixați la v0224.1.LTS, care a ajuns la sfârșitul vieții în martie 2026. Nu sunt afectate alte versiuni API. Echipele de suport pentru învățare și inginerie sisteme investighează în mod activ problema și vor continua cu o actualizare și rezoluție cât mai curând posibil.

2. 8 octombrie 2026 la 13:47 UTCinvestigating

   Începând cu 13:40> UTC, redirecționăm versiuni v0224.1.LTS și API devin accesibile ca actualizările caches. Echipele de Inginerie a Învățământului și Sistemelor continuă să investigheze activ problema și vor continua cu o actualizare și rezoluție cât mai curând posibil.

3. 8 octombrie 2026 la 14:20 UTCinvestigating

   De la ora 14:00 UTC, v0204.1.LTS refacă cu succes ultima versiune LTS din regiunile AMER, inclusiv SUA-Est-1 (VA) și SUA-Vest-2 (OR). Toate API-urile ar trebui să fie accesibile în aceste regiuni. În prezent reluăm legătura în regiunile EMEA şi APAC. Accesul direct la versiunile API active rămâne operațional. Această problemă afectează în prezent doar versiunea de remodelare pentru un microset de clienți din regiunile EMEA și APAC fixat la versiunea v2024.1.LTS API a apus de soare, care a ajuns la EOL în martie 2026. Echipele de Inginerie a Învățământului și Sistemelor continuă să investigheze activ problema și vor continua cu o actualizare și rezoluție cât mai curând posibil.

4. 8 octombrie 2026 la 15:15 UTCresolved

   La ora 15:00 UTC, v0204.1.LTS refacă cu succes în toate regiunile. Folosind acest șir EOL/sunset version ar trebui să acceseze toate API-urile. Echipele de Inginerie a Învățarii și Suportului Sistemelor vor continua cu o autopsie după ce am finalizat analiza cauzelor profunde și am finalizat orice pași sau măsuri preventive necesare. Vă rugăm să ajungeţi dacă aveţi întrebări sau preocupări.

Traducere automată din actualizarea oficială a incidentului.

1. 2 octombrie 2026 la 18:08 UTCinvestigating

   Ca de 16:45 UTC, am început să se confruntă cu un număr foarte scăzut de întârzieri de notare cu serviciul nostru îmbunătățit de matematică în regiunea SUA-Est-1. Toate sesiunile au fost marcate, și nu au avut loc pierderi de date. Nu sunt afectate alte IAP. Investigăm întârzieri în curs limitate la acest serviciu. Echipele de suport pentru învățare și inginerie sisteme investighează în mod activ problema și vor continua cu o actualizare și rezoluție cât mai curând posibil.

2. 2 octombrie 2026 la 18:30 UTCidentified

   Din 18:30 UTC, am identificat o problemă de scalare pentru serviciul îmbunătăţit de evaluare matematică şi lucrăm la rezolvarea problemei. Toate sesiunile continuă să fie capturate fără pierderi de date și toate celelalte API funcționează în mod normal. Echipele de Inginerie a Învățământului și Sistemelor continuă să investigheze activ problema și vor continua cu o actualizare și rezoluție cât mai curând posibil.

3. 2 octombrie 2026 la 19:10 UTCmonitoring

   Începând cu ora 19:00 UTC, nu am mai văzut întârzieri în serviciul îmbunătăţit de evaluare matematică de ceva timp şi vom intra acum într-o fază de monitorizare. Vom continua să monitorizăm timp de 30 de minute înainte de rezolvarea problemei. Echipele de Inginerie a Învățământului și Sistemelor continuă să investigheze activ problema și vor continua cu o actualizare și rezoluție cât mai curând posibil.

4. 2 octombrie 2026 la 19:52 UTCresolved

   Începând cu 19:45 UTC, am rezolvat problema care afectează îmbunătățirea scorului matematic în regiunea SUA-Est-1. Toate API-urile şi serviciile funcţionează normal. Echipele de Inginerie a Învățarii și Suportului Sistemelor vor continua cu o autopsie după ce am finalizat analiza cauzelor profunde și am finalizat orice pași sau măsuri preventive necesare. Vă rugăm să ajungeţi dacă aveţi întrebări sau preocupări.

5. 27 octombrie 2026 la 01:24 UTCpostmortem

   ## **Affected Systems and Regiunis** La 2 octombrie 2026, Learnosity a experimentat erori intermitente de notare și temporizări care afectează tipurile de întrebări matematice în SUA-Est-1. Impactul asupra clienților a început la aproximativ 16:34 UTC și s-a încheiat la 18:47 UTC, timp de aproximativ 2 ore și 13 minute. Cererile afectate ar putea experimenta întârzieri de până la 40 de secunde înainte de a eşua. Alte regiuni nu au fost afectate. ## **Investigation** Incidentul a avut loc atunci când cererea privind serviciul de notare matematică a depășit capacitatea disponibilă. Deși au fost introduse îmbunătățiri ale capacității și ale creșterii în urma unui incident anterior, serviciul a întâmpinat o limită suplimentară în configurația rețelei sale, care a împiedicat furnizarea unor noi cazuri. Impactul a fost agravat de calcule lente care au ocupat cazuri mai lungi decât s-a prevăzut, deoarece termenele de calcul nu au fost aplicate în mod fiabil sub sarcină grea. Împreună, aceste condiții au împiedicat serviciul să crească suficient pentru a gestiona cererea. "Rezoluţia" Inginerii de invataciune au restaurat serviciul prin mutarea serviciului de notare la o configuratie de retea cu capacitate suplimentara de scalare si cresterea resurselor de calcul alocate fiecarei instante. Aceste modificări au permis serviciului să recupereze, cu erori de notare de compensare de 18:47 UTC. ## **Prevention** Learnozitatea a actualizat mecanismul de aplicare a limitelor de timp de calcul pentru a termina în mod fiabil calculele lente sub sarcină grea. De asemenea, controalele sanitare au fost separate de procesul de calcul pentru a preveni înlocuirea inutilă a cazurilor. Serviciul funcționează acum cu capacitate suplimentară de calcul și rețea. Mai multe îmbunătățiri arhitecturale sunt în curs de desfășurare pentru a împiedica capacitatea de rețea să limiteze scalarea viitoare și evaluăm termene mai scurte de calcul pentru a reduce impactul calculelor neobișnuit de lente.

Traducere automată din actualizarea oficială a incidentului.

1. 11 septembrie 2026 la 18:19 UTCinvestigating

   Începând cu ora 17:00 UTC, investigăm în prezent probleme minore intermitente cu scorul în regiunea SUA-Est-1. Echipele de suport pentru învățare și inginerie sisteme investighează în mod activ problema și vor continua cu o actualizare și rezoluție cât mai curând posibil.

2. 11 septembrie 2026 la 18:30 UTCinvestigating

   Din 18:30 UTC, toate API-urile rămân operaționale și monitorizăm eficiența scorului. Echipele de Inginerie a Învățământului și Sistemelor continuă să investigheze activ problema și vor continua cu o actualizare și rezoluție cât mai curând posibil.

3. 11 septembrie 2026 la 19:42 UTCidentified

   Din 19:30 UTC, am confirmat că aceasta este o problemă sporadică cu notarea a doar trei tipuri de întrebări matematice îmbunătățite. Aceste încercări de notare reușesc la retry și nici un alt API nu sunt afectate. Echipele de Inginerie a Învățământului și Sistemelor continuă să investigheze activ problema și vor continua cu o actualizare și rezoluție cât mai curând posibil.

4. 11 septembrie 2026 la 20:53 UTCmonitoring

   Începând cu ora 20:45 UTC, am îmbunătăţit gestionarea cererilor iniţiale de notare a EMS şi vom introduce acum o fază de monitorizare de 60 de minute. Toate API-urile continuă să funcţioneze normal. Echipele de Inginerie a Învățământului și Sistemelor continuă să investigheze activ problema și vor continua cu o actualizare și rezoluție cât mai curând posibil.

5. 11 septembrie 2026 la 21:44 UTCresolved

   Începând cu 21:45 UTC, răspunsurile la întrebări de tip Math Scoring îmbunătăţite marchează în mod normal în regiunea SUA-Est-1, toate API funcţionează normal şi închidem acest incident. Echipele de Inginerie a Învățarii și Suportului Sistemelor vor continua cu o autopsie după ce am finalizat analiza cauzelor profunde și am finalizat orice pași sau măsuri preventive necesare. Vă rugăm să ajungeţi dacă aveţi întrebări sau preocupări.

6. 27 octombrie 2026 la 01:23 UTCpostmortem

   ## **Affected Systems and Regiunis** La 11 septembrie 2026, Learnosity a experimentat erori intermitente de notare și temporizări care afectează tipurile de întrebări matematice în SUA-Est-1. Impactul asupra clienților a început la aproximativ 17:00 UTC și s-a încheiat la 21:45 UTC, cu o durată de aproximativ 4 ore și 45 de minute. Alte tipuri de întrebări au continuat să puncteze în mod normal, iar alte regiuni nu au fost afectate. Cele mai multe cereri eşuate au reuşit să se refacă. ## **Investigation** Incidentul a fost cauzat de capacitatea insuficientă a serviciului de notare matematică în urma creșterii cererii în cursul săptămânilor precedente. Serviciul a atins numărul maxim de cazuri configurate și nu s-a putut extinde mai departe pentru a se adapta sarcinii. Acest lucru a fost compus din resurse limitate de calcul per caz și calcule lente care au ocupat cazuri mai mult decât s-a intenționat. În cazul unei sarcini grele, termenul de calcul nu a fost aplicat în mod fiabil, iar cazurile aglomerate ar putea să nu facă obiectul controalelor de sănătate și să fie înlocuite, reducând în continuare capacitatea disponibilă. "Rezoluţia" Inginerii de invataciune au restaurat serviciul prin cresterea numarului de cazuri de functionare si cresterea limitei maxime de instanta. Operaţiuni normale de notare reluate până la 21:45 UTC, şi toate cererile de notare rămase au fost procesate până la 23:17 UTC. La 14 septembrie, au fost efectuate modificări suplimentare ale configurației pentru a crește resursele de calcul, a îmbunătăți scalarea automată și a reduce înlocuirea inutilă a cazurilor. ## **Prevention** Learnozitatea a crescut capacitatea de notare, a ridicat limitele de instanță, și a îmbunătățit scalarea automată bazată pe utilizarea procesorului. Controalele sanitare au fost separate de prelucrarea calculelor pentru a preveni identificarea incorectă a cazurilor aglomerate ca fiind nesănătoase. De asemenea, am îmbunătățit aplicarea termenului limită de calcul și am extins monitorizarea și alertarea pentru utilizarea resurselor, timpii de răspuns și erorile de notare. Sunt în curs de desfășurare eforturi suplimentare pentru a consolida capacitatea de scalare a rețelei și pentru a evalua termenele de calcul mai scurte.

Traducere automată din actualizarea oficială a incidentului.

1. 24 iulie 2026 la 12:16 UTCinvestigating

   Suntem conştienţi de o problemă AWS aflată în curs de desfăşurare care afectează regiunea US-West-2 (OR), care poate cauza probleme intermitente de conectivitate atunci când accesează mediul de autorizare a learnozităţii. Monitorizăm în mod activ situația și vom furniza actualizări pe măsură ce acestea devin disponibile. În acest moment, impactul asupra clienților Learnosity este scurt și intermitent și limitat la autor. Evaluările şi alte IAP se comportă normal. Echipele de suport pentru învățare și inginerie sisteme investighează în mod activ problema și vor continua cu o actualizare și rezoluție cât mai curând posibil.

2. 24 iulie 2026 la 12:28 UTCmonitoring

   Începând cu 11:02 UTC, Learnosity a început să vadă alerte de scurtă durată, temporizări intermitente atunci când accesează site-ul Autor Learnosity. Nu a fost afectată nicio altă funcționalitate, iar alertele privind learnozitatea au încetat la 11:11 UTC. La 11:40 UTC, AWS a raportat servicii degradate în SUA-Vest-2 (OR). La 11:56 UTC, AWS a raportat recuperarea sistemelor lor. Echipele de suport și inginerie a sistemelor de învățare continuă să monitorizeze în mod activ problema și vor continua cu o actualizare și rezoluție cât mai curând posibil.

3. 24 iulie 2026 la 12:35 UTCmonitoring

   La 12:30 UTC, AWS a raportat că au identificat și corectat problema și că recuperarea continuă. Echipele de suport și inginerie a sistemelor de învățare vor monitoriza problema pentru încă 30 de minute și vor continua cu o actualizare și rezoluție cât mai curând posibil.

4. 24 iulie 2026 la 13:02 UTCresolved

   De la ora 13:00 UTC, numim această problemă rezolvată. Sistemele AWS sunt de recuperare și autorizarea Learnosity a fost neafectată timp de 50 de minute. Echipele de Inginerie a Învățarii și Suportului Sistemelor vor continua cu o autopsie după ce am finalizat analiza cauzelor profunde și am finalizat orice pași sau măsuri preventive necesare. Vă rugăm să ajungeţi dacă aveţi întrebări sau preocupări.

5. 24 iulie 2026 la 13:03 UTCpostmortem

   ### Afectarea sistemelor și regiunilor Pe data de 2026-07-24, Learnozitatea a experimentat scurte perioade intermitente de timp care afectează accesul la site-ul autorului Learnosity din cauza [un incident de rețea în US-West-2 \ [OR\) regiune] [https://health.aws.amazon.com/health/status?eventID=awn:aws:health:us-west-2:::event/MULTIPLLE SERVICES/AWS MULTIPLLE SERVICES OPERATIONAL ISSUE/AWS MULTIPLLE SERVICES OPERATIONAL ISSUE 83A36 24C89B493A6). Impactul asupra clientului a început la aproximativ 11:02 UTC și s-a încheiat la 11:11 UTC. AWS a finalizat ulterior remedierea și și-a închis oficial incidentul regional la 12:12 UTC. Durata totală a impactului posibil asupra clienților Learnosity a fost de aproximativ 9 minute. ### Investigation La 11:02 UTC a primit o alertă internă că serviciul din regiunea RUP a fost afectat și a început imediat o anchetă. Investigaţia iniţială nu a găsit nicio dovadă de degradare a serviciului de învăţare. Anchetă suplimentară a identificat temporizări intermitente care afectează accesul la site-ul autorului Learnosity. Învățământul a confirmat cu AWS că a fost identificată o problemă care a afectat infrastructura de rețea din regiune și că a început remedierea. ### Rezolution Timeouts intermitente care afectează site-ul Autor Learnozitate a încetat de 11:11 UTC, și AWS a rezolvat efectiv problema de 11:15 UTC. AWS a raportat un scurt eveniment de reconversie care a fost rezolvat de 11:59 UTC și a închis oficial incidentul la 12:12 UTC. ### Prevention Nici un sistem de învăţare nu a contribuit la acest incident. Monitorizarea internă și alertarea s-au comportat așa cum era de așteptat.

Traducere automată din actualizarea oficială a incidentului.

1. 17 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 mai 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 mai 2026 la 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 februarie 2026 la 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 februarie 2026 la 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 februarie 2026 la 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 februarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 octombrie 2025 la 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 octombrie 2025 la 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 octombrie 2025 la 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 octombrie 2025 la 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 octombrie 2025 la 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 octombrie 2025 la 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 octombrie 2025 la 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 octombrie 2025 la 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 octombrie 2025 la 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 octombrie 2025 la 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 octombrie 2025 la 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 octombrie 2025 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 septembrie 2025 la 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 la 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 la 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 la 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 la 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 martie 2025 la 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 martie 2025 la 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 martie 2025 la 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 martie 2025 la 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 martie 2025 la 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 martie 2025 la 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 ianuarie 2025 la 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 ianuarie 2025 la 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 ianuarie 2025 la 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 ianuarie 2025 la 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 ianuarie 2025 la 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 octombrie 2024 la 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 octombrie 2024 la 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 octombrie 2024 la 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 octombrie 2024 la 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 septembrie 2024 la 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 septembrie 2024 la 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 septembrie 2024 la 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 septembrie 2024 la 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 mai 2024 la 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 mai 2024 la 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 mai 2024 la 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 mai 2024 la 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 mai 2024 la 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.