DigitalOcean Outage History

DigitalOcean had 60 outages in the last 2 years totaling 69h 16m of downtime — averaging 2.5 incidents per month.

There were 60 DigitalOcean outages since November 8, 2025 totaling 69h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.digitalocean.com

Minor March 20, 2026

App platform seeing delays in deployments across FRA1 region

Detected by Pingoru: Mar 20, 2026, 10:32 AM UTC
Resolved: Mar 20, 2026, 12:01 PM UTC
Duration: 1h 28m

Affected: Frankfurt

Timeline · 3 updates

investigating Mar 20, 2026, 10:32 AM UTC

Our engineers are currently investigating an issue impacting new App Platform deployments using Dedicated Egress IP in FRA1 region. During this time, some users may experience delay when creating new App Platform apps or deploying existing 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.
monitoring Mar 20, 2026, 11:14 AM UTC

Our Engineering team has deployed a fix to resolve the issue impacting new App Platform deployments using Dedicated Egress IP in FRA1 region. We are actively monitoring the situation to ensure stability and will provide an update once the incident has been fully resolved. Thank you for your patience and we apologize for the inconvenience.
resolved Mar 20, 2026, 12:01 PM UTC

The issue impacting delays in App Platform deployments has been confirmed to be resolved. Between approximately 00:08am UTC & 11:46am 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.

Read the full incident report →

Major March 20, 2026

Gradient AI Platform agents and services Accessibility

Detected by Pingoru: Mar 20, 2026, 08:50 AM UTC
Resolved: Mar 20, 2026, 02:14 PM UTC
Duration: 5h 24m

Affected: Agent Runtime

Timeline · 5 updates

investigating Mar 20, 2026, 08:50 AM UTC

We are currently investigating issue affecting the accessibility of agents and services on the Gradient AI Platform. Users may experience failures or unresponsiveness when attempting to use these features. Our engineering team is actively working to identify the root cause and restore full functionality. We apologize for the inconvenience and will share an update once we have more information.
identified Mar 20, 2026, 09:51 AM UTC

We’ve identified the issue and are currently working on restoring the services. We’ll continue to provide updates as progress is made.
identified Mar 20, 2026, 11:05 AM UTC

We've identified the issue and are actively working to restore the affected services. We're making steady progress and closely monitoring the situation. Further updates will be shared as they become available.
monitoring Mar 20, 2026, 02:04 PM UTC

A fix has been implemented and services have been restored. We are continuing to monitor the system to ensure stability. We will provide further updates if needed.
resolved Mar 20, 2026, 02:14 PM UTC

Our Engineering team has implemented a fix, the issues impacting Gradient AI Platform have been resolved. All agents are back up and healthy. Service has been fully restored.

Read the full incident report →

Minor March 17, 2026

Gradient AI model availability

Detected by Pingoru: Mar 17, 2026, 03:00 PM UTC
Resolved: Mar 17, 2026, 07:49 PM UTC
Duration: 4h 48m

Affected: Agent Runtime

Timeline · 2 updates

investigating Mar 17, 2026, 03:00 PM UTC

Our Engineering team is investigating reports of Gradient AI model availability issues impacting multiple models. Users may experience issues with models availability, including Llama3.1-8b and Qwen3-32b, as well as embedding models such as GTE Large (v1.5), All-MiniLM-L6-v2, Multi-QA-mpnet-base-dot-v1, and Qwen3 Embedding 0.6B. Additionally, Guardrails are not available, affecting associated agents, and users attempting to run inference on the Llama3.3-70b model will see degraded performance. We apologize for the inconvenience and will share an update once we have more information.
resolved Mar 17, 2026, 07:49 PM UTC

Our Engineering team has implemented a fix, the issues impacting model availability and performance have been resolved. All models, including those previously degraded, are back up and healthy. Service has been fully restored.

Read the full incident report →

Minor March 15, 2026

Degraded performance with BYOK Anthropic models

Detected by Pingoru: Mar 15, 2026, 02:55 AM UTC
Resolved: Mar 15, 2026, 03:31 AM UTC
Duration: 36m

Affected: Agent Runtime

Timeline · 2 updates

investigating Mar 15, 2026, 02:55 AM UTC

