DigitalOcean outage history

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.

An outage affected DigitalOcean's Cloud Control Panel and public API, hindering access to the dashboard and programmatic tooling. During the incident, Spaces in AMS3, BLR1, and FRA1 were placed into maintenance as a mitigation measure while engineers worked to stabilize the service.

The outage began at 5:30 AM UTC and was resolved by 6:35 AM UTC, lasting a little over an hour. DigitalOcean's engineering team implemented mitigation measures and observed improvements as systems stabilized; monitoring continued to ensure the Cloud Control Panel and public API remained accessible.

The DigitalOcean Cloud Control Panel and public API experienced degraded access, with users seeing login issues and intermittent errors while the data plane remained unaffected. The outage began at 10:30 PM UTC and persisted for about two and a half hours, with restoration by 12:55 AM UTC as API and Cloud Control Panel returned to normal.

Status updates from DigitalOcean described an active investigation into a recurrence of the issue affecting the public API and Cloud Control Panel, noting elevated latency and intermittent errors. The company confirmed the data plane was not impacted and pledged ongoing updates. A small volume of user reports around 10:54 PM UTC described "Service Unavailable" responses and login difficulties, including a report from Toronto, indicating the problem was primarily in the control plane and API rather than core infrastructure.

DigitalOcean faced an outage affecting its public API and Cloud Control Panel starting at Aug 24, 2026 5:20 PM UTC, with elevated 5xx errors on API calls and many users unable to access cloud.digitalocean.com. This disrupted common management tasks, including resource creation and dashboard access, for developers and operators relying on DigitalOcean services. A Lagos-based user reported a Service Unavailable message when loading the dashboard during the incident.