Octopus Outage History

Octopus is up right now

Octopus had 32 outages in the last 2 years totaling 1342h 53m of downtime — averaging 1.3 incidents per month.

There were 32 Octopus outages since November 20, 2024 totaling 1342h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.octopus.com

Major October 5, 2026

Permissions not being applied correctly

Detected by Pingoru
Oct 05, 2026, 03:48 PM UTC
Resolved
Oct 05, 2026, 11:56 PM UTC
Duration
8h 7m
Timeline · 5 updates
  1. investigating Oct 05, 2026, 03:48 PM UTC

    Currently investigating

  2. investigating Oct 05, 2026, 03:53 PM UTC

    We're currently investigating this issue.

  3. investigating Oct 05, 2026, 04:46 PM UTC

    We're currently investigating this issue. This appears to only have affected a few instances.

  4. monitoring Oct 05, 2026, 05:06 PM UTC

    This issue appears to have been intermittent and likely caused by an external service. We're currently monitoring for further reports.

  5. resolved Oct 05, 2026, 11:56 PM UTC

    We've identified and resolved an issue (https://github.com/OctopusDeploy/Issues/issues/10288) that resulted in users being unable to view the audit log page. This is fixed from 2026.4.6234.

Read the full incident report →

Major July 31, 2026

https://g.octopushq.com Certificate issues

Detected by Pingoru
Jul 31, 2026, 01:32 PM UTC
Resolved
Jul 31, 2026, 03:04 PM UTC
Duration
1h 31m
Affected: Octopus.comOctopus Cloud
Timeline · 3 updates
  1. investigating Jul 31, 2026, 01:32 PM UTC

    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. Customers may also see issues with octopus.com.

  2. monitoring Jul 31, 2026, 02:02 PM UTC

    We have identified and mitigated the certificate issues for https://g.octopushq.com. Customers should now be able to download the CLI using V5 and below build server steps. Any certificate issues with octopus.com should now be resolved. Please email [email protected] if you are still seeing issues, we will continue to monitor this over the next few hours.

  3. resolved Jul 31, 2026, 03:04 PM UTC

    This issue has now been resolved. Thank you for your patience whilst we investigated the incident. If you are having any further issues please email [email protected].

Read the full incident report →

Minor July 23, 2026

Service connectivity issues due to upstream Azure outage

Detected by Pingoru
Jul 23, 2026, 04:08 PM UTC
Resolved
Jul 23, 2026, 08:28 PM UTC
Duration
4h 19m
Affected: Octopus.com
Timeline · 4 updates
  1. identified Jul 23, 2026, 04:08 PM UTC

    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.

  2. identified Jul 23, 2026, 04:09 PM UTC

    Known impacted services: - The Octopus.com blog

  3. monitoring Jul 23, 2026, 06:35 PM UTC

    Azure's mitigation has allowed access to the impacted services. We will continue to monitor service availability.

  4. resolved Jul 23, 2026, 08:28 PM UTC

    Azure has resolved this issue.

Read the full incident report →

Major July 3, 2026

Bicep deployments may fail after upgrading to 2026.3.4658 or later

Detected by Pingoru
Jul 03, 2026, 12:25 AM UTC
Resolved
Aug 04, 2026, 12:23 PM UTC
Duration
32d 11h
Timeline · 2 updates
  1. identified Jul 03, 2026, 12:25 AM UTC

    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.

  2. resolved Aug 04, 2026, 12:23 PM UTC

    The fix has been live across all Octopus Cloud servers for several weeks now without further issues.

Read the full incident report →

Minor May 29, 2026

Ability to deploy in West US 2 might be affected

Detected by Pingoru
May 29, 2026, 06:10 AM UTC
Resolved
May 30, 2026, 12:38 AM UTC
Duration
18h 28m
Affected: Octopus Cloud
Timeline · 2 updates
  1. monitoring May 29, 2026, 06:10 AM UTC

    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.

  2. resolved May 30, 2026, 12:38 AM UTC

    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/.

Read the full incident report →

Major May 15, 2026

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

Detected by Pingoru
May 15, 2026, 12:36 PM UTC
Resolved
May 18, 2026, 10:49 AM UTC
Duration
2d 22h
Affected: Octopus Cloud
Timeline · 2 updates
  1. identified May 15, 2026, 12:36 PM UTC

    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

  2. resolved May 18, 2026, 10:49 AM UTC

    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 [email protected] if you are seeing this issue and we can arrange to get your instance upgraded.

Read the full incident report →

Major May 5, 2026

Dynamic Worker issues in West US 2

Detected by Pingoru
May 05, 2026, 01:18 PM UTC
Resolved
May 07, 2026, 06:40 AM UTC
Duration
1d 17h
Affected: Octopus Cloud
Timeline · 5 updates
  1. identified May 05, 2026, 01:18 PM UTC

    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.

  2. identified May 05, 2026, 01:25 PM UTC

    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.

  3. monitoring May 05, 2026, 01:43 PM UTC

    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.

  4. monitoring May 07, 2026, 12:51 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved May 07, 2026, 06:40 AM UTC

    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.

Read the full incident report →

Major April 1, 2026

AWS Deployment Failures for Cloud Customers

Detected by Pingoru
Apr 01, 2026, 08:36 AM UTC
Resolved
Apr 08, 2026, 04:11 AM UTC
Duration
6d 19h
Affected: Octopus Cloud
Timeline · 3 updates
  1. investigating Apr 01, 2026, 08:06 AM UTC

    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= for Bash $env:AWS_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 [email protected]

  2. investigating Apr 01, 2026, 08:36 AM UTC

    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 [email protected]

  3. resolved Apr 08, 2026, 04:11 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 30, 2026

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

Detected by Pingoru
Mar 30, 2026, 12:43 PM UTC
Resolved
Mar 30, 2026, 12:43 PM UTC
Duration
—
Affected: Octopus Cloud
Timeline · 1 update
  1. resolved Mar 30, 2026, 12:43 PM UTC

    We have identified the cause of this issue and have produced a fix in Octopus version 2026.2.3825. Please email [email protected] if you are seeing AWS region endpoint errors in your deployments similar to the one in the title and we can discuss upgrade options.

Read the full incident report →

Major March 24, 2026

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

Detected by Pingoru
Mar 24, 2026, 04:13 AM UTC
Resolved
Mar 25, 2026, 06:09 AM UTC
Duration
1d 1h
Affected: Octopus Cloud
Timeline · 4 updates
  1. investigating Mar 24, 2026, 04:13 AM UTC

    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.

  2. identified Mar 24, 2026, 04:13 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Mar 24, 2026, 05:58 AM UTC

    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.

  4. resolved Mar 25, 2026, 06:09 AM UTC

    This incident has been resolved. Please don't hesitate to reach out to our support team if you are still having any related problems.

Read the full incident report →

Major February 26, 2026

Emails are currently not being delivered

Detected by Pingoru
Feb 26, 2026, 01:51 AM UTC
Resolved
Feb 26, 2026, 05:47 AM UTC
Duration
3h 55m
Affected: Octopus CloudControl Center (billing.octopus.com)Sign-in/Sign-up (octopus.com)
Timeline · 4 updates
  1. identified Feb 26, 2026, 01:51 AM UTC

    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.

  2. identified Feb 26, 2026, 05:11 AM UTC

    We are continuing to work on a fix for this issue.

  3. identified Feb 26, 2026, 05:32 AM UTC

    Sign-in/sign-up emails have been restored. Note: emails will now be sent from [email protected]

  4. resolved Feb 26, 2026, 05:47 AM UTC

    Email services have now been restored. Please contact [email protected] if you encounter any issues with email delivery.

Read the full incident report →

Major November 18, 2025

GitHub upstream outage causing issues with VCS-backed elements

Detected by Pingoru
Nov 18, 2025, 09:11 PM UTC
Resolved
Nov 19, 2025, 12:47 AM UTC
Duration
3h 36m
Timeline · 3 updates
  1. identified Nov 18, 2025, 09:11 PM UTC

    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.

  2. monitoring Nov 18, 2025, 10:01 PM UTC

    GitHub reports that git operations have been restored. We will continue to monitor this situation.

  3. resolved Nov 19, 2025, 12:47 AM UTC

    We have observed no further errors stemming from this issue.

Read the full incident report →

Critical October 29, 2025

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

