Bitbucket: Increased latency merging pull requests
Timeline of updates
- resolved
We are currently in the process of upgrading our repository infrastructure which can result in additional latency with merges. Rest assured, if you are experiencing slow merges, your pull requests will be merged successfully. After initiating a merge request the merge will be processed in the background. This typically only takes a few seconds but may take longer. You can safely navigate away, and the status of the pull request will be updated once it is merged. Also, today we added a notification to the pull request screen explaining how merges are being processed asynchronously now.
From Bitbucket’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on bitbucket.status.atlassian.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Bitbucket, started 2021-06-28 11:21 UTC, resolved after 12 h, 1 update(s).
- Title
- Increased latency merging pull requests
- Vendor
- Bitbucket
- Date
- URL
- https://rewindex.com/company/bitbucket/incidents/8nbqbyxl2t03
Bitbucket profileRecent Bitbucket incidentsAll outages on June 28, 2021Bitbucket in June 2021MarkdownJSON