May 14, 06:48 UTC
Resolved - All products and services impacted by this incident should now be fully recovered, and this incident is resolved.

May 14, 06:41 UTC
Update - We are approaching full system recovery at this time, and are performing final confirmations that services are restored.

May 14, 06:40 UTC
Update - We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

May 14, 05:43 UTC
Monitoring - Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products.
We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place.

May 14, 05:34 UTC
Update - Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products.

At this time, Atlassian customers should also be able to once again raise support requests with our team.

We will provide further update within an hour as we are able to progress mitigating this issue.

May 14, 05:24 UTC
Update - It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident.

We are continuing to receive reports about expanded product impact resulting from this incident.

While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information.

We will provide further update within one hour, or sooner as further information becomes available.

May 14, 05:11 UTC
Identified - Further confirmations of impacted products have now been added to the incident.

Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.

May 14, 05:03 UTC
Investigating - We are aware that the current issues with accessing Atlassian products are impacting additional products. We have now expanded the impact of the incident to cover the known impacted products at this time.
We will provide further update within one hour or sooner as information is available.

May 8, 19:45 UTC
Resolved - On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.

May 8, 11:12 UTC
Update - Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team.

We apologise for the disruption and thank you for your patience.

May 8, 08:03 UTC
Update - We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.

May 8, 05:53 UTC
Monitoring - The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared.

May 8, 04:10 UTC
Update - We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each product page.

May 8, 04:10 UTC
Update - Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

May 8, 04:10 UTC
Update - We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

May 8, 03:00 UTC
Update - Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

May 8, 03:00 UTC
Update - We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

May 8, 02:15 UTC
Identified - We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

May 8, 01:31 UTC
Investigating - We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

Apr 16, 20:44 UTC
Resolved - On April 16 at 8:00PM UTC Bitbucket Pipelines users may have experienced performance degradation running new pipelines. The issue has now been resolved, and the service is operating normally for all affected customers.

Apr 16, 20:44 UTC
Update - We are investigating cases of degraded performance for Atlassian Bitbucket Pipelines customers. We mitigated an issue preventing new pipelines from starting, and have scaled up services are processing a backlog. Customers should see recovery shortly.

Apr 16, 20:23 UTC
Monitoring - We are investigating cases of degraded performance for Atlassian Bitbucket Pipelines customers. We mitigated an issue preventing new pipelines from starting, and have scaled up services are processing a backlog. Customers should see recovery shortly.

Apr 13, 10:17 UTC
Resolved - On April 13, 2026, between 05:49 a.m. and 06:25 a.m. UTC, some users were unable to log in to Atlassian products with their Atlassian accounts. The underlying issue has been addressed, and authentication services have remained stable with no new impact observed.

Apr 13, 08:33 UTC
Update - Atlassian account login services are now operating as expected, and we are not observing new errors. We continue to closely monitor our systems to ensure they remain stable. We will provide another update within 60 minutes or sooner if we detect a change in status.

Apr 13, 07:29 UTC
Monitoring - Our team is aware that some users were unable to log in to Atlassian products with their Atlassian accounts. While we believe this issue is now resolved, we are continuing to monitor all products and services for any ongoing impact.

Our team is investigating with urgency, and we will provide an update within 1 hour.

Mar 12, 12:33 UTC
Resolved - We have successfully mitigated the incident, and the affected service is now fully operational. Our teams have verified that normal functionality has been restored and the service is performing as expected.

Mar 12, 12:05 UTC
Update - Our engineers continue to work actively to identify the root cause. Meanwhile, the affected service is now stable and the error rate has decreased. We will share more details within the next hour, or sooner if more information becomes available.

Mar 12, 10:52 UTC
Update - Our engineers are actively working to resolve the Bitbucket Cloud disruption. No new updates at this moment. We will share more details within the next hour or as soon as we more information is available.

Mar 12, 09:40 UTC
Update - We are actively investigating reports of a service disruption affecting Bitbucket Cloud. We'll share updates here within the next hour or as more information is available.

Mar 12, 08:48 UTC
Investigating - We are actively investigating a service disruption impacting Bitbucket for some customers. We'll share updates here as more information is available.

Mar 6, 05:11 UTC
Resolved - On 06 March 2026 UTC, Bitbucket experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Mar 6, 05:00 UTC
Update - Our team has now put mitigations in place across the majority of Bitbucket services and all are now actively recovering except for Pipelines, which is still being actively investigated.
We are continuing to monitor these services and we will provide further update within 1 hour or when services have fully recovered.

Mar 6, 04:04 UTC
Update - As restoration activities continue, we are now starting to see services recover for customers for Bitbucket Web and for Git HTTPS. We are continuing to work on mitigation across all remaining Bitbucket services.
Our next update will be provided within one hour or if full recovery is seen prior to that time.

Mar 6, 03:10 UTC
Identified - We have identified the cause of the issue, and our teams are diligently working on a mitigation. Affected users will experience Bitbucket being unavailable.
We'll continue to share additional updates here as more information is available, with our next update to be posted within 1 hour.

Mar 6, 02:44 UTC
Investigating - We are actively investigating a service disruption impacting Bitbucket for some customers. We'll share updates here as more information is available.

Jan 28, 20:00 UTC
Resolved - On January 28, 2026, affected Bitbucket Cloud users in eu-west-1 may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.

Jan 28, 16:49 UTC
Monitoring - We received reports of a partial service disruption affecting Bitbucket in eu-west-1 for some customers. We have identified the cause of the issue and our teams have applied mitigations and we are seeing signs of recovery. We'll continue to monitor closely to confirm stability.

Jan 7, 18:53 UTC
Resolved - On Wednesday, January 7, 2026, Bitbucket Cloud experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Jan 7, 17:49 UTC
Monitoring - The issue has now been resolved, and the service is operating normally for all affected customers. We will continue to monitor closely to confirm stability.

Jan 7, 16:38 UTC
Update - We are actively investigating reports of a service disruption affecting Bitbucket Cloud. We'll share updates here within the next hour or as more information is available.

Jan 7, 16:23 UTC
Investigating - We are actively investigating reports of a partial service disruption affecting Bitbucket Cloud for some customers. We'll share updates here within the next hour or as more information is available.

Jan 7, 06:40 UTC
Resolved - We have successfully mitigated the incident and the affected service is now fully operational. Our teams have verified that normal functionality has been restored. Thank you for your patience and understanding while we worked to resolve this issue.

Jan 7, 06:05 UTC
Identified - Users of Bitbucket Cloud currently face difficulties when trying to invite new users to their workspaces. This issue is resulting in a '400 Client Error: Bad Request' message, which stems from a recent change in the invitation flow. The team is actively working on a resolution and is deploying a hotfix. We will provide an update within the next hour.

Dec 27, 05:20 UTC
Resolved - We have successfully mitigated the incident and all affected services are now fully operational. Our teams have verified that normal functionality has been restored across all areas.
Thank you for your patience and understanding while we worked to resolve this issue.

Dec 27, 04:42 UTC
Monitoring - We have taken steps to mitigate the issue and are seeing recovery in the affected services. Our teams will continue to closely monitor the situation and are actively working to confirm that all services are fully restored. We will provide further updates as we make additional progress.