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

WebsiteAPIPipelines

Updates (11)

May 19, 2025, 04:42 PM
Bitbucket has degraded performance
### Summary On May 8, 2025, at 3:26pm UTC, Bitbucket Cloud experienced website and API latency due to an overloaded primary database. The event was caused by a backfill job running from an internal Atlassian service, which triggered an excessive call volume of expensive queries and pressure on database resources. As a result, the primary database automatically failed over, and Bitbucket services recovered in 15 minutes. Our real-time monitoring detected the incident immediately, and the high-intensity backfill job was stopped. However, following the failover, a backlog of retries from downst
Bitbucket ↗
May 9, 2025, 11:17 AM
Bitbucket has degraded performance
This incident has been resolved.
Bitbucket ↗
May 9, 2025, 07:20 AM
Bitbucket has degraded performance
We are continuing to monitor for any further issues.
Bitbucket ↗
May 9, 2025, 04:33 AM
Bitbucket has degraded performance
We are continuing to monitor for any further issues.
Bitbucket ↗
May 9, 2025, 01:21 AM
Bitbucket has degraded performance
We are continuing to monitor for any further issues.
Bitbucket ↗
May 8, 2025, 11:25 PM
Bitbucket has degraded performance
We are continuing to monitor for any further issues.
Bitbucket ↗
May 8, 2025, 09:11 PM
Bitbucket has degraded performance
We are continuing to monitor for any further issues.
Bitbucket ↗
May 8, 2025, 06:48 PM
Bitbucket has degraded performance
We are continuing to monitor for any further issues.
Bitbucket ↗
May 8, 2025, 03:57 PM
Bitbucket has degraded performance
A fix has been implemented and we are monitoring the results.
Bitbucket ↗
May 8, 2025, 03:45 PM
Bitbucket has degraded performance
The issue has been identified and a fix is being implemented.
Bitbucket ↗
May 8, 2025, 03:41 PM
Bitbucket has degraded performance
We are currently investigating this issue.
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.