- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Octopus Cloud
- Down Index
- 36of 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 5d 1h it lasted.
Anything that failed between 2023-12-08 01:23 UTC and 2023-12-13 02:45 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 6
- investigating
Since the morning of Friday 8th December, cloud customers are reporting issues with communicating to listening and polling tentacles. We are investigating this as a priority incident and will work on a resolution as soon as possible.
provider
- investigating
We have identified a suspected root cause and workaround. We suspect this is limited to certificates using a SHA1 algorithm but are investigating further. If affected please try the workaround detailed in this issue: https://github.com/OctopusDeploy/Issues/issues/8523
provider
- identified
The underlying cause has been identified. The issue is currently isolated to cloud customers. A fix is actively being work on.
provider
- monitoring
A fix has been created and is being rolled out to affected customers. This issue affects instances of Tentacle that use SHA1 (an old, unsupported, encryption algorithm), and prevents them from connecting to Octopus Cloud. This was a side effect of the Octopus Server .NET 8 upgrade, and the resulting change to the underlying OS from Debian 11/OpenSSL 1.x to Debian 12/OpenSSL 3.x. If you continue to be affected by this issue, please try the workaround detailed at https://github.com/OctopusDeploy/Issues/issues/8523, or contact support at https://octopus.com/support.
provider
- monitoring
We have identified customers that were most likely affected. and prioritized applying the fix to these customers on the 9th and 10th of December. Rollout continues to all remaining customers, and we anticipate this to be complete by the 12th of December.
provider
- resolved
All Octopus Cloud customers have been upgraded to fixed software versions, resolving this incident. Self-hosted customers were not affected.
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-2ca693dcdd
Is Octopus Deploy still down?
No, this incident was resolved 2023-12-13 02:45 UTC. For Octopus Deploy's live state, see https://down.guide/octopus.
How long did it last?
5d 1h, from 2023-12-08 01:23 UTC to 2023-12-13 02:45 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.