- Level
- confirmed
- Worst impact
- Partial outage
What to do
Check whether your product depends on Octopus Deploy. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 49m it lasted.
Anything that failed between 2025-01-07 00:20 UTC and 2025-01-07 03:10 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 4
- investigating
We are currently investigating the issue.
provider
- identified
14 Instances are down at this time. We've identified the issue and are working to restore services as a matter of priority.
provider
- monitoring
Root cause has been identified and mitigated. All Instances are now running. Further updates will be provided shortly.
provider
- resolved
All affected Instances are now up and healthy.
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-e5d9f1a868
Is Octopus Deploy still down?
No, this incident was resolved 2025-01-07 03:10 UTC. For Octopus Deploy's live state, see https://down.guide/providers/octopus.
How long did it last?
2h 49m, from 2025-01-07 00:20 UTC to 2025-01-07 03:10 UTC, by the times Octopus Deploy posted.
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.