Live › incident › INC-digitalocean-2kxtxyvzzzk0
Go to dashboardNot triaged yet. The sources’ own description is below.
First seen by InfraStack 2026-10-23 19:12 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| DigitalOcean | vendor | – | – |
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The issue affecting Kubernetes deployments in the NYC1 region has been resolved. Our investigation found intermittent DNS timeouts affecting a small number of DOKS clusters, with affected worker nodes running on shared-CPU Droplets. This is a documented limitation for latency-sensitive cluster DNS workloads such as CoreDNS.
The affected clusters are currently functional. To reduce the risk of recurrence, we recommend running CoreDNS on non-shared/dedicated CPU node pools and using sufficient CoreDNS replicas.
If you continue to see DNS failures or NodeNotReady events, please open a support ticket so we can investigate that cluster specifically.
This page as .md · .json · in your agent: get_signal("INC-digitalocean-2kxtxyvzzzk0")