Blackboard 장애 기록

1. 2026년 8월 19일 PM 10:10 UTCinvestigating

   Blackboard는 현재 다수의 고객에 영향을 미치는 서비스 중단을 조사하고 있습니다. 우리는 미국 동부에 블랙 보드 LMS에 배포 된 클라이언트의 그룹에 영향을 미치는 저장 시스템에 관련된 증가 된 오류율입니다. 추가 업데이트는 status.blackboard.com에 게시됩니다

2. 2026년 8월 19일 PM 10:48 UTCinvestigating

   우리는 문제를 조사하고 우리가 할 수있는 빨리 문제를 진단하고 해결하기 위해 Blackboard의 인프라 파트너와 적극적으로 협력하고 있습니다. 우리는 계속 상태에 업데이트를 제공 할 것입니다.blackboard.com

3. 2026년 8월 19일 PM 11:10 UTCinvestigating

   업데이트 : "Blackboard - SaaS - Global"에서 "Blackboard - SaaS (미국)"로 범위를 조정

4. 2026년 8월 20일 AM 1:17 UTCinvestigating

   Blackboard는 우리의 인프라 파트너와 직접 협력하여 문제를 진단하고 해결합니다. 우리는 status.blackboard.com에 업데이트를 계속합니다

5. 2026년 8월 20일 AM 1:40 UTCidentified

   문제는 식별되고, Blackboard는 재시작 및 복구 서비스 작업을 수행하고 있습니다. 우리는 모든 서비스를 완전히 복구하는 것을 보장하기 위해 노력하고있는 동안 불안정한 일 수 있습니다. status.blackboard.com에 다음 업데이트는 1 시간 안에

6. 2026년 8월 20일 AM 3:36 UTCmonitoring

   문제는 식별되고, 영향을받는 서비스는 복원되었습니다. Blackboard는 이러한 underlying 서비스를 모니터링하고 있습니다. 업데이트는 계속 상태에 게시됩니다.blackboard.com 이 사건이 해결 될 때까지.

7. 2026년 8월 20일 AM 4:40 UTCmonitoring

   서비스 복원되었습니다. Blackboard는 이러한 underlying 서비스를 모니터링하고 있습니다.

8. 2026년 8월 20일 AM 9:09 UTCmonitoring

   영향을받는 서비스는 복원되고 안정적으로 유지되었습니다. Blackboard는 지속적인 안정성을 보장하기 위해 underlying 서비스를 계속 모니터링합니다.

9. 2026년 8월 20일 PM 1:41 UTCmonitoring

   영향을받는 서비스는 안정적입니다. Blackboard는 지속적인 안정성을 보장하기 위해 underlying 서비스를 계속 모니터링합니다. 다음 업데이트는 가까운 비즈니스에 의해 제공됩니다.

10. 2026년 8월 20일 PM 9:46 UTCmonitoring

    영향을받는 서비스는 안정적입니다. Blackboard는 지속적인 안정성을 보장하기 위해 underlying 서비스를 계속 모니터링합니다. 다음 업데이트는 내일 (금요일) 아침에 의해 제공됩니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 19일 PM 9:48 UTCidentified

   우리는 미국 동부에 블랙 보드 LMS에 배포 된 클라이언트의 그룹에 영향을 미치는 저장 시스템과 관련된 증가 된 오류율을 조사하고 있습니다

2. 2026년 8월 19일 PM 10:01 UTCidentified

   이 문제를 해결하기 위해 계속 노력하고 있습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 11일 PM 1: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일 PM 2: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일 PM 3: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일 PM 4: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일 PM 5: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일 PM 6: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일 PM 9:05 UTCresolved

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

1. 2026년 8월 3일 PM 2:49 UTCinvestigating

   모든 메시징 기능은 현재 다운됩니다. 우리는 그들이 가동으로 곧 조언할 것입니다.

2. 2026년 8월 3일 PM 5:34 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 16일 PM 6:18 UTCinvestigating

   우리는 표준을 편집하거나 오프라인 보고서를 생성 할 때 인증 및 프로그램 검토에서 표시 오류의 인식입니다. 개발팀은 이 문제를 해결하기 위해 노력하고 있습니다.

2. 2026년 7월 17일 PM 7:17 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 16일 AM 8:33 UTCinvestigating

   우리는 현재 다수 클라이언트를 위한 생산 환경에 영향을 미치는 문제점을 조사하고 있습니다.

