Störungsverlauf von Blackboard

1. 19. August 2026 um 22:10 UTCinvestigating

   Blackboard untersucht derzeit eine Serviceunterbrechung, die eine Reihe von Kunden betrifft. Wir untersuchen erhöhte Fehlerquoten im Zusammenhang mit einem Speichersystem, das sich auf eine Gruppe von Clients auswirkt, die auf Blackboard LMS in den USA im Osten eingesetzt werden. Weitere Updates werden veröffentlicht auf status.blackboard.com

2. 19. August 2026 um 22:48 UTCinvestigating

   Wir untersuchen das Problem weiter und arbeiten aktiv mit den Infrastrukturpartnern von Blackboard zusammen, um das Problem so schnell wie möglich zu diagnostizieren und zu lösen. Wir werden weiterhin Updates unter status.blackboard.com bereitstellen

3. 19. August 2026 um 23:10 UTCinvestigating

   Update: Anpassung des Umfangs von "Blackboard - SaaS - Global" zu "Blackboard - SaaS (US)"

4. 20. August 2026 um 01:17 UTCinvestigating

   Blackboard arbeitet weiterhin direkt mit unseren Infrastrukturpartnern zusammen, um das Problem zu diagnostizieren und zu lösen. Wir werden weiterhin Updates auf status.blackboard.com veröffentlichen

5. 20. August 2026 um 01:40 UTCidentified

   Das Problem wurde identifiziert, und Blackboard arbeitet daran, Dienste neu zu starten und wiederherzustellen. Es kann weiterhin instabilität geben, während wir daran arbeiten, sicherzustellen, dass alle dienste vollständig wiederhergestellt werden. Nächstes Update auf status.blackboard.com wird in 1 Stunde sein

6. 20. August 2026 um 03:36 UTCmonitoring

   Das Problem wurde identifiziert und die betroffenen Dienste wurden wiederhergestellt. Blackboard überwacht weiterhin diese zugrunde liegenden Dienste. Updates werden weiterhin auf status.blackboard.com veröffentlicht, bis dieser Vorfall behoben ist.

7. 20. August 2026 um 04:40 UTCmonitoring

   Die Dienste wurden wiederhergestellt. Blackboard überwacht weiterhin diese zugrunde liegenden Dienste.

8. 20. August 2026 um 09:09 UTCmonitoring

   Die betroffenen Dienste wurden wiederhergestellt und bleiben stabil. Blackboard überwacht weiterhin die zugrunde liegenden Dienste, um eine anhaltende Stabilität zu gewährleisten.

9. 20. August 2026 um 13:41 UTCmonitoring

   Die betroffenen Dienste bleiben stabil. Blackboard überwacht weiterhin die zugrunde liegenden Dienste, um eine anhaltende Stabilität zu gewährleisten. Das nächste Update wird bis zum Geschäftsschluss zur Verfügung gestellt.

10. 20. August 2026 um 21:46 UTCmonitoring

    Die betroffenen Dienste bleiben stabil. Blackboard überwacht weiterhin die zugrunde liegenden Dienste, um eine anhaltende Stabilität zu gewährleisten. Das nächste Update wird von Tomorrow (Freitag) Morning bereitgestellt.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 19. August 2026 um 21:48 UTCidentified

   Wir untersuchen erhöhte Fehlerquoten im Zusammenhang mit einem Speichersystem, das sich auf eine Gruppe von Clients auswirkt, die auf Blackboard LMS in US East eingesetzt werden

2. 19. August 2026 um 22:01 UTCidentified

   Wir arbeiten weiter an einer Lösung für dieses Problem.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 11. August 2026 um 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. 11. August 2026 um 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. 11. August 2026 um 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. 11. August 2026 um 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. 11. August 2026 um 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. 11. August 2026 um 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. 11. August 2026 um 21:05 UTCresolved

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

1. 3. August 2026 um 14:49 UTCinvestigating

   Alle messaging-funktionen sind derzeit ausgefallen. Wir werden beraten, sobald sie einsatzbereit sind.

2. 3. August 2026 um 17:34 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 16. Juli 2026 um 18:18 UTCinvestigating

   Uns sind Fehler bekannt, die in Accreditation & Program Review angezeigt werden, wenn versucht wird, Standards zu bearbeiten oder Offline-Berichte zu erstellen. Das Entwicklungsteam arbeitet daran, dieses Problem zu lösen.

2. 17. Juli 2026 um 19:17 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 16. Juli 2026 um 08:33 UTCinvestigating

   Wir untersuchen derzeit ein Problem, das die Produktionsumgebung für mehrere Kunden betrifft.

