DigitalOcean Outage History

The issue impacting the visibility of Cloud Panel has been confirmed to be resolved. Between approximately 16:08 PM & 17:56 PM UTC, users may have noticed unusual behavior when accessing the console, performing resizing operations, or experiencing issues with the Cloud Panel visibility. Our team has taken necessary corrective measures to restore the service, and we can confirm that it is now functioning as expected. We sincerely apologize for the inconvenience caused and truly appreciate your understanding throughout this process. However, if you continue to experience any issues, please do not hesitate to raise a support ticket for further investigation. We’ll be happy to assist you.

Our team has implemented a fix to address the issue affecting the visibility of the Cloud Panel. We are actively monitoring the situation to ensure overall stability. Users should no longer encounter abnormalities when accessing the console, resizing the Droplet, misalignments within the Cloud Panel, etc. We will provide a further update once the issue is fully confirmed to be resolved.

Our team is currently investigating an issue impacting the visibility of the Control Panel. Users may notice unexpected behavior, such as being prompted for login credentials when accessing the console, being unable to select radio buttons for any plans during resize, columns appearing squished, etc. We apologize for the inconvenience and will share further updates as soon as more information becomes available.

As of 18:55 UTC, our Engineering team has confirmed that the issue causing delays in App Platform deployments has been fully resolved. The fix implemented earlier has been successful, and we are no longer seeing any delays or errors with deployments. Users should now be able to deploy their apps successfully and without any issues. We apologize again for the inconvenience caused. However, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation. We'll be happy to assist you.

Our Engineering team has implemented a fix to address the issue causing delays in App Platform deployments. We are actively monitoring the situation to ensure overall stability. Users may already notice improvements while deploying apps. We appreciate your patience throughout the process and will provide a further update once the issue is fully confirmed to be resolved.

Our engineers are currently investigating an issue impacting new App Platform deployments. During this time, some users may experience delay when creating new App Platform apps. Existing apps are not affected and should continue to function normally. We apologize for any inconvenience, and we'll share more information as it becomes available.

Our Engineering team has confirmed the full resolution of the issue with MongoDB 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.

Our Engineering team has implemented a fix to resolve the issue with MongoDB clusters 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.

Our engineering team has identified the cause of the issue with create, fork and resize events failure for MongoDB clusters in all of our regions and is actively working on a fix. We will post an update as soon as additional information is available.

Our engineering team continues to investigate the issue with create, fork and resize events failure for MongoDB clusters in all of our regions. We appreciate your patience and will post an update as soon as additional information is available.

Our Engineering team is investigating an issue with all events for MongoDB clusters in all of our regions. During this time, users may face issues with creation, fork and resize operations in the MongoDB clusters. We apologize for the inconvenience and will share an update once we have more information.

The issue impacting delays in App Platform deployments has been confirmed to be resolved. Between approximately 08:52 UTC & 13:01 UTC, users may have noticed delays while creating or updating apps, or may have encountered failed deployments. For failed deployments, please trigger a redeploy, which should successfully resolve the issue. We confirmed that the service is functioning as expected. Once again, we sincerely apologize for the inconvenience caused and appreciate your understanding. However, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation. We’ll be happy to assist you.

Our team has implemented a fix to address the issue causing delays in App Platform deployments. We are actively monitoring the situation to ensure overall stability. Users may already notice improvements while deploying apps. We appreciate your patience throughout the process and will provide a further update once the issue is fully confirmed to be resolved.

Our engineers are currently investigating an issue impacting new App Platform deployments. During this time, some users may experience delay when creating new App Platform apps. Existing apps are not affected and should continue to function normally. We apologize for any inconvenience, and we'll share more information as it becomes available.

As of 17:55 UTC, our Engineering team has resolved the timeouts affecting the Cloud Control Panel and API. The issue was caused by a temporary overload on our infrastructure, resulting in 5xx errors for API requests and gateway timeouts for Cloud Control Panel users. If you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused and appreciate your patience and understanding.

Our Engineering team has implemented a fix for the timeouts affecting the Cloud Control Panel and API, and is currently monitoring the situation. Services have recovered, and users should no longer experience 5xx errors when using the API or gateway timeouts when accessing the Cloud Control Panel. We will continue to monitor the situation to ensure that all services are stable and functioning as expected. We will post an update as soon as the issue is fully resolved.

Our Engineering team has identified the cause of the issue impacting the Cloud Control Panel and API and is actively working on deploying a fix. At this time, users will continue to see timeouts/5xx errors, but may intermittently see requests succeeding. We will post further updates as soon as the fix is deployed or there is more information to share.

