Skip to main content
Octopus Deploy

AWS Deployment Failures for Cloud Customers

Partial outage Lasted 6d 19h · started · Octopus Deploy's page

Level
confirmed
Worst impact
Partial outage
Components
Octopus Cloud
Regions
ap-southeast-2, us
Down Index
41of 100

What to do

  • Check whether you use Octopus Deploy Octopus Cloud in ap-southeast-2, us. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 6d 19h it lasted.

    Anything that failed between 2026-04-01 08:36 UTC and 2026-04-08 04:11 UTC may need a replay.
  • Subscribe to Octopus Deploy's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=octopus works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Octopus Deploy 3

  1. investigating

    We are aware of an issue affecting Octopus Cloud customers running deployments that interact with AWS, including EKS/Kubernetes targets and AWS health checks. Impacted customers may see authentication errors when running these deployments. Our team is actively investigating and working to resolve the issue. Workaround: If you are affected, adding your AWS region as an environment variable in your script steps may resolve the issue: export AWS_REGION= for Bash $env:AWS_REGION = " " for Powershell E.g export AWS_REGION=ap-southeast-2 $env:AWS_REGION = "ap-southeast-2" We apologise for the disruption and will share further updates as our investigation progresses. If you need help in the meantime, please contact us at support@octopus.com

    provider

  2. investigating

    We are aware of an issue affecting Octopus Cloud customers running deployments that interact with AWS, including EKS/Kubernetes targets and AWS health checks. Impacted customers may see authentication errors when running these deployments. Our team is actively investigating and working to resolve the issue. Workaround: If you are affected, adding your AWS region as an environment variable in your script steps may resolve the issue: export AWS_REGION=[REGION] for Bash $env:AWS_REGION = "[REGION]" for Powershell E.g export AWS_REGION=ap-southeast-2 $env:AWS_REGION = "ap-southeast-2" We apologise for the disruption and will share further updates as our investigation progresses. If you need help in the meantime, please contact us at support@octopus.com

    provider

  3. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-5df78fdc18

Is Octopus Deploy still down?

No, this incident was resolved 2026-04-08 04:11 UTC. For Octopus Deploy's live state, see https://down.guide/octopus.

How long did it last?

6d 19h, from 2026-04-01 08:36 UTC to 2026-04-08 04:11 UTC, by the times Octopus Deploy posted.

What was affected?

Octopus Deploy named Octopus Cloud in ap-southeast-2, us.

What caused it?

Octopus Deploy hasn't published a root cause. If it does, it shows here.

Where does this come from?

Octopus Deploy's official status page, https://status.octopus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.