GlobalOutageMap
← Live dashboard
Bitbucket logoBitbucket

Unable to connect to Bitbucket Cloud via SSH

ResolvedminorOfficial source confirmedFirst recorded update Sep 9, 2024, 06:30 PM · Resolved Sep 9, 2024, 06:30 PM

### **SUMMARY** On September 10, 2024, between 6:34 PM UTC and 7:19 PM UTC, some Atlassian customers experienced an issue preventing users from connecting to Bitbucket Cloud via SSH. The issue arose from a change in how we determined IP allow lists, which inadvertently blocked access for customers with these controls enabled. The incident was promptly identified through our monitoring systems, and our teams initiated response protocols to mitigate the issue. ### **IMPACT** The incident only affected customers who had IP whitelisting enabled on their Bitbucket Cloud accounts. These...

Bitbucket live status →

Free for 3 services · Pro adds recovery alertsAdd to Chrome

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Bitbucket now? Check the current status

Updates (2)

  1. Sep 13, 2024, 05:20 PM
    Unable to connect to Bitbucket Cloud via SSH

    ### **SUMMARY** On September 10, 2024, between 6:34 PM UTC and 7:19 PM UTC, some Atlassian customers experienced an issue preventing users from connecting to Bitbucket Cloud via SSH. The issue arose from a change in how we determined IP allow lists, which inadvertently blocked access for customers with these controls enabled. The incident was promptly identified through our monitoring systems, and our teams initiated response protocols to mitigate the issue. ### **IMPACT** The incident only affected customers who had IP whitelisting enabled on their Bitbucket Cloud accounts. These customers

    Bitbucket ↗
  2. Sep 9, 2024, 08:30 PM
    Unable to connect to Bitbucket Cloud via SSH

    We experienced connectivity issues with Bitbucket Cloud via SSH, which only affected customers using IP allow listing. The service was unavailable for approximately 40 minutes. However, the issue was identified and resolved, and service was restored around 19:23 UTC.

    Bitbucket ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow Bitbucket's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.