← Live dashboard

Delays with Bitbucket Pipelines Execution

ResolvedminorOfficial source confirmedSpecific component onlyFirst recorded update Sep 16, 2026, 09:32 AM · Resolved Sep 16, 2026, 10:15 AM

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.

Bitbucket live status →

Free for 3 services · Pro adds recovery alertsAdd to Chrome

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Bitbucket now? Check the current status

Affected services

Pipelines

Updates (2)

  1. Sep 16, 2026, 10:15 AM
    Delays with Bitbucket Pipelines Execution

    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.

    Bitbucket ↗
  2. Sep 16, 2026, 09:32 AM
    Delays with Bitbucket Pipelines Execution

    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.

    Bitbucket ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow Bitbucket's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.