Live / DigitalOcean / Incident
DigitalOcean: Kubernetes Deployments in NYC1
DigitalOcean · digitalocean.comMinor incidentResolved2026-07-11 01:27 UTC
Public — what happened
Summary
DigitalOcean said it began looking into a problem with Kubernetes deployments in its NYC1 region on 2026-07-09 at 20:31 UTC, with some users seeing occasional DNS lookup failures and worker nodes being reported as not ready. By 01:18 UTC on 2026-07-10 the company said the problem had eased and workloads should be running normally, and it kept watching the systems. When it marked the incident resolved at 01:27 UTC on 2026-07-11, DigitalOcean said a small number of clusters had been hit by intermittent DNS timeouts and that the affected worker nodes ran on shared-CPU machines, which it described as a known limitation for this kind of DNS workload. The company advised customers to run their cluster DNS service on dedicated-CPU nodes with enough copies, and to contact support if problems continue.
Affected
NYC1
Timeline
- Started — 2026-07-09 20:31 UTC
- Investigating — 2026-07-09 20:31 UTC
- Monitoring — 2026-07-10 01:18 UTC
- Resolved — 2026-07-11 01:27 UTC · 28h 56m 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