Coda: Issue affecting access to coda.io

What to do

Check whether you use Coda Docs, Login. 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 4h 18m it lasted.
Anything that failed between 2026-07-16 08:56 UTC and 2026-07-16 13:15 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.

investigatingJul 16, 2026, 8:56 AM UTC
We have identified an issue affecting access to coda.io and login to the Coda service through superhuman.com. This may be related to a temporary Amazon CloudFront outage. We apologize for any inconvenience, and updates will be provided as they become available.
provider
identifiedJul 16, 2026, 9:00 AM UTC
The issue has been identified.
provider
monitoringJul 16, 2026, 9:11 AM UTC
We introduced temporary changes to mitigate this issue during CloudFront's outage. Access to coda.io and Coda via superhuman.com should now be restored. We are monitoring the results.
provider
resolvedJul 16, 2026, 1:15 PM UTC
Amazon has resolved the CloudFront service outage, and our services are back to normal.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Coda still down?

No, this incident was resolved 2026-07-16 13:15 UTC. For Coda's live state, see https://down.guide/coda.

How long did it last?

4h 18m, from 2026-07-16 08:56 UTC to 2026-07-16 13:15 UTC, by the times Coda posted.

What was affected?

Coda named Docs, Login.

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.