From 14:40 UTC to 14:52 UTC, users may have experienced errors when trying to use the API or while accessing our Cloud Control Panel at https://cloud.digitalocean.com.
Our Engineering team has implemented a fix and confirmed full resolution of the issue. Users should be able to access the API and Cloud Control Panel without issue now.
If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
As of 18:45 UTC, our Engineering team has resolved the issues with OpenAI rate limits that were affecting certain DigitalOcean services. The problem, which began at approximately 09:30 UTC, caused errors (429s) for Agents using OpenAI models for serverless inference.
Systems Affected:
Serverless inference Evaluations
Technical Details: The issue was caused by exceeding OpenAI rate limits, which resulted in 429 errors for OpenAI models.
Duration: The incident lasted for approximately 9 hours, from 09:30 UTC to 18:45 UTC. We apologize for any inconvenience this may have caused and appreciate your patience as we worked to resolve the issue. If you continue to experience problems, please open a ticket with our Support team.
Our Engineering team identified and resolved an issue with the doctl v1.136.0 that was affecting automations and integrations, including App Platform and GitHub Action.
Users with the affected version of doctl may see 404 errors blocking their pipeline. The issue was caused by missing binaries in the release. The broken release has been deleted. Automations depending on doctl should now function as expected.
We apologize for the inconvenience. The new release shall be published soon.
Our Engineering team has implemented a fix for the issue that was preventing users from submitting or viewing tickets through our Support Ticket Portal. At this time, all users should be able to access the portal and manage tickets normally via https://cloudsupport.digitalocean.com/s/.
Additionally, any previously submitted tickets that were affected by this issue have now been successfully routed to our Support Team, who will be addressing them as quickly as possible.
We sincerely apologize for the inconvenience and appreciate your patience while we worked to resolve this issue.
As of 23:43 UTC, July 22, we have confirmed that the issue has been fully resolved. All affected functionality is operating normally, and users should be able to add and update payment methods without any errors.
Thank you for your patience while we worked to address this issue. If you continue to experience issues, then please open a ticket with our Support team for further review.
Our Engineering team, in collaboration with Let's Encrypt, has successfully resolved the issue affecting SSL certificate provisioning for Spaces and Load Balancers. Certificate creation is now fully restored and functioning as expected.
Existing certificates and HTTPS traffic were not impacted during this time. If you continue to experience any issues with certificate provisioning, please open a support ticket for assistance.
We sincerely apologize for any inconvenience this may have caused and appreciate your patience.
Our Engineering team has successfully resolved the issue that was affecting Reserved IPs and Load Balancers. Between 10:45 UTC and 12:10 UTC today, users may have encountered errors while assigning, reserving, or releasing Reserved IPs, or provisioning Load Balancers. All services have now been fully restored and are functioning normally. If you continue to experience any issues, please open a ticket with our support team. We apologize for any inconvenience this may have caused.
From 13:12 UTC to 17:18 UTC, users may have experienced errors with App deployment via App Platform. The deployments particularly failed for the Apps with Databases linked to them.
Our Engineering team has now confirmed the resolution of the issue, and App deployment should be working as expected.
If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Our Engineering team has implemented a fix for the issue that was preventing tickets submitted via the Support Contact Form from reaching our Support team. The form is now working as expected, and all new submissions are being properly routed to our Support team.
Additionally, previously submitted tickets that were impacted by this issue have been successfully routed to our Support Team. The team will address them as soon as possible.
We apologize for any inconvenience caused and appreciate your patience while we worked to resolve this issue.
Our Engineering team has fully resolved the issue with new Kubernetes cluster GPU creations. Users with new clusters should be able to create GPU nodes without issue.
If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.