- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Octopus Cloud
- Regions
- us
What to do
Check whether you use Octopus Deploy Octopus Cloud in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1d 17h it lasted.
Anything that failed between 2026-05-05 13:18 UTC and 2026-05-07 06:40 UTC may need a replay.Subscribe to Octopus Deploy's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=octopus works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Octopus Deploy 5
- identified
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.
provider
- identified
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.
provider
- monitoring
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.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- resolved
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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-db6f387f24
Is Octopus Deploy still down?
No, this incident was resolved 2026-05-07 06:40 UTC. For Octopus Deploy's live state, see https://down.guide/octopus.
How long did it last?
1d 17h, from 2026-05-05 13:18 UTC to 2026-05-07 06:40 UTC, by the times Octopus Deploy posted.
What was affected?
Octopus Deploy named Octopus Cloud in us.
What caused it?
Octopus Deploy hasn't published a root cause. If it does, it shows here.
Where does this come from?
Octopus Deploy's official status page, https://status.octopus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.