Live / Incidents / DigitalOcean
DigitalOcean: Cloud Control Panel and API
DigitalOcean · digitalocean.comImpact: criticalResolved2026-09-15 18:44 UTC
Public — what happened
Summary
## 1. What happened
Between 16:56 UTC and 23:09 UTC on August 24, 2026, customers using DigitalOcean’s Cloud Control Panel, Public API, and dependent product management systems experienced elevated request error rates, peaking at 25%, in two distinct windows totaling 3.5 hours of active degradation within a 6-hour span. Running Droplets, network routing, and block storage \(Volumes\) remained fully functional and unaffected throughout the event. No customer data loss occurred.
The event was initiated during a planned infrastructure migration of the database layer supporting identity, authentication, and authorization services. The migration introduced increased execution latency for a crit
Timeline
- Started — 2026-08-24 17:14 UTC
- Last update — 2026-09-15 18:44 UTC
- Resolved — 2026-08-25 19:04 UTC
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 →