Bitbucket: Customers are reporting intermittent SSH failures
Timeline of updates
- resolved
Customers of Bitbucket attempting to use our SSH based service between roughly 12:11 PM to 12:59 PM UTC on February 10th may have experienced failures with the error message "Permission denied (publickey). fatal: Could not read from remote repository." Only a small percentage of overall customers would have experienced this problem. This was caused by one of our application servers responsible for our SSH service misbehaving. We have identified improvements to our load balancers that will prevent this situation from happening in the future.
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-10 12:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Customers are reporting intermittent SSH failures
- Vendor
- Bitbucket
- Date
- URL
- https://rewindex.com/company/bitbucket/incidents/t2gz4l2ljxm3
Bitbucket profileRecent Bitbucket incidentsAll outages on February 10, 2017Bitbucket in February 2017MarkdownJSON