Octopus experienced a major incident on May 5, 2026 affecting Octopus Cloud, lasting 1d 17h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 05, 2026, 01:18 PM UTC
We have observed issues provisioning Dynamic Workers in our West US 2 region. We are working on mitigations and monitoring. A small number of customers have experienced lease failures.
- identified May 05, 2026, 01:25 PM UTC
We are in the process of switching Octopus Cloud instances in the West US 2 region to use dynamic workers in our standby region (Central US). Customers who have experienced leasing failures should retry their deployments or runbook runs.
- monitoring May 05, 2026, 01:43 PM UTC
We have completed switching Octopus Cloud instances in the West US 2 region to use dynamic workers in our standby region (Central US). This should mitigate this issue for all customers. We will update this incident when dynamic workers in West US 2 are stable and we have reverted all Cloud instances back to using workers in West US 2.
- monitoring May 07, 2026, 12:51 AM UTC
We are continuing to monitor for any further issues.
- resolved May 07, 2026, 06:40 AM UTC
We have not observed any further issues in the West US 2 region so all Octopus Cloud instances in the West US 2 region are using dynamic workers in West US 2 once again.