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.

Apr 24, 16:31 UTC
Resolved - Our Engineering team has confirmed full resolution of the issue impacting event processing in the FRA1, AMS2, BLR1, SGP1, NYC1, and SYD1 regions.

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.

Apr 24, 15:53 UTC
Monitoring - Our Engineering team has identified the cause of the issue causing delays in Droplet event processing in our FRA1 region, and has implemented a fix.

While investigating this issue, our Engineers also observed some events appearing to be stuck or delayed in the AMS2, BLR1, SGP1, NYC1, and SYD1 regions. As of now, the event processing rates have returned to normal in all these regions.

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

Apr 24, 13:41 UTC
Investigating - Our Engineering team is investigating an issue causing delays in Droplet event processing in our FRA1 region.

This includes operations such as creating, resizing, powering on/off, or deleting Droplets. These actions may take longer than usual to complete or may appear to be temporarily stalled.

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

Apr 24, 04:41 UTC
Resolved - Our Engineering team has resolved the issue with the email delivery delays. Services should now be operating normally.

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

Apr 24, 00:28 UTC
Monitoring - Our Engineering team has confirmed the email delivery delays caused by an issue with an upstream provider has been mitigated. We are now seeing successful delivery of previously delayed emails, as well as normal flow of new messages.

We are currently monitoring the situation closely and will share an update as soon as the issue is fully resolved.

Apr 23, 22:34 UTC
Identified - Our Engineering team is aware of an issue with an upstream provider that is impacting the delivery of emails from DigitalOcean to DigitalOcean customers.

Beginning 20:55 UTC, users may experience delays in receiving emails from DigitalOcean, including sign-in verification codes, sign-up verifications, maintenance notifications, and other transactional emails.

Our team is closely monitoring the situation and has begun to see signs of recovery, with both delayed and recent emails starting to be delivered.

We will provide further updates as they are available.

Apr 22, 19:05 UTC
Resolved - From 16:54 to 18:17 UTC, users may have experienced issues creating Spaces from control panel due to the datacenter region options failing to list.

Our Engineering team has implemented a fix and confirmed full resolution of the issue. Users should be able to create Spaces from Cloud Control Panel without issues now.

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

Apr 22, 18:30 UTC
Monitoring - Our Engineering team has implemented a fix to resolve the issue impacting the creation of Spaces. Users should now be able to create Spaces without any issues.

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

Apr 22, 18:08 UTC
Identified - Our Engineering team has identified an issue with creating Spaces through the Cloud Control Panel. During this time, users are unable to create Spaces buckets due to the datacenter region options failing to list. Creating Spaces buckets through the API remains functional. All other Spaces functionality is unaffected.

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

Apr 22, 18:03 UTC
Investigating - Our Engineering team is currently investigating an issue with creating Spaces through the Cloud Control Panel. During this time, users may experience difficulties when selecting the Data Center option, as it is not listing correctly. We apologize for the inconvenience and will provide an update as soon as we have more information.

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.

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.

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.

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.

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.

Mar 27, 16:31 UTC
Resolved - Our Engineering team has confirmed the full resolution of the issue affecting database engine metrics in the Cloud Control Panel for Managed Databases.

Users with PostgreSQL, MySQL, Kafka, OpenSearch, or Caching database clusters should now be able to see the metrics.

Thank you for your patience, and we apologize for any inconvenience. If you continue to experience any issues, please open a Support ticket right away.

Mar 27, 05:44 UTC
Monitoring - Our Engineering team continues to monitor the issue affecting Database Engine metrics in the Cloud Control Panel for Managed Databases. The impact is mitigated and we are rolling out the update gradually during scheduled maintenance windows to avoid disruptions.

We will post another update once we confirm the full resolution. We apologize for the inconvenience and will share an update once we have more information.

Mar 26, 22:24 UTC
Identified - Our Engineering team has identified and is currently repairing an issue affecting database engine metrics in the Cloud Control Panel for Managed Databases.

