Octopus Deploy Outage History
Uptime record, past incidents, and downtime history for Octopus Deploy.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| June 2026 | 100% | 27 | 0 |
| May 2026 | 71% | 31 | 9 |
| April 2026 | 73.3% | 30 | 8 |
| March 2026 | 100% | 3 | 0 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Mar 29
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
May 2026
Ability to deploy in West US 2 might be affected
Started: May 29, 6:10 AM
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.
May 29, 6:10 AM
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
Started: May 15, 12:36 PM
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
May 15, 12:36 PM
Dynamic Worker issues in West US 2
Started: May 5, 1:18 PM
monitoring
We are continuing to monitor for any further issues.
May 7, 12:51 AM
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.
May 5, 1:43 PM
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.
May 5, 1:25 PM
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.
May 5, 1:18 PM
April 2026
AWS Deployment Failures for Cloud Customers
Started: Apr 1, 8:36 AM
investigating
We are aware of an issue affecting Octopus Cloud customers running deployments that interact with AWS, including EKS/Kubernetes targets and AWS health checks. Impacted customers may see authentication errors when running these deployments.
Our team is actively investigating and working to resolve the issue.
Workaround:
If you are affected, adding your AWS region as an environment variable in your script steps may resolve the issue:
export AWS_REGION=[REGION] for Bash
$env:AWS_REGION = "[RE...
Apr 1, 8:36 AM
investigating
We are aware of an issue affecting Octopus Cloud customers running deployments that interact with AWS, including EKS/Kubernetes targets and AWS health checks. Impacted customers may see authentication errors when running these deployments.
Our team is actively investigating and working to resolve the issue.
Workaround:
If you are affected, adding your AWS region as an environment variable in your script steps may resolve the issue:
export AWS_REGION=<REGION> for Bash
$env:AWS_REGION = "<RE...
Apr 1, 8:06 AM