Jun 3, 19:20 UTC
Resolved - Our Engineering team has successfully resolved the issue that was impacting the DBaaS cluster logs. API responses should be successful without any error messages while retrieving logs, and the "Recent Logs" section is also working as expected.

We have continued to monitor the system and have observed stable performance. The issue is now fully resolved.

Thank you for your patience while we worked to address the issue. If you are still facing issues, please open a ticket from within your Cloud Control Panel for further review.

Jun 3, 18:29 UTC
Monitoring - Our Engineering team has now mitigated the issue that affected the DBaaS cluster logs and is currently being monitored. Users should no longer see 500 errors when attempting to retrieve the logs via the API. The "Recent Logs" section in the Logs & Queries tab of the UI should now display logs as expected.

We are continuing to monitor the situation closely to ensure stability. Thank you for your patience during the process and we will provide a final update once we confirm the issue is fully resolved.

Jun 3, 16:26 UTC
Investigating - Our Engineering team is currently investigating an issue with fetching DBaaS cluster logs, affecting all non-MongoDB clusters.

Affected users may encounter 500 errors when attempting to retrieve logs via the API, and no logs will appear in the Recent Logs tab.

We apologize for the inconvenience and will provide updates as soon as we have more information. Thank you for your patience.

May 30, 21:03 UTC
Resolved - Our Engineering team identified an issue impacting GenAI agents via Cloud between 19:55 UTC and 20:36 UTC

During this time, users were unable to view or create GenAI agents in the Cloud Control Panel.

A fix was deployed at 20:36 UTC by our Engineering team and the issue stands resolved now.

We apologize for the inconvenience. If you continue to experience any issues, please open a support ticket from within your account.

May 28, 22:10 UTC
Resolved - From May 28 2025 20:13 UTC to 20:24 UTC, users may have experienced issues accessing the Cloud Control Panel. Specifically, users attempting to access the Projects, Load Balancers, Networking, and Droplet pages may have seen no content or a blank page.

This incident did not impact the DigitalOcean API or the functionality of any existing resources.

Our Engineering team was able to fully resolve the issue and as of 20:24 UTC, the Cloud Control Panel is functioning normally.

If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

May 28, 00:00 UTC
Completed - The scheduled maintenance has been completed.

May 27, 22:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

May 24, 22:23 UTC
Scheduled - Start: 2025-05-27 22:00 UTC
End: 2025-05-28 00:00 UTC

During the above window, our Networking team will be making changes to the core networking infrastructure to improve performance and scalability in the NYC3 region.

Expected impact:

During the maintenance window, users may experience delays or failures with event processing for a brief duration on Droplets and Droplet-based services, including Droplets, Managed Kubernetes, Load Balancers, Container Registry, and App Platform. Additionally, regular requests via the Public API, as well as viewing and submitting requests through the Cloud Control Panel, may time out or fail for up to 5 minutes. We will endeavor to keep this to a minimum for the duration of the change.

If you have any questions related to this issue, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket

May 23, 02:11 UTC
Resolved - Our Engineering team has confirmed full resolution of the issue on the Managed Databases control plane. Users can continue to create and deploy applications without any issue.

We appreciate your patience. If you continue to experience any problems, please open a ticket from your account for further investigation.

May 23, 00:28 UTC
Monitoring - Our Engineering team has taken steps to mitigate the impact on the Managed Databases control plane that was causing delays in API calls, resulting in create and deploy errors for users.

At this time, services remain stable and users can create or deploy applications normally.

We will monitor the environment for an extended period to ensure full function continues. We will post another update by 14:00 UTC today, May 23 or as soon as we have any further information.

If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience

May 22, 22:21 UTC
Update - Our Engineering team continues to investigate an issue with the Managed Databases control plane that is causing delays in the API calls. At this time, we are seeing performance improvement; therefore, Database and App Platform users can create or deploy applications normally.

We are actively working on identifying the root cause and resolving the issue as quickly as possible. We understand the inconvenience this may cause and appreciate your patience.

We will provide further updates as soon as they are available.

May 22, 21:03 UTC
Update - Our Engineering team is continuing to investigate the root cause of the issue affecting Managed Database and App Platform control plane operations.

