Bitbucket: GUI, API, SSH, archiver unresponsive
Timeline of updates
- resolved
Between roughly 21:37 and 21:40 UTC on 2019-02-05, requests to the Bitbucket GUI, API, or SSH services may have experienced an error or higher-than-normal response times due to a database issue. (Git and Mercurial operations over HTTPS were unaffected.) We've resolved the root cause, and services should be responding as normal 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: none) posted by Bitbucket, started 2019-02-05 21:37 UTC, resolved after 0 min, 1 update(s).
- Title
- GUI, API, SSH, archiver unresponsive
- Vendor
- Bitbucket
- Date
- URL
- https://rewindex.com/company/bitbucket/incidents/8f63btmd929d
Bitbucket profileRecent Bitbucket incidentsAll outages on February 5, 2019Bitbucket in February 2019MarkdownJSON