DigitalOcean Outage History

DigitalOcean conducted scheduled maintenance on the NYC3 networking path beginning at 10:00 PM UTC and ending at 12:00 AM UTC. The maintenance affected traffic routed through NYC3, resulting in a brief outage for users relying on that region. The outage lasted approximately 2 hours and was resolved when services returned to normal after the maintenance window. DigitalOcean communicated the maintenance through their status updates, noting the ongoing work and subsequent restoration as the window closed.

DigitalOcean reported an issue affecting managed Kubernetes provisioning and cluster management operations in the TOR1 region. Some users may have experienced errors provisioning new Kubernetes clusters or applying changes to existing clusters, while workloads on TOR1 clusters remained unaffected. The incident began on Oct 6, 2025 6:20 PM UTC and was resolved by Oct 6, 2025 7:15 PM UTC, lasting about 55 minutes. DigitalOcean posted a status update during the incident to inform users, and the issue was scoped to the TOR1 region.

DigitalOcean reported degraded connectivity affecting PostgreSQL Managed Databases clusters across all regions that use PGBouncer and some legacy MD5 passwords. This caused connection failures and latency for applications relying on these databases. The outage began at 12:10 AM UTC and was resolved by 6:10 AM UTC, lasting roughly six hours. DigitalOcean issued two status updates during the incident to communicate findings and recovery progress, with the affected component being Managed Databases / Global.

DigitalOcean conducted scheduled network maintenance for the SFO3 data center. The Networking / SFO3 component transitioned to maintenance at 11:00 AM UTC and returned to normal at 2:00 PM UTC, with the maintenance window lasting about 3 hours. The work was regional to the SFO3 network, and users relying on that region may have experienced connectivity interruptions during the window. DigitalOcean posted two status updates during the incident to communicate progress and resolution.

DigitalOcean performed scheduled maintenance on the Networking / LON1 component starting at 5:00 PM UTC and completing by 8:00 PM UTC. The maintenance led to degraded performance and intermittent errors for users relying on the LON1 network. The London-based LON1 region was affected, and the window lasted about 3 hours. DigitalOcean posted two status updates during the incident, one to announce the maintenance and another to confirm its completion.

DigitalOcean reported intermittent networking issues in the BLR1 region beginning at 14:30 UTC, with users experiencing packet loss, latency, and timeouts when accessing Droplets, LBaaS, Managed Kubernetes, and Managed Database in BLR1. The impact was regional, affecting connectivity to services hosted in this zone rather than the entire platform.

The status page noted ongoing investigation and listed the BLR1 Networking component as degraded. The incident prompted 2 official updates before resolution. The issue was resolved by 19:40 UTC, with connectivity restored for BLR1; the outage lasted approximately 5 hours and 10 minutes, from 2:30 PM UTC to 7:40 PM UTC.

DigitalOcean reported a regional networking issue in the BLR1 region, causing connectivity disruptions to Droplets and Droplet-based services, including Managed Kubernetes and Database Clusters. The impact was limited to the BLR1 region with no indication of a global outage.

The incident began at 1:20 PM UTC and was resolved by 2:00 PM UTC, lasting approximately 40 minutes. DigitalOcean issued two status updates during the incident as engineers investigated the issue and then restored normal operation for the BLR1 networking component.

DigitalOcean reported a brief regional degradation in the FRA1 area impacting Spaces and related services. Users may have experienced slow performance or limited availability when accessing Spaces or its objects via the Control Panel or API, and Container Registry access could also be affected. The impact appeared confined to the FRA1 region and did not indicate a broader outage.

The incident began at 10:30 AM UTC and affected components included Spaces / FRA1, Spaces CDN / FRA1, and Container Registry / FRA1. DigitalOcean issued 2 status updates during the incident and services were restored by 10:35 AM UTC.

DigitalOcean experienced a brief degradation in the FRA1 region affecting Spaces (and Spaces CDN) and Container Registry access. The impact was localized to FRA1, with users potentially encountering slow performance or limited availability when accessing Spaces objects via the Control Panel or API, and container image operations could have been disrupted. The provider issued 2 status updates during the incident.

DigitalOcean reported a DNS incident affecting the .space domain registry, causing some websites to be inaccessible and zone files not appearing in DNS results. The issue was isolated to the DNS service and did not indicate a broader platform failure.

The incident began at Sep 24, 2025 3:15 PM UTC and was resolved by Sep 24, 2025 7:10 PM UTC, lasting approximately 3 hours and 55 minutes. DigitalOcean issued 2 status updates during the incident to communicate progress, and engineers confirmed the issue was with the domain registry and upstream providers.