Skip to main content
DigitalOcean

Newly Created Managed Kubernetes Nodes

Degraded Lasted 5h 9m · started · DigitalOcean's page

Level
confirmed
Worst impact
Degraded
Components
Global
Down Index
21of 100

What to do

  • Check whether you use DigitalOcean Global. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 5h 9m it lasted.

    Anything that failed between 2026-03-13 11:26 UTC and 2026-03-13 16:35 UTC may need a replay.
  • Subscribe to DigitalOcean's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=digitalocean works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from DigitalOcean 4

  1. investigating

    Our Engineering team is investigating an issue impacting newly provisioned Managed Kubernetes nodes. During this time, new nodes may experience DNS timeouts, which could temporarily affect cluster services. We apologize for the inconvenience and will share an update once we have more information.

    provider

  2. identified

    Our Engineering team is investigating an issue impacting newly provisioned Managed Kubernetes nodes. During this time, Only customers who run a NAT Gateway in their VPC and a VPC-native clusters are affected and may experience DNS timeouts. We apologize for the inconvenience and will share an update once we have more information.

    provider

  3. monitoring

    Our Engineering team has implemented a fix to address the issue causing DNS timeouts for newly provisioned Managed Kubernetes nodes. Further investigation has confirmed that this issue primarily affected customers utilizing a NAT Gateway within their VPC and running a VPC-native cluster. We are actively monitoring the situation to ensure overall stability. We appreciate your patience and will provide a further update once the issue is fully confirmed to be resolved.

    provider

  4. resolved

    Our Engineering team has confirmed the resolution of the issue impacting DNS timeouts for newly provisioned Managed Kubernetes nodes. At this time all cluster services should now be functioning normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-34258a660b

Is DigitalOcean still down?

No, this incident was resolved 2026-03-13 16:35 UTC. For DigitalOcean's live state, see https://down.guide/digitalocean.

How long did it last?

5h 9m, from 2026-03-13 11:26 UTC to 2026-03-13 16:35 UTC, by the times DigitalOcean posted.

What was affected?

DigitalOcean named Global.

What caused it?

DigitalOcean hasn't published a root cause. If it does, it shows here.

Where does this come from?

DigitalOcean's official status page, https://status.digitalocean.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.