Jul <var data-var='date'> 3</var>, <var data-var='time'>00:25</var> UTC 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.

Bicep deployments may fail after upgrading to 2026.3.4658 or later

May <var data-var='date'>30</var>, <var data-var='time'>00:38</var> UTC Resolved - Our upstream provider, Azure in West US2, has resolved their issue. While the issue was ongoing, some Octopus Cloud instances in West US2 may have experienced brief downtime and network communication issues. For more details, see Azure's incident report (Tracking ID: GHRP-84G) at https://azure.status.microsoft/en-us/status/history/. May <var data-var='date'>29</var>, <var data-var='time'>06:10</var> UTC 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.

Ability to deploy in West US 2 might be affected

May <var data-var='date'>18</var>, <var data-var='time'>10:49</var> UTC Resolved - We have pushed out a fix for this issue and it should be rolling out to Octopus Cloud customers over the next few days. Please contact support@octopus.com if you are seeing this issue and we can arrange to get your instance upgraded. May <var data-var='date'>15</var>, <var data-var='time'>12:36</var> UTC 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

Amazon ECS Service Steps fail with 'Container.image contains invalid cha...

May <var data-var='date'> 7</var>, <var data-var='time'>06:40</var> UTC Resolved - We have not observed any further issues in the West US 2 region so all Octopus Cloud instances in the West US 2 region are using dynamic workers in West US 2 once again. May <var data-var='date'> 7</var>, <var data-var='time'>00:51</var> UTC Update - We are continuing to monitor for any further issues. May <var data-var='date'> 5</var>, <var data-var='time'>13:43</var> UTC 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 <var data-var='date'> 5</var>, <var data-var='time'>13:25</var> UTC Update - 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 <var data-var='date'> 5</var>, <var data-var='time'>13:18</var> UTC 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.

Dynamic Worker issues in West US 2

Apr <var data-var='date'> 8</var>, <var data-var='time'>04:11</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'> 1</var>, <var data-var='time'>08:36</var> UTC Update - 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 = "[REGION]" for Powershell E.g export AWS_REGION=ap-southeast-2 $env:AWS_REGION = "ap-southeast-2" We apologise for the disruption and will share further updates as our investigation progresses. If you need help in the meantime, please contact us at support@octopus.com Apr <var data-var='date'> 1</var>, <var data-var='time'>08:06</var> UTC 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 = "<REGION_>" for Powershell E.g export AWS_REGION=ap-southeast-2 $env:AWS_REGION = "ap-southeast-2" We apologise for the disruption and will share further updates as our investigation progresses. If you need help in the meantime, please contact us at support@octopus.com

AWS Deployment Failures for Cloud Customers

Mar <var data-var='date'>30</var>, <var data-var='time'>12:43</var> UTC Resolved - We have identified the cause of this issue and have produced a fix in Octopus version 2026.2.3825. Please email support@octopus.com if you are seeing AWS region endpoint errors in your deployments similar to the one in the title and we can discuss upgrade options.

Deployments using AWS-dependent resources may fail with “No RegionEndpoint or ServiceURL configured.”

Mar <var data-var='date'>25</var>, <var data-var='time'>06:09</var> UTC Resolved - This incident has been resolved. Please don't hesitate to reach out to our support team if you are still having any related problems. Mar <var data-var='date'>24</var>, <var data-var='time'>05:58</var> UTC Monitoring - We have a resolution for the issue, and it should be rolled out to customer instances during their next maintenance windows. If this blocks your deployments in the meantime, please reach out to support. Mar <var data-var='date'>24</var>, <var data-var='time'>04:13</var> UTC Identified - The issue has been identified and a fix is being implemented. Mar <var data-var='date'>24</var>, <var data-var='time'>04:13</var> UTC Investigating - We have identified the cause and are working to complete it as quickly as possible. We will provide another update once the issue is resolved.

gRPC port (8443) shows Octopus Cloud instance is Undergoing Maintenance

