- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Octopus Cloud
- Down Index
- 21of 100
What to do
Check whether you use Octopus Deploy Octopus Cloud. 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 0m it lasted.
Anything that failed between 2026-03-30 12:43 UTC and 2026-03-30 12:43 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 1
- resolved
We have identified the cause of this issue and have produced a fix in Octopus version 2026.2.3825. Please email support@octopus.com if you are seeing AWS region endpoint errors in your deployments similar to the one in the title and we can discuss upgrade options.
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-90e980f18d
Is Octopus Deploy still down?
No, this incident was resolved 2026-03-30 12:43 UTC. For Octopus Deploy's live state, see https://down.guide/octopus.
How long did it last?
0m, from 2026-03-30 12:43 UTC to 2026-03-30 12:43 UTC, by the times Octopus Deploy posted.
What was affected?
Octopus Deploy named Octopus Cloud.
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.