Delays in running Bitbucket Pipelines

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 30m it lasted.

  Anything that failed between 2025-09-16 04:00 UTC and 2025-09-16 04:30 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 4

1. investigatingSep 16, 2025, 4:00 AM UTC

   We are investigating cases of degraded performance for Atlassian Bitbucket Cloud Pipelines customers. We will provide more details within the next hour. We have mitigated the impact on self-hosted runners but cloud users are continuing to see delays on pipelines starting.

   provider

2. identifiedSep 16, 2025, 4:13 AM UTC

   We continue to work on resolving the delayed Pipelines for Atlassian Bitbucket. We have identified the root cause and expect recovery shortly.

   provider

3. monitoringSep 16, 2025, 4:19 AM UTC

   We have identified the root cause of the Pipelines delays and have mitigated the problem. We are now monitoring closely.

   provider

4. resolvedSep 16, 2025, 4:30 AM UTC

   Between 03:30 UTC to 03:50 UTC, we experienced delyas in running pipelines for Atlassian Bitbucket. The issue has been resolved and the service is operating normally.

   provider

Corrections

None so far.

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