outages.live
Live

DigitalOcean

DigitalOcean is operational

Checked 50 s ago Operational

History

90 days agoToday

Incidents in 90 days

16

Days with an incident

17

Median duration

1 h 58 min

Longest incident

25 h 50 min

Components

239
API Operational
90 days ago2 days with an incidentToday
Billing Operational
90 days agoNo incidentsToday
BYOIP Operational
90 days agoNo incidentsToday
Cloud Control Panel Operational
90 days ago2 days with an incidentToday
Cloud Firewall Operational
90 days ago1 day with an incidentToday
Community Operational
90 days agoNo incidentsToday
DNS Operational
90 days ago1 day with an incidentToday
Support Center Operational
90 days ago1 day with an incidentToday
Reserved IP Operational
90 days ago2 days with an incidentToday
WWW Operational
90 days agoNo incidentsToday
CSPM Operational
90 days agoNo incidentsToday

Monitoring

Global Operational
90 days agoNo incidentsToday
AMS2 Operational
90 days agoNo incidentsToday
AMS3 Operational
90 days agoNo incidentsToday
ATL1 Operational
90 days agoNo incidentsToday
BLR1 Operational
90 days ago1 day with an incidentToday
FRA1 Operational
90 days agoNo incidentsToday
LON1 Operational
90 days agoNo incidentsToday
MKC1 Operational
90 days agoNo incidentsToday
NYC1 Operational
90 days agoNo incidentsToday
NYC2 Operational
90 days agoNo incidentsToday
NYC3 Operational
90 days agoNo incidentsToday
RIC1 Operational
90 days agoNo incidentsToday
SGP1 Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 27, 2026

Duration3 h 40 min22:14 to 01:55Kubernetes Cluster Management OperationsPartial outage

We have resolved the issue affecting Managed Kubernetes cluster operations across all regions. Cluster creation, deletion, scaling, and upgrade operations have returned to normal. We have monitored the environment and confirmed that services are operating normally. If you continue to experience any issues, please contact our Support team by opening a ticket here: https://cloudsupport.digitalocean.com/s/

Oct 13, 2026

Duration1 min17:09 to 17:09App Platform DeploymentsNotice

Between 04:34 and 12:15 UTC, customers experienced service interruptions affecting App Platform deployment operations. During this window, customers may have been unable to deploy new applications or scale existing deployments. Applications already running prior to the incident were unaffected and continued to operate normally. The disruption was caused by a software update that prevented application containers from starting on newly provisioned infrastructure nodes. Our Engineering team rolled back the update and restored the affected nodes. App Platform deployment and scaling operations have recovered and are operating normally. We sincerely apologize for any inconvenience this caused. If you continue to experience any issues, please open a support ticket and our team will be happy to assist you.

Oct 11, 2026

Duration1 h 27 min22:01 to 23:29DNS Resolution for Managed KubernetesDegraded

Our Engineering team has resolved the external DNS resolution failures affecting Managed Kubernetes across multiple regions. Applications running on Managed Kubernetes can now resolve external domain names. We sincerely apologize for any inconvenience this disruption may have caused to your operations. If you continue to experience problems, please open a ticket with our Support team: https://cloudsupport.digitalocean.com/s/

Oct 5, 2026

Duration1 h 35 min10:38 to 12:13VPC Networking AvailabilityDegraded

Our Engineering team fully resolved the VPC Networking disruption as of 10:29 UTC. Customers can now create and delete VPC peering connections, subnets, and routes as expected. Following the recovery, we monitored the affected systems and confirmed that VPC Networking operations remain stable. We apologize for any inconvenience this disruption may have caused. If you continue to experience unexpected behavior, please open a ticket with our Support team for further assistance.

Oct 3, 2026

Duration1 min14:51 to 14:51A Network Disruption in BLR1 Region Impacted Multiple Products (Resolved)Notice

From 11:59 UTC to 13:02 UTC on October 3, 2026, a networking disruption in our BLR1 region affected multiple products, including Monitoring, App Platform, Managed Databases, Functions, Load Balancers, Spaces, and the Cloud Control Panel. During this period, some users experienced degraded connectivity, increased latency, or intermittent errors when accessing resources in the region. Multiple network paths operated by our upstream connectivity providers were unavailable, including redundant paths intended to maintain connectivity during a disruption. Traffic shifted to a remaining link with insufficient capacity to handle the full load, resulting in network saturation and the connectivity issues described above. Our Engineering and Network teams worked closely with our upstream providers to restore normal routing and connectivity. All affected services have since returned to normal operation. We apologize for the disruption and its impact on your work. If you continue to experience unex

