- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Octopus Cloud
- Down Index
- 28of 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 26m it lasted.
Anything that failed between 2025-01-14 00:12 UTC and 2025-01-14 00:38 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 2
- identified
For customers using Github to store Config As Code projects, an ongoing incident (https://www.githubstatus.com/incidents/qd96yfgvmcf9) with Github is affecting the loading of those projects. There is no impact to projects that are using database storage.
provider
- resolved
The Github incident has been resolved, we have confirmed that Config-as-Code project loading is working correctly
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-9f3db57db4
Is Octopus Deploy still down?
No, this incident was resolved 2025-01-14 00:38 UTC. For Octopus Deploy's live state, see https://down.guide/octopus.
How long did it last?
26m, from 2025-01-14 00:12 UTC to 2025-01-14 00:38 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.