- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 20of 100
What to do
Check whether your product depends on Coda. 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 2h 52m it lasted.
Anything that failed between 2023-05-16 21:02 UTC and 2023-05-16 23:54 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 intermittent user reports of being unable to access docs.
provider
- identified
We have identified the cause for users becoming readonly on docs to be limited to the Brave browser. We're currently working on a fix to fix this problem across Brave browsers.
provider
- resolved
A fix has been deployed for the issue that was impacting Brave browsers. Brave browser users should now be able to edit docs as before. The issue is now 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-d60f4f9a01
Is Coda still down?
No, this incident was resolved 2023-05-16 23:54 UTC. For Coda's live state, see https://down.guide/coda.
How long did it last?
2h 52m, from 2023-05-16 21:02 UTC to 2023-05-16 23:54 UTC, by the times Coda posted.
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.