- Level
- confirmed
- Worst impact
- Degraded
- Components
- Docs
- Down Index
- 21of 100
What to do
Check whether you use Coda Docs. 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 52m it lasted.
Anything that failed between 2019-03-10 18:25 UTC and 2019-03-10 21:17 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 3
- investigating
We are currently investigating an issue where periodic automations are not firing.
provider
- identified
We've identified the root cause of the issue and are working on a fix now.
provider
- resolved
We've resolved the issue. Periodic automations should start executing now and catch up shortly. Sorry for the trouble.
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-cd5294a762
Is Coda still down?
No, this incident was resolved 2019-03-10 21:17 UTC. For Coda's live state, see https://down.guide/providers/coda.
How long did it last?
2h 52m, from 2019-03-10 18:25 UTC to 2019-03-10 21:17 UTC, by the times Coda posted.
What was affected?
Coda named Docs.
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.