Daily provider-status observations and published incident history for Octopus Deploy.
Unknown
Current status for Octopus Deploy cannot be verified right now. Verified .
Official provider source.
Looking for an update now? Check the current status, or follow Octopus Deploy for future changes.
100%of 83 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
October 2026
100%
31
0
September 2026
100%
30
0
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Aug 17Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
This issue appears to have been intermittent and likely caused by an external service. We're currently monitoring for further reports.
investigating
We're currently investigating this issue. This appears to only have affected a few instances.
investigating
We're currently investigating this issue.
investigating
Currently investigating
Legacy Incident Archive
6 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
July 2026
https://g.octopushq.com Certificate issues
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have identified and mitigated the certificate issues for https://g.octopushq.com with our URL Shortening service.
All g.octopushq.com URLs should now present the certificate. Most notably, customers should now be able to download the Octopus CLI tooling when using step versions earlier than 6.
Please email support@octopus.com if you are still seeing issues, we will continue to monitor this over the next few hours.
investigating
We are currently investigating issues with our certificate for https://g.octopushq.com. Customers may see issues with build servers trying to download the CLI using V5 and below build server steps.
Service connectivity issues due to upstream Azure outage
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Azure's mitigation has allowed access to the impacted services. We will continue to monitor service availability.
identified
Known impacted services:
- The Octopus.com blog
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.
Bicep deployments may fail after upgrading to 2026.3.4658 or later
majorSource not attested
Last archived state: resolved
View archived record details
identified
We have identified an issue in Octopus Server 2026.3.4658 or later when existing Bicep deployments may start failing.
We have a public issue tracking this with a workaround https://github.com/OctopusDeploy/Issues/issues/10129
We are working on a fix and will update this incident and the public issue when it's resolved.
May 2026
Ability to deploy in West US 2 might be affected
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Our upstream provider, Azure in West US2, is currently experiencing an issue which might be affecting your ability to deploy.
We will resolve this incident once we have received confirmation the issue has been resolved from our upstream provider.
Amazon ECS Service Steps fail with 'Container.image contains invalid characters' if using a container definition image package ID with a forward slash in it
majorSource not attested
Last archived state: resolved
View archived record details
identified
We have identified the issue and are working on a fix. If you are experiencing this please see the Github issue below for workarounds - https://github.com/OctopusDeploy/Issues/issues/10026
Dynamic Worker issues in West US 2
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
We have completed switching Octopus Cloud instances in the West US 2 region to use dynamic workers in our standby region (Central US). This should mitigate this issue for all customers.
We will update this incident when dynamic workers in West US 2 are stable and we have reverted all Cloud instances back to using workers in West US 2.
identified
We are in the process of switching Octopus Cloud instances in the West US 2 region to use dynamic workers in our standby region (Central US). Customers who have experienced leasing failures should retry their deployments or runbook runs.
identified
We have observed issues provisioning Dynamic Workers in our West US 2 region. We are working on mitigations and monitoring.
A small number of customers have experienced lease failures.
