DigitalOcean Outage History

DigitalOcean Spaces, Container Registry, and App Platform experienced degraded performance beginning at Oct 23, 2025 4:20 PM UTC. Users could see slow responses or limited availability when accessing Spaces or its objects via the Control Panel or API, and Container Registry access/creation and App Platform builds were affected. The impact was global across these three components.

DigitalOcean App Platform Deployments experienced a brief degraded period during the incident window. New and in-progress deployments could become stuck in the build phase or experience delays, and some builds failed after retries. The incident began at 4:40 PM UTC and was resolved by 5:00 PM UTC, lasting about 20 minutes. The incident prompted two official status updates from DigitalOcean as engineers investigated the cause.

DigitalOcean's status page indicated the issue was being addressed in App Platform Deployments, with the first update at 4:40 PM UTC noting an investigation and potential build delays, followed by a second update at 5:00 PM UTC confirming resolution. The impact was limited to App Platform Deployments within DigitalOcean's platform.

DigitalOcean's status page described the incident as a Multiple Services Disruption caused by an upstream provider issue. Engineers were investigating as of 8:00 AM UTC. The impact included problems receiving SMS-based 2FA codes and Docker Hub image hosting being temporarily unavailable, which affected deployments on DigitalOcean Kubernetes (DOKS) and App Platform. The disruption affected two global components: Kubernetes / Global and App Platform / Global. The incident began around 8:00 AM UTC and the status was updated to degraded at 10:25 AM UTC, lasting approximately 21 hours and 45 minutes before a resolution was posted. The provider issued 2 official status updates during the incident.

DigitalOcean reported IPv6 connectivity issues affecting IPv6-enabled resources. The outage began in FRA1 with a subset of users in AMS2 who experienced connection problems to IPv6 endpoints. The issue then expanded to SGP1 and later affected NYC1 and SFO2, indicating regional IPv6 connectivity degradation across Europe, APAC, and North America. Users may have experienced difficulties reaching IPv6-enabled resources during the incident. The outage lasted about 3 hours and 40 minutes, from 12:20 AM UTC to 4:00 AM UTC.

DigitalOcean experienced a GPU provisioning issue that prevented the creation of new Kubernetes clusters with GPU nodes. Existing workloads were not affected, and the problem impacted GPU Droplets and Kubernetes components globally during the incident.

DigitalOcean conducted scheduled maintenance on the NYC1 Networking component from Oct 14, 2025 10:00 PM UTC to Oct 15, 2025 12:00 AM UTC. The maintenance window lasted about 2 hours and may have caused brief connectivity disruption for resources hosted in the NYC1 region. The NYC1 networking component returned to normal operation after the maintenance window, with updates confirming completion.

DigitalOcean reported an incident affecting Managed Databases globally, causing errors when creating MySQL, PostgreSQL, and Valkey clusters via the Cloud Control Panel and API. Users attempting to provision new clusters may have encountered failures or delays. The outage began on Oct 14, 2025 12:00 PM UTC and was resolved by Oct 14, 2025 7:00 PM UTC, lasting approximately 7 hours.

DigitalOcean's status page documented the investigation and subsequent updates, with the Managed Databases / Global component listed as degraded during the incident. The service returned to normal after the final update, with two status changes observed during the event.

DigitalOcean Spaces in the FRA1 region experienced access issues, with attempts to access or list Space objects returning InvalidAccessKeyId errors. The problem was isolated to FRA1 and did not affect other regions or DigitalOcean services.

The incident was acknowledged on the DigitalOcean status page, with the first update at 11:25 AM UTC reporting an investigation, and a subsequent update at 1:40 PM UTC confirming resolution. In total, two status updates were issued. The outage lasted approximately 2 hours and 17 minutes and was limited to the FRA1 region, affecting the Spaces / FRA1 component.

An outage impacted DigitalOcean's API and Cloud Control Panel, causing errors when users attempted to access accounts or call the API. The incident began at Oct 10, 2025 10:00 PM UTC with engineering starting investigation at Oct 10, 2025 9:56 PM UTC and lasted about two hours before services recovered by Oct 11, 2025 12:00 AM UTC. The issue affected two components: API and Cloud Control Panel.

The DigitalOcean status page documented ongoing investigation and two official updates during the incident. Initially, the API was reported as down and the Cloud Control Panel as degraded; by the end of the incident both components were returned to normal operation.

DigitalOcean conducted a scheduled network maintenance on the SYD1 component, causing a temporary connectivity impact in the Sydney region. The maintenance window ran from 11:00 AM UTC to 2:00 PM UTC, a duration of about 3 hours, during which the Networking / SYD1 path was shown as in maintenance on the status page.

The provider issued 2 status updates during the incident, starting with the in-progress note and ending with a completion update confirming that the SYD1 networking components returned to service at 2:00 PM UTC.