Historique des pannes de Blackboard

1. 19 août 2026 à 22:10 UTCinvestigating

   Blackboard enquête actuellement sur une perturbation du service touchant un certain nombre de clients. Nous enquêtons sur l'augmentation des taux d'erreur liés à un système de stockage ayant une incidence sur un groupe de clients déployés sur Blackboard LMS aux États-Unis. Des mises à jour supplémentaires seront affichées sur status.blackboard.com

2. 19 août 2026 à 22:48 UTCinvestigating

   Nous continuons d'étudier la question et travaillons activement avec les partenaires de l'infrastructure de Blackboard pour diagnostiquer et résoudre le problème le plus rapidement possible. Nous continuerons à fournir des mises à jour à status.blackboard.com

3. 19 août 2026 à 23:10 UTCinvestigating

   Mise à jour: Réglage de la portée de "Blackboard - SaaS - Global" à "Blackboard - SaaS (US)"

4. 20 août 2026 à 01:17 UTCinvestigating

   Blackboard continue de travailler directement avec nos partenaires de l'infrastructure pour diagnostiquer et résoudre le problème. Nous continuerons à publier des mises à jour sur status.blackboard.com

5. 20 août 2026 à 01:40 UTCidentified

   Le problème a été identifié et Blackboard s'efforce de redémarrer et de restaurer les services. Il peut y avoir encore de l'instabilité pendant que nous travaillons pour nous assurer que tous les services sont entièrement récupérés. Prochaine mise à jour de status.blackboard.com sera dans 1 heure

6. 20 août 2026 à 03:36 UTCmonitoring

   Le problème a été cerné et les services touchés ont été rétablis. Blackboard continue de surveiller ces services sous-jacents. Les mises à jour continueront d'être affichées sur status.blackboard.com jusqu'à ce que cet incident soit résolu.

7. 20 août 2026 à 04:40 UTCmonitoring

   Les services ont été restaurés. Blackboard continue de surveiller ces services sous-jacents.

8. 20 août 2026 à 09:09 UTCmonitoring

   Les services touchés ont été restaurés et demeurent stables. Blackboard continue de surveiller les services sous-jacents pour assurer une stabilité continue.

9. 20 août 2026 à 13:41 UTCmonitoring

   Les services touchés demeurent stables. Blackboard continue de surveiller les services sous-jacents pour assurer une stabilité continue. La prochaine mise à jour sera fournie par la fermeture des bureaux.

10. 20 août 2026 à 21:46 UTCmonitoring

    Les services touchés demeurent stables. Blackboard continue de surveiller les services sous-jacents pour assurer une stabilité continue. La prochaine mise à jour sera donnée demain ( vendredi) matin.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 19 août 2026 à 21:48 UTCidentified

   Nous enquêtons sur l'augmentation des taux d'erreur liés à un système de stockage ayant une incidence sur un groupe de clients déployés sur Blackboard LMS aux États-Unis Est

2. 19 août 2026 à 22:01 UTCidentified

   Nous continuons de travailler sur une solution à ce problème.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 11 août 2026 à 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 août 2026 à 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 août 2026 à 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 août 2026 à 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 août 2026 à 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 août 2026 à 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 août 2026 à 21:05 UTCresolved

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

1. 3 août 2026 à 14:49 UTCinvestigating

   Toutes les capacités de messagerie sont actuellement désactivées. Nous vous conseillerons dès qu'ils seront opérationnels.

2. 3 août 2026 à 17:34 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 16 juillet 2026 à 18:18 UTCinvestigating

   Nous sommes au courant des erreurs qui apparaissent dans Accréditation et Examen des programmes lorsque nous tentons de modifier des normes ou de générer des rapports hors ligne. L'équipe de développement s'emploie à résoudre ce problème.

2. 17 juillet 2026 à 19:17 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 16 juillet 2026 à 08:33 UTCinvestigating

   Nous enquêtons actuellement sur un problème touchant l'environnement de production de plusieurs clients.

