GlobalOutageMap
← Live dashboard
Bitbucket logoBitbucket

Bitbucket Cloud web, api, and Pipelines service outage

ResolvedminorOfficial source confirmedMulti-region impactFirst recorded update Jan 21, 2025, 03:30 PM · Resolved Jan 22, 2025, 12:08 AM

### Summary On January 21, 2025, between 14:02 and 17:49 UTC, Atlassian customers using Bitbucket Cloud were unable to use the website, API, or Pipelines. The event was triggered by write contention in a high traffic database table. The incident was detected within eight minutes. We then worked to both throttle traffic and improve query performance, which allowed services to recover. The total time to resolution was about three hours and 47 minutes. ### **IMPACT** The overall impact was between 14:02 and 17:49 UTC, affecting Bitbucket Cloud. This impacted customers globally, and they...

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

Affected services

WebsiteAPIGit via SSHAuthentication and user managementGit via HTTPSWebhooksSource downloadsPipelinesGit LFSEmail deliveryPurchasing & LicensingSignup

Updates (9)

  1. Jan 28, 2025, 06:13 PM
    Bitbucket Cloud web, api, and Pipelines service outage

    ### Summary On January 21, 2025, between 14:02 and 17:49 UTC, Atlassian customers using Bitbucket Cloud were unable to use the website, API, or Pipelines. The event was triggered by write contention in a high traffic database table. The incident was detected within eight minutes. We then worked to both throttle traffic and improve query performance, which allowed services to recover. The total time to resolution was about three hours and 47 minutes. ### **IMPACT** The overall impact was between 14:02 and 17:49 UTC, affecting Bitbucket Cloud. This impacted customers globally, and they were u

    Bitbucket ↗
  2. Jan 22, 2025, 12:08 AM
    Bitbucket Cloud web, api, and Pipelines service outage

    Earlier we experienced database contention on high traffic tables, which resulted in website, API, and Pipelines outages. All Bitbucket services are now operational. A full post mortem will be published.

    Bitbucket ↗
  3. Jan 21, 2025, 08:08 PM
    Bitbucket Cloud web, api, and Pipelines service outage

    All Git, Web, API and Pipelines services are now operational. We are continuing to monitor database and Pipelines reliability.

    Bitbucket ↗
  4. Jan 21, 2025, 07:28 PM
    Bitbucket Cloud web, api, and Pipelines service outage

    We have identified the root cause of the database issue that impacted Bitbucket website and Git operations; this has been mitigated now. We are experiencing Pipelines degradation that we are working to resolve.

    Bitbucket ↗
  5. Jan 21, 2025, 06:02 PM
    Bitbucket Cloud web, api, and Pipelines service outage

    We have identified the root cause of the database issue and have mitigated the problem. We are now monitoring closely.

    Bitbucket ↗
  6. Jan 21, 2025, 05:49 PM
    Bitbucket Cloud web, api, and Pipelines service outage

    We are investigating an issue with saturated Bitbucket database that impacts all Bitbucket operations. We will provide more details within the next 30 minutes.

    Bitbucket ↗
  7. Jan 21, 2025, 05:07 PM
    Bitbucket Cloud web, api, and Pipelines service outage

    We are investigating an issue with saturated Bitbucket database that impacts all Bitbucket operations. We will provide more details within the next hour.

    Bitbucket ↗
  8. Jan 21, 2025, 03:58 PM
    Bitbucket Cloud web, api, and Pipelines service outage

    We are still investigating an issue with Bitbucket Web and Git operations that is impacting Atlassian Bitbucket Cloud customers. We will provide more details within the next hour.

    Bitbucket ↗
  9. Jan 21, 2025, 03:30 PM
    Bitbucket Cloud web, api, and Pipelines service outage

    We are investigating an issue with Bitbucket Web and Git operations that is impacting Atlassian Bitbucket Cloud customers. We will provide more details within the next hour.

    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.