Our Engineering team is investigating an issue related to all Gradient AI agents and serverless inference that require BYOK Anthropic modles. Impacted users may experience degraded performance. We will provide an update as soon as possible
resolved Mar 15, 2026, 03:31 AM UTC

The issue is now resolved, all Anthropic BYOK models in Gradient AI should work normally. Contact support if issues persist.

Read the full incident report →

Minor March 13, 2026

Delay in App Platform Deployments

Detected by Pingoru: Mar 13, 2026, 10:01 PM UTC
Resolved: Mar 14, 2026, 01:47 AM UTC
Duration: 3h 46m

Affected: Global

Timeline · 4 updates

monitoring Mar 13, 2026, 09:30 PM UTC

Starting at 20:40 UTC, users may have seen delays with deploying new apps on App Platform. At this time, our Engineering team is seeing signs of recovery, and users should be able to deploy new apps without issue. We're currently monitoring the situation to ensure full recovery. We apologize for the inconvenience. We'll post an update once the issue has been confirmed to be resolved.
identified Mar 13, 2026, 10:01 PM UTC

Our Engineering team is starting to see delays once again with new App Platform deployments. During this time, users may still experience delays with deploying new apps. We're working with our upstream provider to resolve the issue. We again apologize for the inconvenience. We will post further updates once we have more information.
monitoring Mar 13, 2026, 11:39 PM UTC

After working with our upstream provider, our Engineering team has implemented a fix to resolve the issue that was causing delays in the deployment of new apps, and they are currently monitoring the situation. During this time, users should no longer experience issues with creating new apps and all the stalled creation events should provision completely. We will post an update as soon as the issue is fully resolved.
resolved Mar 14, 2026, 01:47 AM UTC

As of 23:00 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.

Read the full incident report →

Minor March 13, 2026

Newly Created Managed Kubernetes Nodes

Detected by Pingoru: Mar 13, 2026, 11:26 AM UTC
Resolved: Mar 13, 2026, 04:35 PM UTC
Duration: 5h 8m

Affected: Global

Timeline · 4 updates

investigating Mar 13, 2026, 11:26 AM UTC

Our Engineering team is investigating an issue impacting newly provisioned Managed Kubernetes nodes. During this time, new nodes may experience DNS timeouts, which could temporarily affect cluster services. We apologize for the inconvenience and will share an update once we have more information.
identified Mar 13, 2026, 12:32 PM UTC

Our Engineering team is investigating an issue impacting newly provisioned Managed Kubernetes nodes. During this time, Only customers who run a NAT Gateway in their VPC and a VPC-native clusters are affected and may experience DNS timeouts. We apologize for the inconvenience and will share an update once we have more information.
monitoring Mar 13, 2026, 01:55 PM UTC

Our Engineering team has implemented a fix to address the issue causing DNS timeouts for newly provisioned Managed Kubernetes nodes. Further investigation has confirmed that this issue primarily affected customers utilizing a NAT Gateway within their VPC and running a VPC-native cluster. We are actively monitoring the situation to ensure overall stability. We appreciate your patience and will provide a further update once the issue is fully confirmed to be resolved.
resolved Mar 13, 2026, 04:35 PM UTC

Our Engineering team has confirmed the resolution of the issue impacting DNS timeouts for newly provisioned Managed Kubernetes nodes. At this time all cluster 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.

Read the full incident report →

Notice March 9, 2026

Ubuntu/Debian Package Mirror Failure

Detected by Pingoru: Mar 09, 2026, 07:23 PM UTC
Resolved: Mar 09, 2026, 07:23 PM UTC
Duration: —

Affected: Global

Timeline · 1 update

resolved Mar 09, 2026, 07:23 PM UTC

From 17:50 to 19:06 UTC, Our Engineering team observed an issue with mirrors.digitalocean.com. During this time, users may have experienced errors when trying to update packages on Debian and Ubuntu Images. Our team has fully resolved the issues as of 19:06 UTC. 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.

Read the full incident report →

Notice March 6, 2026

HTTP 522 Error on App Platform

Detected by Pingoru: Mar 06, 2026, 09:22 PM UTC
Resolved: Mar 06, 2026, 09:22 PM UTC
Duration: —

Affected: Global

Timeline · 1 update

resolved Mar 06, 2026, 09:22 PM UTC

