Learnosity の障害履歴

1. 2026年10月26日 18:05 UTCinvestigating

   17:50現在、全地域におけるアイテムプールに影響を及ぼす問題が発生しています。 学習支援とシステムエンジニアリングチームは、積極的に問題を調査し、できるだけ早くアップデートと解像度でフォローします.

2. 2026年10月26日 18:34 UTCinvestigating

   18:30 UTCでは、アイテムプールの作成と編集時に劣化したパフォーマンスを調査しています。 また、ローカルデバイスアセスメントパッケージの作成と編集に影響を及ぼす可能性のある非対称的な問題を検討しています。 作者、評価および分析の積み重ねの他のすべてのAPIは普通機能しています。 学習支援とシステムエンジニアリングチームは、積極的に問題を調査し続けており、できるだけ早くアップデートと解像度でフォローします.

3. 2026年10月26日 19:01 UTCinvestigating

   UTCは、19時以降、アイテムプールやローカルデバイスアセスメントパッケージの作成や編集時に劣化した性能を調査し続けています。 作者、評価および分析の積み重ねの他のすべてのAPIは普通機能しています。 学習支援とシステムエンジニアリングチームは、積極的に問題を調査し続けており、できるだけ早くアップデートと解像度でフォローします.

4. 2026年10月26日 19:31 UTCmonitoring

   19:30 UTC の項目プールおよびローカル装置の評価の作成はおよそ 30 分のための正常なスループットを見ました。 安定性を確保するために、追加の監視期間を入力します。 学習支援とシステムエンジニアリングチームは、積極的に問題を調査し続けており、できるだけ早くアップデートと解像度でフォローします.

5. 2026年10月26日 20:10 UTCresolved

   20:10のUTCでは、アイテムプールやローカルデバイスアセスメントパッケージの作成やアップデートに関する問題はありません。 この事件を解決し、劣化した性能の根本原因を調査し続けます。 学習支援とシステムエンジニアリングチームは、根本的な原因分析を完了し、次のステップや予防措置を確定したら、ポストモテでフォローアップします。 ご不明な点がございましたら、お気軽にお問い合わせください.

公式のインシデント更新を自動翻訳しています。

1. 2026年10月20日 14:16 UTCinvestigating

   13:20現在、米国東部1地域における高度化した数学のスコアリングサービスで、スコアリングの遅延が始まりました。 データの損失が観察されず、すべてのセッションが最終的にスコアアップされています。 ノックオン効果として、データAPIのスキャリングエンドポイントは、断続的な可用性の問題が発生しています。 許可または評価の配達は影響しません。 学習支援とシステムエンジニアリングチームは、積極的に問題を調査し、できるだけ早くアップデートと解像度でフォローします.

2. 2026年10月20日 15:04 UTCinvestigating

   15:00 UTCと同様に、拡張された数学のスコアリングサービスの短命分解性能を調査していますが、重要なエラーや1時間以上の遅延が見られていません。 セッションのバックログはすぐにスコアリングを待っており、投稿は正常にスコアリングされます。 他のすべての API は影響を受けません。 学習支援とシステムエンジニアリングチームは、積極的に問題を調査し続けており、できるだけ早くアップデートと解像度でフォローします.

3. 2026年10月20日 15:51 UTCmonitoring

   15:45 UTCと同様に、移行対策は正常に送信キューをクリアし、スキャリングは正常に動作し続けてきました。 劣化した性能の期間中に受けた演題を捕捉し、データが失われない。 他のすべての API は動作し続けます。 根本的な原因を調査し続け、調査が完了すると事件の姿勢を共有します。 その間に、事件を閉鎖する前に、継続的な安定性を確認するために、追加の監視期間を入力します.

4. 2026年10月20日 18:17 UTCresolved

   UTCの18時以降は、さらなる問題なく追加の監視期間の長い期間の後、米国東部-1で強化された数学のスコアリングに影響を与えるこの事件を解決しています。 学習支援とシステムエンジニアリングチームは、根本的な原因分析を完了し、次のステップや予防措置を確定したら、ポストモテでフォローアップします。 ご不明な点がございましたら、お気軽にお問い合わせください.

