Octopus Outage History

Octopus is up right now

Octopus had 33 outages in the last 2 years totaling 465h 23m of downtime — averaging 1.4 incidents per month.

There were 33 Octopus outages since June 18, 2024 totaling 465h 23m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.octopus.com

Major November 20, 2024

Octopus Cloud Trial Signup - Service Disruption

Detected by Pingoru
Nov 20, 2024, 06:50 AM UTC
Resolved
Nov 20, 2024, 07:12 AM UTC
Duration
22m
Timeline · 4 updates
  1. investigating Nov 20, 2024, 04:55 AM UTC

    We are currently experiencing an issue with Octopus Cloud Trial signups. New Trial instances are not being provisioned as expected. Our team is actively investigating the root cause and working to resolve the issue as quickly as possible. We will provide updates here as soon as more information becomes available. Users attempting to sign up for new Octopus Cloud Trials are unable to provision new trial instances at this time.

  2. identified Nov 20, 2024, 06:50 AM UTC

    The cause has been identified and engineers are working on a fix

  3. identified Nov 20, 2024, 06:53 AM UTC

    The cause of the issue has been identified and engineers are working on a fix

  4. resolved Nov 20, 2024, 07:12 AM UTC

    This issue has now been resolved and all systems are working as expected

Read the full incident report →

Major November 20, 2024

Octopus ID and a subset of Octopus.com unavailable

Detected by Pingoru
Nov 20, 2024, 03:49 AM UTC
Resolved
Nov 20, 2024, 03:49 AM UTC
Duration
—
Affected: Octopus.com
Timeline · 1 update
  1. resolved Nov 20, 2024, 03:49 AM UTC

    Between 12:15 PM and 12:25 PM AEST, a brief outage affected Octopus ID and a subset of Octopus.com services, including the Profile, Control Centre v1, Blogs, and License Purchasing. During this time, customers were unable to log in to cloud instances using Octopus ID and access certain areas of the site. The issue was caused by an unintended outage during a system upgrade. The issue was identified and resolved promptly, restoring all services within 10 minutes. All impacted systems are fully operational, and no further issues are expected.

Read the full incident report →

Notice October 9, 2024

Unable to sign into Octopus ID

Detected by Pingoru
Oct 09, 2024, 05:26 AM UTC
Resolved
Oct 15, 2024, 10:03 PM UTC
Duration
6d 16h
Affected: Octopus.com
Timeline · 2 updates
  1. monitoring Oct 09, 2024, 05:26 AM UTC

    A recent configuration change to the Octopus ID Web Application Firewall (WAF) caused some customers to be unable to sign into their Octopus Cloud instance using Octopus ID. The change has been rolled back and customers should be able to sign into Octopus ID and their Octopus Cloud instances again. We are monitoring, but if you are having issues, please get in touch at [email protected]

  2. resolved Oct 15, 2024, 10:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical September 27, 2024

Octopus.com/signin Unavaliable

Detected by Pingoru
Sep 27, 2024, 08:04 AM UTC
Resolved
Sep 27, 2024, 09:10 AM UTC
Duration
1h 6m
Affected: Octopus.comOctopus CloudControl Center (billing.octopus.com)
Timeline · 4 updates
  1. investigating Sep 27, 2024, 08:04 AM UTC

    We're investigating an issue with Octopus.com. This also affects all customers attempting to sign in to their Octopus Cloud instances.

  2. monitoring Sep 27, 2024, 08:16 AM UTC

    We're investigating an issue with Octopus.com. This also affects all customers attempting to sign in to their Octopus Cloud instances.

  3. monitoring Sep 27, 2024, 08:17 AM UTC

    octopus.com/signin should be available again and we are monitoring at the moment.

  4. resolved Sep 27, 2024, 09:10 AM UTC

    octopus.com/signin has been up for the last hour; we will continue to monitor it throughout the day. Customers that notified us have confirmed they can now logon to their Octopus Cloud Instances.

Read the full incident report →

Critical August 27, 2024

Octopus ID and a subset of Octopus.com URLS unavailable