2. 16. Juli 2026 um 08:51 UTCidentified

   Wir haben festgestellt, dass das Problem mit AWS CloudFront zusammenhängt. Wir arbeiten aktiv mit AWS zusammen, um den Service so schnell wie möglich wiederherzustellen. Unser Team beobachtet die Situation genau und wird weitere Updates bereitstellen, sobald zusätzliche Informationen verfügbar sind.

3. 16. Juli 2026 um 09:40 UTCidentified

   Wir haben das Problem identifiziert, das eine Teilmenge von Kunden betrifft. AWS hat das Problem bestätigt und arbeitet aktiv an Minderungsmaßnahmen, um die Auswirkungen zu reduzieren. Unsere Teams beobachten die Situation genau, koordinieren sich mit AWS und arbeiten auf eine vollständige Wiederherstellung hin. Wir werden weiterhin Updates bereitstellen, sobald mehr Informationen verfügbar sind.

4. 16. Juli 2026 um 10:25 UTCidentified

   AWS arbeitet weiterhin an Minderungsbemühungen, und unsere Teams bleiben aktiv und koordinieren sich eng mit ihnen. Wir überwachen weiterhin die Umwelt und bieten Updates, wenn Fortschritte gemacht werden.

5. 16. Juli 2026 um 11:24 UTCmonitoring

   AWS hat einen Fix für das zugrunde liegende Problem implementiert. Wir beobachten Anzeichen einer Erholung, und der Service scheint zu diesem Zeitpunkt stabil zu sein. Wir werden die Umwelt weiterhin überwachen und bei Bedarf Updates bereitstellen.

6. 16. Juli 2026 um 12:57 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 2. Juli 2026 um 12:39 UTCinvestigating

   Einige Blackboard LMS-Clients haben derzeit Leistungsprobleme. Das Team untersucht die Ursache und arbeitet daran, die normale Leistung wiederherzustellen.

2. 2. Juli 2026 um 13:14 UTCidentified

   Wir haben die Abfrage identifiziert, die das Leistungsproblem verursacht. Das Team arbeitet aktiv an einem Fix

3. 2. Juli 2026 um 14:44 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 2. Juli 2026 um 21:08 UTCmonitoring

   Das Problem ist gelöst.

5. 3. Juli 2026 um 04:33 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 16. Mai 2026 um 06:48 UTCidentified

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

2. 16. Mai 2026 um 09:01 UTCidentified

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

3. 16. Mai 2026 um 10:14 UTCmonitoring

   A fix has been implemented and we are monitoring the results

4. 16. Mai 2026 um 11:04 UTCidentified

   All sites are online

5. 29. Mai 2026 um 13:24 UTCresolved

   This incident has been resolved.

1. 7. Mai 2026 um 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. 7. Mai 2026 um 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. 8. Mai 2026 um 02: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. 8. Mai 2026 um 09: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. 10. Mai 2026 um 08: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. 11. Mai 2026 um 13:42 UTCresolved

   This incident has been resolved.

1. 27. April 2026 um 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. 28. April 2026 um 11:36 UTCresolved

   This incident has been resolved.

1. 24. April 2026 um 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. 24. April 2026 um 23:29 UTCresolved

   The issue has been resolved.

1. 21. April 2026 um 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. 21. April 2026 um 17:54 UTCmonitoring

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

3. 21. April 2026 um 18:56 UTCresolved

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

1. 16. April 2026 um 07: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. 16. April 2026 um 09: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. 16. April 2026 um 10:08 UTCresolved

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

1. 13. April 2026 um 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. 14. April 2026 um 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. 17. April 2026 um 12:39 UTCresolved

   This incident has been resolved.

1. 30. März 2026 um 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. 30. März 2026 um 21:12 UTCmonitoring

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

3. 1. April 2026 um 11:28 UTCmonitoring

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

4. 3. April 2026 um 20:11 UTCresolved

   This incident has been resolved.

1. 26. März 2026 um 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. 27. März 2026 um 11:30 UTCresolved

   Real time queues have returned to normal levels.

1. 18. März 2026 um 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. 18. März 2026 um 13:19 UTCresolved

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

1. 11. März 2026 um 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. 11. März 2026 um 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. 12. März 2026 um 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. 12. März 2026 um 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. 2. März 2026 um 07: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. 2. März 2026 um 08: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. 2. März 2026 um 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. 3. März 2026 um 04: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. 3. März 2026 um 08: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. 3. März 2026 um 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. 4. März 2026 um 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. 17. März 2026 um 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. 23. März 2026 um 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. 25. März 2026 um 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. 6. April 2026 um 09:19 UTCresolved

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

1. 23. Februar 2026 um 05: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. 23. Februar 2026 um 06: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. 23. Februar 2026 um 06:57 UTCmonitoring

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

4. 23. Februar 2026 um 14:35 UTCresolved

   This incident has been resolved.