DigitalOcean Recovered. Check Your Changes.
DigitalOcean says a global VPC management disruption began at about 08:48 UTC on 5 October. Creating or deleting VPC peerings, VPC Native DOKS clusters and Private Network Connections could be delayed or fail. Routes, subnets and cluster-member changes may also have been affected. Existing VPC resources and connectivity remained unaffected.
DigitalOcean implemented a fix, cleared pending operations and says the disruption was resolved by 10:29 UTC. It reported stable operations at 12:13 UTC.
A recovery notice is not a change receipt
For an operator, those are two different checks. A working connection is useful evidence about traffic already taking that path. It does not, by itself, establish whether a requested configuration change produced the intended result. Treat the provider’s recovery notice as the point to reconcile your own work, not as a substitute for that reconciliation.
Start with the requests made during the incident window. For each one, retain the time, intended result and any returned reference or error. Then compare that record with the resources and configuration you can actually observe. This is particularly important before repeating a deletion or a batch of changes: decide what remains necessary rather than assuming that every earlier attempt failed in the same way.
Verify the result before retrying
Consider a planned connection between two services. Check that the required relationship exists and that the relevant service-to-service traffic works. If the change was meant to remove access, verify the intended separation as well. A successful connection and a successfully enforced restriction are different acceptance tests.
Where the result is still unclear, keep the request evidence together and resolve the uncertainty before a blind resubmission. The checks above are BlackTree’s operational recommendations, not a claim that a particular customer lost a resource or that every attempted change needs to be repeated. DigitalOcean advises contacting support if unexpected behaviour continues.
Source: DigitalOcean incident report, 5 October 2026.
Updated on 15 October 2026 to expand the operational guidance. The original 5 October publication date, incident chronology and URL are unchanged.
