From 20:03 - 20:08 UTC, our Engineering team observed an issue with internal DigitalOcean network connectivity in the NYC3 region. During this time, users might have experienced errors for control plane operations for services in NYC3, such as creating and deleting services, or issuing updates to existing services for products like App Platform Apps, DOKS & Managed Databases.
The incident did not impact public or private network connectivity for customer services.
We apologize for the inconvenience and if you are still experiencing issues or have any additional questions, please open a support ticket from within your account.
Our Engineering team has confirmed resolution of the issue impacting Droplet creation events and event processing and all services should now be operating normally. If you continue to experience any problems, please open a ticket with our Support team. Thank you for your patience and we apologize for any inconvenience.
From 10:30 UTC to 18:04 UTC, users may have experienced delays when adding new nodes to the Cluster or reconciling the Kubernetes Clusters.
Our Engineering team has confirmed the full resolution of the issue. Users should now be able to add new nodes or reconcile Kubernetes Clusters without any delays.
If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel.
From 01:56 to 06:36 UTC, our Engineering team observed an issue with Container Registry and App Platform builds in the BLR1 region.
During this time, users may have experienced delays while building their Apps and could have potentially experienced timeout errors in builds as a result. Additionally, a subset of customers may have experienced latency while interacting with the Container Registries.
Our Engineering team was able to take action to mitigate the impact and resolve the issue. All services are now functioning as expected. Thank you for your patience, and we apologize for any inconvenience.
If you have any questions or continue to experience issues, please reach out via a Support ticket on your account.
Our Engineering team identified an issue with new Droplet creates and rebuilds using Ubuntu 24.10 based Snapshot and Backup Images. From Oct 10 13:33 to Oct 25 19:58 UTC, users may have experienced issues while creating new Droplets using Ubuntu 24.10 based Snapshots and Backup Images in all of our regions.
We have disabled new Droplet creates and rebuilds using Ubuntu 24.10 based Image until new image has been published. Users who are still running Ubuntu 24.10 based Droplets should create offline Snapshots.
We apologize for the inconvenience. If you continue to experience any issues, please open a support ticket from within your account.
From 20:10 - 21:24 UTC, we experienced an issue affecting the creation of Spaces Buckets across all regions, both through the Cloud Control Panel and the API. During this period, users may also have experienced errors in DOCR registry creations and App Platform application creations and deployments.
Our Engineering team was able to take quick action to mitigate the impact and resolve the issue. All services are now functioning as expected. Thank you for your patience, and we apologize for any inconvenience.
If you continue to experience any issues, please open a Support ticket for further analysis.
Our Engineering team identified an issue with NYC1 Snapshot Image Transfers. From Oct 17, 15:09 to Oct 21, 23:08 UTC, users may have experienced issues with transferring images to NYC1 region.
A fix was deployed at Oct 21, 23:08 UTC by our Engineering team and all the pending image transfer events were settled. Users should now be able to transfer Snapshot images to NYC1.
We apologize for the inconvenience. If you continue to experience any issues, please open a support ticket from within your account.
From 04:28 - 05:13 UTC, our Engineering team observed an intermittent issue with uploading Custom Images in LON1 region. During this time, users might have experienced an issue with uploading Custom Images and few Snapshot create failures.
Swift action was taken by our Engineering team to restore full functionality, and now everything is operating normally.
We apologize for any inconvenience this may have caused. If you have any questions or continue to experience issues, please reach out via a Support ticket on your account.