Our Engineering team has identified and resolved an issue that impacted the ability to resize Droplets via both the API and UI from 18:15 until 21:55 UTC. During this time, users might have experienced errors when attempting to resize their Droplets through the API or the UI.
Additionally, in an effort to resolve the issue with resizes, a secondary issue affected all event processing and some API calls for Droplets and related services from 21:50 until 22:00 UTC.
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.
Our Engineering team has confirmed the full resolution of this incident.
From 20:14 to 22:03 UTC, users may have experienced errors when connecting to their Apps or with their Apps connecting to other services, as well as delays in deploying Apps. Users should now be able to connect to their Apps normally, and any delayed deployments should complete successfully.
If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel.
From 21:35 to 00:45 UTC, users may have experienced networking connectivity issues in our SGP1 region, which impacted a subset of DigitalOcean services.
Our Engineering team has confirmed the full resolution of the issue. Users should be able to access all resources as normal.
If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
From 14:15 to 17:53 UTC, users may have experienced delays for App Platform deployments, as well as latency and errors when fetching Spaces endpoint information and toggling the CDN for a Spaces Bucket, due to an upstream provider issue.
Our Engineering team has confirmed the full resolution of the issue with the upstream provider. Users should now be able to deploy to App Platform and manage their Spaces Buckets as normal.
If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Our Engineering team identified an issue with accessing Cloud Panel and Application deployment which is due to the increased level of HTTP 499 errors rates at Upstream Provider end.
From 04:21 - 06:06 UTC, users may have experienced issues while accessing Cloud Panel and Application deployments.
Our Upstream provider and the Engineering team closely worked together to resolve the issue.
The impact has completely subsided and users should no longer see any issues with the impacted services.
If you continue to experience problems, please open a ticket with our support team from your Cloud Control Panel. Thank you for your patience, and we apologize for any inconvenience.
From 15:20 - 16:10 UTC, our Engineering team observed an issue with network connectivity in the BLR1 region. During this time, users might have experienced varying amounts of packet loss and high latency with network connections going in or out of the BLR1 region, resulting in issues connecting to DigitalOcean services.
As of 16:10 UTC, the impact has subsided and users should no longer be facing network connectivity issues. We apologize for the inconvenience and if you are still experiencing issues or have any additional questions then please open a support ticket from within your account.
From 18:23 to 19:21 UTC, users were unable to complete registration of new cloud.digitalocean.com accounts, due to an upstream outage.
This issue is now fully resolved and users should be able to sign up normally.
We apologize for the inconvenience and invite users to retry any failed attempts. If you continue to experience issues or have any questions, please reach out to Support from within your account.
Our Engineering team identified a networking issue with our upstream provider in the SGP1 region. From 00:25 to 04:00 UTC, users may have experienced connectivity issues to DockerHub from Droplets, App Platform and Managed Kubernetes in the SGP1 region.
Our Engineering team has confirmed there is no longer any impact and connectivity should be restored for all customers.
We apologize for the inconvenience. If you continue to experience any issues, please open a support ticket from within your account.