DigitalOcean Outage History

DigitalOcean is up right now

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

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

Source: https://status.digitalocean.com

Notice June 16, 2026

Intermittent 500 Errors on Serverless/GenAI Inference API

Detected by Pingoru
Jun 16, 2026, 10:00 PM UTC
Resolved
Jun 17, 2026, 12:29 AM UTC
Duration
2h 28m
Affected: Inference
Timeline · 3 updates
  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 →

Major June 11, 2026

DeepSeek V4 Pro is returning HTTP 429 "Rate limit exceeded"

Detected by Pingoru
Jun 11, 2026, 02:24 PM UTC
Resolved
Jun 11, 2026, 05:42 PM UTC
Duration
3h 17m
Affected: Model Services
Timeline · 4 updates
  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 →

Minor May 29, 2026

App Platform Deployments

Detected by Pingoru
May 29, 2026, 12:14 AM UTC
Resolved
May 29, 2026, 07:58 AM UTC
Duration
7h 44m
Affected: Global
Timeline · 3 updates
  1. investigating May 29, 2026, 12:14 AM UTC

    Our Engineering team is currently investigating an issue with build failures on App Platform in multiple regions. Users may experience errors when attempting to build their applications, resulting in failed deployments. Our Engineering team is working to fix the issue and will share an update once we have more details. We apologize for the inconvenience this issue may be causing and appreciate your patience as we work to resolve it.

  2. monitoring May 29, 2026, 01:58 AM UTC

    Our Engineering team has implemented a fix to resolve the issue with build failures on App Platform. Users should see their builds deploy successfully now. We are closely monitoring the situation, and will post an update once we've confirmed this is fully resolved.

  3. resolved May 29, 2026, 07:58 AM UTC

    Our Engineering team has confirmed that the issue impacting build failures on App Platform has been resolved at 07:00 am UTC. All App Platform builds are now succeeding as expected. Customers who previously encountered build failures should now be able to deploy their applications without further issues. 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 →

Minor May 20, 2026

Cloud Firewall

Detected by Pingoru
May 20, 2026, 12:08 PM UTC
Resolved
May 20, 2026, 01:03 PM UTC
Duration
54m
Affected: Cloud Firewall
Timeline · 3 updates
  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 →

Minor May 20, 2026

Block Storage Volume Performance

Detected by Pingoru
May 20, 2026, 01:05 AM UTC
Resolved
May 20, 2026, 05:13 AM UTC
Duration
4h 8m
Affected: NYC3
Timeline · 3 updates
  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 →

Major May 15, 2026

Anthropic reported outage that's impacting access to their Serverless Inference models

Detected by Pingoru
May 15, 2026, 01:21 AM UTC
Resolved
May 15, 2026, 02:00 AM UTC
Duration
38m
Affected: Agent Runtime
Timeline · 3 updates
  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 →

Major May 12, 2026

GradientAI: Agent Platform Playground Interaction Errors

Detected by Pingoru
May 12, 2026, 10:50 AM UTC
Resolved
May 12, 2026, 11:37 AM UTC
Duration
47m
Affected: Agent Runtime
Timeline · 5 updates
  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 →

Minor May 9, 2026

Control Panel Errors - Unable to Enable 2FA and Google/GitHub

Detected by Pingoru
May 09, 2026, 11:15 AM UTC
Resolved
May 09, 2026, 02:42 PM UTC
Duration
3h 27m
Affected: Cloud Control Panel
Timeline · 3 updates
  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 →

Minor May 8, 2026

Let's Encrypt Outage Affecting Certificate Issuance and Managed Databases Operations

Detected by Pingoru
May 08, 2026, 08:46 PM UTC
Resolved
May 08, 2026, 09:54 PM UTC
Duration
1h 8m
Affected: GlobalGlobalGlobalGlobalGlobal
Timeline · 2 updates
  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 →

Minor May 8, 2026

Multiple Services in NYC2

Detected by Pingoru
May 08, 2026, 06:01 PM UTC
Resolved
May 08, 2026, 07:59 PM UTC
Duration
1h 58m
Affected: APINew YorkNYC2NYC2NYC2NYC2
Timeline · 4 updates
  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 →

Minor April 28, 2026

Elevated 5xx “context canceled” errors impacting serverless inference

Detected by Pingoru
Apr 28, 2026, 01:45 PM UTC
Resolved
Apr 28, 2026, 07:33 PM UTC
Duration
5h 48m
Affected: Agent Runtime
Timeline · 4 updates
  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 →

Major April 27, 2026

Serverless Inference - Intermittent Rate Limiting Affecting Some Customers Using Anthropic Models

Detected by Pingoru
Apr 27, 2026, 10:38 AM UTC
Resolved
Apr 27, 2026, 11:37 AM UTC
Duration
59m
Affected: Agent Runtime
Timeline · 3 updates
  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 →

Minor April 23, 2026

Intermittent errors impacting some Serverless Inference models in ATL1

Detected by Pingoru
Apr 23, 2026, 10:26 PM UTC
Resolved
Apr 23, 2026, 11:51 PM UTC
Duration
1h 25m
Affected: Agent Runtime
Timeline · 2 updates
  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 →