Our Engineering team is investigating an issue impacting our Cloud Control Panel and API. Users attempting to make API requests could see 5xx errors and users attempting to access the Cloud Control Panel may see gateway timeouts or page timeouts. We apologize for the inconvenience and will share an update once we have more information.

Our Engineering team is investigating an issue impacting our Cloud Control Panel and API. Users attempting to make API requests could see 5xx errors and users attempting to access the Cloud Control Panel may see gateway timeouts or page timeouts. We apologize for the inconvenience and will share an update once we have more information.

Our Engineering team has resolved the issue affecting Kubernetes clusters and Droplet events in the FRA1 region. Between approximately 00:17 UTC and 14:30 UTC, customers may have experienced issues provisioning Kubernetes clusters and mounting volumes. 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.

Our Engineering team has implemented a fix to address the issue affecting Kubernetes clusters and Droplet events in the FRA1 region and is actively monitoring the situation. Customers should no longer experience issues provisioning Kubernetes clusters or mounting volumes. We will provide an update as soon as the issue is fully resolved.

Our Engineering team has identified the root cause of the issue impacting Kubernetes clusters and Droplet events in the FRA1 region and is actively working on a fix. In the meantime, users may continue to experience issues. We appreciate your patience and will share updates as more information becomes available.

Our Engineering team is investigating an issue with Kubernetes clusters in the FRA1 region. During this time, subset of users may experience an issue while provisioning Kubernetes clusters and mounting volumes. Additionally, users may also notice the droplet events appearing to be stuck or delayed in this region. We apologize for the inconvenience and will share an update once we have more information.

Our Engineering team has confirmed that the issue impacting our Droplet-based products in the FRA1 region has been completely mitigated. Users should no longer see issues with their Droplets and Droplet-related services. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Our Engineering team has identified the cause of the issue impacting our Droplet-based products in the FRA1 region and applied a fix. The impact has started to mitigate and users should be able to connect to their Droplets and also start to see events getting processed successfully. We're now monitoring the fix for stability and will post an update once we are confident it is successful.

Our Engineering team is currently investigating an issue affecting events in FRA1. During this time, customers may experience delays or errors when creating or deleting Droplets, as well as when using Droplet-based products such as Load Balancers, Kubernetes Clusters, or Databases. Our teams are actively working to identify the root cause and restore full service as quickly as possible. We apologize for the inconvenience and will provide updates as more information becomes available.

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.

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.

Our Engineering team has resolved the issue with payments failure using PayNow. Users should not see any issues with making payments via PayNow and logging into the accounts on our platform. 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.

Our engineering team is investigating an issue with the suspended user's accounts being unable to access the accounts. During this time users may have experience issues signing in or accessing accounts and the failure in the payments. We apologize for the inconvenience and will share an update once we have more information.

Our Engineering has confirmed resolution of the issue. Users should no longer experience errors with attempting to deploy new static sites in NYC3 on App Platform. If you experience any further problems or have any questions, please open a support ticket within your account.

Our Engineering team has deployed a fix for the issue. Users should no longer experience errors when attempting to deploy new static sites now in NYC3 for App Platform. We will post an update once we've confirmed that the issue is fully resolved.

As of 17:45 UTC, our Engineering team is investigating reports of static site deployment failures in the NYC3 region on App Platform. Users may experience errors when attempting to deploy new static sites, resulting in failed deployments. The existing static sites are still accessible and functioning normally. Our team is actively working on identifying the root cause and implementing the fix. We apologize for the inconvenience and will share an update once we have more information.

Our Engineering team has confirmed full resolution of the issue. Users should no longer experience errors when making requests to the Cloud Control Panel or API. If you experience any further problems or have any questions, please open a support ticket within your account.

As of 17:47 UTC, our Engineering team is investigating reports of intermittent 504 errors when making requests to api.digitalocean.com and cloud.digitalocean.com. Users may experience sporadic errors, resulting in a 504 response code, when attempting to interact with our API or Cloud services. At this point, the issue appears to be intermittent, and not all requests are being affected. We apologize for the inconvenience and will share an update once we have more information.

From 18:57 UTC to 22:05 UTC, customers may have experienced issues accessing the Recovery Console due to a service interruption. During this time, Droplet functionality remained unaffected, and customers were still able to use the Recovery ISO option via SSH. Our Engineering team has confirmed that the issue is now fully resolved, and Recovery Console access has been fully restored and is operating normally. If you continue to experience any difficulties, please open a ticket with our Support team. We apologize for the inconvenience caused.

