Is DigitalOcean Down?
DigitalOcean outage history and incident tracker. 99 incidents analyzed.
Total Incidents
99
Uptime
94.070%
Avg Resolution
4h 26m
Top Cause
network
DigitalOcean Outage Timeline
Outages by Year
Incident Severity
Recent DigitalOcean Incidents
View all →Gradient AI Model Kimi K3 Responses Issues
Our Engineering team has resolved the issue causing empty or broken responses from Kimi-K3. If you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.
Agent Platform Requests Returning HTTP 500 Errors
This incident has been resolved.
Network Connectivity from India to NYC
Between 07:46 UTC & 10:24 UTC today, some users in India accessing resources in the NYC region may have experienced connectivity issues. The impact was limited to users using Airtel as their ISP. Our investigation determined that the issue was caused by an internal network issue within Airtel and was not related to DigitalOcean network. The connectivity issue now appears to be resolved, and users should no longer experience problems accessing their resources. We apologize for any inconvenienc
Llama-4-Maverick Model Availability
This incident has been resolved.
Gradient AI Serverless Inference Requests Timing Out for qwen3.5-397b-a17b
This incident has been resolved.
Block Storage Volume NYC1 and NYC3
Our Engineering team has confirmed that the issue regarding volume attachment to Droplets in the NYC1, NYC3, SGP1, SYD1, and BLR1 regions has been fully resolved, and all 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.
Networking in BLR1
Our engineering team has resolved the outbound network connectivity issue in the BLR1 region. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Reserved IP routing in TOR1
Our Engineering team has confirmed that the underlying issue affecting Reserved IP routing in the TOR1 region 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.
Serverless Inference - Gemma4 Latency Issues Causing Timeouts & Slow Responses
The deployed fix has successfully restored full functionality, and our monitoring shows that system performance has completely stabilized. Response times for all Gemma 4 inference workflows have returned to normal baseline levels. We will continue to track platform stability moving forward to ensure long-term reliability. We apologize for any disruption this may have caused to your workflows and appreciate your patience throughout the recovery process.
Kubernetes Deployments in NYC1
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 Co
Incident Severity Distribution
Frequently Asked Questions
Is DigitalOcean down right now?▾
How often does DigitalOcean have outages?▾
What is DigitalOcean's uptime percentage?▾
What are the most common causes of DigitalOcean outages?▾
How long do DigitalOcean outages typically last?▾
How does DigitalOcean's reliability compare to other cloud providers?▾
Related Resources
Get Notified When DigitalOcean Goes Down
Subscribe to outage alerts via webhook or Slack and be the first to know about DigitalOcean incidents.
Set Up Alerts