Live / DigitalOcean / Incident
DigitalOcean: Major Service Interruption in MKC1
DigitalOcean · digitalocean.comCritical outageResolved2026-08-19 19:34 UTC
Public — what happened
Summary
DigitalOcean reported a critical outage in its MKC1 region beginning at 11:10 UTC on August 19, 2026, with multiple racks and nodes affected, disrupting GPU workloads and Serverless Inference and leaving some Kubernetes worker nodes and cluster controls unreachable. The company said it found the root cause by 12:22 UTC but did not describe it publicly, and it later mentioned working with the facility to restore equipment. By 18:59 UTC, DigitalOcean said the regional control plane and services such as CPU Droplets, managed databases, load balancers, storage and Spaces were working normally again. The incident was marked resolved at 19:34 UTC, though the company said GPU Droplets were still affected and that those customers would get separate updates by Slack and email.
Affected
MKC1, MKC1
Timeline
- Started — 2026-08-19 11:10 UTC
- Investigating — 2026-08-19 11:10 UTC
- Identified — 2026-08-19 12:22 UTC (2 updates)
- Monitoring — 2026-08-19 18:59 UTC
- Resolved — 2026-08-19 19:34 UTC · 8h 25m 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