Users with PostgreSQL, MySQL, Kafka, OpenSearch, or Caching database clusters may be unable to see metrics. Mongo database clusters are not impacted. Additionally, storage metrics and alerts are not impacted and continue to function normally.

While we are working to correct this issue as quickly as possible, we anticipate that a resolution will take multiple days. We will post an update once we have a more definite ETA or additional information becomes available.

We apologize for the inconvenience. If you have any questions, please feel free to reach out to our Support team from within your account.

Mar 25, 07:30 UTC
Resolved - Our Engineering team has confirmed the full resolution of the issue with the Billing page for Teams on the Cloud Control Panel. Services should now be operating normally.

Thank you for your patience, and we apologize for any inconvenience. If you continue to experience any issues, please open a Support ticket right away.

Mar 25, 07:01 UTC
Monitoring - Our Engineering team has now mitigated the issue that affected the Billing page for Teams on the Cloud Control Panel and is currently been monitored. Users should no longer see errors when attempting to access or perform actions within the Cloud Control Panel.

We will continue to monitor this at our end and will share an update once the problem is resolved completely.

Mar 25, 06:32 UTC
Identified - Our Engineering team has Identified the cause of the issue with Billing page on the Control Panel and is actively working on a fix. We will post an update as soon as the issue is fully resolved.

Mar 25, 06:06 UTC
Investigating - Our Engineering team is investigating an issue with the Billing page for Teams on the Cloud Control Panel. During this time, users may receive error messages when attempting to access or perform actions within the Cloud Control Panel. We apologize for the inconvenience and will share an update once we have more information.

Mar 25, 00:45 UTC
Resolved - Our Engineering team has confirmed the full resolution of the issue with Cloud Control Panel.

Thank you for your patience, and we apologize for any inconvenience. If you continue to experience any issues, please open a Support ticket right away.

Mar 25, 00:14 UTC
Monitoring - Our Engineering team is currently monitoring the issue which affected Cloud Control Panel logins and registrations for a brief window of time between 20:55 and 22:15 UTC.

Users should no longer see errors while trying to login Cloud Control Panel. New users should now be able to register in the Cloud Control Panel as normal.

We will continue to monitor this at our end and will share an update once the problem is resolved completely.

Mar 24, 22:23 UTC
Update - Our Engineering team continues to investigate the root cause of the issue with our Cloud Control Panel, but has confirmed error rates are dropping. Most users should now be seeing recovery and be able to login and navigate the site. New users should be able to register.

If you continue to see errors, please reach out to us via https://www.digitalocean.com/company/contact/support

Mar 24, 21:39 UTC
Update - Our Engineering team is continuing to investigate the issue with our Cloud Control Panel. At this time, users may experience errors while attempting to navigate any pages under https://cloud.digitalocean.com, which includes both login and registration attempts. If you need to contact our support team and are unable to do so from within your account, you can still reach us via https://www.digitalocean.com/company/contact/support

Mar 24, 21:23 UTC
Investigating - Our Engineering team is investigating an issue with our Cloud Control Panel. During this time, users may experience errors reaching https://cloud.digitalocean.com/login, issues while signing in there, as well as issues navigating the Cloud Control Panel.

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

Mar 17, 17:50 UTC
Resolved - From 14:23 UTC to 16:16 UTC, users were unable to complete the signups for new accounts. Our Engineering team has resolved the issue affecting new account sign-ups. Users should no longer experience errors and are now able to complete the sign-up process successfully.

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

Mar 17, 16:46 UTC
Monitoring - Our Engineering team has implemented a fix to resolve the issue impacting new account signups and monitoring the situation. At this time, new signups should be functioning as expected. We will post an update as soon as the issue is fully resolved.

Mar 17, 16:22 UTC
Investigating - Our Engineering team is investigating an issue with new customer signups. During this time, some new customers are unable to finish the signup process.

We apologize for the inconvenience and will provide an update as soon as possible.

Mar 18, 22:44 UTC
Completed - The scheduled maintenance for our core networking infrastructure in the LON1 region, originally planned for March 18, 2025, from 20:00 UTC to 23:00 UTC, has been cancelled. No further changes will be made at this time, and all services are currently operating as expected.

