Blackboard Outage History

A service issue affected Blackboard Learn deployments in the AWS Gov Cloud (US) and Europe SaaS regions, impacting all Gov Cloud clients and 8 EU production clients. The incident lasted approximately 13 days, during which Blackboard identified the problem and implemented a fix. All affected sites were restored online and the incident was fully resolved.

Blackboard experienced issues with the 4000.15.0 release that affected assessment visibility and Release Conditions functionality across all major regions including Americas, Europe, Asia Pacific, Saudi Arabia, and AWS Gov Cloud. The problems prevented students from properly viewing assessments when custom access exceptions were configured in the Gradebook. The engineering team identified the root cause, developed a fix, and completed deployment across all production environments after 93.5 hours, with ongoing monitoring to ensure platform stability.

Blackboard's Ally service experienced processing delays for Canvas institutions in the US-east region starting at 11:20 AM EDT on April 27, 2026, due to a spike in activity. New content added to the LMS faced real-time processing delays of 1-2 hours, while existing Ally features for previously processed content remained functional. The incident was resolved after 18.8 hours on April 28, 2026.

Faculty experienced "Upload failed" errors when attempting to add video or audio feedback to quizzes in Blackboard's Overall Feedback area, with uploads consistently failing at the final stage across multiple users and media types. The issue affected all major Blackboard Learn deployments globally including managed hosting and SaaS platforms across Saudi Arabia, Asia Pacific, Europe, Americas, and AWS Gov Cloud. The problem was resolved after 2.2 hours of investigation.

Blackboard's Ally service experienced delays in processing and generating alternative formats for European institutions for 5.2 hours on April 21, 2026. The development team implemented a fix and added resources to clear the existing backlog. Normal processing rates were restored after working through all remaining queued requests.

Blackboard's Illuminate service experienced performance degradation for 2.5 hours, causing Snowflake queries to run slower than usual and Illuminate reports to load slowly or time out. The team identified the root cause and deployed a fix to production. Normal performance was restored and the service is now operating normally.

Blackboard's Ally service experienced delays of 1-2 hours in course sync, copy processes, and report updates across all regions due to high traffic in bulk processing queues. While Ally remained available and real-time processing for new content continued normally, users experienced delays in seeing new indicators and course reports. The incident was resolved after 95 hours once the processing backlog was cleared.

Blackboard experienced a 26-minute service disruption affecting Flywire payment processing in the Asia-Pacific region due to payment infrastructure maintenance. Students and users in the Asia-Pacific region were unable to complete payments through Flywire during this period. The maintenance was completed successfully and payment functionality was fully restored.

Blackboard's Ally service in the US-east region experienced processing delays of approximately 1.5 hours for new content items added to the LMS due to an activity spike. Previously processed content and other Ally features (alternative formats, instructor feedback, and institutional reports) remained functional throughout the incident. The issue was resolved after the development team scaled up resources and monitored the processing queues until they returned to normal levels.

Blackboard's Ally service in the US-east region experienced processing delays for new content added to the LMS, with delays of 1-3 hours affecting institutions in the US starting around noon EST on March 26, 2026. Previously processed content and other Ally features (alternative formats, instructor feedback, and institutional reports) continued to function normally. The issue was resolved after 15.6 hours when real-time queues returned to normal levels on March 27.