DigitalOcean Outage History
Daily status observations, past incidents, and reported issue history for DigitalOcean.
Checking current status...
90-Day Trend
Monthly Status Summary
| Month | Issue-free days | Days Tracked | Days with Issues |
|---|---|---|---|
| August 2026 | 65.2% | 23 | 8 |
| July 2026 | 32.3% | 31 | 21 |
| June 2026 | 73.3% | 30 | 8 |
| May 2026 | 85.7% | 7 | 1 |
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Daily Status (Last 91 Days)
May 25
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
August 2026
Managed Databases Creation
Started:
NYC1
NYC3
monitoring
Our Engineering team has implemented the necessary fixes affecting Managed Database cluster creation in the NYC3 and NYC1 regions. Users should now be able to create new Managed Database clusters.
We are currently monitoring the situation to ensure that the service has returned to normal operation and remains stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.
investigating
We continue to investigate an issue affecting DigitalOcean Managed Databases cluster creation across multiple regions.
During this time, users may experience errors when creating Managed Database clusters via the Cloud Control Panel or API.
Our engineering team is implementing a mitigation and working to restore normal provisioning. We will provide another update as soon as more information is available.
investigating
Our Engineering team is investigating an issue with our Managed Database product. At this time, users may experience errors while creating clusters, both via Cloud Control Panel and API requests.
We apologize for the inconvenience and will share an update once we have more information.
Container Registry and Spaces Accessibility
Started:
Global
Global
monitoring
Our Engineering team has identified the issue affecting Container Registry and Spaces buckets, and a fix has been applied.
Spaces accessibility via the Cloud Control Panel should now be restored, and pushing and pulling container images should be back to normal.
We are continuing to monitor the results to ensure the issue has been fully resolved and will provide another update once we've confirmed normal service has been restored.
investigating
Our Engineering team is currently investigating reports of an issue affecting Container Registry and Spaces buckets in some regions.
During this time, customers may experience failures when pushing or pulling container images. Additionally, customers may experience issues accessing Spaces via the Cloud Control Panel, where the page may display "Looks like something went wrong…"
Our Engineering team is actively investigating the issue and treating it with priority. We will provide another ...
Major Service Interruption in MKC1
Started:
MKC1
MKC1
monitoring
At this time, the regional control plane is fully healthy. CPU Droplets, Managed databases, Load balancers, Block storage and Spaces are operating normally. Droplet create, resize and other management operations are working. Kubernetes (DOKS) control planes are reachable.
Our teams are continuing to work with the facility to restore all equipment. GPU Droplets in MKC1 remain offline or unreachable. DOKS GPU worker nodes may remain NotReady, and GPU-backed inference endpoints in this region m...
identified
Our Engineering team continues to work on the issue affecting the MKC1 region. We are actively working to restore connectivity and bring the impacted nodes back online.
We will provide another update as soon as we have more information.
identified
We have identified the root cause of the issue in the MKC1 region affecting multiple racks and nodes. Our Engineering team is actively implementing remediation steps to restore connectivity and bring the impacted nodes back online.
During this time, customers may continue to experience disruptions to GPU workloads and Serverless Inference. Kubernetes (DOKS) worker nodes may also remain in a NotReady state, and customers may be unable to reach Kubernetes API endpoints or perform cluster-manage...
investigating
Our Engineering team is currently investigating an issue in the MKC1 region affecting multiple racks and nodes.
During this time, customers may experience disruptions to GPU workloads, and Kubernetes (DOKS) worker nodes may enter a NotReady state.
Our team is actively working to restore connectivity and bring impacted nodes back online. If you continue to experience issues, please open a support ticket from within your account.
Account Registration, Droplets, and Related Services
Started:
monitoring
Our Engineering team has implemented a fix for the issue affecting new account registration, Droplets, Reserved IPs, Snapshots, and DOKS clusters across multiple regions, and is currently monitoring the situation. At this time, customers should no longer experience errors with:
New account registration
Droplet creation
Reserved IP allocation
Automated Backups and Snapshots operations
Droplet Autoscale scaling operations
DOKS cluster operations
GenAI services
Access to the Droplet console
Dat...
identified
Our Engineering team continues to work on implementing and rolling out a fix for the issue affecting multiple services across multiple regions, including new account registration, Droplets, Reserved IPs, Automated Backups and Snapshots, Droplet Autoscale, DOKS clusters, GenAI services, the Droplet console, and Database cluster creation.
Customers may continue to experience the previously reported service disruptions while remediation efforts remain in progress. We will provide another update...
identified
Our Engineering team has identified the root cause of the issue affecting new account registration, Droplets, Reserved IPs, Snapshots, and DOKS clusters across multiple regions.
Customers may experience the following:
Unable to create new accounts
Unable to create Droplets
Unable to allocate Reserved IPs
Failures with Automated Backups and Snapshots operations
Droplet Autoscale scaling operations not working as expected
DOKS cluster operations failing
GenAI services impacted
Unable to acces...
investigating
Our Engineering team is continuing to investigate reports of an issue affecting new account registration, Reserved IPs, Snapshots, Droplets and Droplet-based services across multiple regions.
During this time, customers may be unable to create new accounts, create Droplets, allocate Reserved IPs, or perform Automated Backups and Snapshots operations. Droplet Autoscale scaling operations and DOKS cluster operations are also affected.
Further investigation has found that GenAI services are al...
investigating
Our Engineering team is currently investigating reports of an issue affecting new account registration, Reserved IPs, Snapshots, Droplets and Droplet-based services across multiple regions.
During this time, customers may be unable to create new accounts, create Droplets, allocate Reserved IPs, or perform Automated Backups and Snapshots operations. Droplet Autoscale scaling operations and DOKS cluster operations are also affected.
Our Engineering team is actively investigating the issue and...
Functions on App Platform
Started:
monitoring
Our Engineering team has implemented a fix for the issue affecting Functions on App Platform. Functions builds/deploys and requests to Functions endpoints should now be completing successfully. We are currently monitoring the situation to ensure the service has returned to normal operation and remains stable.
We apologize for the inconvenience and will provide a further update once the incident is confirmed resolved.
investigating
Our Engineering team is investigating an issue impacting Functions on App Platform. During this time, users may experience build/deploy failures for Functions components, and requests to Functions endpoints may fail with a 504 error, caused by an SSL error when App Platform attempts to forward requests to Functions. This issue currently appears to be isolated to Functions deployed within App Platform.
We apologize for the inconvenience and will share an update once we have more information.
Spaces Cold Storage Billing
Started:
monitoring
Our Engineering team has implemented a fix for the issue affecting Spaces Cold Storage billing and is currently monitoring the situation. Customers with cold storage buckets should no longer see incorrect values reflected in their daily usage and current invoices. We will post an update as soon as the issue is fully resolved.
identified
Our Engineering team has identified the issue affecting Spaces Cold Storage billing. The team is actively working on a fix to resolve the issue. We apologize for the inconvenience and will provide another update as soon as more information becomes available.
investigating
Our Engineering team is investigating an issue affecting Spaces Cold Storage billing. During this time, customers with cold storage buckets may see incorrect values reflected in their daily usage and current invoices.
We apologize for the inconvenience and are actively working to resolve the issue. We will provide an update as soon as more information becomes available.
Cloud Control Panel Access
Started:
monitoring
We have implemented mitigation for the issue causing some customers to experience intermittent errors when accessing the DigitalOcean Cloud Control Panel. We are seeing recovery and are monitoring the service closely. We will provide another update once we have confirmed the issue is fully resolved
investigating
Beginning at 09:36 UTC on August 3, some customers may experience intermittent errors when accessing the DigitalOcean Cloud Control Panel, including an "mTLS verification failed" message. Our engineering team is actively investigating.
We apologise for the inconvenience this may have caused. We will provide another update as soon as more information is available.
If you have any questions related to this issue, please send us a ticket from your cloud support page. https://cloudsupport.digi...
July 2026
Response Degradation Impacting Kimi-K3
Started:
investigating
Our Engineering team is investigating reports of empty or broken responses impacting Kimi-K3.
At this point, users may experience degraded response quality, specifically empty or broken outputs (including repeated characters), when querying the Kimi-K3 service.
We apologize for the inconvenience and will share an update once we have more information.
investigating
We are currently investigating this issue.
Agent Platform Requests Returning HTTP 500 Errors
Started:
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
Network Connectivity from India to NYC
Started:
monitoring
We are observing improvements in network connectivity for users in India accessing resources in our NYC region. Our team is 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.
identified
We have noticed network connectivity issues affecting some users connecting from India to resources in the NYC region. Based on our current investigation, users on Airtel and BSNL have reported increased latency, packet loss, or intermittent connectivity. We apologize for the inconvenience and will provide an update as soon as more information becomes available.
Llama-4-Maverick Model Availability
Started:
investigating
Our Engineering team is currently investigating an issue where the llama-4-maverick model is unavailable. Users may experience HTTP 500 errors while using this model with Serverless Inference.
We apologize for the inconvenience. Our Engineering team is working with high priority to resolve the issue. Thank you for your patience and understanding.
Gradient AI Serverless Inference Requests Timing Out for qwen3.5-397b-a17b
Started:
investigating
We are currently investigating this issue.
Block Storage Volume NYC1, NYC3, SGP1, SYD1 and BLR1
Started:
monitoring
Our Engineering team has identified the root cause of the issue preventing volume attachments to Droplets in NYC1, NYC3, SGP1, SYD1, and BLR1 and has successfully implemented a fix. You should now be able to attach volumes to your Droplet(s) without encountering any further errors or issues.
We are actively monitoring the situation to ensure the fix remains effective and will provide another update once the issue has been fully resolved.
investigating
We are continuing to investigate this issue.
investigating
We are continuing to investigate this issue.
investigating
Our Engineering team is investigating an issue with attaching volume to the droplets in the NYC1, NYC3, SGP1, SYD1 and BLR1 regions. During this time you may experience an issue with attaching volume to the Droplet(s). We apologize for the inconvenience and will share an update once we have more information.
Networking in BLR1
Started:
monitoring
Our engineering team has implemented the necessary fixes affecting upstream network connectivity for Droplet-based services in the BLR1 region. Users should now be able to connect to the external endpoints from Droplets in BLR1.
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.
identified
Our Engineering team has identified an issue affecting upstream network connectivity for Droplet-based services in the BLR1 region and is actively working with the relevant upstream providers to implement a resolution.
Customers may continue to experience intermittent timeouts or connectivity issues when attempting to reach external endpoints from Droplets in BLR1.
We will provide another update once the issue has been fully resolved or when additional information becomes available.
investigating
We are currently investigating an issue affecting outbound network traffic for Droplets in the BLR1 region. Customers may experience timeout errors or connectivity issues when attempting to reach external services.
Our Engineering team is actively investigating the issue and working to identify the root cause. We will provide additional updates as soon as more information becomes available.
Reserved IP routing in TOR1
Started:
monitoring
Our Engineering team has implemented a fix for the issue affecting Reserved IP routing in the TOR1 region, and we are currently monitoring the results.
Inbound and outbound traffic to and from Reserved IPs in TOR1 should now be restored. If you reassigned your Reserved IP as a workaround and are still experiencing issues, please reach out to our support team.
We will continue to monitor the situation closely and provide a further update once we have confirmed the issue is fully resolved.
identified
Our Engineering team has identified the cause of the issue affecting Reserved IP routing in the TOR1 region, which was causing inbound and outbound traffic to and from Reserved IPs in TOR1 to fail.
Detaching and reassigning the Reserved IP to the Droplet may restore connectivity in the meantime. We recommend trying this workaround if you are still experiencing issues with your Reserved IP in TOR1.
Our engineering team is now working on implementing a fix. We will provide updates as more inf...
investigating
Our Engineering team is investigating an issue affecting Reserved IP routing in the TOR1 region. The issue is causing inbound and outbound traffic to and from Reserved IPs in TOR1 to fail.
In the meantime, detaching and reassigning the Reserved IP to the Droplet may restore connectivity. We recommend trying this workaround if you are experiencing issues with your Reserved IP in TOR1.
Our engineering team is actively investigating the root cause and working towards a resolution. We will prov...
Serverless Inference - Gemma4 Latency Issues Causing Timeouts & Slow Responses
Started:
monitoring
A fix has been deployed to resolve the issue. We are closely monitoring system performance to ensure full recovery and normal response times for all Gemma 4 inference workflows.
identified
We are currently experiencing an issue affecting customers using the Gemma 4 model on our Serverless Inference platform. Customers may experience significantly increased latency or request timeouts.
Our Engineering team has identified a backend configuration issue as the root cause, which is temporarily impacting model performance. 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 inconvenie...
monitoring
A fix has been deployed to resolve the backend configuration issue. We are closely monitoring system performance to ensure full recovery and normal response times for all Gemma 4 inference workflows.
identified
We are currently experiencing an issue where customers using the Gemma 4 model on our Serverless Inference and Dedicated Inference platforms may experience severe latency or request timeouts.
Our engineering team has identified a backend configuration issue as the root cause, which is temporarily degrading performance. We are actively working on a fix to restore normal response times and will provide another update as soon as the mitigation is in place
Kubernetes Deployments in NYC1
Started:
monitoring
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.
investigating
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.
Limited access to Deepseek V4 Pro model
Started:
monitoring
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 t...
investigating
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.
Droplet Actions in NYC3
Started:
monitoring
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.
Managed Database Clusters
Started:
monitoring
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.
investigating
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.
investigating
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.
DNS Lookup Failures for Managed Database
Started:
investigating
We are continuing to investigate this issue.
investigating
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.
Droplet Resize
Started:
monitoring
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.
investigating
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.
Agent Timeouts While Retrieving Data from Knowledge Bases
Started:
identified
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.
investigating
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...
June 2026
Anthropic Inference Model Availability
Started:
monitoring
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 inconvenien...
Monitoring Graphs in the Cloud Control Panel
Started:
monitoring
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 c...
investigating
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
Intermittent 500 Errors on Serverless/GenAI Inference API
Started:
monitoring
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.
investigating
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.
DeepSeek V4 Pro is returning HTTP 429 "Rate limit exceeded"
Started:
identified
The issue has been identified and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
We are currently facing issues with Gradient AI DeepSeek V4 Pro is returning HTTP 429 "Rate limit exceeded"
DNS API Service
Started:
monitoring
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 monit...
identified
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 oper...
investigating
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 ope...
investigating
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 mor...
May 2026
App Platform Deployments
Started:
monitoring
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.
investigating
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.
Cloud Firewall
Started:
monitoring
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.
identified
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.
Cloud Firewall
Started:
monitoring
Our Engineering team has implemented a fix to resolve the issue causing incorrect Cloud Firewall rules to display on the cloud panel. At this time, the user interface is functioning as expected, and we are actively monitoring the situation to ensure continued stability.
We will provide a final update once we have verified that the issue is fully resolved.
investigating
We are currently investigating an issue with incorrect Cloud Firewall rules appearing on the cloud panel. Our engineering team is aware of the situation and actively working to identify the root cause. Since this is a user interface issue, users should not experience any problems with other services or networking.
We apologize for the inconvenience and appreciate your patience. We will continue to provide updates as we learn more.
Block Storage Volume Performance
Started:
monitoring
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
investigating
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.
Anthropic reported outage that's impacting access to their Serverless Inference models
Started:
identified
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.
monitoring
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.
DNS service, Certificates and Managed MongoDB
Started:
monitoring
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 m...
investigating
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 ...
investigating
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.
GradientAI: Agent Platform Playground Interaction Errors
Started:
identified
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.
identified
We have identified the cause of the issue affecting the GradientAI Agent Platform Playground. Our engineering team is implementing a fix, and we will provide another update as soon as it is available.
investigating
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.
Control Panel Errors - Unable to Enable 2FA and Google/GitHub
Started:
monitoring
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.
investigating
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.
Let's Encrypt Outage Affecting Certificate Issuance and Managed Databases Operations
Started:
identified
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 u...
Multiple Services in NYC2
Started:
monitoring
We are continuing to monitor for any further issues.
monitoring
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.
investigating
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.
April 2026
Elevated 5xx “context canceled” errors impacting serverless inference
Started:
monitoring
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.
identified
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.
investigating
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.
Serverless Inference - Intermittent Rate Limiting Affecting Some Customers Using Anthropic Models
Started:
monitoring
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.
investigating
We are investigating an issue affecting some customers using DigitalOcean Serverless Inference with Anthropic models. Over the last two hours, impacted customers may have experienced intermittent request failures, including HTTP 429 responses, on some Anthropic model requests. Our engineering team is actively investigating the issue. We apologize for the inconvenience and will share another update as soon as more information is available.
Intermittent errors impacting some Serverless Inference models in ATL1
Started:
investigating
As of 21:53 UTC, our Engineering team is investigating reports of increased internal errors for models Llama 3.3 70B, GPT OSS 120B, GPT OSS 20B, Qwen3 32B and Deepseek R1 70B hosted 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.
App Platform Deployments
Started:
monitoring
Our Engineering team has implemented a fix to address the issue causing in App Platform deployments and Kubernetes (DOKS) nodes. We are actively monitoring the situation to ensure overall stability.
Users may already notice improvements while deploying apps and DOKS nodes. We appreciate your patience throughout the process and will provide a further update once the issue is fully confirmed to be resolved.
investigating
Our Engineering team is currently investigating reports of build failures on App Platform. During this time, some users may encounter errors while building their applications, which may result in failed deployments.
In addition, we are observing an issue where Kubernetes (DOKS) nodes are being marked as unhealthy by load balancers, which may impact traffic routing for affected services.
Our Engineering team is actively working to resolve these issues and will share an update as soon as more i...
investigating
Our Engineering team is currently investigating reports of build failures on App Platform. 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 information.
We apologize for the inconvenience this issue may be causing and appreciate your patience as we work to resolve it.
Cloud UI for Managed Kubernetes
Started:
investigating
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
investigating
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.
investigating
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.
Cloud Control Panel and API
Started:
monitoring
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.
investigating
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 inconve...
DNS Resolution for .co TLD
Started:
monitoring
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.
identified
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.
Serverless Inference
Started:
monitoring
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.
investigating
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.
Managed Database Resizes
Started:
monitoring
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.
investigating
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.
Droplet Availability in All Regions
Started:
monitoring
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.
Serverless Inference - High error rates for open source models ( Qwen 3 32B)
Started:
identified
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...
investigating
Serverless inference for alibaba-qwen3-32b (Qwen 3 32B) in tor1 is experiencing high error rates starting at 10:46 UTC.
Serverless Inference Issue
Started:
monitoring
A fix has been implemented and we are monitoring the results.
investigating
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.
March 2026
App platform seeing delays in deployments across FRA1 region
Started:
monitoring
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.
investigating
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.
Gradient AI Platform agents and services Accessibility
Started:
monitoring
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.
identified
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.
identified
We’ve identified the issue and are currently working on restoring the services. We’ll continue to provide updates as progress is made.
investigating
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.
Gradient AI model availability
Started:
investigating
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 performan...
Degraded performance with BYOK Anthropic models
Started:
investigating
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
Delay in App Platform Deployments
Started:
monitoring
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.
identified
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
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.
Newly Created Managed Kubernetes Nodes
Started:
monitoring
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.
identified
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.
investigating
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.