Delays with Bitbucket Pipelines Execution

What to do

• Check whether you use Bitbucket Pipelines. 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 44m it lasted.

  Anything that failed between 2026-09-16 09:32 UTC and 2026-09-16 10:15 UTC may need a replay.

• Subscribe to Bitbucket's feed to hear about the next one first. RSS feed

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

Updates from Bitbucket 2

1. monitoringSep 16, 2026, 9:32 AM UTC

   We have identified and resolved the underlying issue causing delays and stuck builds in Bitbucket Pipelines. System recovery is in progress, and we are actively monitoring the pipeline queues to ensure builds are processing normally. Action Recommended: If you have pipelines or builds that remain queued or are stalled, we recommend rerunning them or triggering a new build. We will continue to monitor the service closely and provide a final update once stability is confirmed.

   provider

2. resolvedSep 16, 2026, 10:15 AM UTC

   The incident affecting Bitbucket Pipelines has been fully resolved and the pipeline backlog has cleared. Pipeline scheduling and build executions are now operating normally. Note: If you have any older builds that were queued or stalled during the incident window and did not automatically resume, please re-run or trigger a new build.

   provider

Corrections

None so far.

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