Bitbucket: Bitbucket Pipelines SSH Fingerprinting originating from undocumented sources.
Timeline of updates
- resolved
We've confirmed that our technical platform team have changed the outbound routing behaviour to send connections out from 52.8.84.222 and 52.52.234.127. We will be reviewing this change to better identify how we can schedule and communicate these changes to our customers.
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-02-14 02:16 UTC, resolved after 1.4 h, 1 update(s).
- Title
- Bitbucket Pipelines SSH Fingerprinting originating from undocumented sources.
- Vendor
- Bitbucket
- Date
- URL
- https://rewindex.com/company/bitbucket/incidents/qjfx5f128d35
Bitbucket profileRecent Bitbucket incidentsAll outages on February 14, 2018Bitbucket in February 2018MarkdownJSON