New AI Incident Response, Multi-Region Agents, and Custom-Domain Status Pages, May 2026
Monitor Features overview Vendor status Uptime & synthetic checks SSL monitoring Operate Incident management Live demo
By team SaaS engineering IT & help desk MSPs & service providers By industry Ecommerce AI product teams Education IT By goal Replace your stack Why ServiceAlert Competitor comparisons Alternatives directory By signal Reliability hub   · Uptime rankings   · SLA compliance Outage map
Services
Check & scan Coverage wizard SSL security grader Status checker DNS lookup Response time WHOIS lookup Calculators SLA calculator Downtime calculator Embed Status badges All tools →
Pricing
Guides Help center Uptime monitoring RUM & analytics Teams & shared monitors Developer API reference Status badges Learn Blog Outage reports FAQ Changelog
Dashboard

Octopus Deploy Outage History

Uptime record, past incidents, and downtime history for Octopus Deploy.

Checking current status...
59.3% uptime over 91 days
99.9% ✗ 99.5% ✗ 99% ✗ 95% ✗

90-Day Trend

May 18Aug 15

Monthly Uptime

Month Uptime Days Tracked Days with Issues
August 2026 73.3% 15 4
July 2026 6.5% 31 29
June 2026 100% 30 0
May 2026 73.3% 15 4

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)

May 17 Today
Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

July 2026
https://g.octopushq.com Certificate issues
major

Started: Jul 31, 1:32 PM

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.
Jul 31, 2:02 PM
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.
Jul 31, 1:32 PM
Service connectivity issues due to upstream Azure outage
minor

Started: Jul 23, 4:08 PM

monitoring
Azure's mitigation has allowed access to the impacted services. We will continue to monitor service availability.
Jul 23, 6:35 PM
identified
Known impacted services: - The Octopus.com blog
Jul 23, 4:09 PM
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.
Jul 23, 4:08 PM
Bicep deployments may fail after upgrading to 2026.3.4658 or later
major

Started: Jul 3, 12:25 AM

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.
Jul 3, 12:25 AM
May 2026
Ability to deploy in West US 2 might be affected
minor

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
major

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
major

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
major

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
View live status for Octopus Deploy Browse all services