Feb <var data-var='date'>26</var>, <var data-var='time'>05:47</var> UTC Resolved - Email services have now been restored. Please contact support@octopus.com if you encounter any issues with email delivery. Feb <var data-var='date'>26</var>, <var data-var='time'>05:32</var> UTC Update - Sign-in/sign-up emails have been restored. Note: emails will now be sent from donotreply@octopus.com Feb <var data-var='date'>26</var>, <var data-var='time'>05:11</var> UTC Update - We are continuing to work on a fix for this issue. Feb <var data-var='date'>26</var>, <var data-var='time'>01:51</var> UTC Identified - Our upstream email provider is currently experiencing issues delivering emails from Octopus. This impacts all emails, including email verification during authentication, Octopus Cloud subscription invitations, and billing notifications. We're currently investigating and will update this page when we know more.

Emails are currently not being delivered

Feb <var data-var='date'> 3</var>, <var data-var='time'>21:38</var> UTC Resolved - Azure has resolved the issue that was causing our Dynamic Workers lease failures and we haven't seen any additional failures since yesterday. Feb <var data-var='date'> 2</var>, <var data-var='time'>23:49</var> UTC Update - We are continuing to monitor for any further issues. Feb <var data-var='date'> 2</var>, <var data-var='time'>23:46</var> UTC Monitoring - Azure have rolled out a fix for this issue and we are seeing Dynamic Workers return to normal operation across all regions. Feb <var data-var='date'> 2</var>, <var data-var='time'>22:09</var> UTC Identified - Azure have identified the following issue on their side that affects the Dynamic Workers: Virtual Machines and dependent services - Service management issues in multiple regions. They are actively working to mitigate impact and expect it to be resolved by approximately 00:00 UTC. See Azure status page for additional details: https://azure.status.microsoft/en-gb/status Feb <var data-var='date'> 2</var>, <var data-var='time'>21:31</var> UTC Investigating - Octopus Cloud instances are failing to lease Ubuntu Dynamic Workers due to an issue with our upstream provider. We are currently investigating and working on mitigating the issue.

Ubuntu Dynamic Workers are failing to lease

Nov <var data-var='date'>25</var>, <var data-var='time'>14:57</var> UTC Resolved - Resolved. Nov <var data-var='date'>25</var>, <var data-var='time'>14:56</var> UTC Update - After monitoring the platform following our earlier mitigation, we can confirm that the issue has not resurfaced. OctopusID sign-in is functioning normally, and the incident has been resolved. Nov <var data-var='date'>25</var>, <var data-var='time'>14:00</var> UTC Monitoring - We have performed some changes that based on customer feedback, has mitigated this issue. We are still monitoring to ensure this issue does not reoccur, but customers should be able to sign in via OctopusID again. Nov <var data-var='date'>25</var>, <var data-var='time'>12:58</var> UTC Update - We are currently investigating issues with cloud customers accessing their instance via OctopusID. For some customers, this issue seems to be auto resolving after around 5 minutes. Whilst we are investigating the root cause, we recommend attempting to sign in whenever convenient incase you are able to access the instance. Nov <var data-var='date'>25</var>, <var data-var='time'>12:34</var> UTC Investigating - We are currently investigating issues with cloud customers accessing their instance via OctopusID. For some customers, this issue seems to be auto resolving after around 5 minutes. Whilst we are investigating the root cause, we recommend attempting to sign in whenever convenient incase you are able to access the instance.

OctopusID signin intermittent for cloud customers

Nov <var data-var='date'>19</var>, <var data-var='time'>00:47</var> UTC Resolved - We have observed no further errors stemming from this issue. Nov <var data-var='date'>18</var>, <var data-var='time'>22:01</var> UTC Monitoring - GitHub reports that git operations have been restored. We will continue to monitor this situation. Nov <var data-var='date'>18</var>, <var data-var='time'>21:11</var> UTC Identified - GitHub is experiencing issue with git operations, resulting in in-product git operations to be degraded or fail. We're continuing to monitor this upstream outage.

GitHub upstream outage causing issues with VCS-backed elements

