Live / DigitalOcean / Incident
DigitalOcean: DNS Resolution for Managed Kubernetes
DigitalOcean · digitalocean.comMinor incidentResolved2026-10-11 23:29 UTC
Public — what happened
Summary
DigitalOcean reported a minor issue starting at 22:01 UTC on October 11, 2026, in which Managed Kubernetes clusters in several regions sometimes could not look up outside web addresses, meaning apps on those clusters could occasionally fail to reach external domains. The company said a fix was put in place by 22:54 UTC, after which it watched to confirm the problem was gone. DigitalOcean declared the issue resolved at 23:29 UTC and did not name a cause in its updates.
Affected
Global
Timeline
- Started — 2026-10-11 22:01 UTC
- Investigating — 2026-10-11 22:01 UTC
- Monitoring — 2026-10-11 22:54 UTC
- Resolved — 2026-10-11 23:29 UTC · 1h 27m after it started
What SquidGrid measured
SquidGrid measured 33 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 42, 2026, our weekly internet health report.