Bitbucket Outage History

Started Jul 01, 2025, 03:03 AM UTC· resolved Jul 01, 2025, 05:12 AM UTC

1. investigating Jul 01, 2025, 03:03 AM UTC

   We are aware of some users experiencing issues when attempting to load Bitbucket. Our team is investigating with urgency and will provide an update as soon as possible.

2. investigating Jul 01, 2025, 04:03 AM UTC

   We are continuing to investigate issues that are being experienced by users attempting to load Bitbucket. We apologize for any inconvenience this has caused and we will provide further updates as soon as possible.

3. monitoring Jul 01, 2025, 04:44 AM UTC

   Our team has identified a network configuration error that was causing the issues relating to Bitbucket being unavailable for some users. This error has now been rectified. We will continue to monitor services closely. Additional updates will continue to be shared here.

4. resolved Jul 01, 2025, 05:12 AM UTC

   Between 02:36 UTC to 04:45 UTC 1 July 2025, we experienced a network configuration error for Atlassian Bitbucket, resulting in the product being unavailable for most users during this time. The issue has been resolved and the service is operating normally.

5. postmortem Aug 19, 2025, 08:02 AM UTC

   **Incident Narrative** On July 1, 2025, at 02:36 UTC, a service disruption occurred leaving Atlassian customers unable to access Bitbucket. The primary issue was identified as an inconsistent network access control list \(ACL\) rule, which inadvertently blocked certain IP ranges necessary for file system access. This network misconfiguration caused a service outage until the rule was corrected at 04:35 UTC, restoring normal service operations. **Root Cause** The root cause of the incident was traced to a network ACL misconfiguration during a routine update. A race condition in the deployment software led to an inconsistent state. This left a gap in network traffic management, disrupting essential services and resulting in inaccessibility of Bitbucket functionalities. **Mitigators** To restore service, the team repaired the inconsistent network ACL configuration, recreated the missing network ACL rule, re-establishing connections to the affected file systems. **Actions** In response to the incident, we have implemented additional mechanisms to help prevent the inconsistent network configuration and better ensure the expected network ACL rules remain intact, including during deployment.

Read the full incident report →

Started Jun 25, 2025, 07:52 AM UTC· resolved Jun 25, 2025, 10:11 AM UTC

1. investigating Jun 25, 2025, 07:52 AM UTC

   We are investigating cases of degraded performance for Atlassian Bitbucket Cloud customers. We will provide more details within the next hour.

2. identified Jun 25, 2025, 09:31 AM UTC

   We continue to work on resolving the degraded performance and intermittent failures (due to slow loading times) for Atlassian Bitbucket. We have identified the root cause and taken mitigations to handle the increased load and expect recovery shortly.

3. monitoring Jun 25, 2025, 09:50 AM UTC

   We have identified the root cause of the degraded performance and have mitigated the problem. We are now monitoring closely.

4. resolved Jun 25, 2025, 10:11 AM UTC

   Between 06:35 to 9:27 UTC, we experienced degraded performance for Atlassian Bitbucket. The issue has been resolved and the service is operating normally.

Read the full incident report →

Started Jun 13, 2025, 01:14 PM UTC· resolved Jun 13, 2025, 03:52 PM UTC

1. investigating Jun 13, 2025, 01:14 PM UTC

   We’re experiencing a recurrence of the intermittent issue affecting Bitbucket cloud. Our team is working diligently to resolve this issue, and we’ll keep you posted with further updates.

2. investigating Jun 13, 2025, 01:59 PM UTC

   Our team is focused on investigating and resolving the intermittent issues with Bitbucket, and we’ll keep you posted with further updates.

3. identified Jun 13, 2025, 02:48 PM UTC

   Our team continues to actively investigate and monitor the intermittent issues with Bitbucket. We are working to ensure full stability and will provide further updates as more information becomes available.

4. resolved Jun 13, 2025, 03:52 PM UTC

   Between 08:15 and 14:10 UTC on June 14th, 2025, some Bitbucket Cloud customers experienced an issue loading pages and executing API requests. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The conditions that cause the issue have been addressed and we’re actively working on a permanent fix. Services are now operating normally. Once we complete our internal incident review process, we will publish a more detailed postmortem of what went wrong, along with steps we're taking to prevent this from happening again in the future.

