
© Cheng Xin/Getty Images

© Cheng Xin/Getty Images
Apr 6, 01:01 UTC
Resolved - Our Engineering team has resolved the issue affecting Mongo 8 Database operations. Users should be able to create new Mongo 8 Databases, and other operations such as upgrading, scaling, and forking should complete successfully now.
If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Apr 5, 22:01 UTC
Update - Our Engineering team is actively investigating the issue affecting Mongo 8 Database operations.
We apologize for the continued inconvenience. We will provide additional updates as soon as more information becomes available.
Apr 5, 19:54 UTC
Update - Our Engineering team is continuing to investigate the cause of the issue with Mongo 8 Database creation in our AMS3 region and is taking action to resolve this issue. In addition to the database creation, users may see failures when scaling the instance or performing any control plane operations.
We will continue to share updates as soon as we have new information.
Apr 5, 16:52 UTC
Investigating - Our Engineering team is investigating an issue with Mongo 8 database creation in the AMS3 region. At this time, users may experience errors while attempting to create a new Mongo 8 database instance in the AMS3 region.
We apologize for the inconvenience and will provide another update as soon as possible.
Apr 5, 13:59 UTC
Resolved - Our Engineering team has confirmed the full resolution of the networking issue affecting the LON1 region. Users should be able to access all resources without any issues.
If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Apr 5, 13:35 UTC
Monitoring - Our Engineering team made routing changes to remediate the networking issue due to an impact by an upstream provider and confirmed that it has successfully mitigated the connectivity issues in the LON1 region. Users should not be seeing any issues with networking in the LON1 region.
We will monitor this incident for a short period to confirm full resolution.
Apr 5, 12:45 UTC
Identified - Our Engineering team has identified the cause and applied a fix to mitigate the connectivity issue impacting the entire LON1 region. Users should be seeing improvements in reaching their resources in the LON1 region.
We'll continue to monitor the situation to confirm this incident is fully resolved and will post an update soon.
Apr 5, 12:17 UTC
Investigating - Our Engineering team is currently investigating an issue impacting networking in the LON1 region. Users may experience network connectivity loss to the resources residing in this region.
We apologize for the inconvenience and will share an update once we have more information.


© Coradir
Apr 3, 23:10 UTC
Resolved - Our Engineering team has implemented a fix to resolve the issue with creating certain GenAI Platform agents. Users should now be able to create OpenAI and Llama 3.1 8B agents without issue.
If you continue to experience any problems, please reach out to our support team by opening a ticket from within your Cloud Control Panel.
Apr 3, 21:06 UTC
Investigating - Our Engineering team is investigating an issue affecting GenAI Platform. The GenAI platform is seeing errors creating agents with certain LLMs, specifically OpenAI and Llama 3.1 8B. The user is shown an agreement checkbox even though they have already accepted the agreement. If they try to accept the agreement, they will be thrown an error and prevented from creating the agent.
We apologize for the inconvenience, we will share an update once we have more information.



© Linh Pham for Rest of World
Apr 2, 04:46 UTC
Resolved - Our Engineering Team has implemented a fix to resolve the issues impacting GenAI platform agents. They have also confirmed that the issue has been fully resolved. Now, customers should be able to view and update their GenAI platform agents in the console.
If you continue to experience any problems, please reach out to our support team by opening a ticket from within your Cloud Control Panel.
Apr 2, 03:26 UTC
Investigating - Our Engineering Team is currently investigating an issue where some customers are unable to view their GenAI platform agent in the console. As a result, they are also unable to update their agent via the console. We are working to determine which types of agents are affected, including whether newly created agents are impacted.
We apologize for the inconvenience and will provide another update as soon as possible.

© Augusto Zambonato for Rest of World