Sep 16, 2026

Duration11 h 21 min09:48 to 21:09Support Portal Service DisruptionDegraded

From 08:06 UTC to 13:41 UTC, users may have experienced issues accessing the Support Portal, creating new support tickets, or reviewing existing support requests. Our Engineering team has confirmed the full resolution of the issue affecting the Support Portal following a fix from our upstream provider. We have verified that the Support Portal, ticket creation, and ticket review are now operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience and appreciate your patience.

Sep 9, 2026

Duration1 h 38 min10:47 to 12:25Power Degradation impacting GPU Performance in ATL1Degraded

This incident is now resolved. Power redundancy has been fully restored, and we have confirmed that customer impact has been mitigated. We are closing this incident.

Aug 24, 2026

Duration25 h 50 min17:14 to 19:04Cloud Control Panel and APIMajor outage

## 1. What happened Between 16:56 UTC and 23:09 UTC on August 24, 2026, customers using DigitalOcean’s Cloud Control Panel, Public API, and dependent product management systems experienced elevated request error rates, peaking at 25%, in two distinct windows totaling 3.5 hours of active degradation within a 6-hour span. Running Droplets, network routing, and block storage \(Volumes\) remained fully functional and unaffected throughout the event. No customer data loss occurred. The event was initiated during a planned infrastructure migration of the database layer supporting identity, authentication, and authorization services. The migration introduced increased execution latency for a critical authorization query. In response to the elevated query latency, multiple upstream services initiated automated hedged retries. This secondary request amplification led to queue buildup in excess of the authentication service pool's processing throughput, resulting in cascading request timeouts ac

Aug 23, 2026

Duration9 h 22 min05:11 to 14:33Managed Databases CreationDegraded

Our Engineering team has resolved the issue preventing cluster creation on Managed Databases in the NYC3 and NYC1 regions. Customers can now create new Managed Databases Clusters normally. Our Engineering team has monitored the environment to ensure stability. We sincerely apologize for any inconvenience this disruption may have caused to your operations. If you continue to experience issues, please open a ticket with our Support team: https://cloudsupport.digitalocean.com/s/

Aug 21, 2026

Duration1 h 53 min12:59 to 14:52Container Registry and Spaces AccessibilityDegraded

Our Engineering team has confirmed that the issue impacting Container Registry and Spaces accessibility has been resolved. Spaces accessibility via the Cloud Control Panel is now restored, and pushing and pulling container images is succeeding as expected. Customers who previously encountered these issues should now be able to access Spaces and deploy their container images 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.

Aug 19, 2026

Duration8 h 25 min11:10 to 19:34Major Service Interruption in MKC1Major outage

Our Engineering team has confirmed the regional control plane is healthy and CPU Droplets, Managed databases, Load balancers, Block storage, Kubernetes (DOKS) and Spaces are operating normally. GPU Droplets continue to be impacted and our teams are working to restore all nodes. We will communicate with GPU Droplet customers separately via Slack and email with more information and regular updates. Thank you for your patience throughout this incident. If you continue to experience any issues, please open a support ticket from within your account.

Aug 13, 2026

Duration1 min14:59 to 14:59Volume Attach/Detach events in FRA1Notice

Between Aug 13, 09:50 UTC and 14:30 UTC, customers in the FRA1 region experienced an issue affecting Block Storage Volumes attachment and detachment operations on Droplets and Managed Kubernetes clusters. During this window, customers may have encountered delays or been unable to attach and detach Block Storage Volumes from their resources. Block Storage Volumes attachment and detachment operations now appear to be functioning normally, and customers should no longer experience issues with these operations. For Managed Kubernetes clusters specifically, some residual cleanup of affected volume attachments may still be needed, and our team is actively working through this. We apologize for any inconvenience this may have caused. If you continue to experience issues with Block Storage Volumes operations, please don't hesitate to open a support ticket for further investigation. Our team will be happy to assist you.

Follow DigitalOcean

Your coding agent knows when DigitalOcean is down, and tells you when a failure is theirs, not yours. You can also get DigitalOcean incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "digitalocean" and tell me if DigitalOcean has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=digitalocean
Slack
/feed subscribe https://outages.live/feed.xml?providers=digitalocean

Go from tracking outages to fixing production issues with Polylane.

Try Polylane