Kubernetes Clusters and Droplets in FRA1 region
Summary
Our Engineering team has resolved the issue affecting Kubernetes clusters and Droplet events in the FRA1 region. Between approximately 00:17 UTC and 14:30 UTC, customers may have experienced issues provisioning Kubernetes clusters and mounting volumes. All 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.
Impact
minor
Timeline
[investigating] Our Engineering team is investigating an issue with Kubernetes clusters in the FRA1 region. During this time, subset of users may experience an issue while provisioning Kubernetes clusters and mounting volumes. Additionally, users may also notice the droplet events appearing to be stuck or delayed in this region. We apologize for the inconvenience and will share an update once we have more information.
via statuspage[identified] Our Engineering team has identified the root cause of the issue impacting Kubernetes clusters and Droplet events in the FRA1 region and is actively working on a fix. In the meantime, users may continue to experience issues. We appreciate your patience and will share updates as more information becomes available.
via statuspage[monitoring] Our Engineering team has implemented a fix to address the issue affecting Kubernetes clusters and Droplet events in the FRA1 region and is actively monitoring the situation. Customers should no longer experience issues provisioning Kubernetes clusters or mounting volumes. We will provide an update as soon as the issue is fully resolved.
via statuspage[resolved] Our Engineering team has resolved the issue affecting Kubernetes clusters and Droplet events in the FRA1 region. Between approximately 00:17 UTC and 14:30 UTC, customers may have experienced issues provisioning Kubernetes clusters and mounting volumes. All 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.
via statuspageLessons Learned
⚠DigitalOcean has experienced 46 incidents in the past year. This frequency suggests systemic reliability challenges that may warrant additional monitoring.
📊Incidents related to network, compute have occurred 61 times across all providers in the past year. This is one of the most common failure categories in cloud infrastructure.
💡This incident is categorized as: Network / Routing, Capacity Issue. Consider implementing preventive measures specific to this failure category.
Similar Incidents
Zero Trust Dashboard UI: Issues creating Tunnels with Zero Trust Edit role
Cloudflare · Mar 10, 2026
Ubuntu/Debian Package Mirror Failure
DigitalOcean · Mar 9, 2026
HTTP 522 Error on App Platform
DigitalOcean · Mar 6, 2026
Intermittent connectivity issues in Ashburn, VA
Cloudflare · Mar 6, 2026
Elevated TCP three-way handshake failures on api.anthropic.com
Anthropic · Mar 6, 2026