Bitbucket: Service degradation
Timeline of updates
- resolved
We have successfully returned Bitbucket Cloud to normal response times and will no longer be providing status updates about the recent performance degradation. We want to thank all customers for your patience as we worked on resolving the issue. We know that you rely on Bitbucket to keep your teams working and your businesses running, and apologize for the disruption this has caused. We will be publishing a post-mortem next week on this Statuspage. If you have a specific question about your repository, you can raise an issue with our support team here: https://support.atlassian.com/contact (opens in new tab)
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 2018-01-09 13:47 UTC, resolved after 3 d, 1 update(s).
- Title
- Service degradation
- Vendor
- Bitbucket
- Date
- URL
- https://rewindex.com/company/bitbucket/incidents/z029156p1svh
Bitbucket profileRecent Bitbucket incidentsAll outages on January 9, 2018Bitbucket in January 2018MarkdownJSON