Nov 24, 20:19 UTC
Resolved - From 18:55 to 19:32 UTC, Our Engineering team observed an issue with all control plane operations (Create, Scale, Fork, etc ) for all non-Mongo Managed Database clusters. During this time, users encountered long running requests made either through the Cloud Console UI or API, including provisioning new clusters, listing clusters, etc. Our team has fully resolved the issues as of 19:32 UTC All services for non-Mongo Managed Databases should now be operating normally. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. We apologize for any inconvenience caused.

Nov 25, 21:41 UTC
Completed - The scheduled maintenance has been completed.

Nov 25, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Nov 23, 16:01 UTC
Scheduled - Start: 2025-11-25 16:00 UTC
End: 2025-11-25 22:00 UTC

During the above window, our Engineering team will be performing maintenance on core control plane infrastructure in the SYD1 region. Please note that the existing infrastructure will continue running without issue.

Expected Impact:

We do not anticipate any impact; however, there is a small possibility that Control Panel functionality specifically CRUD (Create, Read, Update, Delete) operations may be affected during the maintenance window. All running workloads are expected to continue operating normally without interruption.

Our team will be actively monitoring the environment throughout the maintenance, and any unexpected events will be promptly communicated through our status page.

If you have any questions or concerns regarding this maintenance, please feel free to open a support ticket from https://cloudsupport.digitalocean.com/s/createticket. We’re here to help.

Nov 18, 20:39 UTC
Resolved - Our Engineering team has confirmed that the external network incident affecting multiple DigitalOcean services has been fully mitigated. The impacted services including Gen AI tools, App Platform, Load Balancers, Spaces, and provisioning or management actions for new clusters have recovered and are now operating normally. All requests are completing successfully.

Thank you for your patience. If you continue to experience any issues, please open a support ticket from within your account.

Nov 18, 19:31 UTC
Monitoring - Our engineering team has observed that the external network incident impacting multiple DigitalOcean services has been mitigated. The affected services including Gen AI tools, App Platform, Load Balancer, Spaces, and provisioning or management actions for new clusters are showing continued signs of recovery, with most requests now completing successfully.

Our engineering team continues to monitor the situation closely. We will post an update as soon as the issue is fully resolved.

We apologize for the disruption and appreciate your patience.

Nov 18, 13:40 UTC
Update - Our Engineering team is actively investigating an issue impacting multiple DigitalOcean services caused by an upstream provider incident. This disruption affects a subset of Gen AI tools, the App Platform, Load Balancer, Spaces and provisioning or management actions for new clusters. Existing clusters are not affected. Users may experience degraded performance or intermittent failures within these services.

We acknowledge the inconvenience this may cause and are working diligently to restore normal operations. Signs of recovery are starting to appear, with most requests beginning to succeed. We will continue to monitor the situation closely and provide timely updates as more information becomes available. Thank you for your patience as we work towards full service restoration.

Nov 18, 12:26 UTC
Investigating - Our Engineering team is actively investigating an issue impacting multiple DigitalOcean services caused by an upstream provider incident. This disruption affects a subset of Gen AI tools, the App Platform, Load Balancer, and Spaces. Users may experience degraded performance or intermittent failures within these services.

We acknowledge the inconvenience this may cause and are working diligently to restore normal operations. Signs of recovery are starting to appear, with most requests beginning to succeed. We will continue to monitor the situation closely and provide timely updates as more information becomes available. Thank you for your patience as we work towards full service restoration

Nov 17, 19:26 UTC
Resolved - From 16:59 to 17:34 UTC, our Engineering team observed an issue with block storage volumes in the NYC1 and AMS3 regions. During this time, users may have experienced failures when attempting create, snapshot, attach, detach, or resize volumes. There was no impact to performance or availability of existing volumes. Our team has fully resolved the issues as of 17:34 UTC and volumes should be operating normally. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. We apologize for any inconvenience caused.

Nov 16, 11:05 UTC
Resolved - Our Engineering team has confirmed full resolution of the issue with failed create events with their Spaces, App Platform, and DOCR services.

From 06:15 UTC AM to 09:53 AM UTC, the Spaces, App Platform, and DOCR services were impacted and have since been restored to normal operation.

If you continue to experience problems, please open a ticket with our support team. Thank you for your patience throughout this incident!

Nov 16, 10:02 UTC
Monitoring - Our Engineering team has implemented a fix to resolve the issue with failed create events with their Spaces, App Platform, and DOCR services and at this time, services should be functioning as expected.

We're monitoring the situation and will post a final update once we confirm this is fully resolved.

Nov 16, 08:31 UTC
Investigating - Our engineering team is investigating an issue with failed create events with their Spaces, App Platform, and DOCR services. At this time, users may experience errors when creating Spaces, App Platform, DOCR services.

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

