Bitbucket: Git via HTTP is delayed, some commands are failing with 502 bad gateway
Timeline of updates
- resolved
Our engineering team resolved this issue at 8:05 UTC. All Bitbucket systems are up and running.
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 2018-10-20 07:41 UTC, resolved after 41 min, 1 update(s).
- Title
- Git via HTTP is delayed, some commands are failing with 502 bad gateway
- Vendor
- Bitbucket
- Date
- URL
- https://rewindex.com/company/bitbucket/incidents/k57q49r8k63q
Bitbucket profileRecent Bitbucket incidentsAll outages on October 20, 2018Bitbucket in October 2018MarkdownJSON