5. 2026年10月27日 13:27 UTCpostmortem

   ## 感染したシステムと地域 2026年10月20日、米国東部-1で強化された数学のスコアリングに影響を及ぼす学習の遅延および断続的な要求の失敗を経験した。 顧客の衝撃は、約13:06 UTCで始まり、13:47 UTCで終了しました。 通常の処理時間よりも長い実績があり、データ API のスコアリングエンドポイントの返されたエラーに対する直接リクエストがいくつかあります。 セッションは、Item API によって保存され、影響を受けたスコアリングリクエストがキューに入れられ、取得され、スコアリングの失敗ではなく、スコアの可用性が遅延しました。 他の地域での数学の質問やサービスがない評価は影響を受けていませんでした。 ## 調査 当社の調査は、予期しない高い処理時間に起因するスコアリング要求の特定のパターンを特定しました。 これにより、他のスコアリングリクエストを処理する能力が低下し、遅延や断続的なタイムアウトを引き起こします。 問題は、要求全体のボリュームの予期しない増加ではなく、特定のスコアリング入力が処理された方法に関連しました。 ## 決断 13:47 UTCで正常に返されたスコアリング性能。 15:12 UTCでは、Wendosityのエンジニアは、影響を受けたスコアリングのワークロードが他の顧客のスコアリング操作に影響を及ぼすことを防ぐため、追加のトラフィックの分離を実施しました。 ## 予防 学習者は、不要なリソース消費を削減し、影響を受けるスコアリングリクエストの回復を改善するために変更を実施しました。 さらなる改良は、スコアリング要求の検証を強化し、処理の安全性を改善し、個々のスコアリングのワークロードがより広いサービスに影響を与えるのを防ぐためのものです。 これらの改善が完了し、その有効性が検証される間、追加の分離対策は所定の位置に残ります.

公式のインシデント更新を自動翻訳しています。

1. 2026年10月8日 13:40 UTCinvestigating

   弊社では、13時現在、全ての地域で最新のLTSリリースに、日没APIバージョンv2024.1.LTSを再マッピングする問題を抱えています。 これは、まだv2024.1.LTSにピン留めされている顧客の非常に小さな数にのみ影響します。, 3月に終了に達した 2026. 他のAPIのバージョンは影響しません。 学習支援とシステムエンジニアリングチームは、積極的に問題を調査し、できるだけ早くアップデートと解像度でフォローします.

2. 2026年10月8日 13:47 UTCinvestigating

   UTCは13:40の時点で、v2024.1.LTSバージョンとAPIをキャッシュ更新としてアクセスできるようにリダイレクトしています。 学習支援とシステムエンジニアリングチームは、積極的に問題を調査し続けており、できるだけ早くアップデートと解像度でフォローします.

3. 2026年10月8日 14:20 UTCinvestigating

   14 UTCと同様に、v2024.1.LTSは、米国東1(VA)と米国西2(OR)を含む、AMER地域の最新のLTSバージョンに正常に再マッピングされます。 これらの領域ですべての API がアクセス可能です。 現在、EMEAとAPAC領域で再マッピング中です。 アクティブな API のバージョンへの直接アクセスは、運用中のままです。 この問題は、EMEAとAPAC領域の微小な顧客のバージョンのリマッピングにのみ影響します。 日没したv2024.1.LTS APIバージョン、それは3月にEOLに達しました 2026. 学習支援とシステムエンジニアリングチームは、積極的に問題を調査し続けており、できるだけ早くアップデートと解像度でフォローします.

4. 2026年10月8日 15:15 UTCresolved

   15:00 UTCと同様に、v2024.1.LTSはすべての地域で正常に再マッピングされます。 この EOL/sunset バージョン文字列を使用して、すべての API にアクセスします。 学習支援とシステムエンジニアリングチームは、根本的な原因分析を完了し、次のステップや予防措置を確定したら、ポストモテでフォローアップします。 ご不明な点がございましたら、お気軽にお問い合わせください.

公式のインシデント更新を自動翻訳しています。

1. 2026年10月2日 18:08 UTCinvestigating

   16:45のUTCでは、米国東1地域における強化された数学のスコアリングサービスで、非常に低い数のスコアリング遅延を経験し始めました。 すべてのセッションが得られ、データの損失は発生しません。 他の API は影響しません。 本サービスに限らず、継続的な遅延を調査しています。 学習支援とシステムエンジニアリングチームは、積極的に問題を調査し、できるだけ早くアップデートと解像度でフォローします.