© Zheng Taotao/Xinhua/Getty Images
Mar 31, 09:30 UTC
Resolved - From 00:13 UTC to 9:09 UTC, users may have experienced errors when attempting to create Managed Database Caching Clusters.
Our Engineering team has confirmed the full resolution of the issue. Users should now be able to create Caching clusters normally.
If you continue to experience issues, please open a support ticket from your Cloud Control Panel.
Mar 31, 07:58 UTC
Monitoring - Our Engineering team has implemented a fix to resolve the issues impacting the creation of Managed Database Clusters.
Users should no longer see any errors while creating a Caching Database Cluster.
We are actively monitoring the situation and will post an update as soon as the issue is fully resolved.
Mar 31, 05:41 UTC
Identified - Our Engineering team has identified the root cause of the issue affecting the creation of Managed Database Clusters and is actively working on a fix.
Users who already have a Caching Database Cluster in their account should be able to create a new Cluster. During this time, users without an existing caching cluster in their account may still see an error while creating a new cluster.
We apologize for the inconvenience and will provide another update as soon as possible.
Mar 31, 04:09 UTC
Investigating - As of 00:13 UTC, our Engineering team is investigating an issue with creating Managed Database clusters.
During this time, users may face issues creating caching clusters.
We apologize for the inconvenience and will share an update once we have more information.
Apr 8, 18:51 UTC
Completed - The scheduled maintenance for our core networking infrastructure in the LON1 region, originally planned for April 8, 2025, from 20:00 UTC to 23:00 UTC, has been cancelled. No changes will be made at this time, and all services will continue to operate as usual.
We will provide an update when this maintenance has a new confirmed date. If you have any questions, please reach out to our support team via Cloud Support.
Thank you for your understanding.
Mar 30, 20:29 UTC
Scheduled - Start: 2025-04-08 20:00 UTC
End: 2025-04-08 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

Mar 29, 00:01 UTC
Resolved - From 23:31 to 23:46 UTC, users may have experienced errors when trying to use the API or while accessing our Cloud Control Panel at https://cloud.digitalocean.com. CRUD operations for all products would have been unavailable, but deployed services continue running without issue.
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.

© Andrius Banelis for Rest of World
Mar 27, 20:48 UTC
Resolved - Beginning at 17:56 UTC, users experienced issues with the using the Cloud Control Panel and the API. By 18:10 UTC, we started seeing signs of recovery and users would've been able to access the Cloud Control and API normally.
We noticed a brief recurrence of the issue at 18:58 UTC in which users would've experienced latency, with recovery starting at around 19:02 UTC.
At 19:02 UTC, our Engineering team has confirmed full resolution of the issue, the Cloud Control Panel and the API should be functioning normally now.
If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Mar 27, 19:34 UTC
Monitoring - Our Engineering team has implemented a fix regarding the issue impacting our Cloud Control Panel and API. We are monitoring the situation to ensure there is no recurrence.
We will post another update once we confirm the issue is fully resolved.
Mar 27, 19:11 UTC
Update - Our Engineering team observed a recurrence of this issue from 18:58 to 19:02 UTC. During that time, API requests and navigating the Cloud Control Panel would have failed/experienced latency. As of 19:02 UTC, users should be able to access services normally, but until our team has confirmed a full resolution, there may be periods of instability.
Our team is looking into this issue further and we will share an update as soon as we have more information.
Mar 27, 18:27 UTC
Identified - As of 18:10 UTC, our Engineering team has identified the cause of the issue impacting our Cloud Control Panel and API to be a backend deployment and has rolled back the breaking change. We are already seeing signs of recovery, and users should now have access to the Cloud Control Panel and API.
We will post an update as soon as additional information is available.
Mar 27, 18:07 UTC
Investigating - As of 17:56 UTC, our Engineering team is investigating an issue impacting our Cloud Control Panel and API.
During this time, users will experience errors when trying to use the public API at api.digitalocean.com or while accessing our Cloud Control Panel at https://cloud.digitalocean.com.
We are now confirming the full impact. We regret any inconvenience and will let you know as soon as more information is available.