Nov 9, 07:11 UTC
Resolved - Our Engineering team has confirmed the full resolution of the networking connectivity issue affecting the BLR1 region. Users should experience expected performance when accessing Droplets and other services.

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

Nov 8, 18:07 UTC
Monitoring - Our Engineering team is still observing intermittent issues impacting network connectivity in the BLR1 region. Between 17:28 and 17:37 UTC, the team observed a major connectivity loss to this region and took immediate steps to reroute traffic via a different upstream provider to alleviate the impact.

The issue BLR1 is experiencing at the moment stems from a broader Internet issue. Network accessibility in the region has improved as of now, and users should already experience better performance when accessing Droplets and other services. We are closely monitoring the situation to ensure stability.

We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.

Nov 8, 15:15 UTC
Resolved - From 13:50 to 14:15 UTC, our Engineering team observed an issue with an upstream provider impacting network connectivity in the BLR1 region.

During this time, users may have experienced increase in latency or packet loss when accessing Droplets and Droplet-based services, like Managed Kubernetes and Database Clusters in BLR1 region.

The impact has now subsided and as of 14:15 UTC, users should already experience better performance when accessing Droplets and other services.

We apologize for the inconvenience. If you are still experiencing any problems or have additional questions, then please open a support ticket within your account.

Oct 29, 23:59 UTC
Resolved - This incident has been resolved.

Oct 29, 21:12 UTC
Update - We are continuing to work on a fix for this issue.

Oct 29, 21:11 UTC
Update - Our Engineering team has identified the cause of the issue with the deployment of Gradient AI Platform Agents in VPCs and is actively working on a fix.

We will post an update as soon as the fix has rolled out or there is additional information to share.

Oct 29, 21:09 UTC
Identified - Our Engineering team has identified the cause of the issue with the deployment of Gradient AI Platform Agents in VPCs and is actively working on a fix.

We will post an update as soon as the fix has rolled out or there is additional information to share.

Oct 29, 20:26 UTC
Investigating - As of 18:50 UTC, our Engineering team is investigating reports of agent creation issues impacting customers using a VPC on the GradientAI platform. At this point, affected users may experience errors where the agent creation process is stuck on "Waiting for Deployment." We apologize for the inconvenience and will share an update once we have more information.

Oct 28, 19:58 UTC
Resolved - Our Engineering team has resolved the issue affecting Garbage Collection in container registries, and all services are operating normally.

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

Oct 28, 19:06 UTC
Monitoring - Our Engineering team has implemented a fix for the Garbage Collection issue affecting container registries and Customers should no longer experience Garbage Collection jobs failing or getting stuck.

We are currently monitoring the situation and will post an update as soon as the issue is fully resolved. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Oct 28, 14:57 UTC
Identified - Our Engineering team has identified the root cause of the issue affecting Garbage Collection in the container registries.

A fix is being implemented to resolve failures and stuck operations. We will provide an update once the mitigation has been deployed.

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

Oct 28, 11:30 UTC
Investigating - Our Engineering team is investigating an issue with the Garbage Collection in the container registries. At this time, users may experience errors with the Garbage Collection failing or being stuck.

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

Oct 24, 18:11 UTC
Resolved - Between 14:28 PM & 14:35 PM UTC today, our Engineering team has identified an issue impacting the availability of multiple services, including Droplets, Volumes, Spaces, Kubernetes, Load Balancers, Managed Databases, etc. During this period, users might have noticed 500 Internal Server Errors or 503 Service Unavailable Errors when accessing these services and other dependent services.

Our team has taken appropriate measures to address the issue. We can confirm that all services have been restored and are now functioning normally.

We regret the inconvenience caused. However, if you continue to experience any issues, please create a support ticket for further analysis.

Oct 23, 18:33 UTC
Resolved - Our Engineering team has resolved the performance issue affecting Spaces. From approximately 15:42 UTC - 16:14 UTC, customers may have experienced slow performance or limited availability when accessing Spaces, its objects via the Control Panel or API. Accessing and creating Container Registry along with App builds were also affected during this time. All services should now be functioning normally.

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

Oct 23, 17:16 UTC
Monitoring - Our Engineering team has implemented a fix to address the performance issue affecting Spaces and is monitoring the situation. Customers should no longer experience slow performance or limited availability when accessing Spaces, its objects via the Control Panel or API. Also, App builds and creating or accessing the Container Registry should work fine.

We will post an update as soon as the issue is fully resolved.

Oct 23, 17:15 UTC
Update - Our Engineering team has implemented a fix to address the performance issue affecting Spaces and is monitoring the situation. Customers should no longer experience slow performance or limited availability when accessing Spaces, its objects via the Control Panel or API. Also, App builds and creating or accessing the Container Registry should work fine.