Our Engineering team identified an issue affecting the App Platform. During the incident, users may have experienced HTTP 522 (Connection Timed Out) errors when accessing their apps. The issue seems to be resolved now. We apologize for the inconvenience caused. If you continue to experience any related errors, please contact our Support team by opening a ticket at https://www.digitalocean.com/support/contact/.

Read the full incident report →

Minor March 5, 2026

Internal Load Balancers Connectivity

Detected by Pingoru: Mar 05, 2026, 12:23 AM UTC
Resolved: Mar 05, 2026, 01:52 AM UTC
Duration: 1h 28m

Affected: Global

Timeline · 3 updates

investigating Mar 05, 2026, 12:23 AM UTC

Our Engineering team is investigating an issue affecting Internal Load Balancers. Customers may experience connectivity loss between Internal Load Balancers and their associated target droplets. We apologize for the inconvenience and will share an update as soon as more information becomes available.
monitoring Mar 05, 2026, 01:19 AM UTC

Our Engineering team has implemented mitigation measures to address the connectivity issues affecting Internal Load Balancers and their associated target droplets. We are actively monitoring the situation to ensure stability and to prevent any recurrence. We will provide a further update once we confirm the issue is fully resolved.
resolved Mar 05, 2026, 01:52 AM UTC

From 19:57 UTC to 01:03 UTC, customers may have experienced connectivity issues between Internal Load Balancers and their associated target droplets, which could have resulted in service disruption or traffic routing failures. Our Engineering team has confirmed full resolution of the issue, and Internal Load Balancers should now be functioning normally. If you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience caused.

Read the full incident report →

Minor February 26, 2026

Intermittent Errors with Llama 3.3-70B

Detected by Pingoru: Feb 26, 2026, 04:00 PM UTC
Resolved: Feb 26, 2026, 10:23 PM UTC
Duration: 6h 23m

Affected: Agent Runtime

Timeline · 3 updates

investigating Feb 26, 2026, 07:38 PM UTC

We are currently investigating an issue affecting the Llama 3.3-70B model. Symptoms: Users may encounter intermittent errors when making serverless inference requests via APIs and Agents. Current Status: Our engineering team is actively investigating the issue to determine the root cause.
monitoring Feb 26, 2026, 09:52 PM UTC

Fix deployed. Monitoring resources related to the Llama 3.3-70B. Users should no longer experience intermittent errors when making serverless inference requests via APIs and Agents . Awaiting confirmation before closure.
resolved Feb 26, 2026, 10:23 PM UTC

Issue resolved. Cause: A few requests made to the Llama 3.3-70B model caused issues. Impact: Intermittent errors when interacting with the model through serverless inference and/or with agents created using this model. Contact support if issues persist.

Read the full incident report →

Minor February 19, 2026

Control Panel Visibility

Detected by Pingoru: Feb 19, 2026, 05:34 PM UTC
Resolved: Feb 19, 2026, 06:42 PM UTC
Duration: 1h 7m

Affected: Cloud Control Panel

Timeline · 3 updates

investigating Feb 19, 2026, 05:34 PM UTC

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.
monitoring Feb 19, 2026, 06:05 PM UTC

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.
resolved Feb 19, 2026, 06:42 PM UTC

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.

Read the full incident report →

Notice February 16, 2026

Spaces Availability in NYC3

Detected by Pingoru: Feb 16, 2026, 07:36 AM UTC
Resolved: Feb 16, 2026, 10:58 AM UTC
Duration: 3h 21m

Affected: NYC3NYC3

Timeline · 2 updates

monitoring Feb 16, 2026, 07:36 AM UTC

Between 5:34 and 6:32 UTC, our Engineering team identified the issue that was impacting the availability of Spaces and the Container Registry in the NYC3 region. A fix has been implemented to resolve the issue. During this time users may have experienced errors while interacting with Spaces. Additionally, CRUD operations (create, read, update, delete) within the Container Registry may have failed or returned errors during this time. We are now monitoring the platform to ensure services remain stable and operating as expected. We will provide a final update once the issue is fully resolved. If you continue to experience any issues, please contact our Support team.
resolved Feb 16, 2026, 10:58 AM UTC

