Blackboard の障害履歴

1. 2026年8月19日 22:10 UTCinvestigating

   ブラックボードは現在、顧客の数に影響を与えるサービスの混乱を調査しています。 米国東部のブラックボードLMSに展開しているクライアントのグループに影響を及ぼすストレージシステムに関するエラー率が増加しました。 追加アップデートはステータスに投稿されます。blackboard.com

2. 2026年8月19日 22:48 UTCinvestigating

   私たちは、問題の調査を続けており、Blackboardのインフラストラクチャパートナーと協力して、問題の診断と解決を迅速に行うことができます。 Status.blackboard.com のアップデートを引き続き提供いたします

3. 2026年8月19日 23:10 UTCinvestigating

   アップデート: 「ブラックボード - SaaS - グローバル」から「ブラックボード - SaaS(US)」へのスコープの調整

4. 2026年8月20日 1:17 UTCinvestigating

   ブラックボードは、インフラストラクチャパートナーと直接連携し、問題を診断および解決しています。 Status.blackboard.com のアップデートを引き続き投稿します

5. 2026年8月20日 1:40 UTCidentified

   問題は特定され、ブラックボードはサービスを再起動し、復元するために作業しています。 すべてのサービスが完全に回復されていることを確認するために働く間、引き続き不安定性があるかもしれません。 Status.blackboard.comへのアップデートは1時間になります

6. 2026年8月20日 3:36 UTCmonitoring

   問題は特定され、影響を受けたサービスは復元されています。 ブラックボードは、これらの下流サービスを監視し続けています。 アップデートは、このインシデントが解決するまで、status.blackboard.comに引き続き投稿されます.

7. 2026年8月20日 4:40 UTCmonitoring

   サービスが復元されました。 ブラックボードは、これらの下流サービスを監視し続けています.

8. 2026年8月20日 9:09 UTCmonitoring

   影響を受けたサービスは復元され、安定しています。 ブラックボードは、継続的な安定性を確保するために、過度のサービスを監視し続けています.

9. 2026年8月20日 13:41 UTCmonitoring

   影響を受けたサービスは安定しています。 ブラックボードは、継続的な安定性を確保するために、過度のサービスを監視し続けています。 次回のアップデートは、ビジネスのクローズにより提供されます.

10. 2026年8月20日 21:46 UTCmonitoring

    影響を受けたサービスは安定しています。 ブラックボードは、継続的な安定性を確保するために、過度のサービスを監視し続けています。 明日(金曜日)の朝から次のアップデートが提供されます.

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

1. 2026年8月19日 21:48 UTCidentified

   米国東部のブラックボードLMSに展開するクライアントのグループに影響を及ぼすストレージシステムに関連するエラー率の上昇を調査しています

2. 2026年8月19日 22:01 UTCidentified

   この問題の修正には引き続き取り組んでいます。

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

1. 2026年8月11日 13:53 UTCidentified

   A few Blackboard LMS clients are currently experiencing Intermittent issues. The team is investigating the root cause and working to restore normal performance.

2. 2026年8月11日 14:28 UTCidentified

   Our team is actively working on the fix and continuing to investigate the root cause. We are closely monitoring the situation and working to restore normal performance as soon as possible.

3. 2026年8月11日 15:16 UTCidentified

   Our team continues to investigate the underlying cause and is actively working toward a permanent resolution. The site has remained stable since 10:00 AM ET. We will continue to closely monitor the service and provide further updates as more information becomes available.

4. 2026年8月11日 16:18 UTCidentified

   Our team continues to investigate the underlying cause and is actively working toward a permanent resolution. The site has remained stable since 10:00 AM ET, with no impact observed during this period. We will continue to closely monitor the service and provide further updates as more information becomes available.

5. 2026年8月11日 17:31 UTCidentified

   Our team has identified the issue and is actively working toward a permanent resolution. The site has remained stable since 10:00 AM ET, with no impact observed during this period. We will continue to closely monitor the service and provide further updates as more information becomes available.

6. 2026年8月11日 18:56 UTCmonitoring

   Our team has identified the issue and is actively working toward a permanent resolution. The site has remained stable since 10:00 AM ET, with no impact observed during this period. We will continue to closely monitor the service and provide further updates as more information becomes available.

7. 2026年8月11日 21:05 UTCresolved

   The sites have remained stable since 10:00 AM ET, with no further issues. Closing the incident.

1. 2026年8月3日 14:49 UTCinvestigating

   すべてのメッセージング機能は現在ダウンしています。 営業担当より迅速に対応いたします.