We apologize for any inconvenience caused and appreciate your patience. We will post further updates as soon we have more information.

May 22, 16:59 UTC
Investigating - Our Engineering team is currently investigating an issue impacting App Platform and Managed Databases across all regions. We've determined this to be related to another recent incident, which was posted on our Status page at the following address:

https://status.digitalocean.com/incidents/2ch98sc024vv

During this time, some users may experience issues with control plane operations (such as listing resources, creating and scaling resources, etc) for Managed Databases and App Platform deployments which have a database.

We are actively working on identifying the root cause and resolving the issue as quickly as possible. We understand the inconvenience this may cause and appreciate your patience.

We will provide further updates as soon as more information is available

May 22, 19:23 UTC
Resolved - Our Engineering has confirmed full resolution of the issue impacting Droplet creation in all regions. Users can now create Droplets and Droplet-based services, including Managed Kubernetes, Managed Databases, and Load Balancers without any issues.

We appreciate your patience while we worked to fix this issue. If you continue to experience any problems, please open a ticket from your account for further investigation.

May 22, 18:43 UTC
Monitoring - Our Engineering team has identified the reason behind the failed Droplet creates and implemented a fix to resolve the issue. Users should now be able to create Droplets and Droplet-based services, including Managed Kubernetes, Managed Databases, and Load Balancers without any issues. Users should no longer see any errors when resizing their existing Droplets from the API as well as the Cloud Panel.

We are actively monitoring the situation and will post an update as soon as the issue is fully resolved.

May 22, 17:07 UTC
Update - Our Engineering team is continuing to investigate the issue with Droplet creation in all regions. During this time, users won't be able to see the Droplet sizes when creating regular/basic Droplets from the Cloud Panel, blocking creates except for the default size Droplet in each region. Resizes for existing basic Droplets are unavailable. Users are also unable to create Load Balancers, Managed Databases, and Kubernetes Clusters via the Cloud Control Panel and will see errors on those pages.

API requests for creating and resizing Droplet-based resources are also impacted.

At this time, our team is working as quickly as possible to mitigate the impact from this incident and is investigating potential workarounds.

We apologize for the inconvenience and will share an update once we have more information.

May 22, 14:59 UTC
Investigating - Our Engineering team is investigating an issue with Droplet creation in multiple regions. During this time, users may see an elevated failure rate for the creation of Droplets and other Droplet-based products, such as Load Balancers, Managed Databases, or Kubernetes in multiple regions. Already running Droplets should not be affected, however, users might not be able to resize their Droplets during this time.

We apologize for the inconvenience and will share an update once we have more information.

May 22, 10:59 UTC
Resolved - From 07:19 UTC to 08:15 UTC, users may have experienced errors with app deployment via App Platform.

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.

May 22, 08:35 UTC
Investigating - As of 07:19 UTC, our Engineering team is currently investigating an issue causing delays in the creation of apps deployed via App Platform. During this time, some users may see app deployment failing to complete.

We are actively working on identifying the root cause of issues and will post further updates as more information is available. We apologize for the inconvenience.

May 22, 09:26 UTC
Resolved - Our Engineering team has confirmed the complete resolution of the issue that was impacting Spaces, App Platform and Container Registry in our BLR1 region. Users should now see improved performance, and error rates have decreased. User should no longer experience errors while deploying their application in App Platform and uploading to Container Registry in the same region.

We appreciate your patience and understanding while we worked to restore normal service.

If you continue to experience any issues, please open a support ticket from within the Cloud Control Panel for further review.

May 22, 09:08 UTC
Monitoring - Our Engineering team has implemented a fix with the issue affecting Spaces, App Platform and Container Registry in our BLR1 region. Users should now see improved performance, and error rates have decreased. User should no longer experience errors while deploying their application in App Platform and uploading to Container Registry in the same region.

We are continuing to monitor the situation closely to ensure stability. Thank you for your patience during the process and we will provide a final update once we confirm the issue is fully resolved.

May 22, 07:41 UTC
Investigating - As of 06:56 UTC, our Engineering team is currently investigating an issue affecting Spaces, App Platform and Container Registry in our BLR1 region. During this time, users may experience a high error rate when attempting to access objects in spaces in this region. Users may also experience errors while deploying their application in App Platform and uploading to Container Registry in the same region.

