Bitbucket: Investigating intermittent timeouts observed with HTTPS Clone operations
Timeline of updates
- resolved
From monitoring our systems and reaching out to affected customers over the past hour, our team is confident that this incident has been resolved. We will continue to monitor our Git services and follow up with an internal post-incident review.
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 2021-04-16 11:35 UTC, resolved after 1.9 h, 1 update(s).
- Title
- Investigating intermittent timeouts observed with HTTPS Clone operations
- Vendor
- Bitbucket
- Date
- URL
- https://rewindex.com/company/bitbucket/incidents/tjbnhmyrr1zw
Bitbucket profileRecent Bitbucket incidentsAll outages on April 16, 2021Bitbucket in April 2021MarkdownJSON