During the scheduled window, we encountered an issue that caused a brief impact on services. As a result, we decided to roll back the maintenance to prevent further disruption. We appreciate your patience and understanding during this time.

We will provide an update once a new date for the maintenance has been confirmed. If you have any questions or experience any ongoing issues, please reach out to our support team via Cloud Support.

Thank you for your understanding.

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

Mar 15, 20:16 UTC
Scheduled - Start: 2025-03-18 20:00 UTC
End: 2025-03-18 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 10, 21:49 UTC
Resolved - From March 1st 12:00 UTC to March 10th 18:43 UTC, a subset of users experienced issues connecting Managed Kubernetes nodes to Droplets as a source to allow traffic, due to an issue with tags being applied internally. Some users may also have experienced issues adding Managed Kubernetes Clusters as a source in Cloud firewalls with related Droplets.

Our Engineering team has confirmed full resolution of the issue. Users should now be able to connect Managed Kubernetes nodes to Droplets and should also be able to add Managed Kubernetes Cluster as a source in the Cloud Firewall with related Droplets.

If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel.

Mar 10, 14:38 UTC
Identified - Our Engineering team has identified the cause of the issue affecting recently created Managed Kubernetes nodes. These nodes are currently unable to connect to Droplets that use the Managed Kubernetes Cluster as a source to allow traffic.
Additionally, users who add a Managed Kubernetes Cluster as a source in the Cloud firewall may experience issues with related Droplets not being added to the firewall as expected.

As a temporary solution, users can continue to add the tag k8s:CLUSTER_UUID, where CLUSTER_UUID is the UUID of the user's Managed Kubernetes Cluster. The UUID can be found in the Cloud Panel URL of the Managed Kubernetes Cluster or by running the following command:

doctl kubernetes cluster list

We are working on a solution and will provide further updates as we progress. We appreciate your patience and understanding.

Mar 10, 12:03 UTC
Investigating - Our Engineering team is currently investigating an issue impacting recently created Managed Kubernetes nodes not being able to connect to Droplets that utilize the Managed Kubernetes Cluster source to allow traffic.

Users adding a Managed Kubernetes Cluster as a source in the Cloud firewall may see related Droplets not added to the Cloud firewall.

As a workaround users can add the tag "k8s:CLUSTER_UUID" where "CLUSTER_UUID" is the user's Clusters UUID.
Users can find the UUID details in the Cloud Panel URL of Managed Kubernetes Cluster or by using the command "doctl kubernetes cluster list"

We apologize for the inconvenience and will share more information as soon as it's available.

Mar 5, 23:11 UTC
Resolved - From 20:08 UTC to 21:49 UTC, users may have experienced issues creating new certificates, provisioning or scaling MongoDB clusters, and issuing certificates for use with LBAAS and CDN services. Additionally, a subset of new custom domains on the App Platform may have taken longer than usual to configure.

Our Certificate Authority has fully resolved the issue with our managed certificates service, and all services have returned to normal operation.

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

Mar 5, 22:07 UTC
Monitoring - Our Certificate Authority has implemented a fix for the issue with our managed certificates service. Services are beginning to recover, and we are closely monitoring the situation to ensure full stability.

Users should now be able to create new certificates, provision and scale MongoDB clusters, and issue certificates for use with LBAAS and CDN services. Additionally, new custom domains on the App Platform should start configuring normally.

We apologize for the inconvenience and will share another update once the matter is fully resolved.

Mar 5, 21:22 UTC
Investigating - Our engineering team is investigating an issue with our managed certificates service due to an unexpected outage from our Certificate Authority.

During this time, users may experience issues creating new certificates, provisioning or scaling MongoDB clusters, and issuing certificates for use with LBAAS and CDN services. Additionally, this may cause a subset of new custom domains on App Platform to take longer than usual to become active.

We apologize for the inconvenience and will provide updates as soon as we receive more information.