Detected by Pingoru
Oct 29, 2025, 04:31 PM UTC
Resolved
Oct 30, 2025, 01:13 AM UTC
Duration
8h 41m
Affected: Octopus.comOctopus CloudControl Center (billing.octopus.com)Octopus GitHub AppSign-in/Sign-up (octopus.com)
Timeline · 6 updates
  1. investigating Oct 29, 2025, 04:31 PM UTC

    We are currently investigating the issue.

  2. identified Oct 29, 2025, 04:39 PM UTC

    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.

  3. identified Oct 29, 2025, 07:00 PM UTC

    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.

  4. identified Oct 29, 2025, 09:13 PM UTC

    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.

  5. identified Oct 29, 2025, 11:57 PM UTC

    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.

  6. resolved Oct 30, 2025, 01:13 AM UTC

    All Octopus services affected by this outage are now operational.

Read the full incident report →

Major October 20, 2025

Docker Hub is down

Detected by Pingoru
Oct 20, 2025, 07:34 AM UTC
Resolved
Oct 21, 2025, 01:11 AM UTC
Duration
17h 37m
Affected: Octopus.comOctopus Cloud
Timeline · 5 updates
  1. identified Oct 20, 2025, 07:34 AM UTC

    Docker Hub experienced issues that prevented access to container images, resulting in deployment failures for projects relying on those images.

  2. monitoring Oct 20, 2025, 12:44 PM UTC

    Docker Hub experienced issues that prevented access to container images, resulting in deployment failures for projects relying on those images.

  3. monitoring Oct 20, 2025, 12:48 PM UTC

    Most of the Docker Hub services seem to be operational but the incident is still on-going.

  4. monitoring Oct 21, 2025, 12:15 AM UTC

    Most of the Docker Hub services seem to be operational and we are continuing to monitor the situation

  5. resolved Oct 21, 2025, 01:11 AM UTC

    Docker Hub have resolved their incident and we have not observed any further issues

Read the full incident report →

Major October 12, 2025

Kubernetes deployments using Kubernetes agent may fail

Detected by Pingoru
Oct 12, 2025, 11:43 PM UTC
Resolved
Oct 13, 2025, 12:24 AM UTC
Duration
41m
Timeline · 3 updates
  1. identified Oct 12, 2025, 11:43 PM UTC

    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.

  2. monitoring Oct 12, 2025, 11:45 PM UTC

    We have fixed the issue and pushed the missing tags to DockerHub. Kubernetes agent deployments should be working again.

  3. resolved Oct 13, 2025, 12:24 AM UTC

    This has been resolved. All missing tags have been published to DockerHub and we are seeing successful deployments using these new tags.

Read the full incident report →

Major September 25, 2025

Docker Hub authentication issues

Detected by Pingoru
Sep 25, 2025, 01:06 AM UTC
Resolved
Sep 25, 2025, 04:18 AM UTC
Duration
3h 12m
Affected: Octopus.comOctopus Cloud
Timeline · 4 updates
  1. identified Sep 25, 2025, 01:06 AM UTC

    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 [email protected].

  2. monitoring Sep 25, 2025, 01:23 AM UTC

    Docker has implemented a fix and we are monitoring.

  3. resolved Sep 25, 2025, 04:18 AM UTC

    The Docker Hub incident is resolved and we have not observed any ongoing issues.

  4. postmortem Oct 09, 2025, 03:37 AM UTC

    # **Incident Summary** Docker Hub experienced authentication issues that prevented access to container images, resulting in deployment failures for projects relying on those images. ## **What We're Doing** Following this incident, we've identified several improvements to enhance service resilience and customer communication: ### **Visibility & Monitoring** * Communicate third-party service outages more clearly on our status page * Explore in-app messaging to alert customers during service disruptions ### **Resilience & Good Practices** * Review image retrieval reliability and address identified risks * Share good practices with customers to help reduce impacts when Docker Hub is unavailable

Read the full incident report →

Major September 15, 2025

Intermittent Azure authentication issues

