- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 27of 100
What to do
Check whether your product depends on Octopus Deploy. 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 41m it lasted.
Anything that failed between 2025-10-12 23:43 UTC and 2025-10-13 00:24 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 3
- identified
We have identified an issue where Kubernetes deployments using the Kubernetes agent may fail due to a failure to pull the octopusdeploy/kubernetes-agent-tools-base docker image.
provider
- monitoring
We have fixed the issue and pushed the missing tags to DockerHub. Kubernetes agent deployments should be working again.
provider
- resolved
This has been resolved. All missing tags have been published to DockerHub and we are seeing successful deployments using these new tags.
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-cf783c32e0
Is Octopus Deploy still down?
No, this incident was resolved 2025-10-13 00:24 UTC. For Octopus Deploy's live state, see https://down.guide/octopus.
How long did it last?
41m, from 2025-10-12 23:43 UTC to 2025-10-13 00:24 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.