2. 2026年8月3日 17:34 UTCresolved

   この事件は解決しました.

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

1. 2026年7月16日 18:18 UTCinvestigating

   基準を編集したり、オフラインレポートを生成しようとすると、認定およびプログラムレビューに表示されるエラーを認識しています。 開発チームは、この問題を解決するために取り組んでいます.

2. 2026年7月17日 19:17 UTCresolved

   この事件は解決しました.

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

1. 2026年7月16日 8:33 UTCinvestigating

   現在、複数のクライアントが生産環境に影響を及ぼす問題について調査しています.

2. 2026年7月16日 8:51 UTCidentified

   AWS CloudFront に関連する問題を特定しました。 AWSと連携し、サービスを迅速に復元します。 当社のチームは、状況を密接に監視し、追加情報が利用可能になったらただちに更新を提供します.

3. 2026年7月16日 9:40 UTCidentified

   お客さまのサブセットに影響を及ぼす問題を特定しました。 AWSでは、問題が確認され、衝撃を低減するための緩和の取り組みに積極的に取り組んでいます。 当社のチームは、状況を密接に監視し、AWSと調整し、完全な回復に向けて取り組んでいます。 今後も、より一層の最新情報をお届けしてまいります.

4. 2026年7月16日 10:25 UTCidentified

   AWSは今後も緩和努力に取り組んでまいります。また、当社のチームは積極的に取り組み、密接に協力し続けています。 今後も環境を監視し、アップデートを進展させていきます.

5. 2026年7月16日 11:24 UTCmonitoring

   AWSは、基礎問題の修正を行いました。 回復の兆候を観察し、この時点では安定しているようです。 環境を監視し、必要に応じて更新を行います.

6. 2026年7月16日 12:57 UTCresolved

   この事件は解決しました.

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

1. 2026年7月2日 12:39 UTCinvestigating

   ブラックボードのLMSクライアントは、現在、パフォーマンスの問題を経験しています。 チームは、根本的な原因を調査し、正常な性能を回復するために働いています.

2. 2026年7月2日 13:14 UTCidentified

   パフォーマンスの問題を引き起こしたクエリを識別しました。 チームは、修正に積極的に取り組んでいます

3. 2026年7月2日 14:44 UTCmonitoring

   修正を実装し、結果を監視しています.

4. 2026年7月2日 21:08 UTCmonitoring

   問題は解決しました.

5. 2026年7月3日 4:33 UTCresolved

   この事件は解決しました.

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

1. 2026年5月16日 6:48 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 2026年5月16日 9:01 UTCidentified

   We are continuing to work on a fix for this issue.

3. 2026年5月16日 10:14 UTCmonitoring

   A fix has been implemented and we are monitoring the results

4. 2026年5月16日 11:04 UTCidentified

   All sites are online

5. 2026年5月29日 13:24 UTCresolved

   This incident has been resolved.

1. 2026年5月7日 16:13 UTCinvestigating

   We are investigating a number of issues reported with the 4000.15.0 release to production environments. Multiple teams are working on this and we will provide more information as it becomes available.

2. 2026年5月7日 19:11 UTCinvestigating

   As we investigate an issue related to Release Conditions, the release of 4000.15.0 will be paused until this issue can be resolved, so the US East release is now on hold. Once resolved all sites will be updated with the fix.

3. 2026年5月8日 2:40 UTCidentified

   We have identified the root cause of the issue related to Release Conditions. The team is working on a fix that will be released as soon as possible. In the meantime, we have updated production instances for customers that have opened a support ticket.

4. 2026年5月8日 9:28 UTCidentified

   The engineering team is actively working on a resolution for the Release condition issue. As a temporary workaround until the fix is available, please remove any assessment access exceptions configured in the Gradebook (for example, custom start/end dates assigned to individual students). Once the exceptions are removed, the assessment will appear correctly in the student view. We appreciate your patience and understanding while we work toward a permanent resolution.

5. 2026年5月10日 8:49 UTCidentified

   Resolved Update - The engineering team has completed the fix for the Release Conditions issue identified in version 4000.15.0. Deployment of the fix to production environments is currently in progress and will continue across all the sites. Once the deployment is completed, the issue related to assessment visibility and Release Conditions will be fully resolved. The team will continue to closely monitor the environments following the deployment to ensure platform stability and expected behavior. We appreciate your patience and understanding throughout this process.

6. 2026年5月11日 13:42 UTCresolved

   This incident has been resolved.