We are actively working on identifying the root cause and resolving the issue as quickly as possible. We understand the inconvenience this may cause and appreciate your patience.

We will provide further updates in due course.

May 21, 21:23 UTC
Resolved - From 12:00 UTC to 20:05 UTC, users may have experienced an issue creating new apps and adding domains to the apps deployed via App Platform.

Our engineering team has now confirmed the full resolution of the issue and all new apps are working as expected.
If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

May 21, 21:00 UTC
Monitoring - Our Engineering team has implemented a fix to the issue that caused delays in the creation of new apps and adding domains to the apps deployed via App Platform.

The team is monitoring the situation, and we will share an update once this is fully resolved.

May 21, 20:13 UTC
Investigating - Our Engineering team is currently investigating an issue causing delays in the creation of new apps deployed via App Platform. During this time some users might be experiencing delays while attempting to link the domains during app deployment. This issue does not affect existing apps or domains that are already correctly configured.

We are actively working on identifying the root cause of issues and will post further updates as more information is available. We apologize for inconvenience.

May 15, 17:01 UTC
Resolved - From 13:45 UTC to 15:50 UTC, users may have experienced an issue affecting the GenAI Platform agents using Llama 3.3 70B.

Our Engineering team has confirmed full resolution of the issue.

If you continue to experience any issues, please reach out to our support team by opening a ticket from within your Cloud Control Panel.

May 15, 16:18 UTC
Monitoring - Our Engineering team has implemented a fix to address the issue impacting the GenAI Platform agents using Llama 3.3 70B. As of now, GenAI Platform agents using Llama 3.3 70B should respond without any issues.

We are actively monitoring the situation and will post an update as soon as the issue is fully resolved.

We apologize for the inconvenience and appreciate your patience.

May 15, 15:26 UTC
Identified - Our Engineering team has identified the cause of the issue affecting the GenAI Platform. During this time, GenAI Platform agents using Llama 3.3 70B will fail to respond.

A fix is in progress, and we will provide an update as soon as we have more information.

May 15, 14:58 UTC
Investigating - Our Engineering Team is currently investigating an issue with the GenAI Platform where the GenAI Platform agents using Llama 3.3 70B are failing to respond.

We are actively working to identify the root cause. We apologize for the inconvenience and will share an update once we have more information.

May 15, 06:53 UTC
Resolved - From 03:20 UTC to 06:01 UTC, users may have experienced an issue affecting the GenAI Platform using Llama 3.370B where chatbots are failing to respond

Our Engineering team has confirmed full resolution of the issue. Users should now be able to run chatbots normally.

If you continue to experience any issues, please reach out to our support team by opening a ticket from within your Cloud Control Panel.

May 15, 06:17 UTC
Monitoring - Our Engineering team has implemented a fix to address the issue impacting with the GenAI Platform agents using Llama 3.370B where chatbots are failing to respond. We are currently monitoring the issue.

We will provide an update as soon as more information becomes available.

We apologize for the inconvenience and appreciate your patience.

May 15, 05:41 UTC
Investigating - We are investigating an issue where GenAI Platform agents are failing to respond. We apologize for the inconvenience this may cause.

May 14, 15:43 UTC
Resolved - Our Engineering team has completely resolved the issue that was affecting the Droplet search functionality within the DigitalOcean Cloud Control Panel. We have observed normal functionality following the fix and continued monitoring has shown stable behavior. Users should be able to successfully search for and locate their Droplets. The issue is now considered resolved.

We appreciate your patience and apologize for any inconvenience this may have caused. However, if you continue to face issues then please open a ticket with our Support team for further review.

May 14, 14:32 UTC
Monitoring - Our Engineering team has implemented a fix for the issue affecting the droplet search functionality within the DigitalOcean Cloud Control Panel. Users should now be able to search for the droplets using the search box on the droplets listing page.

We are continuing to monitor the situation closely to ensure stability. Thank you for your patience during the process and we will provide a final update once we confirm the issue is fully resolved.

May 14, 12:34 UTC
Investigating - Our Engineering team is currently investigating an issue affecting the Droplet search functionality within the DigitalOcean Cloud Panel. Some customers may be experiencing difficulties when attempting to search for and locate their Droplets.