Oct <var data-var='date'>30</var>, <var data-var='time'>01:13</var> UTC Resolved - All Octopus services affected by this outage are now operational. Oct <var data-var='date'>29</var>, <var data-var='time'>23:57</var> UTC Update - As we continue to monitor Octopus.com and Octopus services, metrics are showing services becoming more reliably available. We are still waiting for our upstream provider's resolution and expect to give another update approximately 1 hour from now (approximately 00:55 UTC on 30 October 2025). We will continue to provide additional updates as the situation necessitates. Oct <var data-var='date'>29</var>, <var data-var='time'>21:13</var> UTC Update - As we continue to monitor Octopus.com and Octopus services, metrics are showing services becoming more reliably available. Our upstream provider is currently estimating full or near full mitigation approximately 2 hours from now (approximately 23:20 UTC on 29 October 2025). We will provide additional updates as the situation necessitates. Oct <var data-var='date'>29</var>, <var data-var='time'>19:00</var> UTC Update - Customers may notice intermittent access to Octopus.com and Octopus services. Our upstream provider has made progress to mitigate the issue. We will continue to monitor the situation. We have contingency plans we are prepared to deploy if service recovery progress from the upstream provider mitigation stalls. Oct <var data-var='date'>29</var>, <var data-var='time'>16:39</var> UTC Identified - It appears this outage is due to a DNS issue with our upstream provider. We are currently awaiting for mitigation from the upstream provider to restore Octopus.com and related services. Oct <var data-var='date'>29</var>, <var data-var='time'>16:31</var> UTC Investigating - We are currently investigating the issue.

Octopus.com and billing portal may be unavailable in certain regions

Oct <var data-var='date'>21</var>, <var data-var='time'>01:11</var> UTC Resolved - Docker Hub have resolved their incident and we have not observed any further issues Oct <var data-var='date'>21</var>, <var data-var='time'>00:15</var> UTC Update - Most of the Docker Hub services seem to be operational and we are continuing to monitor the situation Oct <var data-var='date'>20</var>, <var data-var='time'>12:48</var> UTC Update - Most of the Docker Hub services seem to be operational but the incident is still on-going. Oct <var data-var='date'>20</var>, <var data-var='time'>12:44</var> UTC Monitoring - Docker Hub experienced issues that prevented access to container images, resulting in deployment failures for projects relying on those images. Oct <var data-var='date'>20</var>, <var data-var='time'>07:34</var> UTC Identified - Docker Hub experienced issues that prevented access to container images, resulting in deployment failures for projects relying on those images.

Docker Hub is down

Oct <var data-var='date'>13</var>, <var data-var='time'>00:24</var> UTC Resolved - This has been resolved. All missing tags have been published to DockerHub and we are seeing successful deployments using these new tags. Oct <var data-var='date'>12</var>, <var data-var='time'>23:45</var> UTC Monitoring - We have fixed the issue and pushed the missing tags to DockerHub. Kubernetes agent deployments should be working again. Oct <var data-var='date'>12</var>, <var data-var='time'>23:43</var> UTC 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.

Kubernetes deployments using Kubernetes agent may fail

Sep <var data-var='date'>25</var>, <var data-var='time'>04:18</var> UTC Resolved - The Docker Hub incident is resolved and we have not observed any ongoing issues. Sep <var data-var='date'>25</var>, <var data-var='time'>01:23</var> UTC Monitoring - Docker has implemented a fix and we are monitoring. Sep <var data-var='date'>25</var>, <var data-var='time'>01:06</var> UTC Identified - Docker Hub is experiencing an active incident: https://www.dockerstatus.com/pages/incident/533c6539221ae15e3f000031/68d47a2f93c09e05486d93a9 Octopus customers may experience issues pulling images from Docker Hub, including: 1. Octopus Server self-host images 2. Deployment process container images including execution containers and reference packages hosted by Docker Workarounds are available, please contact support@octopus.com.

Docker Hub authentication issues

Sep <var data-var='date'>15</var>, <var data-var='time'>06:05</var> UTC Resolved - The downstream issue with Azure CLI login commands has been resolved by Azure. Sep <var data-var='date'>15</var>, <var data-var='time'>05:57</var> UTC Monitoring - The downstream issue with running `az login` commands in Azure steps appears to be working again. We will be continuing to monitor this. Sep <var data-var='date'>15</var>, <var data-var='time'>03:11</var> UTC Investigating - We are investigating reports of intermittent Azure authentication issues during deployments and runbook runs. We are working with Microsoft to resolve this issue.

Intermittent Azure authentication issues

