Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Octopus Deploy Outage History

Every past Octopus Deploy outage tracked by IsDown, with detection times, duration, and resolution details.

There were 113 Octopus Deploy outages since June 2020. The 15 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Major May 15, 2026

May 2026: Amazon ECS Service Steps fail with 'Container.image contains invalid characters' if using a container definition image package ID with a forward slash in it

Detected May 15, 2026 8:36 AM EDT · Resolved May 18, 2026 6:52 AM EDT · Duration 3 days

Amazon ECS Service Steps in Octopus Deploy failed with 'Container.image contains invalid characters' errors when using container definition image package IDs containing forward slashes. The issue affected Octopus Cloud customers for 70.3 hours, preventing successful ECS deployments. A fix was deployed and rolled out to Octopus Cloud instances, with workarounds available through a GitHub issue during the incident.

Major May 5, 2026

May 2026: Dynamic Worker issues in West US 2

Detected May 5, 2026 9:18 AM EDT · Resolved May 7, 2026 2:43 AM EDT · Duration 1 day

Octopus Deploy experienced issues provisioning Dynamic Workers in the West US 2 region, causing lease failures for a small number of customers using Octopus Cloud. The service was restored by switching affected Cloud instances to use dynamic workers in the Central US standby region, and later reverting back to West US 2 once the region stabilized. The incident lasted 41.4 hours before full resolution.

Major April 1, 2026

April 2026: AWS Deployment Failures for Cloud Customers

Detected Apr 1, 2026 4:06 AM EDT · Resolved Apr 8, 2026 12:15 AM EDT · Duration 7 days

Octopus Cloud customers experienced authentication errors when running deployments that interact with AWS services, including EKS/Kubernetes targets and AWS health checks, for approximately 164 hours. A workaround was provided requiring users to manually add AWS region environment variables to their script steps. The incident was fully resolved on April 8th, 2026.

Major March 24, 2026

March 2026: gRPC port (8443) shows Octopus Cloud instance is Undergoing Maintenance

Detected Mar 24, 2026 12:13 AM EDT · Resolved Mar 25, 2026 2:10 AM EDT · Duration 1 day

Octopus Deploy Cloud instances experienced a major service disruption where the gRPC port (8443) incorrectly displayed maintenance status messages for 26 hours. The issue was identified and a fix was implemented, with the resolution rolled out to customer instances during their scheduled maintenance windows. The incident was fully resolved and customers were advised to contact support if they continued experiencing deployment blockages.

Major February 25, 2026

February 2026: Emails are currently not being delivered

Detected Feb 25, 2026 8:51 PM EST · Resolved Feb 26, 2026 12:48 AM EST · Duration about 4 hours

Octopus Deploy experienced a major email delivery outage lasting 3.9 hours due to issues with their upstream email provider. The incident affected all email functionality including authentication verification, subscription invitations, and billing notifications for Octopus Cloud users. The service was fully restored with emails now being sent from a new address (donotreply@octopus.com).