We are actively working to identify the root cause and will provide updates as we learn more. We understand how critical this functionality is for managing your infrastructure, and we appreciate your patience during the process.

We will share an update as more information becomes available.

May 13, 23:22 UTC
Resolved - Our Engineering team has confirmed that the issue affecting the GenAI Platform DeepSeek model has been fully resolved. Users should no longer encounter the message "It looks like the agent ran out of tokens while reasoning. Please try again or increase the max tokens."

All functionality remains unaffected, and users should no longer experience any interruptions.

If you continue to experience any issues, please reach out to our support team by opening a ticket from within your Cloud Control Panel.

May 13, 22:51 UTC
Monitoring - Our Engineering team has implemented a fix to address the issue impacting the GenAI Platform's DeepSeek model, where some users were encountering the message "It looks like the agent ran out of tokens while reasoning. Please try again or increase the max tokens".

At this time, users should be seeing agents run normally.

We are actively monitoring the situation and will post an update as soon as the issue is fully resolved.

May 13, 21:50 UTC
Investigating - Our Engineering Team is currently investigating an issue with the GenAI Platform DeepSeek model where some users may encounter the message "It looks like the agent ran out of tokens while reasoning. Please try again or increase the max tokens."

We will provide an update as soon as more information becomes available.

We apologize for the inconvenience and appreciate your patience.

May 8, 13:01 UTC
Resolved - Our Engineering team has confirmed the resolution of the issue affecting certain Droplet metrics in the BLR1 region. Users should no longer see intermittent gaps in monitoring graphs for Droplets in the BLR1 region.

We appreciate your patience and apologize for any inconvenience this may have caused.

May 8, 01:26 UTC
Monitoring - Our Engineering team has implemented a fix to address the intermittent unavailability of Droplet metrics and delayed Resource Alerts in the BLR1 region.

Our team is now and monitoring the results and will continue to do so for an extended period to ensure this sporadic issue is addressed by the implemented fix.

At this time, we expect users not to experience further metrics gaps or delays in alerts.

We will post an update as soon as we confirm this incident is fully resolved or once we have further information. Thank you for your patience.

May 7, 22:04 UTC
Update - Our Engineering team is continuing to investigate the root cause of the issue with intermittent unavailability of Droplet metrics in the BLR1 region. Multiple reproduction efforts and testing against potential root causes are underway. Due to the sporadic nature of the issue, we anticipate incident updates for this issue to be less frequent, but we will share new information as soon as it is available.

At this time, users impacted by this incident will experience intermittent gaps in monitoring graphs for Droplets in BLR1, as well as delayed notifications for Resource Alerts (for any resources in BLR1).

We apologize for the inconvenience, and we'll share an update once we have more information.

May 7, 09:41 UTC
Update - Our Engineering team continues to investigate the intermittent unavailability of certain Droplet metrics in the BLR1 region. Due to the sporadic nature of this issue, our analysis requires additional time to correlate patterns and isolate the root cause.

We apologize for the inconvenience, and we'll share an update once we have more information.

May 6, 13:00 UTC
Investigating - Our Engineering team is currently investigating issues with certain Droplet metrics that are missing for the BLR1 region. Users may experience issues when accessing certain metrics on Droplets.

We apologize for the inconvenience, and we'll share an update once we have more information.

May 5, 15:46 UTC
Resolved - Our Engineering team has confirmed the complete resolution of the issue that was affecting Droplet creation and console access in the NYC1 region. Users should now be able to deploy new droplets and access them normally in the NYC1 region.

All systems are now operating normally. We appreciate your patience and apologize for any inconvenience this may have caused.

May 5, 15:18 UTC
Monitoring - Our Engineering team has implemented a fix for the issue affecting Droplet creation and console access in the NYC1 region. Impacted users may have seen 504 Gateway Timeout errors during Droplet creation or when accessing the Droplet console.

Our team is currently monitoring the situation to ensure stability. We will provide a final update once we confirm the issue is fully resolved.

May 5, 14:18 UTC
Investigating - Our Engineering team is currently investigating an issue with creating Droplets in NYC1 region. During this time, users may see 504 Gateway Timeout errors when creating droplets in the NYC1 region.

We apologize for the inconvenience and will provide an update as soon as we have more information.