Our Engineering team has deployed a fix to resolve the issue causing the Recovery Console to be unavailable. We are currently monitoring the situation to ensure access is fully restored and stable. Please note that Droplet functionality was not impacted by this issue. We will post another update once we confirm the issue is fully resolved.

Our Engineering team is actively investigating an issue causing the Recovery Console to be unavailable. Droplet functionality is not impacted. If customers need recovery iso, they can still select the "Boot from Recovery ISO" option in the recovery tab as seen in the guide here https://docs.digitalocean.com/products/droplets/how-to/recovery/recovery-iso/ but will need to use SSH to access their droplets. We apologize for the inconvenience and will share an update once we have more information.

As of 18:15 UTC, our Engineering team has confirmed the issue impacting accessibility of App Platform static websites has been resolved. Service has been restored and are now functioning normally. We appreciate your patience and regret the inconvenience caused. If you continue to experience any issues, feel free to open a Support ticket for further investigation.

Our Engineering team has implemented a fix impacting the availability of App Platform static websites. Users should now experience improved performance when accessing the sites. We are actively monitoring the situation and will provide an update once we can confirm the issue has been fully resolved.

Our Engineering team is currently investigating an issue impacting App Platform static websites. During this period, users may notice 404 Not Found errors while accessing the sites. Our team is actively working on identifying the root cause and implementing the fix. We apologize for the inconvenience and will share an update once we have more information.

From 18:02 UTC to 21:10 UTC, customers in the BLR1 region who had not previously created an app may have experienced DOCR (DigitalOcean Container Registry) access errors when attempting to create new apps. Our Engineering team has confirmed that the issue is fully resolved, and all systems are now operating normally. If you continue to experience any problems, please open a ticket with our Support team. We apologize for the inconvenience caused.

Our Engineering team has deployed a fix for the issue affecting the creation of new apps in the BLR1 region, where customers who had not previously created an app encountered DOCR (DigitalOcean Container Registry) access errors. We are currently monitoring the situation to ensure that the issue does not recur and that all functionality remains stable. We will post another update once we confirm the issue is fully resolved.

Our Engineering team is currently investigating an issue affecting the creation of new apps in the BLR1 region. Customers who have not previously created an app may encounter DOCR (DigitalOcean Container Registry) access errors. Our team is actively deploying a fix to restore normal functionality. We apologize for the inconvenience and will share an update once we have more information.

Our Engineering team has confirmed the full resolution of this issue. From approximately 08:51 UTC – 09:12 UTC, users may have experienced difficulties signing in or accessing resources through the Control Panel and API due to an upstream provider issue. The upstream provider has fixed the issue, and all services are now functioning normally. 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.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

Our Engineering team has been made aware of an issue with an upstream provider that was affecting the Control Panel and API and has deployed a fix to resolve it. Users may have experienced issues signing in or accessing resources through the Control Panel. We are monitoring the situation closely and will share an update once the issue is resolved completely.

From As of 16:34 to 19:47 UTC, may have encountered errors listing backup operations for their PostgreSQL, MySQL, OpenSearch, Redis and Kafa clusters through the API and UI. Our Engineering team has confirmed full resolution of the issue, users should no longer experience issues with listing backup operations. Thank you for your patience, and we apologize for the inconvenience. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel.

As of 19:47 UTC, our Engineering team has implemented a fix for the errors on Managed Database list backup operations, which was related to a dependency issue. The situation is currently improving, and we are seeing a reduction in error rates. The impact was limited to list backup operations for PostgreSQL, MySQL, OpenSearch, Redis, and Kafka engines, where users may have experienced errors when attempting to retrieve a list of backups through both the API and UI. We are now monitoring the situation to ensure that the fix is fully effective and that all operations are functioning normally. Users should no longer experience errors when listing backups, and all other control plane operations, such as creating, updating, or deleting databases, should continue to function normally. We will continue to monitor the situation to ensure that the issue is fully resolved. We apologize for the disruption and appreciate your patience.

As of 16:34 UTC, our Engineering team is investigating reports of errors and timeouts on control plane operations for Managed Databases. The issue is affecting multiple database engines, including PostgreSQL, MySQL, OpenSearch, Redis, and Kafka. Users may experience errors or timeouts when attempting to list backups, through both the API and UI. We want to emphasize that this issue does not currently appear to be impacting the data plane, and databases should continue to be accessible and functional. Our team is working to determine the root cause of the issue and will share an update once we have more information. We apologize for the inconvenience and appreciate your patience as we work to resolve this incident. We will provide further updates as soon as more information is available.