Our Engineering team has confirmed that the issue impacting the availability of Spaces and the Container Registry in the NYC3 region has been fully resolved. A fix was implemented, and services have been restored. All operations are now succeeding normally. If you experience any further issues, please contact Support by creating a Support ticket from within your account. Thank you for your patience while we worked to resolve this issue.

Read the full incident report →

Notice February 16, 2026

Droplet Limit Increase Feature

Detected by Pingoru: Feb 16, 2026, 06:38 AM UTC
Resolved: Feb 16, 2026, 09:24 AM UTC
Duration: 2h 46m

Timeline · 3 updates

investigating Feb 16, 2026, 06:38 AM UTC

Our Engineering team is currently investigating an issue affecting the Droplet limit increase feature within the Cloud Control Panel. At this time requests to increase Droplet limits submitted through the Control Panel are not being processed. Customer submissions to increase limits are not generating support tickets as expected. We are actively working to identify the root cause and restore normal functionality as quickly as possible. If you urgently require a Droplet limit increase, please contact Support directly by creating a Support ticket from within your account.
monitoring Feb 16, 2026, 08:37 AM UTC

The issue affecting the Droplet limit increase feature within the Cloud Control Panel has been identified and a fix has been implemented. Requests submitted through the Control Panel are now generating Support tickets as expected. Our team is continuing to monitor the system to ensure full functionality and stability. If you experience any further issues with Droplet limit increase requests, please contact Support directly by creating a Support ticket from within your account.
resolved Feb 16, 2026, 09:24 AM UTC

Our Engineering team has confirmed that the issue affecting the Droplet limit increase feature within the Cloud Control Panel has been fully resolved. Requests to increase Droplet limits submitted through the Control Panel are now being processed correctly, and Support tickets are being generated as expected. If you experience any further issues, please contact Support by creating a Support ticket from within your account. Thank you for your patience while we worked to resolve this issue.

Read the full incident report →

Minor February 12, 2026

MongoDB Cluster Creation

Detected by Pingoru: Feb 12, 2026, 05:42 AM UTC
Resolved: Feb 12, 2026, 12:06 PM UTC
Duration: 6h 24m

Affected: Global

Timeline · 5 updates

investigating Feb 12, 2026, 05:42 AM UTC

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.
investigating Feb 12, 2026, 07:34 AM UTC

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.
identified Feb 12, 2026, 09:04 AM UTC

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.
monitoring Feb 12, 2026, 09:50 AM UTC

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.
resolved Feb 12, 2026, 12:06 PM UTC

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.

Read the full incident report →

Minor February 11, 2026

App platform seeing delays in deployments across all regions.

Detected by Pingoru: Feb 11, 2026, 11:50 AM UTC
Resolved: Feb 11, 2026, 01:08 PM UTC
Duration: 1h 18m

Affected: Global

Timeline · 3 updates

investigating Feb 11, 2026, 11:50 AM UTC

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.
monitoring Feb 11, 2026, 12:03 PM UTC

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.
resolved Feb 11, 2026, 01:08 PM UTC

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.

Read the full incident report →

Minor February 3, 2026

Cloud Control Panel

Detected by Pingoru: Feb 03, 2026, 05:27 PM UTC
Resolved: Feb 03, 2026, 06:53 PM UTC
Duration: 1h 26m

Affected: APICloud Control Panel

Timeline · 5 updates

investigating Feb 03, 2026, 05:27 PM UTC

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.
investigating Feb 03, 2026, 05:32 PM UTC

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.
identified Feb 03, 2026, 05:51 PM UTC

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.
monitoring Feb 03, 2026, 06:03 PM UTC

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.
resolved Feb 03, 2026, 06:53 PM UTC

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.

Read the full incident report →

Minor January 28, 2026

Kubernetes Clusters and Droplets in FRA1 region

Detected by Pingoru: Jan 28, 2026, 11:27 AM UTC
Resolved: Jan 28, 2026, 05:37 PM UTC
Duration: 6h 10m

Affected: FRA1FRA1

Timeline · 4 updates

investigating Jan 28, 2026, 11:27 AM UTC

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.
identified Jan 28, 2026, 01:30 PM UTC

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.
monitoring Jan 28, 2026, 02:47 PM UTC

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.
resolved Jan 28, 2026, 05:37 PM UTC

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.

Read the full incident report →

Minor January 28, 2026

Droplet Based Events in FRA1

Detected by Pingoru: Jan 28, 2026, 12:45 AM UTC
Resolved: Jan 28, 2026, 04:27 AM UTC
Duration: 3h 41m

Affected: FRA1FRA1FRA1FRA1

Timeline · 3 updates

investigating Jan 28, 2026, 12:45 AM UTC

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.
monitoring Jan 28, 2026, 04:11 AM UTC

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.
resolved Jan 28, 2026, 04:27 AM UTC

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.

Read the full incident report →

Minor January 15, 2026

Account access and Payment

Detected by Pingoru: Jan 15, 2026, 07:16 AM UTC
Resolved: Jan 15, 2026, 09:18 AM UTC
Duration: 2h 2m

Affected: GlobalBillingCloud Control Panel

Timeline · 2 updates

investigating Jan 15, 2026, 07:16 AM UTC

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.
resolved Jan 15, 2026, 09:18 AM UTC

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.

Read the full incident report →

Minor December 18, 2025

App Platform Static Websites in NYC3 Region

Detected by Pingoru: Dec 18, 2025, 07:25 PM UTC
Resolved: Dec 18, 2025, 10:34 PM UTC
Duration: 3h 9m

Affected: New York

Timeline · 3 updates

investigating Dec 18, 2025, 07:25 PM UTC

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.
investigating Dec 18, 2025, 10:06 PM UTC

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.
resolved Dec 18, 2025, 10:34 PM UTC

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.

Read the full incident report →

Minor December 18, 2025

API and Cloud Requests

Detected by Pingoru: Dec 18, 2025, 06:46 PM UTC
Resolved: Dec 18, 2025, 09:34 PM UTC
Duration: 2h 47m

Affected: APICloud Control Panel

Timeline · 2 updates

investigating Dec 18, 2025, 06:46 PM UTC

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.
resolved Dec 18, 2025, 09:34 PM UTC

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.

Read the full incident report →

Notice December 15, 2025

Spaces Access Keys and DigitalOcean Container Registry

Detected by Pingoru: Dec 15, 2025, 04:19 PM UTC
Resolved: Dec 15, 2025, 04:19 PM UTC
Duration: —

Affected: AMS3AMS3

Timeline · 1 update

resolved Dec 15, 2025, 04:19 PM UTC

From 08:28 to 13:03 UTC, Our Engineering team observed an issue with Spaces Access keys for DOCR in AMS3 region. During this time, users encountered an error with "403 (InvalidAccessKeyId): The access key ID you provided does not exist in our records" while accessing spaces keys. Our team has fully resolved the issues as of 13:03 UTC. 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.

Read the full incident report →

Minor December 10, 2025

Recovery Console Accessibility

Detected by Pingoru: Dec 10, 2025, 08:33 PM UTC
Resolved: Dec 11, 2025, 12:00 AM UTC
Duration: 3h 26m

Affected: Global

Timeline · 3 updates

investigating Dec 10, 2025, 08:33 PM UTC

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.
monitoring Dec 10, 2025, 10:43 PM UTC

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.
resolved Dec 11, 2025, 12:00 AM UTC

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.

Read the full incident report →

Minor December 10, 2025

App Platform Static Websites

Detected by Pingoru: Dec 10, 2025, 06:08 PM UTC
Resolved: Dec 10, 2025, 07:08 PM UTC
Duration: 1h

Affected: Global

Timeline · 3 updates

investigating Dec 10, 2025, 06:08 PM UTC

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.
monitoring Dec 10, 2025, 06:41 PM UTC

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.
resolved Dec 10, 2025, 07:08 PM UTC

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.

Read the full incident report →

Minor December 9, 2025

DOCR Access Errors for New App Creation

Detected by Pingoru: Dec 09, 2025, 08:41 PM UTC
Resolved: Dec 09, 2025, 10:08 PM UTC
Duration: 1h 27m

Affected: BLR1

Timeline · 3 updates

investigating Dec 09, 2025, 08:41 PM UTC

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.
monitoring Dec 09, 2025, 09:31 PM UTC

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.
resolved Dec 09, 2025, 10:08 PM UTC

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.

Read the full incident report →