DigitalOcean Outage History

DigitalOcean experienced a partial outage that affected the Cloud Control Panel and API, causing errors when users attempted to sign in or perform API requests. The issue began around 9:10 PM UTC, with user reports of problems starting around 9:00 PM UTC. Access to the Cloud Control Panel and API was intermittently degraded during the incident, indicating issues with authentication and API calls.

DigitalOcean published two status updates during the incident as engineers investigated and then resolved the issue. The services were restored by 10:45 PM UTC, ending the outage after roughly 1 hour 35 minutes. The affected components were the API and Cloud Control Panel.

DigitalOcean reported a brief degradation impacting App Platform Deployments globally, affecting both new and in-progress deployments. The incident began at Jan 20, 2026 6:05 PM UTC and was resolved by Jan 20, 2026 6:25 PM UTC, lasting about 20 minutes. DigitalOcean's status updates noted that engineering had implemented changes to address the issue and that deployment performance should improve as monitoring continued; the service returned to normal after the final update. The incident involved the App Platform Global component and was addressed with two official updates during the event.

DigitalOcean experienced a partial outage affecting login access and payments. The incident impacted suspended user accounts and prevented sign-in and billing operations, with three components affected: Cloud Control Panel, Event Processing / Global, and Billing. The outage began at Jan 15, 2026 7:20 AM UTC and was resolved by Jan 15, 2026 9:20 AM UTC. DigitalOcean issued two status updates during the incident as engineering investigated and then restored access.

The issue was addressed by the time services returned to normal, and affected users could resume signing in and completing payments after the restoration.

An incident in DigitalOcean's NYC3 region affected API and Cloud Control Panel access and disrupted App Platform static site deployments. Users could experience intermittent 504 errors when accessing api.digitalocean.com and cloud.digitalocean.com, while attempts to deploy new static sites in NYC3 could fail. The issue began around Dec 18, 2025 5:45 PM UTC and persisted for about 4 hours and 25 minutes, with existing sites remaining accessible during the event.

DigitalOcean experienced a brief outage where the Recovery Console for Droplets globally was inaccessible, while standard Droplet functionality remained available. The issue began at Dec 10, 2025 8:35 PM UTC and was resolved by Dec 11, 2025 12:00 AM UTC, lasting about 3 hours and 25 minutes. DigitalOcean's status page acknowledged the problem and advised users to use the Recovery ISO option in the Recovery tab and SSH into their droplets as a workaround. The incident included two official status updates before resolution.

DigitalOcean ran a scheduled Core Infrastructure Maintenance window starting at 6:00 PM UTC, affecting 12 global components including App Platform, API, Droplets, Kubernetes, Load Balancers, and more. During the window, some App Platform Static Websites returned 404 Not Found errors for certain sites, with issues first observed around 6:08 PM UTC. The incident caused degraded experience for users visiting App Platform static sites during the maintenance period.

Status updates documented the investigation and fix. The App Platform component transitioned from maintenance to warn and then back to up as the issue was resolved. A fix was implemented by 6:41 PM UTC, and overall service status returned to up for affected components by 8:00 PM UTC. In total, the provider issued four status updates about the incident.

DigitalOcean conducted scheduled core infrastructure maintenance for the SFO2 region, affecting six components: Load Balancers / SFO2, Kubernetes / SFO2, API, Managed Databases / SFO2, Cloud Control Panel, and Droplets / SFO2. The maintenance began at 9:05 AM UTC and concluded at 12:30 PM UTC, lasting approximately 3 hours and 25 minutes. The incident involved two official status updates and no user reports were received. All affected components returned to normal operation after the maintenance window, with updates indicating completion.

DigitalOcean reported DOCR access errors in the BLR1 region that prevented the creation of new apps using DigitalOcean Container Registry. This caused onboarding and app provisioning work for customers attempting to deploy new apps to BLR1 to be blocked or slowed. The issue began at 8:45 PM UTC and was resolved by 10:10 PM UTC, lasting about 1 hour and 25 minutes. DigitalOcean issued 2 status updates during the incident and implemented a fix to restore normal functionality for the BLR1 Container Registry.

DigitalOcean conducted scheduled core infrastructure maintenance in the NYC3 region, placing six components into maintenance mode: Managed Databases, Kubernetes, Load Balancers, Droplets, API, and the Cloud Control Panel. The maintenance window began around 9:00 AM UTC and lasted about 2 hours and 55 minutes, with services restored by 12:00 PM UTC. DigitalOcean issued two status updates during the incident (one noting the maintenance in progress and another confirming restoration). This was a regional event affecting NYC3 components, and customers could experience temporary service interruptions or degraded performance during the window.

DigitalOcean conducted scheduled core infrastructure maintenance in the FRA1 region, causing temporary disruption across several services. The maintenance affected 6 components: Droplets / FRA1, Cloud Control Panel, Managed Databases / FRA1, Kubernetes / FRA1, Load Balancers / FRA1, and API. The maintenance window began at 4:00 PM UTC and concluded at 10:10 PM UTC, for a total duration of about 6 hours and 10 minutes, during which users may have experienced intermittent access or degraded performance. DigitalOcean posted two official updates during the incident to communicate status and progress.