Our Engineering team has fully implemented and confirmed the effectiveness of the fix for the increased guardrail latency. System performance has returned to normal, and all affected services are operating as expected. We have observed stable metrics during extended monitoring and have not detected any further latency or interruptions. 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 that has significantly reduced the impact of the issue, largely mitigating the outage. Although the situation has improved, some users may still experience intermittent latency issues. We are closely monitoring the results and will continue to work towards full resolution. We will provide another update once we have confirmed the issue is fully resolved.

Our Engineering team is currently investigating increased guardrail latency, which may cause long response times for agents with attached guardrails. We apologize for the inconvenience and will share an update once we have more information. Thank you for your patience and understanding as we work to resolve this issue.

As of 20:07 UTC on December 2, 2025, our Engineering team has detected increased guardrail latency which may produce long response times for agents with attached guardrails. Engineering is working on a fix. We apologize for the inconvenience and will share an update once we have more information. Thank you for your patience and understanding as we work to resolve this issue.

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.

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.

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.

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

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!

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.

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.

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.

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.

This incident has been resolved.

We are continuing to work on a fix for this issue.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Our Engineering team has resolved the issue impacting Managed Kubernetes clusters in our TOR1 region. We apologize for the inconvenience and appreciate your patience throughout this event. If you experience any further problems or have any questions, please open a support ticket within your account.

Our Engineering team is investigating an issue impacting Managed Kubernetes cluster creation and management operations in TOR1 region. During this time, some users may experience errors provisioning new Kubernetes clusters as well as making changes to existing clusters. Workloads on existing clusters are not impacted at this time. We apologize for the inconvenience and will share an update once we have more information.

Our Engineering team has resolved the connectivity issue with Managed Database PostgreSQL clusters in all regions that are using PGBouncer and some legacy MD5 passwords. 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 connectivity issues impacting Managed Database PostgreSQL clusters using PGBouncer with some legacy MD5 passwords. We are currently monitoring the situation and will provide an update once the issue is fully resolved.

Our Engineering team has identified an issues with connectivity for Managed Database PostgreSQL clusters in all regions that are using PGBouncer and some legacy MD5 passwords. We are actively monitoring the situation and will provide updates as soon as more information becomes available.

Our Engineering team has confirmed the full resolution of the networking connectivity issue affecting the BLR1 region after monitoring. Users should be able to access droplets and all other resources without any issues. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

The network connectivity issue affecting the BLR1 region, which was caused by a broader internet issue, has been mitigated. Network accessibility in the region has improved, 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.

Our Engineering team is still observing intermittent issues impacting network connectivity in the BLR1 region. This stems from a broader Internet issue impacting the BLR1 region. As a result, users may still continue to experience packet loss/latency, timeouts, and related issues with Droplet-based services in this region, including Droplets, LBaaS, Managed Kubernetes, and Managed Database. Our Engineering team is actively investigating the issue. We will post an update as soon as additional information is available.

The network connectivity issue impacting the BLR1 region has been mitigated. Users should no longer experience packet loss/latency, timeouts, and related issues with Droplet-based services in this region, including Droplets, LBaas, Managed Kubernetes, and Managed Database. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.

Our Engineering team is investigating an issue impacting networking connectivity in BLR1 region with upstream provider. Users may experience network connectivity loss to Droplets and Droplet-based services, like Managed Kubernetes and Database Clusters. We apologize for the inconvenience and will share an update once we have more information.

Our Engineering team has resolved the performance issue affecting Spaces in the FRA1 region. From approximately 08:02 UTC - 09:40 UTC, customers may have experienced slow performance or limited availability when accessing Spaces, its objects via the Control Panel or API, or Container Registry. 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.

Our Engineering team has implemented a fix to address the performance issue affecting Spaces in the FRA1 region 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, and Container Registry access. We will post an update as soon as the issue is fully resolved.

Our Engineering team is investigating a performance issue affecting Spaces in the FRA1 region. During this time, customers may experience slow performance or limited availability when accessing Spaces or its objects via the Control Panel or API, and Container Registry access may also be affected. We apologize for the inconvenience and will share an update once we have more information.

Our Engineering team has confirmed that the issue affecting .space domains has been resolved, and customers should now be able to access their .space domains successfully. If you continue to experience any issues, please open a support ticket for assistance.

