DigitalOcean outage history

DigitalOcean experienced a degraded state for Kubernetes cluster management operations starting Oct 27, 2026 10:15 PM UTC, which escalated to a full outage by Oct 27, 2026 11:26 PM UTC. The disruption prevented typical cluster management actions such as creating, deleting, scaling, or upgrading clusters across all regions, while existing workloads continued to run normally. The impact was global to DigitalOcean's Kubernetes service, with users likely facing delays or failures when performing management tasks.

A fix was implemented at Oct 28, 2026 1:35 AM UTC and recovery progressed, with cluster management operations returning to normal by Oct 28, 2026 1:55 AM UTC. DigitalOcean indicated that cluster lifecycle tasks were functioning as expected again and noted ongoing monitoring to confirm stability across all regions.

The DigitalOcean Managed Kubernetes service experienced intermittent external DNS lookup failures, causing applications on affected clusters to intermittently fail to resolve external domain names. The issue began at 10:05 PM UTC and impacted multiple regions, leading to paused or degraded access to external resources for some workloads.

Engineering investigated and implemented a fix by 10:55 PM UTC, with monitoring continuing to ensure the problem was resolved. The issue was marked resolved by 11:30 PM UTC, and DNS resolution returned to normal on the remaining affected clusters.

DigitalOcean reported a temporary disruption to VPC networking beginning around 8:48 AM UTC, with users experiencing delays or failures when creating or deleting VPC peerings, VPC Native DOKS clusters, or Private Network Connections (PNCs). Adding cluster members and provisioning routes or subnets could also have been affected during the incident window. An official update at 10:40 AM UTC labeled the issue as VPC Networking Availability and indicated engineers were investigating as operations were degraded.

The issue was resolved in stages, with the VPC / Global component returning to up by 11:05 AM UTC as services were restored and monitoring continued. The impact was limited to networking components, with other DigitalOcean services remaining unaffected.

Users were unable to access the DigitalOcean Support Portal or submit new tickets starting at 9:50 AM UTC. DigitalOcean attributed the disruption to a third-party service issue affecting the Support Center, and existing support requests could experience delayed responses. As a workaround, customers could submit requests via the Support Contact form.

The issue appeared to improve later in the day. By 2:10 PM UTC the portal and ticket creation were accessible again after an upstream fix, with DigitalOcean planning to monitor for the next two hours to confirm stability. Later, by 9:10 PM UTC the Support Center returned to normal operation, marking the incident as resolved.

A power degradation in DigitalOcean's ATL1 datacenter reduced available power, which could degrade GPU workloads during periods of high utilization. Redundant power systems kept servers online and there were no outages observed; the affected component was GPU Droplets / ATL1. Impact began at 10:50 AM UTC.

Datacenter and infrastructure teams investigated and restored full power redundancy, returning the GPU Droplets / ATL1 to normal operation. The issue was resolved by 11:35 AM UTC.

DigitalOcean conducted a brief maintenance window for Spaces in the BLR1 region. The window began at 4:00 PM UTC and was resolved by 5:40 PM UTC, with Spaces in BLR1 temporarily unavailable during that time. The BLR1 component returned to normal after maintenance and service resumed. No other components were affected.

DigitalOcean Spaces in NYC3, SFO2, and SFO3 entered maintenance at 5:30 AM UTC, temporarily affecting object storage operations in those regions. The maintenance window lasted about three hours, with services returning to normal by 8:30 AM UTC. During the window, users attempting to access or manage data in these Regions may have experienced interruptions or degraded storage performance. The affected components were Spaces in NYC3, SFO2, and SFO3, and these regions returned to online operation once the maintenance completed.

DigitalOcean Spaces in the BLR1 region entered a brief maintenance window starting at 4:00 PM UTC and returned to normal by 4:30 PM UTC. The maintenance was localized to the BLR1 region and could have caused brief disruptions to object storage access during the window. DigitalOcean’s status page shows Spaces / BLR1 moving from up to maintenance and back to up as the work completed, with the overall window lasting about 30 minutes.

DigitalOcean Spaces in the AMS3 region (Amsterdam) and the FRA1 region (Frankfurt) entered maintenance at 6:10 AM UTC, causing a temporary disruption for users in those regions. Access to Spaces was affected during the maintenance window. The services were restored to normal when maintenance ended at 9:01 AM UTC, with both Spaces / AMS3 and Spaces / FRA1 returning to full operation after about two hours and fifty minutes. The impact was confined to the two regions listed, with no broader service impact reported.

DigitalOcean Spaces in FRA1 (France) and AMS3 (Amsterdam) entered a brief maintenance window starting at 6:00 AM UTC, lasting about five minutes. During the window, Spaces / FRA1 and Spaces / AMS3 were taken offline for maintenance and were brought back online when the window ended.

Status updates indicate both Regions returned to normal by 6:05 AM UTC. The impact was limited to these two Spaces regions; other DigitalOcean Spaces regions remained unaffected. No user reports were recorded during this period.