- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 12of 100
What to do
Check whether you use Coda in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-05-04 23:00 UTC and 2026-05-04 23:00 UTC may need a replay.Subscribe to Coda's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=coda works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Coda 1
- resolved
We 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 reconnect the Coda MCP in Claude. Find more instructions here: https://help.coda.io/hc/en-us/articles/44722661982989.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-33add94bb8
Is Coda still down?
No, this incident was resolved 2026-05-04 23:00 UTC. For Coda's live state, see https://down.guide/coda.
How long did it last?
0m, from 2026-05-04 23:00 UTC to 2026-05-04 23:00 UTC, by the times Coda posted.
What was affected?
Coda named in us.
What caused it?
Coda hasn't published a root cause. If it does, it shows here.
Where does this come from?
Coda's official status page, https://status.coda.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.