Octopus incident

Deployments using AWS-dependent resources may fail with “No RegionEndpoint or ServiceURL configured.”

Resolved on March 30, 2026, affecting Octopus Cloud.

resolved Mar 30, 2026, 12:43 PM UTC

We have identified the cause of this issue and have produced a fix in Octopus version 2026.2.3825. Please email [email protected] if you are seeing AWS region endpoint errors in your deployments similar to the one in the title and we can discuss upgrade options.

Started
Mar 30, 2026, 12:43 PM UTC
Resolved
Mar 30, 2026, 12:43 PM UTC
Duration
–
Detected by Pingoru
Mar 30, 2026, 12:43 PM UTC

Affected components

Octopus Cloud

Update timeline

  1. resolved Mar 30, 2026, 12:43 PM UTC

    We have identified the cause of this issue and have produced a fix in Octopus version 2026.2.3825. Please email [email protected] if you are seeing AWS region endpoint errors in your deployments similar to the one in the title and we can discuss upgrade options.

Your product runs on more than Octopus

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →