DigitalOcean Outage History

Started Jul 09, 2026, 08:31 PM UTC· resolved Jul 11, 2026, 01:27 AM UTC

1. investigating Jul 09, 2026, 08:31 PM UTC

   Our Engineering team is investigating an issue affecting Kubernetes deployments in NYC1. Users may see intermittent DNS failures and NodeNotReady events from application workloads during this time. We apologize for the inconvenience, we'll share new information on this page as soon as it is available.

2. monitoring Jul 10, 2026, 01:18 AM UTC

   The issue affecting Kubernetes deployments in NYC1 has subsided. Workloads should now be functioning normally. Our Engineering team is continuing to monitor the affected systems to confirm full resolution. We'll update this page if any further action is needed. We apologize for the inconvenience this may have caused.

3. resolved Jul 11, 2026, 01:27 AM UTC

   The issue affecting Kubernetes deployments in the NYC1 region has been resolved. Our investigation found intermittent DNS timeouts affecting a small number of DOKS clusters, with affected worker nodes running on shared-CPU Droplets. This is a documented limitation for latency-sensitive cluster DNS workloads such as CoreDNS. The affected clusters are currently functional. To reduce the risk of recurrence, we recommend running CoreDNS on non-shared/dedicated CPU node pools and using sufficient CoreDNS replicas. If you continue to see DNS failures or NodeNotReady events, please open a support ticket so we can investigate that cluster specifically.

Read the full incident report →

Started Jul 04, 2026, 10:13 PM UTC· resolved Jul 05, 2026, 12:53 AM UTC

1. investigating Jul 04, 2026, 10:13 PM UTC

   Our Engineering team is investigating reports of an incident affecting the Deepseek V4 Pro model in Serverless Inference and Agent Platform. Users may experience errors when attempting to use this model, specifically receiving error 429 messages. We apologize for the inconvenience and are working to resolve the issue as soon as possible. We will provide an update once we have more information.

2. monitoring Jul 04, 2026, 11:18 PM UTC

   Our Engineering team has implemented a fix for the issue with the Deepseek V4 Pro model in Serverless Inference and Agent Platform. The model should now be operational, and users should no longer receive error 429 messages when attempting to use it. We are currently monitoring the situation to ensure the fix is successful and the model is functioning as expected. We will post an update if any further issues arise. If you continue to experience problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.

3. resolved Jul 05, 2026, 12:53 AM UTC

   Our Engineering team has confirmed that the issue with the Deepseek V4 Pro model in Serverless Inference and Agent Platform has been fully resolved. The model is now operational, and users should be able to use it without experiencing any errors. 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.

Read the full incident report →

Started Jul 04, 2026, 02:42 PM UTC· resolved Jul 04, 2026, 03:10 PM UTC

1. monitoring Jul 04, 2026, 02:42 PM UTC

   Our Engineering team has implemented a fix to address the issue affecting Droplets in the NYC3 region. The issue, which began at 12:38 UTC, caused disruptions to customers attempting to perform actions on their Droplets in the NYC3 region. During this time, customers may also have experienced errors when trying to create Droplets in this region. We are actively monitoring the situation to ensure the fix remains effective and will provide another update once the issue has been fully resolved.

2. resolved Jul 04, 2026, 03:10 PM UTC

   Our Engineering team has confirmed that the issue impacting Droplets in the NYC3 region has been fully resolved. Users can now perform actions on their Droplets or create new Droplets in this region without any issues. We appreciate your patience while we worked to resolve this issue. If you continue to experience any problems, please open a support ticket from your account so our team can investigate further.

Read the full incident report →

Started Jul 02, 2026, 10:04 PM UTC· resolved Jul 03, 2026, 08:20 AM UTC

1. investigating Jul 02, 2026, 10:04 PM UTC

   Our engineering team is investigating an issue affecting Managed Database Clusters. Currently, users may encounter delays when creating/scaling/forking and restoring Standard MySQL, Standard PostgreSQL, OpenSearch, Kafka, and Valkey clusters through the Cloud Control Panel or API. We apologize for the inconvenience and will provide further updates as soon as more information is available.

2. investigating Jul 03, 2026, 02:28 AM UTC

   Our engineering team is still investigating the issue affecting Managed Database Clusters. Users may still encounter delays creating/scaling/forking/restoring the aforementioned Managed Database Clusters. We are working to resolve this as soon as possible. we apologize for the inconvenience. We will post an update here once we have more information.