Minor April 23, 2026

Cloud UI for Managed Kubernetes

Detected by Pingoru
Apr 23, 2026, 07:01 AM UTC
Resolved
Apr 23, 2026, 08:46 AM UTC
Duration
1h 44m
Affected: Global
Timeline · 4 updates
  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 →

Minor April 22, 2026

Cloud Control Panel and API

Detected by Pingoru
Apr 22, 2026, 11:06 AM UTC
Resolved
Apr 22, 2026, 11:47 AM UTC
Duration
40m
Affected: APICloud Control Panel
Timeline · 3 updates
  1. investigating Apr 22, 2026, 11:06 AM UTC

    Our Engineering team is currently investigating an issue affecting the Cloud Control Panel and API. During this time, API requests to create, destroy, or trigger events on droplets may not succeed. Additionally, the Droplets page in the Cloud Control Panel may not load properly, and users could experience issues while reviewing the droplet listing. We are actively looking into the root cause and will provide updates as soon as more information becomes available. We apologize for the inconvenience and appreciate your patience.

  2. monitoring Apr 22, 2026, 11:25 AM UTC

    Our Engineering team has implemented a fix for the issue affecting the DigitalOcean API and the Cloud Control Panel. We are now actively monitoring the system to ensure full stability and will provide a final update once the issue is completely resolved. We sincerely appreciate your patience and understanding as we work to restore normal service.

  3. resolved Apr 22, 2026, 11:47 AM UTC

    Our Engineering team has resolved the issue that was impacting the DigitalOcean API and the Cloud Control Panel. The system is now operating normally. During the incident, users may have experienced difficulties accessing droplets, viewing the Droplets page, or performing CRUD (Create, Read, Update, Delete) operations via the API. We have verified that the issue has been fully resolved. We apologize for the inconvenience this may have caused. If you continue to experience any issues, please submit a support ticket through the Cloud Control Panel so our team can assist you further.

Read the full incident report →

Minor April 17, 2026

DNS Resolution for .co TLD

Detected by Pingoru
Apr 17, 2026, 09:22 PM UTC
Resolved
Apr 18, 2026, 02:10 PM UTC
Duration
16h 47m
Affected: DNS
Timeline · 3 updates
  1. identified Apr 17, 2026, 09:22 PM UTC

    Our Engineering team is aware of a widespread, external issue affecting .co top-level domain (TLD). While this incident originates outside of DigitalOcean's infrastructure, you may experience errors when querying a .co domain, regardless of the DNS resolver being used. Our Engineers are actively deploying temporary backend mitigations to help minimize the impact on our customers. We will continue to monitor the situation closely and post updates as more information becomes available.

  2. monitoring Apr 17, 2026, 10:53 PM UTC

    Our Engineering team has implemented a fix to resolve the issue that was affecting the DNS resolution of .co top-level domain (TLD). During this time, users who are using DigitalOcean DNS resolvers in their resources should no longer experience issues related to the DNS resolution. Our Engineers are currently monitoring the situation. We will post an update as soon as the issue is fully resolved.

  3. resolved Apr 18, 2026, 02:10 PM UTC

    Our Engineering team has confirmed that the issue affecting the DNS resolution of .co top-level domain (TLD) has been resolved. The DNS resolution for .co domains is now working as expected. We apologize for the inconvenience. If you continue to face any issues, please open a support ticket from within your account.

Read the full incident report →

Notice April 17, 2026

Spaces availability in NYC3

Detected by Pingoru
Apr 17, 2026, 06:27 PM UTC
Resolved
Apr 17, 2026, 06:27 PM UTC
Duration
—
Affected: NYC3
Timeline · 1 update
  1. resolved Apr 17, 2026, 06:27 PM UTC

    From 17:22 to 17:46 UTC, our Engineering team observed an issue impacting Spaces availability in the NYC3 region. During this time, customers may have encountered 500 errors and degraded performance while accessing Spaces buckets. The issue has now been fully resolved. 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 April 15, 2026

Serverless Inference

Detected by Pingoru
Apr 15, 2026, 01:07 AM UTC
Resolved
Apr 15, 2026, 02:56 AM UTC
Duration
1h 48m
Affected: Agent Runtime
Timeline · 3 updates
  1. investigating Apr 15, 2026, 01:07 AM UTC

    Our Engineering team is investigating an issue causing elevated error rates due to service instability and terminating open connections which causes some 500s. Some requests may fail while we work to resolve it. We apologize for the inconvenience and will share an update once we have more information.

  2. monitoring Apr 15, 2026, 02:24 AM UTC

    Our Engineering team has implemented a fix for the issue causing elevated error rates due to service instability. We are currently monitoring the situation to ensure stability and confirm that error rates, including HTTP 500 responses, have returned to normal levels. We will provide a further update once we confirm the issue is fully resolved.

  3. resolved Apr 15, 2026, 02:56 AM UTC

    From 23:20 UTC to 02:00 UTC, users may have experienced elevated error rates due to service instability, which resulted in intermittent HTTP 500 errors and terminated connections. Our Engineering team has confirmed full resolution of the issue, and all systems are now operating normally. If you continue to experience any issues, please open a ticket with our support team. We apologize for any inconvenience caused.

