Bitbucket: Sporadic gitweb slowness, 500 errors, timeouts
Timeline of updates
- resolved
Users attempting to perform git operations over HTTPS between roughly 15:45 and 16:45 UTC may have experienced sporadic slowness, timeouts, or internal service errors. During that time, our servers were handling HTTP keepalives inappropriately on gitweb traffic, causing user connections to be queued improperly. We've resolved the issue, and traffic should be back to normal.
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 2016-01-04 12:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Sporadic gitweb slowness, 500 errors, timeouts
- Vendor
- Bitbucket
- Date
- URL
- https://rewindex.com/company/bitbucket/incidents/ghjkllnkhfnm
Bitbucket profileRecent Bitbucket incidentsAll outages on January 4, 2016Bitbucket in January 2016MarkdownJSON