5. postmortem Jun 27, 2025, 03:11 AM UTC

   ### **SUMMARY** On June 13, 2025, between 08:58 UTC and 09:34 UTC, a subset of Bitbucket website and API users experienced an error page when attempting to load the website or make API requests. This was caused by high resource usage on a core Bitbucket service’s database, leading to an increase in query response times. A reoccurrence of the issue impacted website reliability again between 12:24 UTC and 14:02 UTC. The incident was detected within 6 minutes by monitoring and was fully mitigated by running scaling database capacity, running database maintenance operations, and removing a faulty read replica, which put Atlassian systems into a known good state. The total time to resolution was about 36 minutes for the first occurrence and one hour and 38 minutes for the second occurrence. ### **IMPACT** The total window during which we saw the impact was June 13, 2025, between 08:58 UTC and 14:02 UTC. The incident caused service disruption to customers trying to access the [Bitbucket.org](http://bitbucket.org/) website and APIs. Customers may have seen a “something went wrong” error page when trying to access the website or APIs. Git operations over SSH and HTTPS were not impacted. ### **ROOT CAUSE** The issue originated from a problem with query plan execution time on read replica instances. This led to increased query latency, spikes in CPU usage, and ultimately resulted in longer request times. As a result, the influx of incoming requests to Bitbucket led to a saturation of connections. This resulted in Bitbucket web requests returning slowly or showing an error page. ### **REMEDIAL ACTION PLAN & NEXT STEPS** We fully understand that outages impact your productivity. While we have a number of testing and preventative processes in place, this specific issue wasn’t identified with existing coverage. We are prioritizing the following improvement actions designed to avoid repeating this type of incident: * Continue to improve database resiliency and read replica routing for Bitbucket Cloud’s dependencies * Improve database monitoring and failover speed to reduce time to recovery * Run database maintenance tasks and improve process to discover and upgrade all databases to well known versions We apologize to customers whose services were impacted during this incident; we are taking steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support

Read the full incident report →

Started Jun 13, 2025, 09:14 AM UTC· resolved Jun 13, 2025, 11:21 AM UTC

1. investigating Jun 13, 2025, 09:14 AM UTC

   We are currently experiencing intermittent issues with Bitbucket. Our team is working diligently to resolve this issue, and we'll keep you posted with further updates.

2. investigating Jun 13, 2025, 09:53 AM UTC

   Our team is still investigating the intermittent issues with Bitbucket, and we’ll keep you posted with further updates.

3. monitoring Jun 13, 2025, 10:31 AM UTC

   The issues causing intermittence in Bitbucket have been mitigated, and services are now operating normally for all affected users. We will monitor it closely to ensure stability.

4. resolved Jun 13, 2025, 11:21 AM UTC

   On June 13, Bitbucket Cloud experienced intermittent availability. The issue has now been resolved, and the service is operating normally for all affected users.

Read the full incident report →

Started Jun 04, 2025, 05:17 PM UTC· resolved Jun 04, 2025, 08:59 PM UTC

1. investigating Jun 04, 2025, 05:17 PM UTC

   We were experiencing cases of degraded performance for outgoing emails from Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas and Compass Cloud customers. The system is recovering and mail is being processed normally as of 16:45 UTC. We will continue to monitor system performance and will provide more details within the next hour.

2. resolved Jun 04, 2025, 05:59 PM UTC

   Between 2025-06-04 14:11 UTC to 20:18 UTC, we experienced delays in delivering emails for Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas, Compass. The issue has been resolved and the service is operating normally.

Read the full incident report →

Started May 30, 2025, 01:42 PM UTC· resolved May 30, 2025, 03:00 PM UTC

1. investigating May 30, 2025, 01:42 PM UTC

   We are investigating an issue affecting Bitbucket, where steps are queued and delayed from starting. Our team is working diligently to resolve this issue and restore services as quickly as possible. We'll keep you posted with further updates.

2. identified May 30, 2025, 02:08 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring May 30, 2025, 02:44 PM UTC

   The Bitbucket issues, where steps were queued and delayed, have been mitigated. Services are now functioning normally for all affected customers. We will monitor it closely to ensure stability.

4. resolved May 30, 2025, 03:00 PM UTC

   On May 30th, there was an issue where Bitbucket pipeline steps were queued and delayed from starting. This problem has now been resolved, and the service operates normally for all customers.

Read the full incident report →

Started May 25, 2025, 11:45 PM UTC· resolved May 26, 2025, 12:56 AM UTC

1. investigating May 25, 2025, 11:45 PM UTC

   We are aware of some users experiencing issues loading Bitbucket and may be receiving errors such as '500 internal server error'. Our team is investigating this issue with urgency and will provide an update as soon as possible.

2. monitoring May 26, 2025, 12:24 AM UTC

   Our team has mitigated the issue that caused error messages when loading Bitbucket. We are continuing to monitor at this time to ensure performance has been restored, and resolve the root cause.

3. resolved May 26, 2025, 12:56 AM UTC

   Our team has mitigated the issue that caused error messages when loading Bitbucket. Bitbucket should now function correctly for all previously impacted users.

