DigitalOcean Outage History

DigitalOcean reported a temporary visibility issue in the Cloud Control Panel that affected console access and UI interactions. Users could encounter login prompts when opening the console, difficulties selecting options during droplet resize, and misaligned UI elements such as squished columns, resulting in a degraded experience when managing resources.

The incident began at Feb 19, 2026 5:35 PM UTC and was mitigated with a fix by Feb 19, 2026 6:10 PM UTC, with full recovery by Feb 19, 2026 6:45 PM UTC. The Cloud Control Panel returned to normal after the updates, and DigitalOcean issued 3 status updates over the course of the incident.

DigitalOcean experienced a partial outage affecting the Droplet limit increase feature within the Cloud Control Panel. As of 6:40 AM UTC, requests to raise Droplet limits submitted through the Control Panel were not being processed, and submissions were not generating support tickets as expected. This degraded functionality impacted users trying to increase Droplet limits. The incident lasted until 11:00 AM UTC, roughly 4 hours and 20 minutes, and the provider published 2 status updates during the event. The issue specifically affected the Droplet limit increase workflow in the Cloud Control Panel.

DigitalOcean experienced a short-lived delay affecting new App Platform deployments, while existing apps continued to function normally. The issue began at 7:10 PM UTC and was resolved by 7:35 PM UTC. DigitalOcean issued three status updates during the incident, noting ongoing investigation, the implementation of a fix, and the return to normal deployment activity. The problem was isolated to the App Platform / Global component and lasted about 25 minutes.

The DigitalOcean MongoDB cluster creation issue affected managed databases across all regions. The incident began at 5:45 AM UTC and hindered creation, fork, and resize operations for MongoDB clusters. The disruption lasted approximately 6 hours and 25 minutes across DigitalOcean's global Managed Databases.

A fix was implemented at 9:55 AM UTC, with guidance that services should be functioning as expected while the team continues to monitor for full restoration. The status was restored to up by 12:10 PM UTC. DigitalOcean issued updates during the incident to inform users of progress and confirm restoration of MongoDB cluster creation operations across all regions.

DigitalOcean reported delays affecting App Platform deployments across all regions, with only new app creation impacted while existing apps continued to function. The incident began at 11:55 AM UTC and lasted about 1 hour 15 minutes, resolving by 1:10 PM UTC. The App Platform / Global component was affected. The provider issued three status updates during the incident, including a fix implemented by 12:05 PM UTC and ongoing monitoring before confirming resolution.

DigitalOcean conducted a scheduled maintenance on the Networking / AMS2 component. The maintenance window began at 9:00 AM UTC and concluded at 5:00 PM UTC. AMS2 was listed in maintenance during this period and then returned to normal. The provider published two status updates, one at the start and one at the end. No user reports of impact were observed during the window.

DigitalOcean experienced an outage affecting the Cloud Control Panel and API, with users reporting gateway timeouts on the dashboard and 5xx errors when calling API endpoints. This degraded access to management and deployment workflows for developers and operators. The incident began at Feb 3, 2026 5:30 PM UTC and impacted both web and programmatic access. The provider posted updates as the issue developed.

The provider issued three status updates during the incident, noting ongoing investigation and eventual recovery. The Cloud Control Panel and API were returned to normal by Feb 3, 2026 6:55 PM UTC.

DigitalOcean reported an issue in the FRA1 region affecting Kubernetes Clusters and Droplets, causing provisioning delays and volume mounting problems. In this region, some droplet events appeared stuck or delayed. The incident began around 11:27 AM UTC and was raised to a warning at 11:35 AM UTC. The outage lasted from 11:27 AM UTC to 5:40 PM UTC, roughly 6 hours and 13 minutes. DigitalOcean issued two status updates during the incident and service was restored by 5:40 PM UTC. The impact was primarily in the FRA1 region and affected Kubernetes Clusters and Droplets in that area.

DigitalOcean FRA1 experienced a brief degradation in Droplet-based services. In the FRA1 region, users may have encountered delays or errors when creating or deleting Droplets and while using Droplet-based products such as Load Balancers, Kubernetes Clusters, and Databases. The incident affected four components: Droplets / FRA1, Managed Databases / FRA1, Kubernetes / FRA1, and Load Balancers / FRA1.

The issue began at Jan 28, 2026 12:50 AM UTC and was resolved by Jan 28, 2026 4:15 AM UTC, lasting approximately 3 hours and 25 minutes. DigitalOcean issued 2 status updates during the event, noting an investigation and restoration of services in FRA1 as engineers worked to restore full functionality.

The scheduled network maintenance for DigitalOcean's NYC3 region ran from 9:00 AM UTC to 1:00 PM UTC, lasting about 4 hours. During the maintenance window, connectivity to resources routed through NYC3 could have been intermittent and users may have experienced degraded networking in that region. The NYC3 networking component was in maintenance during this period.

DigitalOcean posted updates noting the maintenance was in progress and later confirmed the component returned to normal after the window. The impact appeared localized to the NYC3 network path, with a small amount of user reports observed around the start of the maintenance.