- Level
- confirmed
- Worst impact
- Degraded
- Components
- Octopus.com
- Regions
- us
- Down Index
- 25of 100
What to do
Check whether you use Octopus Deploy Octopus.com in us. 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 4h 19m it lasted.
Anything that failed between 2026-07-23 16:08 UTC and 2026-07-23 20:28 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
- identified
Due to upstream Azure issues in the West US region, some services may have no or intermittent connectivity. We are continuing to monitor the impact on our systems.
provider
- identified
Known impacted services: - The Octopus.com blog
provider
- monitoring
Azure's mitigation has allowed access to the impacted services. We will continue to monitor service availability.
provider
- resolved
Azure has resolved this issue.
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-6f965ed765
Is Octopus Deploy still down?
No, this incident was resolved 2026-07-23 20:28 UTC. For Octopus Deploy's live state, see https://down.guide/octopus.
How long did it last?
4h 19m, from 2026-07-23 16:08 UTC to 2026-07-23 20:28 UTC, by the times Octopus Deploy posted.
What was affected?
Octopus Deploy named Octopus.com in us.
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.