- Level
- confirmed
- Worst impact
- Degraded
- Components
- Agent Runtime
- Down Index
- 18of 100
What to do
Check whether you use DigitalOcean Agent Runtime. 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 1h 25m it lasted.
Anything that failed between 2026-04-23 22:26 UTC and 2026-04-23 23:51 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 2
- investigating
As of 21:53 UTC, our Engineering team is investigating reports of increased internal errors for models Llama 3.3 70B, GPT OSS 120B, GPT OSS 20B, Qwen3 32B and Deepseek R1 70B hosted in the ATL1 region, impacting Serverless Inference. At this point, users with models hosted in ATL1 may experience intermittent errors when using Serverless Inference. We apologize for the inconvenience and will share an update once we have more information.
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-5252c5b208
Is DigitalOcean still down?
No, this incident was resolved 2026-04-23 23:51 UTC. For DigitalOcean's live state, see https://down.guide/digitalocean.
How long did it last?
1h 25m, from 2026-04-23 22:26 UTC to 2026-04-23 23:51 UTC, by the times DigitalOcean posted.
What was affected?
DigitalOcean named Agent Runtime.
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.