DNS Resolution for Managed Kubernetes
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/
The latest update from DigitalOcean.
State
Resolved
Started
21 d ago
2026-10-11 22:01 UTC
Lasted
1 h 27 min
until 2026-10-11 23:29 UTC
Worst impact
Degraded
Timeline
3 updatesInvestigating
53 min 60%
Monitoring
35 min 40%
Updates
Times in UTCAs posted by DigitalOcean
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/
Our Engineering team has implemented a fix to address the intermittent external DNS lookup failures affecting Managed Kubernetes clusters in multiple regions. We are currently monitoring the results to ensure the issue is fully resolved. We will provide another update as soon as the issue is confirmed to be resolved.
Our Engineering team is investigating an issue causing intermittent external DNS lookup failures for Managed Kubernetes clusters in multiple regions. Applications running on affected clusters may intermittently fail to resolve external domain names. We apologize for the inconvenience and will provide further updates as more information becomes available.
Affected components
2DigitalOcean in the last 90 days
Full historyIncidents in 90 days
17
Days with an incident
18
Median duration
2 h 4 min
This incident
29% shorter than the median
Other DigitalOcean incidents
All incidentsDigitalOcean·Kubernetes Cluster Management Operations
We have resolved the issue affecting Managed Kubernetes cluster operations across all regions. Cluster creation, deletion, scaling, and upgrade operations have returned to normal. We have monitored the environment and confirmed that services are operating normally. If you continue to experience any issues, please contact our Support team by opening a ticket here: https://cloudsupport.digitalocean.com/s/
DigitalOcean·App Platform Deployments
Between 04:34 and 12:15 UTC, customers experienced service interruptions affecting App Platform deployment operations. During this window, customers may have been unable to deploy new applications or scale existing deployments. Applications already running prior to the incident were unaffected and continued to operate normally. The disruption was caused by a software update that prevented application containers from starting on newly provisioned infrastructure nodes. Our Engineering team rolled back the update and restored the affected nodes. App Platform deployment and scaling operations have recovered and are operating normally. We sincerely apologize for any inconvenience this caused. If you continue to experience any issues, please open a support ticket and our team will be happy to assist you.
DigitalOcean·VPC Networking Availability
Our Engineering team fully resolved the VPC Networking disruption as of 10:29 UTC. Customers can now create and delete VPC peering connections, subnets, and routes as expected. Following the recovery, we monitored the affected systems and confirmed that VPC Networking operations remain stable. We apologize for any inconvenience this disruption may have caused. If you continue to experience unexpected behavior, please open a ticket with our Support team for further assistance.
DigitalOcean·A Network Disruption in BLR1 Region Impacted Multiple Products (Resolved)
From 11:59 UTC to 13:02 UTC on October 3, 2026, a networking disruption in our BLR1 region affected multiple products, including Monitoring, App Platform, Managed Databases, Functions, Load Balancers, Spaces, and the Cloud Control Panel. During this period, some users experienced degraded connectivity, increased latency, or intermittent errors when accessing resources in the region. Multiple network paths operated by our upstream connectivity providers were unavailable, including redundant paths intended to maintain connectivity during a disruption. Traffic shifted to a remaining link with insufficient capacity to handle the full load, resulting in network saturation and the connectivity issues described above. Our Engineering and Network teams worked closely with our upstream providers to restore normal routing and connectivity. All affected services have since returned to normal operation. We apologize for the disruption and its impact on your work. If you continue to experience unex
DigitalOcean·Support Portal Service Disruption
From 08:06 UTC to 13:41 UTC, users may have experienced issues accessing the Support Portal, creating new support tickets, or reviewing existing support requests. Our Engineering team has confirmed the full resolution of the issue affecting the Support Portal following a fix from our upstream provider. We have verified that the Support Portal, ticket creation, and ticket review are now operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience and appreciate your patience.
Follow DigitalOcean
Your coding agent knows when DigitalOcean is down, and tells you when a failure is theirs, not yours. You can also get DigitalOcean incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "digitalocean" and tell me if DigitalOcean has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=digitalocean/feed subscribe https://outages.cc/feed.xml?providers=digitaloceanFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane