Skip to main content
Octopus Deploy

Dynamic Worker Leases failing in East AU

Partial outage Lasted 14d 7h · started · Octopus Deploy's page

Level
confirmed
Worst impact
Partial outage
Components
Octopus Cloud
Regions
au
Down Index
37of 100

What to do

  • Check whether you use Octopus Deploy Octopus Cloud in au. 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 14d 7h it lasted.

    Anything that failed between 2024-04-28 23:56 UTC and 2024-05-13 07:34 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 7

  1. investigating

    Octopus Cloud is experiencing issues leasing Dynamic Workers in Australia East. The issue is currently under investigation and this incident will be updated when further details are known.

    provider

  2. investigating

    Our upstream provider, Microsoft Azure, is currently experiencing an issue which is affecting our ability to provision worker virtual machines for customers in East AU. We are working with Azure to resolve the issue. If you experience this problem, deployments utilizing dynamic workers will fail with an error specifying that Octopus Deploy could not obtain a dynamic worker lease. We will resolve this incident once we have received confirmation the issue has been resolved from our upstream provider.

    provider

  3. monitoring

    Dynamic Workers are now provisioning successfully in East AU. We are continuing to monitor for any degradation of service.

    provider

  4. monitoring

    We are continuing to see periods of service degradation in the Australia East region. New Dynamic Workers will be provisioned in the Australia Southeast region until we have confirmation from our service provider that the issue has been resolved.

    provider

  5. monitoring

    Our service provider, Microsoft Azure, has confirmed that the underlying issue has been resolved. We are continuing to monitor for any degradation of service.

    provider

  6. monitoring

    We have resumed provisioning Dynamic Workers in East AU (from Australia Southeast). We are continuing to monitor for any degradation of service.

    provider

  7. 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-e00d8333f1

Is Octopus Deploy still down?

No, this incident was resolved 2024-05-13 07:34 UTC. For Octopus Deploy's live state, see https://down.guide/octopus.

How long did it last?

14d 7h, from 2024-04-28 23:56 UTC to 2024-05-13 07:34 UTC, by the times Octopus Deploy posted.

What was affected?

Octopus Deploy named Octopus Cloud in au.

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.