Between 08:00 UTC and 22:53 UTC, an issue with an upstream provider affected multiple DigitalOcean services, including SMS-based 2FA (causing code delivery failures), Docker Hub-hosted images (impacting Managed Kubernetes and App Platform deployments), and SnapShooter backup jobs. The issue has been resolved, and all services are now stable and operating normally.
We appreciate your patience throughout this but if you continue to experience any issues, please create a support ticket from within the Cloud Control Panel for further analysis.
Our Engineering team has confirmed that the IPv6 connectivity issue has been fully resolved across all regions. Users should no longer face IPv6 connectivity issues. If you continue to experience problems, please open a ticket with our support team. Thank you for your patience and we apologize for any inconvenience.
Our Engineering team has resolved the issue affecting the creation of NVDIA GPU nodes on new Kubernetes clusters. Users will no longer encounter issues when creating NVDIA GPU nodes on new Kubernetes clusters.
If you continue to experience any issues, please open a support ticket. We sincerely apologize for the inconvenience caused and appreciate your understanding.
Our Engineering team has confirmed the full resolution of the issue with Managed Database Clusters.
Thank you for your patience, and we apologize for any inconvenience. If you continue to experience any issues, please open a Support ticket right away.
Our Engineering team has confirmed that the issue affecting Spaces access in the FRA1 region has been fully resolved.
Users should now be able to list and access their Spaces objects without any errors. We appreciate your patience and understanding while we worked to restore normal service.
If you experience any further problems or have any questions, please open a support ticket within your account.
Our Engineering team has resolved the issue impacting Managed Kubernetes clusters in our TOR1 region. We apologize for the inconvenience and appreciate your patience throughout this event. If you experience any further problems or have any questions, please open a support ticket within your account.
From 14:30 to 14:44 UTC, our Engineering team observed an issue impacting our API.
During this time, users may have experienced intermittent errors when trying to use the public API at api.digitalocean.com or processing API requests. Users may have also experienced issues with processing Droplet and Kubernetes cluster creations and cluster actions.
The impact has now subsided and as of 14:44 UTC, users should no longer be experiencing issues with accessing the API and 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.
Our Engineering team has resolved the connectivity issue with Managed Database PostgreSQL clusters in all regions that are using PGBouncer and some legacy MD5 passwords.
If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
From 05.45 to 9.20 UTC, our Engineering team observed a Networking issue in the SFO3 and AMS3 region related to DDoS mitigation workflows. During this time, a subset of Droplets remained in protective filtering longer than intended due to a monitoring issue in AMS3 that caused a small number of IPs to stay blocked incorrectly. Users should no longer be experiencing these issues.
We apologize for the inconvenience. If you have any questions or continue to experience issues, please reach out via a Support ticket on your account.