2. 2026年10月2日 18:30 UTCidentified

   18:30 UTCでは、強化された数学のスコアリングサービスのスケーリング問題を特定し、問題の解決に取り組んでいます。 すべてのセッションは、データの損失なくキャプチャされ、他のすべての API は正常に動作しています。 学習支援とシステムエンジニアリングチームは、積極的に問題を調査し続けており、できるだけ早くアップデートと解像度でフォローします.

3. 2026年10月2日 19:10 UTCmonitoring

   19:00 UTCの時点では、拡張された数学のスコアリングサービスの遅延は見られず、監視フェーズに入ります。 問題解決の30分前にモニターを続けていきます。 学習支援とシステムエンジニアリングチームは、積極的に問題を調査し続けており、できるだけ早くアップデートと解像度でフォローします.

4. 2026年10月2日 19:52 UTCresolved

   19:45のUTCでは、米国東1地域における高機能化の課題を解決しました。 すべての API およびサービスは正常に機能します。 学習支援とシステムエンジニアリングチームは、根本的な原因分析を完了し、次のステップや予防措置を確定したら、ポストモテでフォローアップします。 ご不明な点がございましたら、お気軽にお問い合わせください.

5. 2026年10月27日 1:24 UTCpostmortem

   ##**感染したシステムと地域** 2026年10月2日、Wendosityは、米国東1の数学質問タイプに影響を与える断続的なスコアリングエラーとタイムアウトを経験しました。 顧客の影響は、約16:34 UTCで始まり、18:47 UTCで終了し、約2時間13分持続します。 欠陥のあるリクエストは、失敗する前に最大40秒の遅延が発生する可能性があります。 その他の地域は影響を受けません。 ## **調査** 数学のスコアリングサービスの需要が利用可能な容量を超えた場合に発生した事故。 以前のインシデントでは、容量とスケーリングの改善が導入されましたが、サービスでは、さらなるインスタンスがプロビデントされるのを防ぐネットワーク設定で追加の制限が発生しました。 この影響は、計算時間制限が重負荷の下で確実に強制されないため、想定されるよりも長いインスタンスを占有する遅い計算によって合成されました。 これらの条件は、要求を処理するために十分なスケーリングからサービスを防止しました。 ##**ソリューション** 学習エンジニアは、スコアリングサービスをネットワーク設定に移動し、追加のスケーリング能力を拡張し、各インスタンスに割り当てられたコンピュートリソースを増加させることでサービスを復元する。 これらの変更は、サービスが回復することを可能にします, スコアリングエラーでクリア 18:47 UTC. ##**予防措置** 学習者は、計算時間制限の執行メカニズムを更新し、重負荷下での遅い計算を確実に終了させました。 健康診断は、計算処理から分離され、不要なインスタンスの置換を防ぎます。 サービスは、追加のコンピュートとネットワーク容量で動作します。 さらなるアーキテクチャの改善は、ネットワーク容量が将来のスケーリングを制限するのを防ぐためです。また、短時間で計算時間を制限し、異常に遅い計算の影響を削減します.

公式のインシデント更新を自動翻訳しています。

1. 2026年9月11日 18:19 UTCinvestigating

   現在、米国東部1地域におけるスコーリングに関するマイナーな断続的な問題を調査中です。 学習支援とシステムエンジニアリングチームは、積極的に問題を調査し、できるだけ早くアップデートと解像度でフォローします.

2. 2026年9月11日 18:30 UTCinvestigating

   18:30 UTC 以降、全ての API は動作し、スコーリング効率を監視しています。 学習支援とシステムエンジニアリングチームは、積極的に問題を調査し続けており、できるだけ早くアップデートと解像度でフォローします.

3. 2026年9月11日 19:42 UTCidentified

   19:30 UTC では、3つの数学の質問タイプだけをスキャリングして、これを確認しました。 これらのスコアリングの試みは再試行に成功し、他のAPIは影響しません。 学習支援とシステムエンジニアリングチームは、積極的に問題を調査し続けており、できるだけ早くアップデートと解像度でフォローします.