3. monitoring Jul 03, 2026, 06:08 AM UTC

   Our engineering team has implemented a fix to resolve the issue with Managed Database Clusters and is monitoring the situation. We will post an update as soon as the issue is fully resolved.

4. resolved Jul 03, 2026, 08:20 AM UTC

   Our engineering team has resolved the issue with Managed Database Clusters. All database systems 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 →

Started Jul 01, 2026, 11:35 AM UTC· resolved Jul 01, 2026, 04:28 PM UTC

1. investigating Jul 01, 2026, 11:35 AM UTC

   As of 06:39 UTC, our Engineering team is investigating reports of intermittent DNS lookup failures for Managed Database hostnames from Managed Kubernetes, primarily affecting connections from Managed Kubernetes to Managed Database hostnames. At this point, customers in the FRA1 region may experience intermittent connectivity issues. We apologize for the inconvenience and will share an update once we have more information.

2. investigating Jul 01, 2026, 12:15 PM UTC

   We are continuing to investigate this issue.

3. resolved Jul 01, 2026, 04:28 PM UTC

   The intermittent DNS lookup failures between Managed Kubernetes and Managed Database hostnames in the FRA1 region have been resolved for now but please let us know if you see the issue again. Connectivity has remained stable, and all systems are operating normally. If you continue to experience any problems, please open a ticket with our support team. Thank you for your patience, and we apologize for any inconvenience.

Read the full incident report →

Started Jul 01, 2026, 11:13 AM UTC· resolved Jul 01, 2026, 01:28 PM UTC

1. investigating Jul 01, 2026, 11:13 AM UTC

   Our Engineering team is investigating an issue affecting Droplet resizes using the "Downscale Anytime" option. At this time users may find this option unavailable or unresponsive in the Cloud Control Panel. As a workaround, resizes can be performed via the API while we work to resolve this issue. We apologize for the inconvenience and will share an update once we have more information.

2. monitoring Jul 01, 2026, 12:43 PM UTC

   Our Engineering team has identified the root cause of the issue affecting Droplet resizes using the "Downscale Anytime" option and has implemented a fix. Users should now be able to resize their Droplets using the "Downscale Anytime" option without experiencing any issues or errors. We are actively monitoring the situation to ensure the fix remains effective and will provide another update once the issue has been fully resolved.

3. resolved Jul 01, 2026, 01:28 PM UTC

   Our Engineering team has confirmed that the issue impacting Droplet resizes using the "Downscale Anytime" option has been fully resolved. Users can now resize their Droplets using the "Downscale Anytime" option without any issues. We appreciate your patience while we worked to resolve this issue. If you continue to experience any problems, please open a support ticket from your account so our team can investigate further.

Read the full incident report →

Started Jul 01, 2026, 06:25 AM UTC· resolved Jul 02, 2026, 03:38 AM UTC

1. investigating Jul 01, 2026, 06:25 AM UTC

   Our Engineering team is currently investigating an issue where Agents are experiencing timeouts while retrieving data from Knowledge Bases. As a result, affected Agents may fail to retrieve data and return the following error: "Failed to retrieve data from Knowledge base(s) - timeout" Please be assured that we are treating this as a high-priority issue and are actively working to mitigate it. We sincerely apologise for any inconvenience this may have caused and appreciate your patience and understanding. If you have any further questions, please create a support ticket so that we can investigate your specific case further.

2. identified Jul 01, 2026, 08:39 AM UTC

   Our Engineering team has identified the issue causing Agents to experience timeouts while retrieving data from Knowledge Bases. Please be assured that our Engineering team is actively working on a fix and is treating this issue with high priority. We sincerely apologise for any inconvenience this may have caused and appreciate your patience and understanding. If you have any further questions, please create a support ticket so that we can investigate your specific case further.

3. resolved Jul 02, 2026, 03:38 AM UTC

   This incident has been resolved, and our teams continue to monitor the results. If you experience any further issues, please contact support.

Read the full incident report →

Started Jun 27, 2026, 06:24 PM UTC· resolved Jun 27, 2026, 06:24 PM UTC

