Bitbucket: Database server hiccup caused 500 errors
Timeline of updates
- resolved
A brief issue on our primary database server caused queries to back up. As a result, some users received a 500 or 503 error while attempting to connect. The issue has cleared, and traffic is flowing normally once more. We apologize for the inconvenience, and we'll continue to keep an eye on that particular host.
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-08-04 23:30 UTC, resolved after 0 min, 1 update(s).
- Title
- Database server hiccup caused 500 errors
- Vendor
- Bitbucket
- Date
- URL
- https://rewindex.com/company/bitbucket/incidents/j6qwyq84hmc8
Bitbucket profileRecent Bitbucket incidentsAll outages on August 4, 2015Bitbucket in August 2015MarkdownJSON