Live / DigitalOcean / Incident
DigitalOcean: Cloud Control Panel and API
DigitalOcean · digitalocean.comCritical outageResolved2026-09-15 18:44 UTC
Public — what happened
Summary
DigitalOcean reported a critical incident on August 24, 2026 in which its Cloud Control Panel and public API returned errors, with some users unable to reach the control panel and Serverless Inference users also seeing failed requests. The company said running Droplets, networking and storage volumes kept working and no data was lost, and that fewer than 2% of active accounts hit at least one failure, with error rates peaking at 25%. In its postmortem, DigitalOcean said a planned database migration for its login and permissions systems slowed a key query, and automatic retries from other services then overloaded the system. A fix restored service that evening, but the problem returned when traffic was shifted back, and after a second fix and a period of monitoring the company marked the incident resolved at 19:04 UTC on August 25.
Affected
API, Cloud Control Panel
Timeline
- Started — 2026-08-24 17:14 UTC
- Investigating — 2026-08-24 17:14 UTC (2 updates)
- Monitoring — 2026-08-24 19:14 UTC
- Investigating — 2026-08-24 22:27 UTC
- Monitoring — 2026-08-25 00:54 UTC (2 updates)
- Postmortem — 2026-09-15 18:44 UTC
- Resolved — 2026-08-25 19:04 UTC · 25h 50m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach DigitalOcean against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for DigitalOcean: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the DigitalOcean report →
More from DigitalOcean