4. 2026年9月11日 20:53 UTCmonitoring

   20:45 UTC では、EMS スコアリングリクエストとレトリーの処理を改善し、60分監視フェーズに入ります。 すべての API は正常に機能し続けます。 学習支援とシステムエンジニアリングチームは、積極的に問題を調査し続けており、できるだけ早くアップデートと解像度でフォローします.

5. 2026年9月11日 21:44 UTCresolved

   21:45 UTC と同様に、数学のスコアリング 質問型応答は、米国東1地域では正常にスコアリングされ、すべての API は正常に機能しており、このインシデントを閉鎖しています。 学習支援とシステムエンジニアリングチームは、根本的な原因分析を完了し、次のステップや予防措置を確定したら、ポストモテでフォローアップします。 ご不明な点がございましたら、お気軽にお問い合わせください.

6. 2026年10月27日 1:23 UTCpostmortem

   ##**感染したシステムと地域** 2026年9月11日、Wendosityは、米国東1の数学質問タイプに影響を与える断続的なスコアリングエラーとタイムアウトを経験しました。 顧客への影響は、約17時から始まり、21:45 UTCで終了し、約4時間45分です。 その他の質問は、通常スコアを続け、他の地域は影響を受けていませんでした。 取得時に失敗したリクエストのほとんどが成功しました。 ## **調査** 前週の需要増加後、数学のスコアリングサービスの不十分な容量による事件が発生しました。 サービスは、その設定された最大インスタンス数に達し、負荷に対応するため、さらに拡張できませんでした。 これは、インスタンスごとの限られた計算リソースと意図よりも長いインスタンスを占有する遅い計算によって合成されました。 重負荷下では、計算時間制限が確実に施行されず、繁忙期のインスタンスは健康チェックに失敗し、交換され、利用可能な容量をさらに削減できます。 ##**ソリューション** 学習エンジニアは、実行インスタンスの数を増やし、最大インスタンスの制限を上げることでサービスを復元する。 通常のスコアリング操作は21:45 UTCで再開し、残りのキュートスコアリングリクエストはすべて23:17 UTCによって処理されました。 9月14日には、コンピュートリソースを増加させ、自動スケーリングを改善し、不要なインスタンスの交換を削減するために、追加の構成の変更が展開されました。 ##**予防措置** 学習力は、スキャリング能力を高め、インスタンスの制限を増加させ、プロセッサ利用に基づいて自動スケーリングを改善しました。 健康診断は、計算処理から分離され、忙しいインスタンスが不健康なように誤って識別されるのを防ぐことができます。 また、資源利用、応答時間、スキャリングエラーに対して、計算時間制限の執行と拡張監視および警告を改善しました。 ネットワークのスケーリング能力を強化し、より短い計算時間制限を評価するために、さらなる作業が進んでいます.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月24日 12:16 UTCinvestigating

   米国西部-2(OR)地域に影響を及ぼすAWSの問題は、学習者の許可環境にアクセスする際に断続的な接続の問題を引き起こす可能性があります。 状況を積極的に監視し、アップデートを配信します。 現時点では、Wendosityのお客様へのインパクトは簡潔で断続的であり、許可に限定されています。 アセスメント、その他の API は、通常は値下げされます。 学習支援とシステムエンジニアリングチームは、積極的に問題を調査し、できるだけ早くアップデートと解像度でフォローします.

2. 2026年7月24日 12:28 UTCmonitoring

   11:02 UTCと同様に、学習者は、学習者のサイトにアクセスする際に、短時間、断続的なタイムアウトのモニターアラートを見始めました。 他の機能が影響されず、11:11 UTCで終了したGenchosityアラート。 AWS は、米国西2(OR)で、11:40 UTC で劣化したサービスを報告しました。 11:56 UTCでは、AWSはシステムが回復していたと報告した。 学習支援とシステムエンジニアリングチームは、積極的に問題を監視し続けており、できるだけ早くアップデートと解像度をフォローします.

3. 2026年7月24日 12:35 UTCmonitoring

   12:30 UTC では、AWS は、問題を特定し修正したことを報告し、その回復は継続している。 学習支援とシステムエンジニアリングチームは、30分間問題を監視し、できるだけ早くアップデートと解像度でフォローします.

