{
"vendor": "Octopus",
"slug": "octopus",
"platform": "statuspage",
"status_url": "https://status.octopus.com",
"last_checked": "2026-09-16T12:28:20Z",
"last_state": "ok",
"history_backfilled": true,
"first_watched": "2026-09-04T07:06:16Z",
"incidents": [
{
"body": "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 support@octopus.com.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-31T15:04:03.243Z",
"resolved_inferred": false,
"started_at": "2026-07-31T13:32:24.942Z",
"state": "resolved",
"title": "https://g.octopushq.com Certificate issues",
"updated_at": "2026-07-31T15:04:03.265Z",
"url": "https://stspg.io/jch14qntcrn4"
},
{
"body": "Azure has resolved this issue.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-23T20:28:11.039Z",
"resolved_inferred": false,
"started_at": "2026-07-23T16:08:43.170Z",
"state": "resolved",
"title": "Service connectivity issues due to upstream Azure outage",
"updated_at": "2026-07-23T20:28:11.057Z",
"url": "https://stspg.io/6mjw4268d4d6"
},
{
"body": "The fix has been live across all Octopus Cloud servers for several weeks now without further issues.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-04T12:23:59.142Z",
"resolved_inferred": false,
"started_at": "2026-07-03T00:25:44.406Z",
"state": "resolved",
"title": "Bicep deployments may fail after upgrading to 2026.3.4658 or later",
"updated_at": "2026-08-04T12:23:59.159Z",
"url": "https://stspg.io/pyyh2y43ljbm"
},
{
"body": "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/.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-30T00:38:20.862Z",
"resolved_inferred": false,
"started_at": "2026-05-29T06:10:04.469Z",
"state": "resolved",
"title": "Ability to deploy in West US 2 might be affected",
"updated_at": "2026-05-30T00:38:20.879Z",
"url": "https://stspg.io/2njlj5pnsppk"
},
{
"body": "We have pushed out a fix for this issue and it should be rolling out to Octopus Cloud customers over the next few days. \nPlease contact support@octopus.com if you are seeing this issue and we can arrange to get your instance upgraded.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-18T10:49:01.834Z",
"resolved_inferred": false,
"started_at": "2026-05-15T12:36:03.385Z",
"state": "resolved",
"title": "Amazon ECS Service Steps fail with 'Container.image contains invalid cha...",
"updated_at": "2026-05-18T10:49:01.853Z",
"url": "https://stspg.io/xp9qxttg4ym1"
},
{
"body": "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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-07T06:40:35.798Z",
"resolved_inferred": false,
"started_at": "2026-05-05T13:18:47.601Z",
"state": "resolved",
"title": "Dynamic Worker issues in West US 2",
"updated_at": "2026-05-07T06:40:35.814Z",
"url": "https://stspg.io/1f20tgkzq23j"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-04-08T04:11:47.072Z",
"resolved_inferred": false,
"started_at": "2026-04-01T08:06:18.168Z",
"state": "resolved",
"title": "AWS Deployment Failures for Cloud Customers",
"updated_at": "2026-04-08T04:18:05.270Z",
"url": "https://stspg.io/slpby92g6q6f"
},
{
"body": "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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-30T12:43:39.947Z",
"resolved_inferred": false,
"started_at": "2026-03-30T12:43:39.888Z",
"state": "resolved",
"title": "Deployments using AWS-dependent resources may fail with \u201cNo RegionEndpoint or ServiceURL configured.\u201d",
"updated_at": "2026-03-30T12:43:39.957Z",
"url": "https://stspg.io/hjv0y0z6scrx"
},
{
"body": "This incident has been resolved. Please don't hesitate to reach out to our support team if you are still having any related problems.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-25T06:09:24.036Z",
"resolved_inferred": false,
"started_at": "2026-03-24T04:13:03.328Z",
"state": "resolved",
"title": "gRPC port (8443) shows Octopus Cloud instance is Undergoing Maintenance",
"updated_at": "2026-03-25T06:09:24.054Z",
"url": "https://stspg.io/jpwpyx1n49ww"
},
{
"body": "Email services have now been restored. Please contact support@octopus.com if you encounter any issues with email delivery.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-02-26T05:47:50.771Z",
"resolved_inferred": false,
"started_at": "2026-02-26T01:51:58.000Z",
"state": "resolved",
"title": "Emails are currently not being delivered",
"updated_at": "2026-02-26T05:47:50.787Z",
"url": "https://stspg.io/h6972d163hcg"
},
{
"body": "# Summary\n\nOn 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.\u00a0\n\nThis 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/).\u00a0\n\n# Background\n\nOctopus 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. Customers can use both Windows and Ubuntu Dynamic Workers.\u00a0\n\nOctopus provides a [dynamic worker pool](https://octopus.com/docs/infrastructure/workers/dynamic-worker-pools) of these virtual machine types from which, as required by your deployment/runbook steps, your Octopus Cloud will exclusively lease a freshly provisioned dynamic worker VM for a limited time.\n\n## Dynamic Workers Lifecycle\n\n1. **Provisioning** - a new Azure Virtual Machine is provisioned, using the requested [Dynamic Worker image](https://octopus.com/docs/infrastructure/workers/dynamic-worker-pools#dynamic-worker-images) \\(Windows/Ubuntu with a set of pre-installed tools\\).\n2. **Pool** - the newly created Dynamic Worker \\(VM\\) is placed in a worker pool until an instance requests a Dynamic Worker in one of its deployments/runbooks steps. Each region \\(US, Europe and Australia\\) has different pools for Windows and Ubuntu workers, with additional standby pools that can be turned on in cases of a temporary outage in an Azure region \\(see below\\). Octopus Cloud continuously monitors the pools\u2019 levels and provision new workers automatically to keep them full.\n3. **Leasing** - When a [deployment/runbook that uses a Dynamic Worker](https://octopus.com/docs/infrastructure/workers#where-steps-run) starts, if the instance doesn\u2019t have a leased worker already \\(in which case, it will continue using this worker, extending the worker\u2019s lease for the new run\\), the Octopus Server will request a new worker from the appropriate pool. This worker will be exclusively leased to this instance until it is no longer needed \\(i.e. wasn\u2019t used for an hour\\) or until its maximum lifespan is reached \\(3 days by default\\).\u00a0\n4. **Deletion** - After a worker is no longer needed or it has reached its maximum lifespan, it is considered expired and will be deleted by the system automatically. The next time that the same instance will require a worker, it will lease a new one from the pool \\(see above\\).\n\n## System Resilience & Safeguards\n\nOctopus Cloud implements multiple layers of protection to ensure Dynamic Workers\u2019 availability and minimize customer impact in cases of service disruptions:\n\n* **Pre-provisioned Worker Pools:** We maintain multiple [dynamic worker pools](https://octopus.com/docs/infrastructure/workers/dynamic-worker-pools) \\(for the different virtual machine OS and sizes\\) with ready-to-use workers to provide immediate availability when deployments/runbooks are triggered, rather than waiting for on-demand provisioning. This also provides a safety buffer in cases where we can\u2019t provision new Dynamic Workers due to temporary outages.\n* **Standby Services in Multiple Regions:** We maintain standby Dynamic Worker services in alternate Azure regions that we activate to provide continuity when a primary region experiences issues\n\n# Key Timing\n\n\u200c\n\n# Timeline and Impact\n\nAll dates and times below are in UTC\n\n**Feb 2 2026:**\n\n**18:52:** 1st failed Dynamic Worker provisioning - At this point, our Dynamic Workers Service continued supplying workers successfully from the pools. However, since we couldn\u2019t provision new workers, the pools started depleting.\u00a0\n\n**20:13:** 1st Ubuntu Dynamic Worker lease failed in `West US2` Azure region \\(once the pool was depleted\\) - start of customer impact\n\n**20:47:** Octopus on-call was paged after 3 Dynamic Worker lease requests failed in `West US2`. The on-call then started the incident to investigate the issue\n\n**20:47-21:20**:\u00a0\n\n* Octopus engineers started setting up a Dynamic Workers Service on a different Azure region in the US to mitigate the issue.\u00a0\n* During the investigation we saw that Dynamic Workers were also failing to provision in the `West Europe` and `East Australia` Azure regions. At this point we realized that this was a multi-region outage in Azure and decided to open a support ticket with them.\n* Octopus Engineers turned off non-essential services \\(e.g. Instance Upgrades\\) to preserve the available Dynamic Workers for customer use.\n\n**21:24:** an on-call engineer opened a Sev A support ticket with Azure\n\n**21:31:** We published the initial partial outage alert for Octopus Cloud on [https://status.octopus.com/](https://status.octopus.com/)\u00a0\n\n**21:33:** 1st Dynamic Worker lease failed in `West Europe`\n\n**21:42:** Azure acknowledged the multi-region issue and reported that they are investigating it.\n\n**22:56:** We saw the last Dynamic Worker lease failure. After this time, we were able to provision the required Virtual Machines and return the Dynamic Workers successfully to all lease requests.\n\n**23:46:** After verifying that all Dynamic Worker pools have been restored and we didn\u2019t see any additional provisioning failures, we updated the incident status to \u201cMitigated\u201d, and updated the Status page.\n\n\u200c\n\n**Feb 3 2026:**\n\n**6:05:** Azure confirmed that the issue was fully resolved on their side.\n\n**21:38:** Incident was resolved and Status page updated\n\n\u200c\n\n# Technical Details\n\nOctopus Cloud uses Azure Virtual Machines in order to supply Dynamic Workers to customers. During this Azure outage, we couldn\u2019t provision new Azure Virtual Machines for our Ubuntu Dynamic Workers. Our pre-provisioned Dynamic Workers\u2019 pools continued supplying Dynamic Workers for additional\u00a0\n\n* 1:21 hours in `West US 2` and\u00a0\n* 2:41 hours in `West Europe`\u00a0\n\nbefore they were depleted and customer requests for new Dynamic Workers started failing. It\u2019s worth noting that `East Australia` customers were not impacted because the pools in this region didn\u2019t deplete during the incident. Additionally, customers that already had a Dynamic Worker leased at the time of the outage were not impacted \\(unless their Dynamic Worker expired so a new one was requested during the incident\\).\n\n\u200c\n\nWe made preparations to switch to our Dynamic Workers Standby Service on different Azure regions. However, once we realized that this was a multi-region outage, we decided to revert the switch since it wouldn\u2019t have resolved the issue.\n\n\u200c\n\nOnce we saw that we couldn\u2019t supply Dynamic Workers from our standby regions, we turned off non-essential services \\(e.g. Instance Upgrades\\) to preserve the available Dynamic Workers for customer use.\u00a0\n\n\u200c\n\nOnce Azure mitigated the issue on their side, our system recovered automatically and resumed providing new Dynamic Workers successfully.\u00a0\n\n\u200c\n\n# Remediation\n\nOctopus takes service availability seriously. Despite the difficulty with upstream cloud provider outages, especially ones that are widespread across multiple regions, we fully review and remediate any outages that occur. We do this so that we\u2019re continuously improving and maintaining the best possible service we can.\n\nFollowing our post mortem, we identified the following improvements to our system to help identify and mitigate \\(where possible\\) similar issues earlier:\n\n* **Page an on-call earlier -** \u00a0add an alert to page the on-call when multiple Dynamic Workers in the same region fail to provision. This will allow us to detect similar incidents quicker and give us more time to mitigate the issue, before any Dynamic Worker leases fail and customers are impacted.\n* **Improve our Dynamic Workers Incident Playbook** to identify multi-regions incidents quicker in order to engage Azure support earlier to resolve the root cause of similar incidents.\u00a0\n\n# Conclusion\n\nWe apologize to our customers for any disruption and inconvenience as a result of this incident.\n\nWe have started work on the identified remediations to ensure that we can detect similar incidents more quickly and reduce the impact on our customers as much as possible.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-02-03T21:38:42.727Z",
"resolved_inferred": false,
"started_at": "2026-02-02T21:31:14.614Z",
"state": "postmortem",
"title": "Ubuntu Dynamic Workers are failing to lease",
"updated_at": "2026-02-13T05:10:02.616Z",
"url": "https://stspg.io/czrr4lws5zww"
},
{
"body": "# Intermittent sign-in issues for Octopus Cloud instances\n\n## Summary\n\nBetween 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.\n\n### Timings\n\nTime to detection: 9hrs 41mins\n\nTime to incident declaration: 9hrs 41mins\n\nTime to resolution: 12hrs 15mins\n\n## What happened?\n\n\\(All dates and times below are in AEST\\)\n\n### November 25\n\n**12:43 pm** We deployed a change to our authorization service. This change introduced a bug resulting in database connection leaks. The connection leak only became apparent in high-traffic scenarios, which our current test suite doesn't replicate. As a result, our test suite didn't detect the issue.\n\n**10:24 pm** A DevOps Support Engineer declared an incident after receiving reports from customers that they were having difficulty signing into Octopus Cloud instances.\n\n**10:24 pm - 11:41 pm** Investigations showed that the issue was due to database connection timeouts.\n\n**11:42 pm** Temporary mitigations implemented, including restarting services to release database connections.\n\n**11:42 pm - 11:59 pm** Effects of mitigations observed and deemed successful. Incident marked as mitigated.\n\n### November 26\n\n**12:00 am - 12:57 am** Incident responders continue to watch systems.\n\n**12:58 am** Mitigation steps considered successful, and the incident marked as resolved.\n\n**6:55 am** Root cause of database connection timeouts identified as a connection leak.\n\n**6:55 am - 8:33 am** Permanent fix implemented and deployed.\n\n## Remediation and next steps\n\nWe deployed a new service version to remove the database connection leak. We have also conducted an incident review to identify process improvements to prevent this from occurring in the future. We continue to work towards improving the reliability and security of our authentication and authorization services.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-11-25T14:57:46.057Z",
"resolved_inferred": false,
"started_at": "2025-11-25T12:34:28.801Z",
"state": "postmortem",
"title": "OctopusID signin intermittent for cloud customers",
"updated_at": "2025-12-08T21:55:14.984Z",
"url": "https://stspg.io/m72cwhzx3pmx"
},
{
"body": "We have observed no further errors stemming from this issue.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-11-19T00:47:43.194Z",
"resolved_inferred": false,
"started_at": "2025-11-18T21:11:25.133Z",
"state": "resolved",
"title": "GitHub upstream outage causing issues with VCS-backed elements",
"updated_at": "2025-11-19T00:47:43.209Z",
"url": "https://stspg.io/7l33709ml2wq"
},
{
"body": "All Octopus services affected by this outage are now operational.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-30T01:13:36.031Z",
"resolved_inferred": false,
"started_at": "2025-10-29T16:31:49.564Z",
"state": "resolved",
"title": "Octopus.com and billing portal may be unavailable in certain regions",
"updated_at": "2025-10-30T01:13:36.050Z",
"url": "https://stspg.io/13fnd1fgrzky"
},
{
"body": "Docker Hub have resolved their incident and we have not observed any further issues",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-21T01:11:53.190Z",
"resolved_inferred": false,
"started_at": "2025-10-20T07:34:33.883Z",
"state": "resolved",
"title": "Docker Hub is down",
"updated_at": "2025-10-21T01:11:53.208Z",
"url": "https://stspg.io/r8500hm0c5sf"
},
{
"body": "This has been resolved. All missing tags have been published to DockerHub and we are seeing successful deployments using these new tags.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-13T00:24:17.344Z",
"resolved_inferred": false,
"started_at": "2025-10-12T23:43:06.000Z",
"state": "resolved",
"title": "Kubernetes deployments using Kubernetes agent may fail",
"updated_at": "2025-10-13T00:24:17.364Z",
"url": "https://stspg.io/fly31dn40jj9"
},
{
"body": "# **Incident Summary**\n\nDocker Hub experienced authentication issues that prevented access to container images, resulting in deployment failures for projects relying on those images.\n\n## **What We're Doing**\n\nFollowing this incident, we've identified several improvements to enhance service resilience and customer communication:\n\n### **Visibility & Monitoring**\n\n* Communicate third-party service outages more clearly on our status page\n* Explore in-app messaging to alert customers during service disruptions\n\n### **Resilience & Good Practices**\n\n* Review image retrieval reliability and address identified risks\n* Share good practices with customers to help reduce impacts when Docker Hub is unavailable",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-25T04:18:59.632Z",
"resolved_inferred": false,
"started_at": "2025-09-25T01:06:30.966Z",
"state": "postmortem",
"title": "Docker Hub authentication issues",
"updated_at": "2025-10-09T03:39:22.041Z",
"url": "https://stspg.io/07crzf0gqrvv"
},
{
"body": "The downstream issue with Azure CLI login commands has been resolved by Azure.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-15T06:05:33.167Z",
"resolved_inferred": false,
"started_at": "2025-09-15T03:11:19.350Z",
"state": "resolved",
"title": "Intermittent Azure authentication issues",
"updated_at": "2025-09-15T06:05:33.183Z",
"url": "https://stspg.io/6rk6y15t7k0k"
},
{
"body": "This issue is resolved, please reach out to https://octopus.com/support if you are still experiencing deployments that fail to start.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-05T03:50:03.134Z",
"resolved_inferred": false,
"started_at": "2025-09-04T02:31:49.720Z",
"state": "resolved",
"title": "(Resolved) Some Deployments/Runbooks in Octopus Cloud may be failing to start",
"updated_at": "2025-09-05T03:50:03.151Z",
"url": "https://stspg.io/srpm2dt2217k"
}
]
}