Octopus Deploy Outage History

15 incidents recorded over the last 365 days, 15 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Octopus Deploy status100.00% uptime history

Every Recorded Octopus Deploy Incident

Octopus Deploy incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 22, 2026Customers with instances using GitHub could be affected by GitHub outageAccording to GitHub, their services have resumed normal operation. You can find out more by visiting: https://www.githubstatus.com1h 44mResolved
Oct 5, 2026Permissions not being applied correctlyWe'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.8h 7mResolved
Jul 31, 2026https://g.octopushq.com Certificate issuesThis 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.1h 31mResolved
Jul 23, 2026Service connectivity issues due to upstream Azure outageAzure has resolved this issue.4h 19mResolved
Jul 3, 2026Bicep deployments may fail after upgrading to 2026.3.4658 or laterThe fix has been live across all Octopus Cloud servers for several weeks now without further issues.779h 58mResolved
May 29, 2026Ability to deploy in West US 2 might be affectedOur 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…18h 28mResolved
May 15, 2026Amazon ECS Service Steps fail with 'Container.image contains invalid cha...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 support@octopus.com if you are seeing this issue and we can arrange to get your…70h 12mResolved
May 5, 2026Dynamic Worker issues in West US 2We 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.41h 21mResolved
Apr 1, 2026AWS Deployment Failures for Cloud CustomersThis incident has been resolved.163h 35mResolved
Mar 30, 2026Deployments using AWS-dependent resources may fail with “No RegionEndpoint or ServiceURL configured.”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…0 minResolved
Mar 24, 2026gRPC port (8443) shows Octopus Cloud instance is Undergoing MaintenanceThis incident has been resolved. Please don't hesitate to reach out to our support team if you are still having any related problems.25h 56mResolved
Feb 26, 2026Emails are currently not being deliveredEmail services have now been restored. Please contact support@octopus.com if you encounter any issues with email delivery.3h 55mResolved
Feb 2, 2026Ubuntu Dynamic Workers are failing to lease# 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…24h 7mResolved
Nov 25, 2025OctopusID signin intermittent for cloud customers# 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…2h 23mResolved
Nov 18, 2025GitHub upstream outage causing issues with VCS-backed elementsWe have observed no further errors stemming from this issue.3h 36mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Octopus Deploy incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Octopus Deploy Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Octopus Deploy acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Octopus Deploy outage in this window ran 32d 11h, against a mean recovery of 3d 4h. If you depend on Octopus Deploy in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.