May 7, 23:00 UTC
Completed - The scheduled maintenance has been completed.

May 7, 20:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

May 4, 20:10 UTC
Scheduled - Start: 2025-05-07 20:00 UTC
End: 2025-05-07 23:00 UTC

During the above window, our Networking team will be making changes to the core networking infrastructure to improve performance and scalability in the LON1 region.

Expected impact:

During the maintenance window, users may experience delays or failures with event processing for a brief duration on Droplets and Droplet-based services, including Droplets, Managed Kubernetes, Load Balancers, Container Registry, and App Platform. We will endeavor to keep this to a minimum for the duration of the change.

If you have any questions related to this issue, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket

Apr 30, 14:57 UTC
Resolved - Our Engineering team has confirmed the complete resolution of the issue that was impacting the availability of Spaces in our FRA1 region. Users should no longer experience elevated error rates when accessing Spaces in the region.

We appreciate your patience and understanding while we worked to restore normal service.

If you continue to experience any issues, please open a support ticket from within the Cloud Control Panel for further review.

Apr 30, 14:14 UTC
Monitoring - Our Engineering team has implemented a fix for the issue affecting the availability of Spaces in our FRA1 region. Users should now see improved performance, and error rates have decreased.

We are continuing to monitor the situation closely to ensure stability. Thank you for your patience during the process and we will provide a final update once we confirm the issue is fully resolved.

Apr 30, 13:06 UTC
Investigating - Our Engineering team is currently investigating an issue affecting the availability of Spaces in our FRA1 region. During this time, users may experience high error rate when attempting to access Spaces in this region.

We are actively working on identifying the root cause and resolving the issue as quickly as possible. We understand the inconvenience this may cause and appreciate your patience.

We will provide further updates in the due course.

Apr 30, 00:11 UTC
Resolved - Our Engineering team has confirmed full resolution of the network issue with new DOKS worker nodes in our SFO2 region.

If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Apr 29, 23:49 UTC
Monitoring - Our Engineering team identified the cause of the issue and has rolled out a fix to resolve the network issue with new DOKS worker nodes. At this time, all services should be operating normally.

We are actively monitoring the fix and will post an update as soon as the issue is fully resolved.

Apr 29, 22:25 UTC
Investigating - Our Engineering team is investigating an issue causing new DOKS worker nodes to have network issues in our SFO2 region. Operations such as creating new DOKS nodes, manually or autoscaled, will have network connectivity issues within the clusters they are added to during this time.

Our Engineering team is actively working to identify the root cause and restore service as quickly as possible. We will continue to provide updates here as we make progress.

Apr 30, 21:00 UTC
Completed - The scheduled maintenance has been completed.

Apr 30, 13:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Apr 28, 13:25 UTC
Scheduled - Start: 2025-04-30 13:00 UTC
End: 2025-04-30 21:00 UTC

Hello,

During the above window, our Engineering team will be performing maintenance on core control plane infrastructure. Please note that the existing infrastructure will continue running without issue. This maintenance may impact create, read, update, and delete (CRUD) operations in all regions.

Expected Impact:

During the maintenance window, users may experience increased latency during two 5 minute windows with the following platform operations:

Cloud Control Panel and API operations
Event processing
Droplet creates, resizes, rebuilds, and power events
Managed Kubernetes reconciliation and scaling
Load Balancer operations
Container Registry operations
App Platform operations
Managed Database creation and scaling

We do not expect any impact to customer traffic due to this maintenance. If an unexpected issue for the control plane arises, we will endeavor to keep any impact to a minimum and may revert if required.

If you have any questions related to this maintenance please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket

Thank you,
Team DigitalOcean

Apr 28, 11:17 UTC
Resolved - This incident has been resolved.

Apr 28, 11:14 UTC
Investigating - Between 09:58 UTC and 10:11 UTC, our Engineering team observed issues impacting DNS resolution in our LON1 region. During this time, some users may have experienced errors while trying to resolve domain names from within Digitalocean resources.

Our team was able to take quick action to mitigate the impact and resolve the issue, and all services in the LON1 region are now functioning normally. Thank you for your patience, and we apologize for any inconvenience.

If you are still experiencing issues or have additional questions, please open a Support ticket right away.