Monitoring - We have implemented a fix in v2024.1.6809 which will be rolling out to cloud customers over the next two days. If you need the fix in your cloud instance sooner, please contact https://octopus.com/support. We will continue to monitor for any further issues.
Jan 09, 2024 - 04:03 UTC
Identified - We have found a likely cause of this issue and are working on a fix. In the meantime, please refer to the Github issue for more updates - https://github.com/OctopusDeploy/Issues/issues/8551
Jan 08, 2024 - 22:44 UTC
Investigating - We're investigating AWS deployment failures for customers upgraded to 2024.1.6245 and are using the "AWS service role for an EC2 instance" option, which throw the error "An account identifier was not found".

For more details of the issue and a possible workaround see the Github issue https://github.com/OctopusDeploy/Issues/issues/8551

Jan 08, 2024 - 21:22 UTC
Octopus.com / OctopusId ? Operational
Octopus Cloud ? Operational
Cloud Control Center (billing.octopus.com) ? Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Past Incidents
Jan 28, 2024

No incidents reported today.

Jan 27, 2024

No incidents reported.

Jan 26, 2024

No incidents reported.

Jan 25, 2024

No incidents reported.

Jan 24, 2024
Resolved - This issue was resolved in 2023.4.8185 and 2024.1.5399.
Jan 24, 03:48 UTC
Monitoring - A fix for this issue has been released in version 2023.4.8185 which is now available for download, and 2024.1.5399 which will be rolling out to cloud customers early in the new year. If you need the fix in your cloud instance sooner, please contact https://octopus.com/support. We will continue to monitor for any further issues.
Dec 19, 23:53 UTC
Identified - We are currently investigating an issue where API requests for the projects associated with a lifecycle may hang indefinitely, never responding. We believe we have identified the cause and are working on rolling out a version containing a fix. For more details see this GitHub issue: https://github.com/OctopusDeploy/Issues/issues/8533
Dec 19, 02:49 UTC
Resolved - This issue was resolved in 2023.4.8166.
Jan 24, 03:46 UTC
Monitoring - With the release of 2023.4.8166, we believe we have addressed the memory and CPU usage spikes associated with the variables endpoints. We continue to monitor to ensure these endpoints operate smoothly. For more details see this GitHub issue: https://github.com/OctopusDeploy/Issues/issues/8529
Dec 20, 00:25 UTC
Update - We have implemented a fix in v2023.4.8166. Should you encounter any issues after upgrading, please do not hesitate to reach out to our support team.
Dec 15, 07:48 UTC
Update - We are actively continuing our investigation into the reported issue. Thank you for your ongoing patience as we work towards a resolution.
Dec 13, 07:12 UTC
Investigating - We are currently investigating this issue that has been reported, as a high priority.
Dec 12, 23:57 UTC
Jan 23, 2024

No incidents reported.

Jan 22, 2024

No incidents reported.

Jan 21, 2024
Resolved - Azure has advised that this issue has been resolved. A preliminary root cause has been published here: https://azure.status.microsoft/en-us/status/history/
Jan 21, 23:09 UTC
Monitoring - Dynamic Workers are now provisioning successfully. We are continuing to monitor for any degradation of service.
Jan 21, 09:17 UTC
Update - We continue to see issues with our upstream. We are investigating a workaround. Another update will be provided within the next hour.
Jan 21, 07:31 UTC
Identified - Our upstream provider, Microsoft Azure, is currently experiencing an issue which is affecting our ability to provision worker virtual machines for a subset of customers in WestEU.
See https://azure.status.microsoft/en-gb/status for more details.

If you experience this problem, deployments utilising dynamic workers will fail with an error specifying that Octopus Deploy could not obtain a dynamic worker lease.

We will provide an update in an hour, at approximately 0730 UTC.

We will resolve this incident once we have received confirmation the issue has been resolved from our upstream provider.

Jan 21, 06:31 UTC
Jan 20, 2024

No incidents reported.

Jan 19, 2024

No incidents reported.

Jan 18, 2024

No incidents reported.

Jan 17, 2024

No incidents reported.

Jan 16, 2024

No incidents reported.

Jan 15, 2024

No incidents reported.

Jan 14, 2024

No incidents reported.