Read the full incident report →

Started May 08, 2025, 03:41 PM UTC· resolved May 09, 2025, 11:17 AM UTC

1. investigating May 08, 2025, 03:41 PM UTC

   We are currently investigating this issue.

2. identified May 08, 2025, 03:45 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring May 08, 2025, 03:57 PM UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring May 08, 2025, 06:48 PM UTC

   We are continuing to monitor for any further issues.

5. monitoring May 08, 2025, 09:11 PM UTC

   We are continuing to monitor for any further issues.

6. monitoring May 08, 2025, 11:25 PM UTC

   We are continuing to monitor for any further issues.

7. monitoring May 09, 2025, 01:21 AM UTC

   We are continuing to monitor for any further issues.

8. monitoring May 09, 2025, 04:33 AM UTC

   We are continuing to monitor for any further issues.

9. monitoring May 09, 2025, 07:20 AM UTC

   We are continuing to monitor for any further issues.

10. resolved May 09, 2025, 11:17 AM UTC

    This incident has been resolved.

11. postmortem May 19, 2025, 04:42 PM UTC

    ### 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 downstream services continued to impact overall database performance. Customers may have seen intermittent errors or website latency during this time. During this period following the failover, the engineering team implemented several strategies to further shed database load, successfully alleviating pressure on resources and improving performance. On May 9th at 11:19 AM UTC, Bitbucket Cloud systems were fully operational. ### **Impact** The overall impact occurred between May 8th, 2025, at 3:26 PM and May 9th at 11:19 AM UTC on Bitbucket Cloud. The incident resulted in increased latency and intermittent failures across Bitbucket Cloud services, including the website, API, and Bitbucket Pipelines. ### **Root cause** The issue was caused by an internal high-scale backfill job that triggered excessive load on certain API endpoints, which eventually impacted the database through resource-intensive queries and operations. This led to additional load from retries by dependent services, increasing the total recovery time. ### **Remedial action plan and next steps** We know that outages impact your productivity. While we have several testing and preventative processes in place, this specific issue wasn’t identified during our testing, as it was related to a specific high-scale backfill job run by an internal component, which impacted highly resource-intensive database queries. To prevent this type of incident from recurring, we are prioritizing the following improvement actions: * Improve database request routing so that more reads go to read replicas instead of the write-primary database. * Adjust rate limits for internal API endpoints with resource-intensive database operations. * Optimize database queries so that they can run more efficiently. * Tune retry policies from downstream services. We apologize to customers whose services were interrupted by this incident, and we are taking immediate steps to improve the platform’s reliability. Thanks, Atlassian Customer Support

Read the full incident report →

Started May 07, 2025, 08:40 PM UTC· resolved May 07, 2025, 10:24 PM UTC

1. investigating May 07, 2025, 08:40 PM UTC

   We are investigating an issue with pipeline builds not triggering that is impacting some Bitbucket customers. We will provide more details within the next hour.

2. identified May 07, 2025, 09:28 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring May 07, 2025, 10:00 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved May 07, 2025, 10:24 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 20, 2025, 06:11 AM UTC· resolved Mar 20, 2025, 07:01 AM UTC

1. investigating Mar 20, 2025, 06:11 AM UTC

   We are aware of an issue where users are receiving an error message when running a build. Although we believe builds are still running successfully our team is investigating with urgency and an update will be provided when available.

2. resolved Mar 20, 2025, 07:01 AM UTC

   The issue where users running builds would receive an error message should now be resolved. This issue was impacting only those using self-hosted runners. It is expected that builds should have still run as expected despite this error message in the meantime.

Read the full incident report →

Started Mar 11, 2025, 11:34 PM UTC· resolved Mar 12, 2025, 12:28 AM UTC

1. investigating Mar 11, 2025, 11:34 PM UTC

   Some customers are experiencing issues with our web and git operations. We are investigating.

2. investigating Mar 11, 2025, 11:35 PM UTC

   We are continuing to investigate this issue.

3. monitoring Mar 12, 2025, 12:03 AM UTC

   We are monitoring an identified fix and seeing signs of recovery.

4. resolved Mar 12, 2025, 12:28 AM UTC

   Between 11/Mar/25 23:02 UTC and 11/Mar/25 23:59 UTC, some Bitbucket Cloud customers experienced issues accessing our website, API, and git services. We have mitigated the problem and will take steps to avoid this issue in the future.

Read the full incident report →

Started Feb 20, 2025, 11:52 AM UTC· resolved Feb 20, 2025, 10:00 PM UTC

