https://approjects-vendor-status-watch.static.hf.space/v/octopus.htmlIncidents from Octopus's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/jch14qntcrn4octopus:2026-07-31T13:32:24.942ZFri, 31 Jul 2026 13:32:24 +0000This issue has now been resolved. Thank you for your patience whilst we investigated the incident. If you are having any further issues please email support@octopus.com.https://stspg.io/6mjw4268d4d6octopus:2026-07-23T16:08:43.170ZThu, 23 Jul 2026 16:08:43 +0000Azure has resolved this issue.https://stspg.io/pyyh2y43ljbmoctopus:2026-07-03T00:25:44.406ZFri, 03 Jul 2026 00:25:44 +0000The fix has been live across all Octopus Cloud servers for several weeks now without further issues.https://stspg.io/2njlj5pnsppkoctopus:2026-05-29T06:10:04.469ZFri, 29 May 2026 06:10:04 +0000Our 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/.https://stspg.io/xp9qxttg4ym1octopus:2026-05-15T12:36:03.385ZFri, 15 May 2026 12:36:03 +0000We 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.https://stspg.io/1f20tgkzq23joctopus:2026-05-05T13:18:47.601ZTue, 05 May 2026 13:18:47 +0000We 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.https://stspg.io/slpby92g6q6foctopus:2026-04-01T08:06:18.168ZWed, 01 Apr 2026 08:06:18 +0000This incident has been resolved.https://stspg.io/hjv0y0z6scrxoctopus:2026-03-30T12:43:39.888ZMon, 30 Mar 2026 12:43:39 +0000We 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.https://stspg.io/jpwpyx1n49wwoctopus:2026-03-24T04:13:03.328ZTue, 24 Mar 2026 04:13:03 +0000This incident has been resolved. Please don't hesitate to reach out to our support team if you are still having any related problems.https://stspg.io/h6972d163hcgoctopus:2026-02-26T01:51:58.000ZThu, 26 Feb 2026 01:51:58 +0000Email services have now been restored. Please contact support@octopus.com if you encounter any issues with email delivery.https://stspg.io/czrr4lws5zwwoctopus:2026-02-02T21:31:14.614ZMon, 02 Feb 2026 21:31:14 +0000# Summary On 2 Feb 2026, between 20:13:34 to 22:56:04 UTC, Octopus Cloud customers in `West US 2` and `West Europe` may have experienced failed deployments or failed runbook runs due to `Ubuntu Dynamic Worker` steps failing on Leasing timeout.  This disruption was caused by Azure failing to provision Virtual Machines across multiple regions - see Azure Issue `FNJ8-VQZ` on [Azure Status History](https://azure.status.microsoft/en-us/status/history/).  # Background Octopus Cloud [Dynamic Workers](https://octopus.com/docs/octopus-cloud/dynamic-worker) are isolated virtual machines that we provide as part of our Octopus Cloud Subscription offering as a way to execute deployment and runbook steps and scripts, without needing to run on the Octopus Server or deployment targets themselves. Custhttps://stspg.io/m72cwhzx3pmxoctopus:2025-11-25T12:34:28.801ZTue, 25 Nov 2025 12:34:28 +0000# Intermittent sign-in issues for Octopus Cloud instances ## Summary Between November 25, at 10:24 pm AEST, and November 26, at 12:58 am AEST, customers experienced sporadic issues signing into Octopus Cloud instances. These issues stemmed from a database connection leak, which caused some sign-in requests to time out. We apologize for the inconvenience this has caused our customers and are taking steps to prevent it from happening again. ### Timings Time to detection: 9hrs 41mins Time to incident declaration: 9hrs 41mins Time to resolution: 12hrs 15mins ## What happened? \(All dates and times below are in AEST\) ### November 25 **12:43 pm** We deployed a change to our authorization service. This change introduced a bug resulting in database connection leaks. The connection leak https://stspg.io/7l33709ml2wqoctopus:2025-11-18T21:11:25.133ZTue, 18 Nov 2025 21:11:25 +0000We have observed no further errors stemming from this issue.https://stspg.io/13fnd1fgrzkyoctopus:2025-10-29T16:31:49.564ZWed, 29 Oct 2025 16:31:49 +0000All Octopus services affected by this outage are now operational.https://stspg.io/r8500hm0c5sfoctopus:2025-10-20T07:34:33.883ZMon, 20 Oct 2025 07:34:33 +0000Docker Hub have resolved their incident and we have not observed any further issueshttps://stspg.io/fly31dn40jj9octopus:2025-10-12T23:43:06.000ZSun, 12 Oct 2025 23:43:06 +0000This has been resolved. All missing tags have been published to DockerHub and we are seeing successful deployments using these new tags.https://stspg.io/07crzf0gqrvvoctopus:2025-09-25T01:06:30.966ZThu, 25 Sep 2025 01:06:30 +0000# **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 unavailablehttps://stspg.io/6rk6y15t7k0koctopus:2025-09-15T03:11:19.350ZMon, 15 Sep 2025 03:11:19 +0000The downstream issue with Azure CLI login commands has been resolved by Azure.https://stspg.io/srpm2dt2217koctopus:2025-09-04T02:31:49.720ZThu, 04 Sep 2025 02:31:49 +0000This issue is resolved, please reach out to https://octopus.com/support if you are still experiencing deployments that fail to start.