1. 2026年4月27日 16:51 UTCinvestigating

   We are experiencing a spike in activity beginning at 11:20AM EDT which has caused intermittent delays in the real-time processing of new content added to the LMS for Canvas institutions in the US. Real-time processing delays of approximately 1 to 2 hours for new content items may be seen during this time. Note that all other Ally features (alternative formats, instructor feedback and institutional report) for previously processed content items should still be working as expected.

2. 2026年4月28日 11:36 UTCresolved

   This incident has been resolved.

1. 2026年4月24日 21:19 UTCinvestigating

   Faculty are receiving an "Upload failed" error message when they try to add video or audio feedback on a quiz in the Overall Feedback area for their students. The upload process fails at the final stage. This has been confirmed across multiple users and different media types. Browsers: Verified on latest versions of Chrome; persists after clearing cache, cookies, and restarting systems. Error Message: "Upload Failed" appears on the progress bar in the Video Details pane.

2. 2026年4月24日 23:29 UTCresolved

   The issue has been resolved.

1. 2026年4月21日 13:47 UTCidentified

   We are currently experiencing delays in the processing and generation of Alternative Formats for institutions in Europe. The Ally development team is treating this as a high priority while adding resources to process the existing backlog.

2. 2026年4月21日 17:54 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2026年4月21日 18:56 UTCresolved

   Ally has worked through the remaining backlog and alternative formats are processing at a normal rate again.

1. 2026年4月16日 7:37 UTCinvestigating

   We are currently experiencing performance degradation. As a result, some Snowflake queries may run slower than usual, and Illuminate reports may take longer to load or could time out. Our team is actively investigating the issue and working to restore normal performance at the earliest

2. 2026年4月16日 9:19 UTCmonitoring

   We have identified the root cause of the issue and deployed a fix to production. The team is closely monitoring performance to ensure stability

3. 2026年4月16日 10:08 UTCresolved

   The performance issue has been resolved. Snowflake queries and Illuminate reports are now operating normally

1. 2026年4月13日 13:41 UTCinvestigating

   Ally's bulk processing queues that handle updates from course syncs and course onboards are currently experiencing high traffic which may result in a delay of 1-2 hours for showing new indicators and/or new course reports. During this high traffic period Ally and its associated components remain available, however there may be delays in processing some of these updates including course copy processes. Real time processing for new content items remains at expected levels, but users may see a slight delay in report updates during this time as these processes catch up.

2. 2026年4月14日 12:44 UTCmonitoring

   Ally has processed the majority of the backlog in our bulk processing queues which should decrease the delays for course syncs, copy processes and onboards. The Ally development team will continue to monitor progress and performance.

3. 2026年4月17日 12:39 UTCresolved

   This incident has been resolved.

1. 2026年3月30日 17:30 UTCidentified

   We are experiencing another spike in activity which has caused intermittent delays in the processing of content added to the LMS for institutions in the US. Real time processing delays of approximately 1.5 hours for new content items may be seen during this time. Note that all other Ally features (alternative formats, instructor feedback and institutional report) for previously processed content items should still be working as expected.

2. 2026年3月30日 21:12 UTCmonitoring

   The Ally development team has scaled up resources based on demand and will continue to monitor progress.

3. 2026年4月1日 11:28 UTCmonitoring

   Real time processing queues have returned to normal levels while the team continues to monitor.

4. 2026年4月3日 20:11 UTCresolved

   This incident has been resolved.

1. 2026年3月26日 19:56 UTCidentified

   We are experiencing a spike in activity beginning just before noon EST which has caused intermittent delays in the processing of content added to the LMS for institutions in the US. Real time processing delays of approximately 1 to 3 hours for new content items may be seen during this time. Note that all other Ally features (alternative formats, instructor feedback and institutional report) for previously processed content items should still be working as expected.

2. 2026年3月27日 11:30 UTCresolved

   Real time queues have returned to normal levels.

1. 2026年3月18日 12:53 UTCinvestigating

   We are currently experiencing an issue with Single Sign-On that may prevent some users from logging in to Illuminate across all regions. We are actively working to resolve it.

2. 2026年3月18日 13:19 UTCresolved

   The issue has been resolved and users should now be able to log in to Illuminate without issues.

1. 2026年3月11日 16:53 UTCinvestigating

   We are experiencing issues on AI image generation within Blackboard LMS. Instructors receive an error when attempting to generate new images. Previously generated images applied to courses are fine and not effected. We are investigating and working with our service provider towards a solution.

