DigitalOcean Outage History

Some DigitalOcean customers were unable to view their GenAI Platform Agent in the DigitalOcean Console, and could not update agents via the console. The GenAI Platform component was affected. The incident began around 3:30 AM UTC and was resolved by 4:55 AM UTC, lasting about 1 hour 25 minutes. DigitalOcean issued 2 status updates during the incident, documenting the investigation and eventual restoration of the GenAI Platform Agent visibility and update functionality. The update noted that the scope included questions about which agent types were affected, including newly created agents.

DigitalOcean experienced a partial outage affecting the creation of Managed Database clusters, including Redis Caching clusters. Users attempting to create new clusters may have encountered failures during the incident. The issue began around 12:13 AM UTC and the status page indicated a degraded condition at 4:11 AM UTC as engineers investigated. The problem affected the Managed Databases / Global component.

DigitalOcean experienced an outage affecting its public API (api.digitalocean.com) and the Cloud Control Panel (cloud.digitalocean.com), causing errors for developers trying to access resources or manage their accounts. The issue began around Mar 27, 2025 5:56 PM UTC with engineers investigating, and by Mar 27, 2025 6:10 PM UTC the status page indicated the impact. The disruption affected two core components: API and Cloud Control Panel.

Two official updates were posted during the incident. The first at Mar 27, 2025 6:10 PM UTC confirmed the degraded state for API and Cloud Control Panel; the issue was resolved by 8:50 PM UTC, with services returning to normal. The outage lasted approximately 2 hours and 54 minutes.

DigitalOcean reported a metrics visibility issue in the Cloud Control Panel for Managed Databases. This impacted visibility of engine metrics for PostgreSQL, MySQL, Kafka, OpenSearch, and Caching database clusters, while MongoDB clusters were not affected. Storage metrics and alerts continued to function normally. The incident began at 10:25 PM UTC and was resolved by 5:45 AM UTC, lasting roughly 7 hours and 20 minutes. The DigitalOcean status page issued two updates during the incident as engineers worked to restore metric visibility.

DigitalOcean experienced a brief degraded experience affecting the Cloud Control Panel's Billing page for Teams. Users attempting to access or perform actions within Billing reported errors. The incident began at Mar 25, 2025 6:06 AM UTC and the degraded state appeared around Mar 25, 2025 6:10 AM UTC, with the service returning to normal by Mar 25, 2025 7:05 AM UTC.

The DigitalOcean Cloud Control Panel (cloud.digitalocean.com) experienced an outage affecting login and navigation for a period of about 3 hours 19 minutes. The incident began with an investigation at Mar 24, 2025 9:23 PM UTC, with the Cloud Control Panel degraded at Mar 24, 2025 9:26 PM UTC and escalating to a full outage by Mar 24, 2025 9:40 PM UTC. The panel was restored at Mar 25, 2025 12:45 AM UTC.

DigitalOcean issued three status updates detailing the progression and restoration. The outage was scoped to the Cloud Control Panel component; no other DigitalOcean services were indicated in the public updates. Users reported issues signing in and navigating within the panel during the incident.

DigitalOcean conducted scheduled maintenance on the LON1 network. The status page showed the maintenance as in progress from 8:00 PM UTC and completing by 10:45 PM UTC, with the Networking / LON1 component returning to an operational state after the maintenance window. The provider issued two status updates during the incident to communicate progress and completion. The maintenance appears localized to the LON1 networking, with no broader impact communicated across other DigitalOcean services.

DigitalOcean reported a brief partial outage affecting new user signups in the Cloud Control Panel. Between 4:25 PM UTC and 4:50 PM UTC UTC, some new users were unable to finish the signup process while engineers investigated the cause. DigitalOcean issued two official status updates during the incident, noting an ongoing investigation and a degraded signup experience. The issue appeared isolated to the signup workflow and did not indicate a broader service disruption. The outage lasted about 25 minutes, with the Cloud Control Panel returning to normal after the final update.

A connectivity issue impacted newly created DigitalOcean Managed Kubernetes nodes and their ability to connect to Droplets used to allow traffic via the cluster source, potentially causing Droplets to be omitted from the Cloud Firewall. A workaround is to add the tag k8s:CLUSTER_UUID to the cluster, where CLUSTER_UUID is the cluster's UUID. The incident began at Mar 10, 2025 12:05 PM UTC and was resolved by Mar 10, 2025 9:50 PM UTC, lasting about 9 hours and 45 minutes. DigitalOcean issued 2 status updates during the incident, and the issue appeared to affect the Kubernetes / Global component globally.

The DigitalOcean managed certificates service experienced a disruption caused by an unexpected outage from the issuing Certificate Authority. This degraded ability to create new certificates, provision or scale MongoDB clusters, and issue certificates for use with Load Balancers and CDN services. A subset of new custom domains on App Platform could take longer than usual to become active. The outage began at Mar 5, 2025 9:25 PM UTC and was resolved by Mar 5, 2025 11:55 PM UTC. The issue affected global components including Managed Databases, Spaces CDN, Load Balancers, and App Platform.