Seesaw Outage History
5 incidents recorded over the last 365 days, 4 of them resolved, 1 still open. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Seesaw Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 4, 2026 | Seesaw iOS App failing to load with latest releaseThe issue has been identified and a fix is currently being implemented and testing underway | — | Investigating |
| May 8, 2026 | Planned Downtime for Image LibraryUpdate is complete, Image Library is now available. | 1h 20m | Resolved |
| Feb 10, 2026 | Some images not loading in SeesawThe incident has been resolved. Our cloud service provider (AWS) has remediated the issue, and all images are now functioning as expected. | 8h 20m | Resolved |
| Jan 28, 2026 | Scheduled Messages DelayedThis incident is now resolved. Customers will receive all messages that were scheduled during our downtime. | 1h 37m | Resolved |
| Jan 13, 2026 | Issues Uploading to Student Journals and ActivitiesThis issue has been resolved. For students who continue to see a "No Internet Connection" error, they will need to force quit the app and reopen it, or refresh their browser page to continue working. Autosave will… | 27 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Seesaw incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Seesaw Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Seesaw acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Seesaw outage in this window ran 8h 20m, against a mean recovery of 2h 56m. If you depend on Seesaw in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.