Bitbucket: Brief degradation on all services
Timeline of updates
- resolved
A piece of hardware in Bitbucket's internal network infrastructure failed at roughly 17:38 UTC on Saturday 18th February 2017. Automated failover systems kicked in as intended, and performed as intended; the load balancers also began queueing connection requests (as intended) while the failover process completed. Unfortunately, all this intentional behavior led to an unintentional time of service degradation between (roughly) 17:38 and 17:45; load balancer backlogs caused many requests to wait far longer than anticipated, and some requests may have timed out as a result. We apologize for any inconvenience, and we're re-examining our failover strategy so that the backlog remains small when this happens next.
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 2017-02-18 12:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Brief degradation on all services
- Vendor
- Bitbucket
- Date
- URL
- https://rewindex.com/company/bitbucket/incidents/49kl7w7mj1mq
Bitbucket profileRecent Bitbucket incidentsAll outages on February 18, 2017Bitbucket in February 2017MarkdownJSON