Sep <var data-var='date'> 5</var>, <var data-var='time'>03:50</var> UTC Resolved - This issue is resolved, please reach out to https://octopus.com/support if you are still experiencing deployments that fail to start. Sep <var data-var='date'> 4</var>, <var data-var='time'>02:31</var> UTC Monitoring - Symptom: The Deployment or Runbook appears to have started but has not produced any logs after an extended period of time. Mitigation: Manually cancel the Deployment or Runbook, then re-run the task. Please note that cancellation may take approximately 10 minutes. After the next maintenance window all affected tasks will be automatically cancelled. Please reach out to https://octopus.com/support if you would like tasks to be automatically cancelled earlier.

(Resolved) Some Deployments/Runbooks in Octopus Cloud may be failing to start

May <var data-var='date'>23</var>, <var data-var='time'>03:34</var> UTC Resolved - We have fixed the issue with the navigation bar on octopus.com/downloads May <var data-var='date'>23</var>, <var data-var='time'>03:27</var> UTC Monitoring - We have shipped a change to fix the navigation bar issue and are monitoring to ensure it works in all regions. May <var data-var='date'>23</var>, <var data-var='time'>01:40</var> UTC Identified - We have identified the issue with the top navigation bar loading and are working on a fix. May <var data-var='date'>22</var>, <var data-var='time'>23:35</var> UTC Investigating - octopus.com/downloads top navigation bar is failing to load correctly. We are investigating the cause. Links to downloads from this website are still correct. Please reload the page if you cannot see the content.

octopus.com/downloads degraded

Mar <var data-var='date'>28</var>, <var data-var='time'>13:10</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'>28</var>, <var data-var='time'>12:02</var> UTC Monitoring - We have uploaded a new version of the ECS Update step. Affected customers can manually force a re-acquisition of the updated packages via the following steps 1. Go to Tasks 2. Click Show Advanced filters 3. Check "Include System Tasks" 4. Select the "Acquire new steps and targets" from the Task Type 5. Choose the most previously run task 6. Select "Re-run" from the context menu (3 dots). Mar <var data-var='date'>28</var>, <var data-var='time'>11:54</var> UTC Identified - We are aware of an issue where a recent update has caused ECS Update steps to fail deployment.

ECS Update steps failing to execute

Mar <var data-var='date'> 5</var>, <var data-var='time'>22:23</var> UTC Resolved - Azure have advised us this issue has been mitigated. Octopus Cloud instances in the West Europe region were affected on 5 March from 6 AM to 5 PM UTC. Azure will be providing us with a Root Cause Analysis, after which we can share more information. Mar <var data-var='date'> 5</var>, <var data-var='time'>16:17</var> UTC Update - We continue to see issues with our upstream to instances within the WestEU region. We are awaiting further information from Azure. Mar <var data-var='date'> 5</var>, <var data-var='time'>14:17</var> UTC Investigating - Octopus Deploy is aware of performance issues for some customers on Octopus Cloud. Our engineers are investigating and we will provide an update soon.

Performance issues identified with Octopus Cloud

Feb <var data-var='date'>12</var>, <var data-var='time'>21:36</var> UTC Resolved - We've had no further reports of this issue following the certificate update, and customers have indicated that they are back up and deploying. If you encounter any further issues, please email support@octopus.com Feb <var data-var='date'>12</var>, <var data-var='time'>16:32</var> UTC Monitoring - We have updated the certificate chain on our host, which has resolved the verification issues. We are continuing to monitor the outcome of this change. Feb <var data-var='date'>12</var>, <var data-var='time'>13:47</var> UTC Investigating - We're investigating an issue with the v5 and below versions of the step 'Use Octopus CLI Tool' on build servers where customers are seeing the error 'unable to verify the first certificate'. This is currently affecting customer deployments due to not being able to install the depreciated version of the OctoCLI. The v6 versions of our ADO extension tasks do not require the OctoCLI so upgrading to our v6 steps will resolve this issue. Find out more information about the migration to the new step version here: https://octopus.com/blog/azure-devops-octopus-v6

ADO 'Use Octopus CLI Tool' step Certificate Issue

Feb <var data-var='date'> 4</var>, <var data-var='time'>03:07</var> UTC Resolved - Two seperate recent changes were identified as causes of the excess memory use. These changes have been rolled back, and we have confirmed through monitoring that memory use has returned to normal on the affected instances. No further crashes terminations have been observed. Jan <var data-var='date'>30</var>, <var data-var='time'>07:24</var> UTC Investigating - Internal monitoring notified us that a small number of Octopus Cloud instances were terminated for excess memory use up to 12 hours after a recent a software upgrade. These instances were automatically restarted and resumed functioning correctly. At this stage we are investigating to determine the cause of the excess memory use. If you believe you are affected by this issue please contact support@octopus.com

