Bitbucket: Git and Mercurial over HTTPS slow or not responding
Timeline of updates
- resolved
Our Git and Mercurial HTTPS services had sporadic issues between roughly 02:00 and 03:00 UTC on 15 October 2015. During that time, users attempting to push, pull, or clone repos over HTTPS may have experienced very slow response times or timeouts. Pushes and pulls over SSH were unaffected, as were the GUI, the API, and source downloads. Upon investigation, we tracked the problem to a database server that handles authentication queries for the affected services. Once we failed those queries over to another server, normal service was restored.
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 2015-10-15 12:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Git and Mercurial over HTTPS slow or not responding
- Vendor
- Bitbucket
- Date
- URL
- https://rewindex.com/company/bitbucket/incidents/fnnnh50yh0bl
Bitbucket profileRecent Bitbucket incidentsAll outages on October 15, 2015Bitbucket in October 2015MarkdownJSON