Seesaw Outage History

Seesaw experienced an outage where some images did not load in the Seesaw app, impacting users’ ability to view content. The incident began on Feb 10, 2026 9:06 PM UTC with a status change from up to warn as Seesaw suspected instability in their underlying cloud provider (AWS) and continued while the team investigated the root cause. The incident lasted about 8 hours and 20 minutes and the status was restored to up by Feb 11, 2026 5:26 AM UTC. Seesaw posted two updates during the incident, describing ongoing investigation and eventual restoration of normal service as the cloud issues were addressed.

On Jan 28, 2026 6:21 PM UTC, Seesaw announced a degraded state due to delays in the delivery of scheduled messages, with items arriving later than expected. This primarily affected the Seesaw component and could impact scheduling workflows for users. The incident lasted about 1 hour 35 minutes, ending with service restoration by Jan 28, 2026 7:56 PM UTC. The status page posted two updates during the event detailing the delay and the eventual resolution.

Seesaw experienced a brief outage that prevented uploading content to student journals and activities. The incident began at Jan 13, 2026 9:11 PM UTC when Seesaw's status page indicated Investigating, and was resolved by Jan 13, 2026 9:36 PM UTC. The outage lasted about 25 minutes, with two official status updates during the event and a return to normal after the investigation.

During the incident, users attempting to upload to student journals and activities would have encountered failures or delays; once resolved, uploads returned to normal.

The Seesaw app experienced crashes for users opening from push notifications on iOS version 10.89, while launching from the Home Screen worked normally. The issue began on Aug 14, 2025 2:51 PM UTC and was resolved by Aug 18, 2025 1:16 PM UTC, lasting roughly 3 days and 22 hours. The Seesaw status page indicated an active investigation and confirmed the Home Screen path was unaffected. The incident prompted two official updates over the period, describing the investigation and eventual return to normal operation for the app.

Seesaw encountered a partial outage affecting the QR codes used to share student posts from the student work menu. Student login QR codes were not affected. The issue began at 8:36 PM UTC and was resolved by 10:32 PM UTC, lasting roughly 1 hour and 56 minutes. Seesaw indicated that a fix had been identified and was in progress. The incident prompted two status updates during the window, after which normal operation was restored.

The incident began on Apr 16, 2025 6:26 PM UTC when Seesaw entered a degraded state due to a ClassLink API connection issue, preventing the nightly sync from completing for some ClassLink districts.

The Seesaw team issued two official updates while investigating with ClassLink, and the status returned to up on Apr 18, 2025 12:16 AM UTC.

Impact: Nightly district synchronization relying on the ClassLink API was incomplete for affected districts, potentially delaying district data updates and related workflows. The issue was isolated to the ClassLink integration; other Seesaw features remained available.

Seesaw experienced an outage affecting its website and mobile apps, leaving users unable to load pages or sign in across multiple devices. Reports from across the United States indicate a broad impact on classrooms and personal use. The outage began at 1:20 PM UTC and was resolved by 2:57 PM UTC, lasting roughly 1 hour and 37 minutes. A sustained flow of user reports suggested widespread disruption during the incident. Seesaw did not publish any official updates on their status page during the event. StatusGator recorded an Early Warning Signal starting at Feb 27, 2025 1:20 PM UTC and ending at Feb 27, 2025 2:57 PM UTC indicating issues across multiple devices before any official acknowledgment.

Seesaw experienced an outage affecting class creation via CSV, causing failures for users attempting to import classes. The status page indicated a degraded operation beginning at 1:16 AM UTC as the team investigated the cause.

The outage lasted approximately 15 hours and 35 minutes and was resolved by 4:51 PM UTC. Seesaw issued 2 official updates during the incident, documenting the investigation and recovery, and the service was returned to normal after the underlying issue was addressed.