- Level
- confirmed
- Worst impact
- Operational
- Regions
- us
What to do
Check whether you use Coda in us. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 24m it lasted.
Anything that failed between 2025-03-07 03:35 UTC and 2025-03-07 05:59 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 2
- investigating
We have identified an issue with sending emails to users and are currently working on a fix. In the meantime, users might not be able to receive some emails from us, including but not limited to: sign ups, password-less logins, invitations, mentions, and document shares.
provider
- resolved
This incident has been resolved.
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-d1b105f461
Is Coda still down?
No, this incident was resolved 2025-03-07 05:59 UTC. For Coda's live state, see https://down.guide/providers/coda.
How long did it last?
2h 24m, from 2025-03-07 03:35 UTC to 2025-03-07 05:59 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.