Read the full incident report →

Minor April 14, 2026

Managed Database Resizes

Detected by Pingoru
Apr 14, 2026, 12:53 PM UTC
Resolved
Apr 14, 2026, 03:19 PM UTC
Duration
2h 26m
Affected: GlobalGlobal
Timeline · 3 updates
  1. investigating Apr 14, 2026, 12:53 PM UTC

    Our engineering team is investigating an issue impacting resize operations for Managed Databases. During this time, users may experience error when attempting to resize Managed Database via Cloud Control Panel and API in all regions. We apologize for the inconvenience and will share an update once we have more information.

  2. monitoring Apr 14, 2026, 02:30 PM UTC

    Our Engineering team has taken action to mitigate the issue with resize operations for Managed Databases and implemented a fix . We are monitoring the situation and will post an update as soon as we confirm that the issue is fully resolved.

  3. resolved Apr 14, 2026, 03:19 PM UTC

    Our Engineering team has resolved the issue with resize operations for Managed Databases and should now be operating normally. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. We apologize for any inconvenience.

Read the full incident report →

Notice April 10, 2026

Droplet Availability in All Regions

Detected by Pingoru
Apr 10, 2026, 08:32 PM UTC
Resolved
Apr 10, 2026, 09:06 PM UTC
Duration
33m
Affected: APIGlobalGlobalCloud Control Panel
Timeline · 2 updates
  1. monitoring Apr 10, 2026, 08:32 PM UTC

    Subject: Droplet Availability in All Regions Our Engineering team has identifed an issue with Droplet creates in all regions. A root cause has been found, a fix has been put in place and we are currently monitoring the situation to ensure full resolution. Users should be able to create new Droplets at this time. We will continue to monitor and we will post an update as soon as it is fully resolved. We apologize for the inconvenience.

  2. resolved Apr 10, 2026, 09:06 PM UTC

    Our Engineering team has confirmed full resolution of the issue with creating Droplets in all regions. Users should be able to create Droplets without issue. We apologize for the inconvenience. If you continue to face any issues, please open a support ticket from within your account.

Read the full incident report →

Notice April 7, 2026

Control Plane

Detected by Pingoru
Apr 07, 2026, 05:49 PM UTC
Resolved
Apr 07, 2026, 05:49 PM UTC
Duration
—
Affected: APICloud Control Panel
Timeline · 1 update
  1. resolved Apr 07, 2026, 05:49 PM UTC

    Our Engineering team has resolved the control plane disruption that occurred from 17:06 to 17:18 UTC. During this time, users may have experienced intermittent issues with managing their resources through the Cloud Control Panel or DigitalOcean API. The root cause of the disruption was identified and addressed, and all services are now operating normally. If you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.

Read the full incident report →

Minor April 7, 2026

Serverless Inference - High error rates for open source models ( Qwen 3 32B)

Detected by Pingoru
Apr 07, 2026, 12:49 PM UTC
Resolved
Apr 07, 2026, 03:50 PM UTC
Duration
3h 1m
Affected: Agent Runtime
Timeline · 3 updates
  1. investigating Apr 07, 2026, 12:49 PM UTC

    Serverless inference for alibaba-qwen3-32b (Qwen 3 32B) in tor1 is experiencing high error rates starting at 10:46 UTC.

  2. identified Apr 07, 2026, 12:55 PM UTC

    We are currently investigating reports of elevated latency affecting requests to this model when using Serverless Inference and Agents. Earlier observations indicated increased error rates for the open-source Qwen 3 32B model. The Ray dashboard also showed multiple workers in a pending state, suggesting capacity constraints. Our analysis determined that the model was experiencing higher-than-expected request volume without sufficient resources to scale accordingly. To address this, the node pool size has been increased to improve available capacity. However, there are still insufficient nodes to fully support the desired number of model replicas. Following the node pool expansion, a new pod-related error has been identified. Our Engineering team is actively working to resolve this issue and restore full service performance.

  3. resolved Apr 07, 2026, 03:50 PM UTC

    Service has been fully restored, and the model is now operating normally. We have implemented improvements to enhance stability and reduce the likelihood of similar issues in the future.

Read the full incident report →

Minor April 6, 2026

Serverless Inference Issue

Detected by Pingoru
Apr 06, 2026, 12:28 PM UTC
Resolved
Apr 06, 2026, 06:02 PM UTC
Duration
5h 34m
Affected: Agent Runtime
Timeline · 3 updates
  1. investigating Apr 06, 2026, 12:28 PM UTC

    Our Engineering team is investigating an issue with Serverless inference. At this time, users may experience high error rates for open source models (llama 3.3 70b). We apologize for the inconvenience and will share an update once we have more information.

  2. monitoring Apr 06, 2026, 03:15 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 06, 2026, 06:02 PM UTC

    This incident has been resolved.

Read the full incident report →