---
id: "INC-digitalocean-qfg5hmfhxw5d"
kind: "incident"
aliases: []
title: "DigitalOcean: DNS Resolution for Managed Kubernetes"
severity: "medium"
cvss: null
epss: null
exploited: false
status: "resolved"
category: "vendor"
products: [{"name": "DigitalOcean", "fixed": [], "affected": "", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["digitalocean", "hosting", "incident", "ops", "vendor"]
not_affected_if: []
published_at: "2026-10-11T22:01:39+00:00"
first_seen_at: "2026-10-23T19:12:22+00:00"
updated_at: "2026-10-23T20:17:58+00:00"
sources: [{"source": "statuspage", "url": "https://stspg.io/61n77v08qp0j", "first_seen_at": "2026-10-23T19:12:22+00:00"}]
---

# DigitalOcean: DNS Resolution for Managed Kubernetes

## Affected

- vendor:DigitalOcean affected ? fixed ?

## Timeline

- 2026-10-23T19:12:22+00:00 statuspage https://stspg.io/61n77v08qp0j

## From the sources

Our Engineering team has resolved the external DNS resolution failures affecting Managed Kubernetes across multiple regions. Applications running on Managed Kubernetes can now resolve external domain names.

We sincerely apologize for any inconvenience this disruption may have caused to your operations. If you continue to experience problems, please open a ticket with our Support team: https://cloudsupport.digitalocean.com/s/

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_