Intermittent service disruption for a small number of customers

Jan <var data-var='date'>27</var>, <var data-var='time'>22:21</var> UTC Resolved - This issue has been resolved and will be rolling out to Octopus Cloud customers in the next couple of days. If you are affected by this issue, please get in touch with support@octopus.com Jan <var data-var='date'>24</var>, <var data-var='time'>08:58</var> UTC Monitoring - We have fixed the issue, but due to timing and other factors will not be rolling this out immediately. If you are affected by this issue, please get in touch with support@octopus.com who can manually update your instance. Jan <var data-var='date'>24</var>, <var data-var='time'>01:35</var> UTC Identified - We have had reports of and have identified an issue with variable substitution with Helm template sources. We are tracking the fix here: https://github.com/OctopusDeploy/Issues/issues/9224

Some Octopus Cloud customers affected by missing variable substitution on Helm template sources

Jan <var data-var='date'>23</var>, <var data-var='time'>07:49</var> UTC Resolved - We are currently rolling out the fix to Cloud customers. Instances will be upgraded in their next maintenance window. If you are affected by this issue and want to expedite the upgrade, please contact support@octopus.com Jan <var data-var='date'>23</var>, <var data-var='time'>02:47</var> UTC Monitoring - A fix has been implemented and will be rolled out to affected cloud customers in their next maintenance window. Jan <var data-var='date'>23</var>, <var data-var='time'>01:42</var> UTC Identified - We have identified the issue with a recently released version of Octopus Server to cloud customers. A recent change has caused config maps with multi-line variables, created via the Kubernetes containers deployment step, to fail. Config maps created by the dedicated Kubernetes config map step are not affected, nor config maps created by Raw YAML or Helm steps. We are in the process of fixing this and will update the public issue with the fixed version: https://github.com/OctopusDeploy/Issues/issues/9221. Jan <var data-var='date'>22</var>, <var data-var='time'>17:47</var> UTC Investigating - We are currently investigating the issue

Some Octopus Cloud customers affected by parsing issue with ConfigMap on Kubernetes deployments

Jan <var data-var='date'>14</var>, <var data-var='time'>00:38</var> UTC Resolved - The Github incident has been resolved, we have confirmed that Config-as-Code project loading is working correctly Jan <var data-var='date'>14</var>, <var data-var='time'>00:12</var> UTC Identified - For customers using Github to store Config As Code projects, an ongoing incident (https://www.githubstatus.com/incidents/qd96yfgvmcf9) with Github is affecting the loading of those projects. There is no impact to projects that are using database storage.

Is Octopus Deploy down?

Octopus Deploy status is UP

Lastest published events

Bicep deployments may fail after upgrading to 2026.3.4658 or later

Ability to deploy in West US 2 might be affected

Amazon ECS Service Steps fail with 'Container.image contains invalid cha...

Octopus Deploy Services, Components and Regions

Recent Octopus Deploy events

Bicep deployments may fail after upgrading to 2026.3.4658 or later

Ability to deploy in West US 2 might be affected

Amazon ECS Service Steps fail with 'Container.image contains invalid cha...

Dynamic Worker issues in West US 2

AWS Deployment Failures for Cloud Customers

Deployments using AWS-dependent resources may fail with “No RegionEndpoint or ServiceURL configured.”

Get your FREE account now,
5 monitors included!

Is Octopus Deploy down?

Octopus Deploy status is UP

Lastest published events

Bicep deployments may fail after upgrading to 2026.3.4658 or later

Ability to deploy in West US 2 might be affected

Amazon ECS Service Steps fail with 'Container.image contains invalid cha...

Octopus Deploy Services, Components and Regions

Recent Octopus Deploy events

Bicep deployments may fail after upgrading to 2026.3.4658 or later

Ability to deploy in West US 2 might be affected

Amazon ECS Service Steps fail with 'Container.image contains invalid cha...

Dynamic Worker issues in West US 2

AWS Deployment Failures for Cloud Customers

Deployments using AWS-dependent resources may fail with “No RegionEndpoint or ServiceURL configured.”

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!