Coda Outage History
7 incidents recorded over the last 365 days, 7 of them resolved. 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 Coda Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 13, 2026 | The option to create new packs and docs via pack.new and coda.new is not availableThe incident has been resolved. | 25h 40m | Resolved |
| Jul 29, 2026 | Superhuman Docs may work slowly or intermittentlyThis incident has been resolved. | 37 min | Resolved |
| Jul 16, 2026 | Issue affecting access to coda.ioAmazon has resolved the CloudFront service outage, and our services are back to normal. | 4h 18m | Resolved |
| May 22, 2026 | Document search is unavailableThis incident has been resolved. | 50h 40m | Resolved |
| May 4, 2026 | Issue affecting Claude desktop and web connectionsWe identified an issue with Claude's desktop and web connections to Coda MCP. The issue has been resolved, and you should now be able to set up connections. If you set up any connections before May 4, you may need to… | 0 min | Resolved |
| Jan 20, 2026 | Site-wide outageThis incident has been resolved. | 31 min | Resolved |
| Oct 20, 2025 | Attachment and image processing delaysThis incident has been resolved. | 1h 59m | 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 Coda 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 Coda 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 Coda 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 Coda outage in this window ran 2d 2h, against a mean recovery of 11h 58m. If you depend on Coda 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.