4. 2026年7月24日 13:02 UTCresolved

   13:00 UTCの時点で、この問題は解決しました。 AWSシステムが回復し、学習者の許可が50分もたらされていない。 学習支援とシステムエンジニアリングチームは、根本的な原因分析を完了し、次のステップや予防措置を確定したら、ポストモテでフォローアップします。 ご不明な点がございましたら、お気軽にお問い合わせください.

5. 2026年7月24日 13:03 UTCpostmortem

   ## 感染したシステムと地域 2026-07-24, Learnosityは、AWS US-West-2\(OR\)領域におけるネットワークインシデントによる学習者サイトへのアクセスに影響を与える簡単な断続的なタイムアウトを経験しました。(https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-west-2::event/MULTIPLE SERVICES/AWS MULTIPLE SERVICES/AWS MULTIPLE SERVICES/SERVICES/SERVICES/SERVICES/SERVS/SERVICES/SERVS/SERVS/SERVS/SERVS/SERVS/SERVS/SERVS/ASEASEASEASEASES/S/S/S/S/SERVICES/S/SERVICES/SERVS/SERVS/SERVICES/SERVICES/SERVS/SERVS/SERVS/SERVS/SERVS/SERVS/SERVICES/SERVS/S/SERVS/SERV 学習客のインパクトは、約11:02 UTCで始まり、11:11 UTCで終了しました。 AWS は、その地域の事故を 12:12 UTC で正式に終了しました。 学習客に及ぼす影響は、約9分程度でした。 ### 調査 学習者は、OR地域のサービスが影響を受けた11:02 UTCで内部アラートを受け取り、すぐに調査を開始しました。 初期調査では、学習サービス劣化の証拠が見つかりませんでした。 さらなる調査は、学習者のサイトへのアクセスに影響を与える断続的なタイムアウトを特定しました。 AWSでは、地域のネットワークインフラに影響を及ぼす問題が特定され、是正が始まりました。 ## 決断 学習者のサイトに影響する断続的なタイムアウトは11:11 UTCによって中止され、AWSは11:15 UTCによって効果的に問題を解決しました。 AWSは11:59 UTCによって解決された簡単な再構成イベントを報告し、12:12 UTCで正式に事件を閉鎖した。 ### 予防 学習システムがこの事件に寄与しない 内部監視と警告は期待どおりに動作します.

公式のインシデント更新を自動翻訳しています。

1. 2026年4月17日 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. 2026年4月17日 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. 2026年4月17日 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. 2026年4月17日 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. 2026年5月4日 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. 2026年4月16日 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. 2026年4月16日 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. 2026年5月4日 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. 2026年2月4日 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. 2026年2月4日 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. 2026年2月4日 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. 2026年2月10日 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. 2026年1月12日 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. 2026年1月12日 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. 2026年1月12日 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. 2025年10月20日 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. 2025年10月20日 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. 2025年10月20日 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. 2025年10月20日 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. 2025年10月20日 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. 2025年10月20日 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. 2025年10月20日 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. 2025年10月20日 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. 2025年10月20日 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. 2025年10月2日 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. 2025年10月2日 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. 2025年10月2日 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. 2025年8月19日 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. 2025年8月19日 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. 2025年8月19日 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. 2025年8月19日 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. 2025年8月19日 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. 2025年8月19日 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. 2025年8月19日 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. 2025年8月19日 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. 2025年9月19日 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. 2025年8月8日 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. 2025年8月8日 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. 2025年8月8日 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. 2025年8月8日 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. 2025年3月3日 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. 2025年3月3日 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. 2025年3月3日 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. 2025年3月3日 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. 2025年3月3日 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. 2025年3月14日 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. 2025年1月9日 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. 2025年1月9日 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. 2025年1月9日 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. 2025年1月9日 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. 2025年1月14日 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. 2024年10月1日 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. 2024年10月1日 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. 2024年10月1日 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. 2024年10月1日 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. 2024年9月13日 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. 2024年9月13日 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. 2024年9月13日 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. 2024年9月13日 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. 2024年5月22日 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. 2024年5月22日 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. 2024年5月22日 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. 2024年5月22日 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. 2024年5月22日 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.