We will post an update as soon as the issue is fully resolved.

Oct 23, 16:17 UTC
Investigating - Our Engineering team is investigating a performance issue affecting Spaces. During this time, customers may experience slow performance or limited availability when accessing Spaces or its objects via the Control Panel or API. In additon to that, Container Registry access/creation and app builds may also be affected.

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

Oct 22, 17:12 UTC
Resolved - The issue impacting App Platform deployments has been successfully resolved. Users should no longer encounter delays during the build phase or have deployments getting stuck. All services are now confirmed to be stable and operating normally.

We appreciate your patience throughout this but if you continue to experience any issues, please create a support ticket for further analysis.

Oct 22, 16:58 UTC
Monitoring - Our Engineering team has implemented necessary changes to address the issue impacting both new and in-progress App Platform Deployments. Our team is currently monitoring the situation. Users should now notice improvements in deployment performance.

We appreciate your patience. We'll update once the issue is confirmed to be resolved.

Oct 22, 16:40 UTC
Investigating - Our Engineering team is currently investigating an issue impacting both new and in-progress App Platform Deployments. During this period, users may notice app deployments getting stuck in the build phase or even delayed builds. In some cases, builds may even fail shortly after retries are exhausted.

We apologize for the inconvenience caused and appreciate your patience while we work to resolve this issue. We'll update once we have more information.

Oct 21, 05:41 UTC
Resolved - Between 08:00 UTC and 22:53 UTC, an issue with an upstream provider affected multiple DigitalOcean services, including SMS-based 2FA (causing code delivery failures), Docker Hub-hosted images (impacting Managed Kubernetes and App Platform deployments), and SnapShooter backup jobs. The issue has been resolved, and all services are now stable and operating normally.

We appreciate your patience throughout this but if you continue to experience any issues, please create a support ticket from within the Cloud Control Panel for further analysis.

Oct 20, 10:21 UTC
Investigating - As of 08:00 UTC our Engineering team is investigating an issue affecting multiple DigitalOcean services due to an incident with an upstream provider. As a result, users attempting to log in using SMS-based 2FA may experience problems receiveing codes and complete authentication. Images hosted exclusively on Docker Hub may also be temporarily unavailable, impacting deployments on DigitalOcean Kubernetes (DOKS) and App Platform.

Additionally, the users leveraging SnapShooter for serverless backups may encounter failures in backup jobs as well. We're now seeing signs of recovery, and most of the requests should be succeeding. We will continue to monitor closely to ensure full service restoration and will share an update as more information becomes available.

Oct 17, 04:28 UTC
Resolved - Our Engineering team has confirmed that the IPv6 connectivity issue has been fully resolved across all regions. Users should no longer face IPv6 connectivity issues. If you continue to experience problems, please open a ticket with our support team. Thank you for your patience and we apologize for any inconvenience.

Oct 17, 03:56 UTC
Monitoring - Our Engineering team has implemented the fix to resolve the IPv6 networking issues in multiple regions. Users should no longer have issues connecting to via IPv6 to their Droplets.

We will continue to monitor the situation, and we will post an update once we've confirmed complete resolution.

Oct 17, 02:52 UTC
Identified - Our Engineering team has identified the issue and are implementing a fix. Our team has resolved the IPv6 connectivity issue in FRA1 and are monitoring the situation.

In addition, it was discovered that the NYC1, and SFO2 regions were affected by this issue as well, and our team is currently working to resolve the issue in those regions. To summarize, users in the regions of AMS2, SGP1, NYC1, and SFO2 may still experience connection issues via IPv6.

We are rapidly working on a fix. We will share more information once available.

Oct 17, 00:44 UTC
Update - While investigating this issue, our Engineering team has noticed that the issue is occurring in SGP1 as well. Users in SGP1 may also experience IPv6 connectivity issues at this time.

We are working to resolve this issue as quickly as possible. We will post updates as soon as we have more information.

Oct 17, 00:19 UTC
Investigating - Our Engineering team is investigating an issue affecting IPv6 connectivity in FRA1, and a small subset of users in AMS2. At this time, users may experience issues connecting to IPv6-enabled resources.

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

Oct 15, 14:25 UTC
Resolved - Our Engineering team has resolved the issue affecting the creation of NVDIA GPU nodes on new Kubernetes clusters. Users will no longer encounter issues when creating NVDIA GPU nodes on new Kubernetes clusters.

If you continue to experience any issues, please open a support ticket. We sincerely apologize for the inconvenience caused and appreciate your understanding.

Oct 15, 12:18 UTC
Identified - Our Engineering team has identified the issue affecting the creation of GPU nodes on new Kubernetes clusters. Users may continue to experience difficulties when attempting to create GPU nodes on new Kubernetes clusters.