1. resolved Jun 27, 2026, 06:24 PM UTC

   Between 00:00 UTC & 16:00 UTC today, our Engineering team identified an issue affecting backup operations on Droplets. During this period, backups scheduled within this window may not have been created and may appear as missing. Our team has taken necessary measures to resolve the issue, and we can confirm that the backup service has been restored and is now functioning normally. Upcoming scheduled backups should be performed as expected. We sincerely apologize for any inconvenience this may have caused and appreciate your understanding. However, if you have any further questions or concerns, please create a support ticket for further analysis.

Read the full incident report →

Started Jun 27, 2026, 04:43 AM UTC· resolved Jun 27, 2026, 05:15 AM UTC

1. monitoring Jun 27, 2026, 04:43 AM UTC

   Our Engineering team has mitigated an issue with Anthropic models. Previously, users may have encountered 400 errors when attempting to use any Anthropic model. Although the root cause of the issue is still being addressed by Anthropic, users should now be able to access and use Anthropic models again. We will continue to monitor the situation and provide updates if necessary. If you continue to experience problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.

2. resolved Jun 27, 2026, 05:15 AM UTC

   Our Engineering team has resolved the issue that was causing HTTP 400 errors for requests to Anthropic models. Users should now be able to access Anthropic models without any issues. If you continue to experience problems, please open a ticket with our Support team so we can investigate further. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Jun 19, 2026, 02:00 PM UTC· resolved Jun 19, 2026, 04:37 PM UTC

1. investigating Jun 19, 2026, 02:00 PM UTC

   Our Engineering team is currently investigating an issue affecting the visibility of monitoring graphs within the Cloud Panel. During this period, users may notice missing or unavailable monitoring graphs for services such as Droplets(with DO agent installed), Load Balancers, Databases, etc. We apologize for the inconvenience caused. We'll update once we have more information

2. monitoring Jun 19, 2026, 02:50 PM UTC

   Our engineering team has implemented the necessary fixes to address the issue affecting the visibility of monitoring graphs within the Cloud Panel. Users should now be able to view monitoring graphs for their services, including Droplets with DO Agent installed, Load Balancers, Databases, etc. We are currently monitoring the situation to ensure that the service has returned to normal operation and remain stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.

3. resolved Jun 19, 2026, 04:37 PM UTC

   Between 13:22 & 14:26 UTC today, users have experienced missing monitoring graphs for Droplets (with DO agent installed), Load Balancers, Databases, and other services within the Cloud Control Panel. Our engineering team has identified the root cause of the issue and has taken appropriate steps to restore functionality. We can confirm that services have been restored and are functioning as expected. We apologize for any inconvenience this may have caused. If you continue to experience issues viewing monitoring graphs, please create a support ticket for further analysis. Thank you for your patience and understanding

Read the full incident report →

Started Jun 16, 2026, 10:00 PM UTC· resolved Jun 17, 2026, 12:29 AM UTC