1. investigating Feb 20, 2025, 11:52 AM UTC

   We are currently investigating an issue impacting some customers who are seeing intermittent errors accessing the Bitbucket.org website.

2. identified Feb 20, 2025, 12:57 PM UTC

   We've identified an issue with some customers DNS configuration that can be blocking some Bitbucket assets. We are still investigating and will update statuspage with more information shortly.

3. identified Feb 20, 2025, 02:05 PM UTC

   We've identified an issue with some customers DNS configuration not resolving Atlassian domains correctly. If you are experiencing errors accessing Bitbucket, we advise allowlisting the following domains in your DNS configuration: https://support.atlassian.com/organization-administration/docs/ip-addresses-and-domains-for-atlassian-cloud-products/ We are still investigating the issue with vendors and will update statuspage as we learn more.

4. monitoring Feb 20, 2025, 06:44 PM UTC

   We have rolled out a fix for this issue and are seeing recovery for Bitbucket users. Please refresh the page and it should fix the issue. We are currently monitoring the fix and further investigating root cause.

5. resolved Feb 20, 2025, 10:00 PM UTC

   After monitoring, this incident is now resolved. If you continue to see issues, please ensure you are not using a stale / old tab and are loading a fresh version of Bitbucket in your browser.

Read the full incident report →

Started Jan 21, 2025, 03:30 PM UTC· resolved Jan 22, 2025, 12:08 AM UTC

1. investigating Jan 21, 2025, 03:30 PM UTC

   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.

2. investigating Jan 21, 2025, 03:58 PM UTC

   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.

3. investigating Jan 21, 2025, 05:07 PM UTC

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

4. investigating Jan 21, 2025, 05:49 PM UTC

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

5. monitoring Jan 21, 2025, 06:02 PM UTC

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

6. monitoring Jan 21, 2025, 07:28 PM UTC

   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.

7. monitoring Jan 21, 2025, 08:08 PM UTC

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

8. resolved Jan 22, 2025, 12:08 AM UTC

   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.

9. postmortem Jan 28, 2025, 06:13 PM UTC

   ### 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 unable to use the website, APIs, or Pipelines services. Git hosting \(SSH\) was unaffected. ### **ROOT CAUSE** The issue was caused by an increase in API traffic triggering write contention on a high-traffic table, resulting in increased CPU usage and degraded database performance. This ultimately impacted the availability of core services \(web, API, and Pipelines\). ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. While we have several testing and preventative processes in place, this specific issue wasn’t identified because the code path being triggered does not commonly experience this type of traffic. We are prioritizing the following improvement actions to avoid repeating this type of incident: * Running additional maintenance on core database tables * Added throttling on write-heavy operations To improve service resilience and recovery time for our environments, we will implement additional preventative measures such as: * Improving database observability to isolate failures * Continuing to shard data to better distribute traffic load We apologize to customers whose services were impacted by this incident and are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support

Read the full incident report →

Started Dec 31, 2024, 11:41 AM UTC· resolved Jan 02, 2025, 01:40 AM UTC

1. investigating Dec 31, 2024, 11:41 AM UTC

   Bitbucket Cloud support has observed a small increase in errors with all Bitbucket cloud APIs, we are investigating the issue and looking into root cause.

2. monitoring Dec 31, 2024, 01:14 PM UTC

   A solution has been implemented, and we're monitoring the fix to confirm resolution.

3. resolved Jan 02, 2025, 01:40 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 18, 2024, 12:51 PM UTC· resolved Dec 18, 2024, 01:35 PM UTC

1. identified Dec 18, 2024, 12:51 PM UTC

   We have identified the issue and we are working to fix the issue.

2. identified Dec 18, 2024, 12:53 PM UTC

   We are continuing to work on a fix for this issue.

3. monitoring Dec 18, 2024, 01:15 PM UTC

   A fix has been implemented and we are monitoring the result.

4. resolved Dec 18, 2024, 01:35 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 04, 2024, 09:37 AM UTC· resolved Nov 04, 2024, 12:02 PM UTC

1. investigating Nov 04, 2024, 09:37 AM UTC

   We are investigating reports of intermittent errors for some Atlassian customers when they are trying to invite users using their admin panels (admin.atlassian.com) We will provide more details once we identify the root cause.

2. identified Nov 04, 2024, 11:49 AM UTC

   We continue to work on resolving the invitation workflow in admin.atlassian.com We have identified the root cause and performed changes in the environment to mitigate the issue.

3. resolved Nov 04, 2024, 12:02 PM UTC

   Between 08:00 UTC to 11:54 UTC, we experienced problems with the invitation of new users for Cloud customers on admin.atlassian.com. The issue has been resolved and the service is operating normally.

Read the full incident report →