Our team is actively working to resolve the issue and will provide an update as soon as we have more information. We sincerely apologize for the inconvenience and appreciate your patience.

Oct 15, 11:29 UTC
Investigating - Our Engineering team has identified an issue impacting creation of GPU nodes on new Kubernetes clusters. During this time, you will not be able to launch a new Kubernetes cluster with NVIDIA GPU nodes. Existing workloads are not impacted. We apologize for the inconvenience and will share an update once we have more information.

Oct 14, 22:18 UTC
Resolved - Our Engineering team has confirmed the full resolution of the issue with Managed Database Clusters.

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.

Oct 14, 19:00 UTC
Monitoring - Our engineering team has implemented a fix for the issue that affected a subset of customers who were unable to provision Managed Database Clusters, including MySQL, PostgreSQL, Valkey, OpenSearch, and Kafka.

We will continue to closely monitor the situation to ensure full stability and will provide an update once the issue is fully resolved.

Oct 14, 17:10 UTC
Identified - Our engineering team has identified the cause of the issue affecting a subset of our customer who were unable to provision Managed Database Clusters including MySQL, PostgreSQL, Valkey, OpenSearch, and Kafka.

Our team is actively working on remediation steps and will share an update as soon as more information becomes available.

Oct 14, 11:56 UTC
Investigating - Our engineering team is investigating an ongoing issue affecting Managed Database Clusters. Currently, users may encounter errors when creating MySQL, PostgreSQL, Valkey, OpenSearch, and Kafka clusters through the Cloud Control Panel or API requests.

We apologize for the inconvenience and will provide further updates as soon as more information is available.

Oct 13, 14:45 UTC
Resolved - Our Engineering team has confirmed that the issue affecting Spaces access in the FRA1 region has been fully resolved.

Users should now be able to list and access their Spaces objects without any errors. We appreciate your patience and understanding while we worked to restore normal service.

If you experience any further problems or have any questions, please open a support ticket within your account.

Oct 13, 13:38 UTC
Monitoring - Our Engineering team has implemented a fix for the issue affecting Spaces access in the FRA1 region. We are observing recovery, and users should now be able to list and access their Spaces objects without encountering InvalidAccessKeyId errors.

We will continue to closely monitor the situation to ensure full stability and will provide an update once the issue is fully resolved.

Oct 13, 11:23 UTC
Investigating - Our Engineering team is currently investigating an issue affecting Spaces access in the FRA1 region.

During this time users trying to access or list the Spaces objects will be experiencing InvalidAccessKeyId errors.

This issue appears to be isolated to the FRA1 region. Our engineering team is actively investigating the root cause. We will provide an update as soon as more information becomes available.

Oct 15, 00:00 UTC
Completed - The scheduled maintenance has been completed.

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

Oct 12, 22:08 UTC
Scheduled - Start: 2025-10-14 22:00 UTC
End: 2025-10-15 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 NYC1 region.

Expected impact:

During the maintenance window, we do not anticipate any downtime for Droplets or Droplet related services. If an unexpected issue arises, users may experience brief delays or failures in event processing including Droplets, Managed Kubernetes, Load Balancers, Container Registry, Public API, Cloud Control Panel 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

Oct 10, 23:58 UTC
Resolved - Our Engineering team has resolved the issue affecting multiple services, including the Cloud Control Panel and API.

Users should now be able to access their accounts and use the API without any errors.

If you still encounter any issues, please launch a ticket with our Support team.

Oct 10, 22:29 UTC
Monitoring - Our Engineering team has implemented a fix for the issue affecting the Cloud Control Panel, API, and related services. We are observing recovery, and users should now be able to access their accounts and use the API without errors.

We are continuing to monitor the situation closely and will provide an update once full resolution is confirmed.

Oct 10, 21:56 UTC
Investigating - Our Engineering team is investigating an issue impacting multiple services including the Cloud Control Panel and API.

Users may encounter errors when accessing their accounts or using the API.

We are actively working to resolve this issue and will provide updates as soon as more information becomes available.

Oct 9, 14:00 UTC
Completed - The scheduled maintenance has been completed.

Oct 9, 11:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Oct 7, 11:26 UTC
Update - We will be undergoing scheduled maintenance during this time.

Oct 7, 11:24 UTC
Scheduled - Start: Oct 09, 2025, 11:00 UTC
End: Oct 09, 2025, 14: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 SYD1 region.

Expected impact:

We do not anticipate any downtime for Droplets or Droplet-related services, including Managed Databases, Load Balancers, App Platform, and Managed Kubernetes, as this maintenance has been carefully designed and tested to be seamless. In the unlikely event that an undetected misconfiguration occurs, a subset of customers could experience temporary network disruption. 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