1. investigating Jun 16, 2026, 10:52 PM UTC

   We are actively investigating an issue causing elevated HTTP 500 error rates for customers utilizing our Serverless/GenAI Inference API. Customer Impact: Customers making calls to the inference API—specifically targeting /v1/* endpoints—will experience intermittent HTTP 500 errors and failed requests.

2. monitoring Jun 16, 2026, 11:29 PM UTC

   Our engineering teams have successfully begun implementing mitigation steps to resolve the connectivity issues affecting the inference API. We will provide another update once the API has fully recovered and error rates return to normal.

3. resolved Jun 17, 2026, 12:29 AM UTC

   The connectivity issues affecting our Serverless/GenAI Inference API have been fully resolved. Our engineering teams successfully completed the connectivity restoration. All systems should be functioning normally, and the endpoint should be fully operational.

Read the full incident report →

Started Jun 11, 2026, 02:24 PM UTC· resolved Jun 11, 2026, 05:42 PM UTC

1. investigating Jun 11, 2026, 02:24 PM UTC

   We are currently facing issues with Gradient AI DeepSeek V4 Pro is returning HTTP 429 "Rate limit exceeded"

2. investigating Jun 11, 2026, 02:30 PM UTC

   We are continuing to investigate this issue.

3. identified Jun 11, 2026, 02:31 PM UTC

   The issue has been identified and a fix is being implemented.

4. resolved Jun 11, 2026, 05:42 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 04, 2026, 10:12 AM UTC· resolved Jun 04, 2026, 11:47 AM UTC

1. investigating Jun 04, 2026, 10:12 AM UTC

   Our Engineering team is investigating an issue impacting our DNS API service. During this time, users may experience issues performing domain and DNS record management operations from the Control Panel and API, including creating, updating, or deleting DNS records. As a result, services that rely on DNS API operations, such as Let's Encrypt certificate provisioning and MongoDB cluster creation, may also be impacted. We apologize for the inconvenience and will share an update once we have more information.

2. investigating Jun 04, 2026, 10:59 AM UTC

   Our Engineering team continues to investigate an issue impacting our DNS API service. During this time, users may experience issues performing domain and DNS record management operations from the Control Panel and API, including creating, updating, or deleting DNS records. As a result, services that depend on DNS API operations, including Let's Encrypt certificate provisioning, MongoDB cluster creation, App Platform deployments, and DigitalOcean Kubernetes (DOKS) cluster create and delete operations, may also be impacted. We apologize for the inconvenience and will share more information as it becomes available.

3. identified Jun 04, 2026, 11:32 AM UTC

   Our Engineering team has identified the cause of the issue impacting our DNS API service and is actively working on a fix. During this time, users may experience errors when attempting to create, update, or delete domains and DNS records through the Control Panel and API. As a result, services that depend on DNS API operations, including Let's Encrypt certificate provisioning, MongoDB cluster creation, App Platform deployments, and DigitalOcean Kubernetes (DOKS) cluster create and delete operations, may also be impacted. We will post an update as soon as additional information is available.

4. monitoring Jun 04, 2026, 11:39 AM UTC

   Our Engineering team has implemented a fix to resolve the issue impacting our DNS API service. Users should now be able to perform domain and DNS record management operations successfully through the Control Panel and API. Additionally, services affected by this issue, including Let's Encrypt certificate provisioning, MongoDB cluster creation, App Platform deployments, and DigitalOcean Kubernetes (DOKS) cluster create and delete operations, should now be functioning as expected. We are monitoring the situation closely and will share an update once the issue is resolved completely.

5. resolved Jun 04, 2026, 11:47 AM UTC

   Between 09:41 and 11:24 UTC, our Engineering team identified an issue impacting the DNS API service. During this period, users may have experienced issues performing domain and DNS record management operations through the Control Panel and API. Services dependent on DNS API operations, including Let's Encrypt certificate provisioning, MongoDB cluster creation, App Platform deployments, and DigitalOcean Kubernetes (DOKS) cluster create and delete operations, were also impacted. Our Engineering team has confirmed that the underlying issue affecting the DNS API service has been fully resolved, and all affected services are now operating normally. If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.

Read the full incident report →

Started May 20, 2026, 12:08 PM UTC· resolved May 20, 2026, 01:03 PM UTC

1. identified May 20, 2026, 12:08 PM UTC

   Our engineering team identified an issue impacting Cloud Firewall Product. During this time, users may notice HTTP 500 errors when updating firewalls. We apologize for the inconvenience and will share an update once more information is available.

2. monitoring May 20, 2026, 12:43 PM UTC

   Our engineering team has implemented a fix that affected the Cloud Firewall rules. Users should now be able to update their firewalls successfully. We are actively monitoring the situation to ensure overall stability. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.

3. resolved May 20, 2026, 01:03 PM UTC

   Between 06:35 UTC & 12:36 UTC today, our engineering team identified an issue impacting the Cloud Firewall. During this period, users might have encountered issues while updating their firewall rules. Our team has taken appropriate measures to address the issue. We can confirm that service has been restored and is now functioning normally. We regret the inconvenience caused and appreciate your patience and understanding. However, if you continue to experience any issues, please create a support ticket for further analysis.

Read the full incident report →

Started May 20, 2026, 01:05 AM UTC· resolved May 20, 2026, 05:13 AM UTC

1. investigating May 20, 2026, 01:05 AM UTC

   Our Engineering team is currently investigating an ongoing infrastructure issue in the NYC3 region affecting Block Storage Volumes at the storage layer. Users may experience degraded write performance and intermittent impact to services dependent on the affected storage infrastructure. We apologize for the inconvenience and will continue to provide updates as more information becomes available.

2. monitoring May 20, 2026, 02:19 AM UTC

   Our Engineering team has implemented mitigation measures for the infrastructure issue affecting Block Storage Volumes in the NYC3 region. The team is monitoring the situation, and we will share another update once the issue is fully resolved

3. resolved May 20, 2026, 05:13 AM UTC

   From 00:00 UTC to 05:15 UTC, users may have experienced degraded write performance and intermittent impacts to workloads dependent on Block Storage Volumes in the NYC3 region. Our Engineering team has confirmed that the underlying infrastructure issue affecting Block Storage Volumes at the storage layer has been fully resolved, and services are now operating normally. If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.

Read the full incident report →

Started May 15, 2026, 01:21 AM UTC· resolved May 15, 2026, 02:00 AM UTC

1. monitoring May 15, 2026, 01:21 AM UTC

   As of the current time, our Engineering team is aware of an ongoing incident with our provider, Anthropic, that is impacting Serverless Inference. The outage is affecting all users attempting to use Sonnet 4.6 and Opus 4.7 models. According to Anthropic's status page (https://status.claude.com/incidents/8z7l5zcy0v3b), they are currently experiencing an outage that is causing this disruption. We apologize for the inconvenience and will provide updates as more information becomes available.

2. identified May 15, 2026, 01:23 AM UTC

   According to Anthropic's status page (https://status.claude.com/incidents/8z7l5zcy0v3b), they have identified the root cause and are actively working on a fix. At this time, users may continue to experience errors when attempting to use Sonnet 4.6 and Opus 4.7 models. We will provide another update once Anthropic has implemented a fix and service is restored.

3. resolved May 15, 2026, 02:00 AM UTC

   As of the current time, our Engineering team has confirmed that the issue with Serverless Inference has been resolved. The root cause of the issue was an outage with our provider, Anthropic, which affected users of Sonnet 4.6 and Opus 4.7 models. According to Anthropic's status page (https://status.claude.com/incidents/8z7l5zcy0v3b), they have resolved the outage. If you continue to experience problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started May 14, 2026, 01:57 PM UTC· resolved May 14, 2026, 08:46 PM UTC

1. investigating May 14, 2026, 01:57 PM UTC

   Our Engineering team is investigating an issue affecting our DNS service. At this time, DNS resolution remains functional but any changes to DNS records are not being reflected at the edge. Additionally, customers may be unable to create new Let's Encrypt certificates at this time. Our engineering team is actively working to identify the root cause and restore full functionality. We apologize for any inconvenience, and we'll share more information as it becomes available.

2. investigating May 14, 2026, 03:52 PM UTC

   Our engineering team continues to investigate an issue affecting our DNS service. At this time, DNS resolution remains functional; however, new changes to DNS records are currently not being reflected at the edge. This issue is also impacting related services. Specifically, customers may be unable to create new Let's Encrypt certificates. Regarding Managed MongoDB, customers will be able to submit requests to create new clusters or scale existing ones, but the completion of the provisioning process is currently delayed. This is due to the dependency on Let's Encrypt certificate issuance, which requires functional DNS propagation. Affected clusters will automatically recover and complete their provisioning once the DNS issue is resolved. Our engineering team is actively working to restore full functionality across all affected services. We apologize for the inconvenience and will share more information as it becomes available.

3. monitoring May 14, 2026, 04:42 PM UTC

   Our Engineering team has implemented a fix for the issue affecting our DNS service and are now seeing DNS record updates successfully propagate to the edge. As a result, Let's Encrypt certificate issuance and Managed MongoDB provisioning (including scaling operations) should resume. We are currently monitoring the systems as they process the backlog of delayed requests. Affected MongoDB clusters and certificate requests should complete their provisioning automatically. We will continue to monitor the situation closely to ensure full stability. We appreciate your patience throughout this process and will provide an update once the issue is fully confirmed as resolved.

4. resolved May 14, 2026, 08:46 PM UTC

   As of 19:50 UTC, the issue affecting the DNS service has been fully resolved, and all related services, including Let's Encrypt certificate issuance and Managed MongoDB provisioning, are now operating normally. The backlog of delayed requests has been successfully processed, and all DNS record updates, pending certificate, and MongoDB operations should now be complete. We apologize for the disruption this caused and appreciate your patience while our team worked to restore full functionality. 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 →

Started May 12, 2026, 10:50 AM UTC· resolved May 12, 2026, 11:37 AM UTC

1. investigating May 12, 2026, 10:24 AM UTC

   We are currently investigating an issue affecting the GradientAI Agent Platform Playground. Users may see a “Something went wrong” error for all agent interactions in the Playground. Agent functionality through API endpoints remains unaffected. We are actively working to identify the cause and will provide an update as soon as more information is available.

2. identified May 12, 2026, 10:50 AM UTC

   The issue affecting the GradientAI Agent Platform Playground has been identified by our engineering team. A fix is being implemented to resolve this issue.

3. identified May 12, 2026, 11:14 AM UTC

   A fix has been deployed for the issue affecting the GradientAI Agent Platform Playground, and the service is now operating normally. We are monitoring to ensure stability.

4. monitoring May 12, 2026, 11:36 AM UTC

   A fix has been deployed for the issue affecting the GradientAI Agent Platform Playground, and the service is now operating normally. We are monitoring to ensure stability.

5. resolved May 12, 2026, 11:37 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 09, 2026, 11:15 AM UTC· resolved May 09, 2026, 02:42 PM UTC

1. investigating May 09, 2026, 11:15 AM UTC

   Our Engineering team is investigating an issue affecting the ability to enable Two-Factor Authentication (2FA) and Google/GitHub authentication through the Control Panel. During this time, users may encounter errors while enabling these authentication methods and could also experience issues accessing teams with secure sign-in enabled. We apologize for the inconvenience and will provide an update as soon as more information becomes available.

2. monitoring May 09, 2026, 01:51 PM UTC

   Our Engineering team has implemented necessary changes to address the issue affecting the ability to enable Two-Factor Authentication (2FA) and Google/GitHub authentication through the Control Panel. Our team is currently monitoring the situation to ensure stability. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.

3. resolved May 09, 2026, 02:42 PM UTC

   Between 5:35 and 14:25 UTC today, our Engineering team identified an issue that prevents enabling Two-Factor Authentication (2FA) and Google/GitHub authentication through the Control Panel. During this period, users might have encountered issues while enabling authentication methods and accessing teams with secure sign-in enabled. Our team has taken appropriate measures to address the issue. We can confirm that service has been restored and is now functioning normally. We regret the inconvenience caused. However, if you continue to experience any issues, please create a support ticket for further analysis.

Read the full incident report →

Started May 08, 2026, 08:46 PM UTC· resolved May 08, 2026, 09:54 PM UTC

1. identified May 08, 2026, 08:46 PM UTC

   Our Engineering team is aware of an upstream outage with Let's Encrypt (see https://letsencrypt.status.io/) which impacts the following services: - Inability to create new Let's Encrypt certificates for Spaces, Load Balancers, and App Platform Custom Domains - Stuck or delayed creates/forks/restores on Mongo, PG, and MySQL databases. Please note that operations related to Managed Databases and App Platform Custom Domains will automatically retry and should complete successfully once the upstream outage is resolved. We'll continue to monitor this situation and provide updates. We apologize for the inconvenience.

2. resolved May 08, 2026, 09:54 PM UTC

   The upstream outage with Let's Encrypt has been resolved. Customers should now be able to issue Let's Encrypt certificates for Spaces, Load Balancers, and App Platform Custom Domains. Our Engineering team has also confirmed that stuck or delayed actions with Mongo, Advanced PG, and Advanced MySQL databases should complete normally now. We appreciate your patience. If you continue to experience any issues, please open a support ticket from within your account.

Read the full incident report →

Started May 08, 2026, 06:01 PM UTC· resolved May 08, 2026, 07:59 PM UTC

1. investigating May 08, 2026, 06:01 PM UTC

   We are currently investigating an issue affecting multiple services in our NYC2 region. Our engineering team is aware of the situation and is working to identify the root cause and restore full connectivity as quickly as possible. Users with resources in the NYC2 region may experience issues with Droplet connectivity, API requests, or other services. We will provide additional updates as more information becomes available. We apologize for any inconvenience this may cause.

2. monitoring May 08, 2026, 07:21 PM UTC

   Our Engineering team has identified the issue and implemented a fix to resolve the issues with multiple services, and is monitoring the situation. We will post an update as soon as the issue is fully resolved.

3. monitoring May 08, 2026, 07:53 PM UTC

   We are continuing to monitor for any further issues.

4. resolved May 08, 2026, 07:59 PM UTC

   Our engineering team has resolved the issue with multiple services in NYC2 region, and all 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 and thank you for your patience.

Read the full incident report →

Started Apr 28, 2026, 01:45 PM UTC· resolved Apr 28, 2026, 07:33 PM UTC

1. investigating Apr 28, 2026, 01:45 PM UTC

   Serverless inference customers are experiencing elevated 5xx errors, including “context canceled” responses. This may result in intermittent request failures. Our team is actively investigating and will provide updates as more information becomes available.

2. identified Apr 28, 2026, 03:59 PM UTC

   We have identified an issue affecting our service and are currently working to implement a fix. Our team is actively investigating and taking the necessary steps to restore normal operations as quickly as possible. We appreciate your patience and will provide updates as soon as more information becomes available.

3. monitoring Apr 28, 2026, 07:00 PM UTC

   Service for Serverless Inference has been restored. We’ve implemented tighter rate limits to help prevent recurrence and are closely monitoring system performance. Some users may still experience intermittent latency as we complete final stabilization efforts. Our team remains actively engaged to ensure full recovery. We appreciate your patience and will provide further updates as needed.

4. resolved Apr 28, 2026, 07:33 PM UTC

   All services are operating normally. We will continue to monitor the system to ensure ongoing reliability. Thank you for your patience while we worked to resolve this issue.

Read the full incident report →

Started Apr 27, 2026, 10:38 AM UTC· resolved Apr 27, 2026, 11:37 AM UTC

1. investigating Apr 27, 2026, 10:38 AM UTC

   We are currently investigating an issue impacting DigitalOcean Serverless Inference for all Anthropic models. Customers may experience an elevated rate of failed requests, including HTTP 429 responses. Our engineering team is actively working to identify the cause and mitigate the impact. We apologize for the inconvenience and will share another update as soon as more information is available.

2. monitoring Apr 27, 2026, 11:07 AM UTC

   We identified the cause of intermittent HTTP 429 responses affecting some customers using Anthropic models on DigitalOcean Serverless Inference and applied a mitigation. Service has recovered, and we are monitoring stability.

3. resolved Apr 27, 2026, 11:37 AM UTC

   The issue is resolved, and service is operating normally.

Read the full incident report →

Started Apr 23, 2026, 10:26 PM UTC· resolved Apr 23, 2026, 11:51 PM UTC

1. investigating Apr 23, 2026, 10:26 PM UTC

   As of 21:53 UTC, our Engineering team is investigating reports of increased internal errors for hosted models in the ATL1 region, impacting Serverless Inference. At this point, users with models hosted in ATL1 may experience intermittent errors when using Serverless Inference. We apologize for the inconvenience and will share an update once we have more information.

2. resolved Apr 23, 2026, 11:51 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 23, 2026, 07:01 AM UTC· resolved Apr 23, 2026, 08:46 AM UTC

1. investigating Apr 23, 2026, 07:01 AM UTC

   Our Engineering team is currently investigating an issue impacting Managed Kubernetes UI across all regions. During this time, some users may experience the Kubernetes UI page not loading in DigitalOcean Onboarding. We apologize for the inconvenience and will share more information as soon as it's available.

2. investigating Apr 23, 2026, 07:14 AM UTC

   Our Engineering team is currently investigating an issue impacting the Create Managed Kubernetes UI across all regions. During this time, users with a Member role may experience the Kubernetes UI page not loading in the cloud console. As a workaround, the DigitalOcean API and doctl (CLI) continue to function normally, and you can use them to manage your Kubernetes resources in the meantime. We apologize for the inconvenience and will share more information as soon as it becomes available.

3. investigating Apr 23, 2026, 07:52 AM UTC

   Our Engineering team is currently investigating an issue impacting the Managed Kubernetes UI across all regions. During this time, users with a Member role may experience the Kubernetes UI page not loading in the cloud console. As a workaround, the DigitalOcean API and doctl (CLI) continue to function normally, and you can use them to manage your Kubernetes resources in the meantime. We apologize for the inconvenience and will share more information as soon as it becomes available

4. resolved Apr 23, 2026, 08:46 AM UTC

   Our Engineering team has confirmed full resolution of the issue with Cloud UI for Managed Kubernetes at 09:19 UTC. All the services should be functioning as expected. If you continue to experience problems, please open a ticket with our support team. Thank you for your patience throughout this incident!

Read the full incident report →