2. 2026年3月11日 21:13 UTCidentified

   We have identified the root cause of the issue and are analyzing the options available to us to bring image generation back online. Please bear with us as we work through this. We are 'following the sun' on getting a solution deployed as soon as possible.

3. 2026年3月12日 14:43 UTCmonitoring

   We have found a fix for AI image generation in Blackboard LMS. This has been through our QA process, the rollout has begun with positive initial signs of service restoration in production instances. We aim to post a final status on this once the rollout process to all instances has completed and post rollout QA is successful.

4. 2026年3月12日 19:06 UTCresolved

   We can report that the rollout to all production instances and final QA testing is now complete. Image generation is fully restored in all instances of Blackboard LMS. As part of this fix, you may notice an improvement in the generated image quality. If you have any further concerns or still are experience image generation issues, please raise a support ticket through the usual channels.

1. 2026年3月2日 7:31 UTCinvestigating

   We are experiencing issue on AWS services in ME-Central region due to power issue in few of the availability zones, We are actively working with our service provider.

2. 2026年3月2日 8:41 UTCidentified

   Our service provider is still working on the power issue. We are closely monitoring these efforts to ensure service is restored as quickly as possible. We will provide an update if new information becomes available.

3. 2026年3月2日 18:37 UTCidentified

   Some users may experience difficulties accessing content or performing certain operations due to an increased error rate caused by a power issue. Our service provider is actively working to resolve the problem. We will share further updates as soon as more information becomes available.

4. 2026年3月3日 4:11 UTCidentified

   Our service provider is still working on the primary root cause. We are closely monitoring these efforts to ensure service is restored as quickly as possible. We recognize the critical nature of these services and sincerely apologize for the disruption. We will provide an update if new information becomes available.

5. 2026年3月3日 8:09 UTCidentified

   We are currently observing that additional sites are being affected due to the ongoing power outage. We are actively working with our service provider to explore available options. Our service provider is closely working on the recovery efforts. We will continue to monitor the situation and share updates as they become available.

6. 2026年3月3日 11:44 UTCidentified

   Most of the sites hosted in the Middle East region are currently impacted due to the ongoing power outage. We are actively working with our service provider to assess the situation and explore all available options. Our service provider is closely engaged in recovery efforts to restore services. We will provide an update if new information becomes available.

7. 2026年3月4日 19:52 UTCidentified

   Many Blackboard sites hosted in the Middle East region are currently impacted due to the ongoing power outage. We are actively working with our service provider (AWS) to assess the situation and explore all available options, including restoring services in another AWS Region. If your site is impacted, please look for further direct communication from our Client Support team. We will provide an update as new information becomes available.

8. 2026年3月17日 17:22 UTCidentified

   Many Blackboard sites hosted in the Middle East region are currently impacted due to infrastructure damage. We are beginning to see partial recovery of the underlying services required to restore Blackboard sites to full functionality. To ensure quality of services, access to Blackboard sites will be restricted until further recovery efforts are completed. We are actively working with our service provider (AWS) to assess the situation and explore all available options, including restoring services in another AWS Region. Our Client Support team is communicating directly with impacted clients. We will continue to provide updates as new information becomes available.

9. 2026年3月23日 12:59 UTCidentified

   All Blackboard sites hosted in the Middle East region are currently impacted due to infrastructure damage. The AWS services required to restore Blackboard sites to full functionality are not yet available. To ensure quality of services, access to Blackboard sites will be restricted until further recovery efforts are completed. We are actively working with our service provider (AWS) to assess the situation and explore all available options, including restoring services in another AWS Region. Our Client Support team is communicating directly with impacted clients. We will continue to provide updates as new information becomes available.

10. 2026年3月25日 21:36 UTCidentified

    We have successfully restored several Blackboard sites previously hosted in the Middle East to an alternate AWS region. Recovery of additional sites is in progress. Our Client Support team is communicating directly with impacted clients. We will continue to provide updates as new information becomes available.

11. 2026年4月6日 9:19 UTCresolved

    We have successfully restored all production Blackboard sites previously hosted in the Middle East to an alternate AWS region.

1. 2026年2月23日 5:10 UTCinvestigating

   We are aware of the email issue that users are encountering while sending emails from Blackboard. Our teams are investigating this on priority to have this addressed as soon as possible.

2. 2026年2月23日 6:04 UTCidentified

   We have identified the issue and continuing to work on a fix for this issue. We will share an ETA as soon as it becomes available.

3. 2026年2月23日 6:57 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 2026年2月23日 14:35 UTCresolved

   This incident has been resolved.