2. 2026년 7월 16일 AM 8:51 UTCidentified

   AWS CloudFront와 관련된 이슈를 확인했습니다. AWS와 함께 일하고 있습니다. 우리의 팀은 상황을 감시하고 추가 정보가 유효하기 때문에 더 많은 업데이트를 제공할 것입니다.

3. 2026년 7월 16일 AM 9:40 UTCidentified

   우리는 고객의 subset에 영향을 미치는 문제점을 발견했습니다. AWS는 문제점을 확인하고 충격을 감소시키는 완화 노력에 적극적으로 일하고 있습니다. 우리의 팀은 AWS와 공동으로 하는 상황을 감시하고, 가득 차있는 회복을 향해 일하. 더 많은 정보로 업데이트를 계속 제공 할 것입니다.

4. 2026년 7월 16일 AM 10:25 UTCidentified

   AWS는 완화 노력에 지속적으로 노력하고 있으며, 저희 팀은 적극적으로 참여하고 긴밀히 협력하고 있습니다. 우리는 환경을 모니터링하고 진행 상황을 제공하는 것을 계속합니다.

5. 2026년 7월 16일 AM 11:24 UTCmonitoring

   AWS는 아래의 문제점에 대한 수정을 구현했습니다. 우리는 복구 표지판을 관찰하고, 서비스는이 시간에 안정적으로 나타납니다. 우리는 환경을 계속 모니터링하고 필요한 경우 업데이트를 제공합니다.

6. 2026년 7월 16일 PM 12:57 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 2일 PM 12:39 UTCinvestigating

   몇몇 Blackboard LMS 클라이언트는 현재 성과 문제점을 경험하고 있습니다. 팀은 뿌리 원인을 조사하고 정상 성능을 복원하기 위해 노력하고 있습니다.

2. 2026년 7월 2일 PM 1:14 UTCidentified

   우리는 성과 문제점을 일으키는 조회를 확인했습니다. 팀은 해결에 적극적으로 노력하고 있습니다

3. 2026년 7월 2일 PM 2:44 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

4. 2026년 7월 2일 PM 9:08 UTCmonitoring

   문제는 해결되었습니다.

5. 2026년 7월 3일 AM 4:33 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 5월 16일 AM 6:48 UTCidentified

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

2. 2026년 5월 16일 AM 9:01 UTCidentified

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

3. 2026년 5월 16일 AM 10:14 UTCmonitoring

   A fix has been implemented and we are monitoring the results

4. 2026년 5월 16일 AM 11:04 UTCidentified

   All sites are online

5. 2026년 5월 29일 PM 1:24 UTCresolved

   This incident has been resolved.

1. 2026년 5월 7일 PM 4: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일 PM 7: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일 AM 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일 AM 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일 AM 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일 PM 1:42 UTCresolved

   This incident has been resolved.

1. 2026년 4월 27일 PM 4: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일 AM 11:36 UTCresolved

   This incident has been resolved.

1. 2026년 4월 24일 PM 9: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일 PM 11:29 UTCresolved

   The issue has been resolved.

1. 2026년 4월 21일 PM 1: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일 PM 5:54 UTCmonitoring

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

3. 2026년 4월 21일 PM 6:56 UTCresolved

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

1. 2026년 4월 16일 AM 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일 AM 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일 AM 10:08 UTCresolved

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

1. 2026년 4월 13일 PM 1: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일 PM 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일 PM 12:39 UTCresolved

   This incident has been resolved.

1. 2026년 3월 30일 PM 5: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일 PM 9:12 UTCmonitoring

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

3. 2026년 4월 1일 AM 11:28 UTCmonitoring

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

4. 2026년 4월 3일 PM 8:11 UTCresolved

   This incident has been resolved.

1. 2026년 3월 26일 PM 7: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일 AM 11:30 UTCresolved

   Real time queues have returned to normal levels.

1. 2026년 3월 18일 PM 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일 PM 1:19 UTCresolved

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

1. 2026년 3월 11일 PM 4: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일 PM 9: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일 PM 2: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일 PM 7: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일 AM 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일 AM 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일 PM 6: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일 AM 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일 AM 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일 AM 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일 PM 7: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일 PM 5: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일 PM 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일 PM 9: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일 AM 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일 AM 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일 AM 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일 AM 6:57 UTCmonitoring

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

4. 2026년 2월 23일 PM 2:35 UTCresolved

   This incident has been resolved.