Detected by Pingoru
Sep 15, 2025, 03:11 AM UTC
Resolved
Sep 15, 2025, 06:05 AM UTC
Duration
2h 54m
Affected: Octopus Cloud
Timeline · 3 updates
  1. investigating Sep 15, 2025, 03:11 AM UTC

    We are investigating reports of intermittent Azure authentication issues during deployments and runbook runs. We are working with Microsoft to resolve this issue.

  2. monitoring Sep 15, 2025, 05:57 AM UTC

    The downstream issue with running `az login` commands in Azure steps appears to be working again. We will be continuing to monitor this.

  3. resolved Sep 15, 2025, 06:05 AM UTC

    The downstream issue with Azure CLI login commands has been resolved by Azure.

Read the full incident report →

Minor September 4, 2025

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

Detected by Pingoru
Sep 04, 2025, 02:31 AM UTC
Resolved
Sep 05, 2025, 03:50 AM UTC
Duration
1d 1h
Affected: Octopus Cloud
Timeline · 2 updates
  1. monitoring Sep 04, 2025, 02:31 AM UTC

    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.

  2. resolved Sep 05, 2025, 03:50 AM UTC

    This issue is resolved, please reach out to https://octopus.com/support if you are still experiencing deployments that fail to start.

Read the full incident report →

Minor May 22, 2025

octopus.com/downloads degraded

Detected by Pingoru
May 22, 2025, 11:35 PM UTC
Resolved
May 23, 2025, 03:34 AM UTC
Duration
3h 59m
Affected: Octopus.com
Timeline · 4 updates
  1. investigating May 22, 2025, 11:35 PM UTC

    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.

  2. identified May 23, 2025, 01:40 AM UTC

    We have identified the issue with the top navigation bar loading and are working on a fix.

  3. monitoring May 23, 2025, 03:27 AM UTC

    We have shipped a change to fix the navigation bar issue and are monitoring to ensure it works in all regions.

  4. resolved May 23, 2025, 03:34 AM UTC

    We have fixed the issue with the navigation bar on octopus.com/downloads

Read the full incident report →

Major March 28, 2025

ECS Update steps failing to execute

Detected by Pingoru
Mar 28, 2025, 11:54 AM UTC
Resolved
Mar 28, 2025, 01:10 PM UTC
Duration
1h 16m
Timeline · 3 updates
  1. identified Mar 28, 2025, 11:54 AM UTC

    We are aware of an issue where a recent update has caused ECS Update steps to fail deployment.

  2. monitoring Mar 28, 2025, 12:02 PM UTC

    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).

  3. resolved Mar 28, 2025, 01:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 5, 2025

Performance issues identified with Octopus Cloud

Detected by Pingoru
Mar 05, 2025, 02:17 PM UTC
Resolved
Mar 05, 2025, 10:23 PM UTC
Duration
8h 5m
Affected: Octopus Cloud
Timeline · 3 updates
  1. investigating Mar 05, 2025, 02:17 PM UTC

    Octopus Deploy is aware of performance issues for some customers on Octopus Cloud. Our engineers are investigating and we will provide an update soon.

  2. investigating Mar 05, 2025, 04:17 PM UTC

    We continue to see issues with our upstream to instances within the WestEU region. We are awaiting further information from Azure.

  3. resolved Mar 05, 2025, 10:23 PM UTC

    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.

Read the full incident report →

Minor February 12, 2025

ADO 'Use Octopus CLI Tool' step Certificate Issue

Detected by Pingoru
Feb 12, 2025, 01:47 PM UTC
Resolved
Feb 12, 2025, 09:36 PM UTC
Duration
7h 49m
Timeline · 3 updates
  1. investigating Feb 12, 2025, 01:47 PM UTC

    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

  2. monitoring Feb 12, 2025, 04:32 PM UTC

    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.

  3. resolved Feb 12, 2025, 09:36 PM UTC

    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 [email protected]

Read the full incident report →

Major January 30, 2025

Intermittent service disruption for a small number of customers

Detected by Pingoru
Jan 30, 2025, 07:24 AM UTC
Resolved
Feb 04, 2025, 03:07 AM UTC
Duration
4d 19h
Affected: Octopus Cloud
Timeline · 2 updates
  1. investigating Jan 30, 2025, 07:24 AM UTC

    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 [email protected]

  2. resolved Feb 04, 2025, 03:07 AM UTC

    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.

Read the full incident report →