- Level
- confirmed
- Worst impact
- Degraded
- Components
- Global
- Down Index
- 8of 100
What to do
Check whether you use DigitalOcean Global. 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-03-06 21:22 UTC and 2026-03-06 21:22 UTC may need a replay.Subscribe to DigitalOcean's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=digitalocean works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from DigitalOcean 1
- resolved
Our Engineering team identified an issue affecting the App Platform. During the incident, users may have experienced HTTP 522 (Connection Timed Out) errors when accessing their apps. The issue seems to be resolved now. We apologize for the inconvenience caused. If you continue to experience any related errors, please contact our Support team by opening a ticket at https://www.digitalocean.com/support/contact/.
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-56ef1458c1
Is DigitalOcean still down?
No, this incident was resolved 2026-03-06 21:22 UTC. For DigitalOcean's live state, see https://down.guide/digitalocean.
How long did it last?
0m, from 2026-03-06 21:22 UTC to 2026-03-06 21:22 UTC, by the times DigitalOcean posted.
What was affected?
DigitalOcean named Global.
What caused it?
DigitalOcean hasn't published a root cause. If it does, it shows here.
Where does this come from?
DigitalOcean's official status page, https://status.digitalocean.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.