2. 16 juillet 2026 à 08:51 UTCidentified

   Nous avons identifié le problème comme étant lié à AWS CloudFront. Nous travaillons activement avec AWS pour rétablir le service le plus rapidement possible. Notre équipe suit de près la situation et fournira d'autres mises à jour dès que des informations supplémentaires seront disponibles.

3. 16 juillet 2026 à 09:40 UTCidentified

   Nous avons identifié le problème ayant une incidence sur un sous-ensemble de clients. AWS a confirmé la question et travaille activement aux efforts d'atténuation pour réduire l'impact. Nos équipes surveillent de près la situation, coordonnent leurs activités avec les SSFE et s'emploient à assurer un rétablissement complet. Nous continuerons de fournir des mises à jour à mesure que de plus amples renseignements seront disponibles.

4. 16 juillet 2026 à 10:25 UTCidentified

   Le SSFE continue de travailler sur les efforts d'atténuation, et nos équipes demeurent activement engagées et étroitement coordonnées avec elles. Nous continuons de surveiller l'environnement et de fournir des mises à jour au fur et à mesure des progrès.

5. 16 juillet 2026 à 11:24 UTCmonitoring

   AWS a mis en place un correctif pour le problème sous-jacent. Nous observons des signes de rétablissement, et le service semble être stable à l'heure actuelle. Nous continuerons de surveiller l'environnement et de fournir des mises à jour si nécessaire.

6. 16 juillet 2026 à 12:57 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 2 juillet 2026 à 12:39 UTCinvestigating

   Quelques clients de Blackboard LMS connaissent actuellement des problèmes de performance. L'équipe enquête sur la cause profonde et travaille pour rétablir des performances normales.

2. 2 juillet 2026 à 13:14 UTCidentified

   Nous avons identifié la requête qui cause le problème de performance. L'équipe travaille activement sur une solution

3. 2 juillet 2026 à 14:44 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats.

4. 2 juillet 2026 à 21:08 UTCmonitoring

   La question a été réglée.

5. 3 juillet 2026 à 04:33 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 16 mai 2026 à 06:48 UTCidentified

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

2. 16 mai 2026 à 09:01 UTCidentified

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

3. 16 mai 2026 à 10:14 UTCmonitoring

   A fix has been implemented and we are monitoring the results

4. 16 mai 2026 à 11:04 UTCidentified

   All sites are online

5. 29 mai 2026 à 13:24 UTCresolved

   This incident has been resolved.

1. 7 mai 2026 à 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 à 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 à 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 à 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 à 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 à 13:42 UTCresolved

   This incident has been resolved.

1. 27 avril 2026 à 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 avril 2026 à 11:36 UTCresolved

   This incident has been resolved.

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

   The issue has been resolved.

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

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

3. 21 avril 2026 à 18:56 UTCresolved

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

1. 16 avril 2026 à 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 avril 2026 à 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 avril 2026 à 10:08 UTCresolved

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

1. 13 avril 2026 à 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 avril 2026 à 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 avril 2026 à 12:39 UTCresolved

   This incident has been resolved.

1. 30 mars 2026 à 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 mars 2026 à 21:12 UTCmonitoring

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

3. 1 avril 2026 à 11:28 UTCmonitoring

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

4. 3 avril 2026 à 20:11 UTCresolved

   This incident has been resolved.

1. 26 mars 2026 à 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 mars 2026 à 11:30 UTCresolved

   Real time queues have returned to normal levels.

1. 18 mars 2026 à 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 mars 2026 à 13:19 UTCresolved

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

1. 11 mars 2026 à 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 mars 2026 à 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 mars 2026 à 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 mars 2026 à 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 mars 2026 à 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 mars 2026 à 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 mars 2026 à 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 mars 2026 à 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 mars 2026 à 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 mars 2026 à 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 mars 2026 à 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 mars 2026 à 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 mars 2026 à 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 mars 2026 à 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 avril 2026 à 09:19 UTCresolved

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

1. 23 février 2026 à 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 février 2026 à 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 février 2026 à 06:57 UTCmonitoring

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

4. 23 février 2026 à 14:35 UTCresolved

   This incident has been resolved.