Bitbucket: Increased error rates
Timeline of updates
- resolved
Between 12:52 to 13:58 UTC on Monday Nov 19, 2018 Bitbucket customers may have experienced increased error rates returned by some Bitbucket services such as webhooks and Pipelines. This was caused by an upstream dependency for the platform failing. Further information regarding how this problem impacted Bitbucket Pipelines: Some pipelines will not have been generated via pushes, if you do not see a pipeline after 15 minutes of then pushing it manually will allow you to start the pipeline correctly. Some pipelines failed during cloning, these builds are marked as failed and you will not be charged, in this case simply re-run them. Some build statuses in the Bitbucket API may be misaligned with the actual status in Pipelines, we are aware of this issue and will investigate a remedy.
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 2018-11-19 14:19 UTC, resolved after 0 min, 1 update(s).
- Title
- Increased error rates
- Vendor
- Bitbucket
- Date
- URL
- https://rewindex.com/company/bitbucket/incidents/nxb09vvd015w
Bitbucket profileRecent Bitbucket incidentsAll outages on November 19, 2018Bitbucket in November 2018MarkdownJSON