Our Engineering team has identified issues affecting .space domains. As a result, some customers may be unable to access their websites, and zone files may not appear in dig results. The engineers have confirmed that this is an issue with the registry and have informed upstream providers. We apologize for the inconvenience and will provide updates as soon as more information is available.

Our Engineering team has resolved the issue that was affecting the ability to access and manage the Managed Databases and App Platform in the Cloud Control Panel. Users should now no longer experience slowness, timeouts, or errors when interacting with Managed Databases or App Platform services. All operations should be functioning normally. 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 to resolve the issue that was resulting in the degradation of the Managed Database and App platform deployment in the Cloud Control Panel. During this time, users should no longer experience slowness issues with Managed Database and App Platform, and any other previously mentioned timeouts and errors. We will post an update as soon as the issue is fully resolved.

Our Engineering team has identified an issue affecting the ability to access and manage the Managed databases and App platform in the Cloud Control Panel. While there is no impact on data-plane availability, Users may experience some issues like UI taking a while to load, request timeouts, some delays in App platform deployment for apps that have databases, and some API errors. Our Engineering team is already working on this issue for the resolution. We apologize for the inconvenience and will share an update once we have more information.

Our Engineering team has confirmed that our upstream providers have been able to mitigate the network connectivity issues in the BLR1 and SGP1 regions. At this time users should not experience intermittent degraded performance and timeout errors with Droplet-based services to and from these regions. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Our Engineering team has observed significant improvements with the network latency and packet loss during peak hours today. This is a result of our upstream providers making some routing adjustments. We are carefully monitoring the network performance for the next 24 hours. We will communicate any further relevant information as we have it. We apologize for the inconvenience in the meantime.

Significant submarine cable outages continue to impact multiple network carriers on the Indian subcontinent, with increased latency and packet loss to our BLR1 region occurring sporadically throughout the day. On a positive note, our upstream providers have worked diligently over the past couple of days to minimize the impact of the loss of submarine capacity. As a result, we are now mainly seeing service degradation during the busier evening peak hours only. For the moment, we have no updates to provide regarding when the situation might improve. Repair times for submarine cables are typically on the order of weeks or months. However, further short-term improvements may still be possible as upstream carriers work to re-balance traffic where feasible. Separately, we continue to look into potential avenues for additional mitigations and will keep our customers aprised as we make progress in this area. We apologize for the ongoing inconvenience created by this extraordinary situation and thank our customers for their patience.

Our Engineering team confirms that multiple subsea cable cuts are impacting connectivity in the APAC region, which also affects traffic to Europe and the U.S. East Coast. Traffic is being rerouted through alternate paths to maintain service continuity. As a result, users may experience higher latency and intermittent connectivity issues. Our engineering team continues to monitor the situation closely and is working with upstream providers as repair efforts progress. We will share further updates as they become available. We apologize for the disruption and appreciate your patience.

We are continuing to work on a fix for this issue.

Our Engineering team has implemented changes to optimize traffic routing in the BLR and SGP regions, addressing networking issues stemming from our upstream providers, which are affected by major submarine cable outages in the APAC region. Despite these adjustments, users may still encounter intermittent packet loss or connectivity issues when accessing resources in the affected areas. We are working with our upstream vendors to gain further insights and achieve a definitive resolution. We apologize for any inconvenience caused.

Our Engineering team has identified the cause of the issue impacting networking connectivity in BLR1 region to be with our upstream provider. Our team is actively working on remediation steps. We will post an update as soon as we have more information.

Our Engineering team is currently investigating an issue impacting networking in BLR1 region. Users may experience network connectivity loss to Droplets and Droplet-based services, like Managed Kubernetes and Database Clusters. We apologize for the inconvenience and will share an update once we have more information.

Our Engineering team has confirmed the full resolution of the issue with the upstream provider. Users should now be able to deploy to App Platform and manage their Spaces Buckets as normal. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Our Engineering team has identified that the ongoing issue with the upstream provider is also impacting DigitalOcean Spaces. They continue to monitor the ongoing issue with the upstream provider impacting DigitalOcean Spaces and App Platform services. Improvements are being seen with lower error rates and latency for App Platform deployments as well as for fetching Spaces endpoints. We apologize for the inconvenience and will share further updates in the due course.

Our Engineering team is aware of an upstream provider issue that is causing impact to some DigitalOcean services. More details are being gathered. At this time, users may experience delayed App Platform deployments. We apologize for the inconvenience and will provide another update as soon as possible.