Bitbucket: Delays with Bitbucket Pipelines Execution
Salesforce outage, Sep 16, 2026 · 16 vendors, 21 incidents
Bitbucket’s incident started in the same window without naming Salesforce (timing only, not evidence of a link). (timing only, posted +2 h 13 min vs Salesforce’s own post)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Salesforce<br/>posted 07:19 UTC"]:::root
h4["1 to 4 hours later<br/>4 vendors, 4 blamed Salesforce<br/>Braze, Gong, ClickHouse Cloud, Smartsheet"]:::blames
root --> h4
later["Later<br/>1 vendor, 1 blamed Salesforce<br/>Salesloft"]:::blames
root --> later
me["Bitbucket (this incident)<br/>posted +2 h 13 min"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Affected components: Pipelines
Timeline of updates
- monitoring
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.
- resolved
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.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured 18:22 UTC
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on Oct 19, 23:18 UTC. Record hash
66d0c1dc24f138af…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).