DigitalOcean Outage History

DigitalOcean experienced a brief issue affecting GPU node provisioning for new Kubernetes clusters. New clusters on the latest version could not launch a new GPU node, while existing workloads were unaffected. The incident began at 9:20 PM UTC and was resolved by 11:15 PM UTC, lasting about 1 hour and 55 minutes. The status page showed impact across three components—GPU Droplets / Global, Kubernetes / ATL1, and Kubernetes / TOR1—and the provider issued two updates during the incident as they worked toward a fix. Services returned to normal after the updates.

DigitalOcean conducted a scheduled maintenance window for the NYC1 region beginning at 10:00 PM UTC and ending at 12:00 AM UTC. The maintenance affected seven NYC1 components, including App Platform New York, Managed Databases NYC1, Networking NYC1, Load Balancers NYC1, Cloud Firewall, Kubernetes NYC1, and Droplets NYC1. During the window, users in the NYC1 region may have experienced temporary disruption or degraded performance as services were brought offline and then brought back online. The window lasted approximately 2 hours.

An outage affected DigitalOcean's App Platform deployments and all non-Mongo Managed Database clusters, disrupting core management operations (Create, Read, Update, Delete). Users attempting to provision new clusters, list existing ones, or modify configurations could encounter long-running queries or failures. App Platform deployments that rely on Managed Databases were also impacted, potentially delaying or failing deployments. The incident began at Jul 8, 2025 3:00 PM UTC and was resolved by Jul 8, 2025 4:05 PM UTC, lasting about 1 hour and 5 minutes. During the incident, DigitalOcean issued two status updates detailing the investigation and subsequent restoration.

The outage began on Jul 1, 2025 7:05 PM UTC with SSL/TLS handshake failures impacting DigitalOcean Spaces in FRA1 and SFO3, causing connection errors or timeouts when accessing buckets over HTTPS. The incident lasted roughly 2 days and 55 minutes, and users in these regions experienced degraded access to object storage during the initial event.

On Jul 2, 2025 2:25 PM UTC, the issue expanded as teams investigated problems related to creating agents with attached knowledge bases. By Jul 2, 2025 5:00 PM UTC, additional impacts affected App Platform deployments and Managed Databases provisioning, potentially delaying new database clusters and app deployments. The provider issued six status updates over the course of the incident, covering components such as GenAI Platform, App Platform, and Managed Databases as issues were identified and addressed. The issues were progressively resolved and services began returning to normal as fixes were applied.

All issues were resolved by Jul 3, 2025 8:00 PM UTC, with FRA1 and SFO3 Spaces, the GenAI Platform, App Platform, and Managed Databases returning to normal operation.

DigitalOcean reported a global issue affecting MongoDB cluster creation across all regions. Users may have faced failures when creating new MongoDB clusters managed by DigitalOcean. The incident began at Jul 1, 2025 2:00 AM UTC and was resolved by Jul 1, 2025 2:35 AM UTC, lasting roughly 35 minutes. The impact was limited to the MongoDB creation workflow within the Managed Databases / Global component.

DigitalOcean posted two status updates during the incident as engineers investigated and then confirmed recovery, with the MongoDB cluster creation issue subsequently resolved and normal service restored.

DigitalOcean reported an issue affecting the creation of Managed Databases via the Cloud Panel and API. A subset of users may have experienced errors or delays when provisioning new database clusters, while existing clusters remained operational. The incident began at Jun 30, 2025 6:40 PM UTC and was resolved by Jun 30, 2025 9:30 PM UTC, lasting approximately 2 hours and 50 minutes. DigitalOcean posted updates as the situation progressed, indicating they were actively working to restore the service.

The issue affected the Managed Databases component globally and the provider issued 2 status updates during the incident.

DigitalOcean reported a brief issue affecting the creation of Managed Databases through the Cloud Panel and API. A subset of users attempting to provision new database clusters may have experienced errors or delays, while existing clusters remained operational. The disruption began at 6:25 PM UTC and lasted about 10 minutes, with services returning to normal by 6:35 PM UTC. The Global Managed Databases component was affected. DigitalOcean posted two status updates during the incident, describing an identified issue and efforts to restore provisioning.

DigitalOcean's Functions component across all regions experienced an outage that affected creating, deleting, and deploying apps using Functions. Users attempting these actions may have encountered failures or errors during the incident window, with the issue impacting Function-based workflows globally. The outage began around 10:50 AM UTC and persisted until 1:00 PM UTC, lasting roughly 2 hours and 10 minutes.

DigitalOcean experienced two related issues on Jun 16, 2025 2:38 PM UTC: App Platform deployments across regions were delayed, though previously deployed running apps were not impacted. In parallel, Spaces availability in FRA1 degraded, with errors when uploading, retrieving, or listing objects, affecting operations in that region.

According to DigitalOcean's status updates, the incident timeline included FRA1 Spaces being flagged at Jun 16, 2025 2:58 PM UTC and a fix implemented by Jun 16, 2025 3:25 PM UTC. App Platform deployments were restored by Jun 16, 2025 3:30 PM UTC, while FRA1 Spaces fully recovered by Jun 16, 2025 6:00 PM UTC. The provider issued 4 status updates during the incident.

Overall, the disruption was regional for Spaces and global for deployments, with no complete platform outage. The incident lasted roughly 3 hours for FRA1 Spaces and under an hour for App Platform deployments.

DigitalOcean reported a brief issue affecting Droplet creation in all regions for users with Member or Modifier roles, which could prevent creating Droplets via the Cloud Control Panel and API. The incident began at 8:40 PM UTC and was resolved by 9:45 PM UTC, with the issue impacting the Event Processing / Global, Cloud Control Panel, and API components. DigitalOcean issued two status updates during the incident as they investigated and worked to restore full functionality.