Detected by Pingoru
Aug 27, 2024, 01:30 PM UTC
Resolved
Sep 03, 2024, 04:55 AM UTC
Duration
6d 15h
Affected: Octopus.comOctopus CloudControl Center (billing.octopus.com)
Timeline · 3 updates
  1. investigating Aug 27, 2024, 02:05 PM UTC

    Users are reporting 502 and 504 timeouts when attempting to log into their Octopus.com accounts, limiting access to Octopus Cloud and Control Center. A small subset of Octopus.com URLs are also impacted: Octopus.com/blog Octopus.com/start

  2. monitoring Aug 27, 2024, 02:07 PM UTC

    Services are currently operational. Our team is continuing to investigate the root cause.

  3. resolved Sep 03, 2024, 04:55 AM UTC

    Services have been operational and stable since recovery 6 days ago. The incident was caused by an abnormally high frequency of requests, resulting in degraded service. We have relieved the bottleneck and are investigating why the compensating controls we had in place didn't compensate as expected.

Read the full incident report →

Major July 30, 2024

Connectivity issues with Octopus.com

Detected by Pingoru
Jul 30, 2024, 01:38 PM UTC
Resolved
Jul 30, 2024, 09:13 PM UTC
Duration
7h 34m
Affected: Octopus.comControl Center (billing.octopus.com)
Timeline · 4 updates
  1. identified Jul 30, 2024, 01:38 PM UTC

    Due to an upstream issue with Azure, some users are reporting connectivity issues to Octopus.com, billing.octopus.com, and potentially other Octopus-hosted services.

  2. monitoring Jul 30, 2024, 03:12 PM UTC

    Azure has reported improved service availability. We will continue to monitor this situation.

  3. monitoring Jul 30, 2024, 07:22 PM UTC

    Azure is continuing the global rollout of their mitigation measures. We continue to monitor this situation, and await the completion of this rollout by Azure engineers.

  4. resolved Jul 30, 2024, 09:13 PM UTC

    Azure has resolved the underlying issue causing these connectivity problems.

Read the full incident report →

Major July 19, 2024

Windows2022 Dynamic Workers crashing and failing to lease

Detected by Pingoru
Jul 19, 2024, 06:16 AM UTC
Resolved
Jul 21, 2024, 11:15 PM UTC
Duration
2d 16h
Affected: Octopus Cloud
Timeline · 3 updates
  1. identified Jul 19, 2024, 06:16 AM UTC

    Our upstream provider, CrowdStrike, is currently experiencing an issue which is affecting our ability to lease Windows2022 Dynamic Workers. We will resolve this incident once we have received confirmation the issue has been resolved from our upstream provider.

  2. monitoring Jul 19, 2024, 06:31 AM UTC

    Incident has been mitigated and Windows Dynamic Workers are operating normally.

  3. resolved Jul 21, 2024, 11:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 18, 2024

Octopus Cloud - intermittent deployment failures when using Git Credentials - MultipleActiveResultSets error

Detected by Pingoru
Jun 18, 2024, 09:01 AM UTC
Resolved
Jun 21, 2024, 08:20 AM UTC
Duration
2d 23h
Timeline · 2 updates
  1. identified Jun 18, 2024, 09:01 AM UTC

    Customers have reported intermittent failures when deploying using Git Credentials. Deployments fail, showing an error message similar to "There is already an open DataReader associated with this connection which must be closed first. The connection does not support MultipleActiveResultSets". We have identified this problem was introduced by a recent code change, affecting Octopus Deploy versions 2024.3.2940 or higher. Our engineering team is investigating further to determine a fix. Potential Workaround: Retry the deployment. The problem is intermittent in nature.

  2. resolved Jun 21, 2024, 08:20 AM UTC

    Octopus Cloud Customers have reported intermittent failures when deploying using Git Credentials. Deployments fail, showing an error message similar to "There is already an open DataReader associated with this connection which must be closed first. The connection does not support MultipleActiveResultSets".We have identified this problem was introduced by a recent code change, affecting Octopus Deploy versions 2024.3.2940 or higher. All known instances of this issue have been resolved.

Read the full incident report →