Live / DigitalOcean / Incident
DigitalOcean: Kubernetes Cluster Management Operations
DigitalOcean · digitalocean.comMajor incidentResolved2026-10-28 01:55 UTC
Public — what happened
Summary
DigitalOcean said its engineering team began investigating a problem with Managed Kubernetes cluster operations at 22:14 UTC on 2026-10-27, which it rated as minor. The company said customers may see delays or errors when creating, deleting, scaling or upgrading clusters, or doing other management tasks. It said workloads already running on Managed Kubernetes are not affected and should keep running normally. No cause had been identified and the issue was not resolved at the time of its latest update, which promised more information when available.
Affected
Global
Timeline
- Started — 2026-10-27 22:14 UTC
- Investigating — 2026-10-27 22:14 UTC (2 updates)
- Monitoring — 2026-10-28 01:34 UTC
- Resolved — 2026-10-28 01:55 UTC · 3h 40m after it started
What SquidGrid measured
SquidGrid measured 70 internet paths into DigitalOcean’s network during this incident. None of them ran meaningfully slower than the same paths the day before.
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
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.