Atlassian Outage History

Started Feb 03, 2026, 10:19 AM UTC· resolved Feb 03, 2026, 10:50 AM UTC

1. investigating Feb 03, 2026, 10:19 AM UTC

   Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

2. investigating Feb 03, 2026, 10:24 AM UTC

   Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

3. resolved Feb 03, 2026, 10:50 AM UTC

   Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.

Read the full incident report →

Started Feb 03, 2026, 10:19 AM UTC· resolved Feb 03, 2026, 10:50 AM UTC

1. investigating Feb 03, 2026, 10:19 AM UTC

   Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

2. investigating Feb 03, 2026, 10:24 AM UTC

   Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

3. resolved Feb 03, 2026, 10:50 AM UTC

   Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.

Read the full incident report →

Started Feb 03, 2026, 10:19 AM UTC· resolved Feb 03, 2026, 10:50 AM UTC

1. investigating Feb 03, 2026, 10:19 AM UTC

   Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

2. investigating Feb 03, 2026, 10:24 AM UTC

   Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

3. resolved Feb 03, 2026, 10:50 AM UTC

   Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.

Read the full incident report →

Started Feb 03, 2026, 10:19 AM UTC· resolved Feb 03, 2026, 10:50 AM UTC

1. investigating Feb 03, 2026, 10:19 AM UTC

   Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

2. investigating Feb 03, 2026, 10:24 AM UTC

   Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

3. resolved Feb 03, 2026, 10:50 AM UTC

   Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.

Read the full incident report →

Started Jan 28, 2026, 06:12 PM UTC· resolved Jan 28, 2026, 07:42 PM UTC

1. identified Jan 28, 2026, 06:12 PM UTC

   We are actively investigating an issue affecting Jira, Jira Product Discovery, and Jira Service Management. Affected users may experience delayed issue data in some experiences, such as issue view. We will share updates here in one hour or as more information becomes available.

2. identified Jan 28, 2026, 06:50 PM UTC

   We are continuing to investigate an issue affecting Jira, Jira Product Discovery, and Jira Service Management. Affected users may experience delayed issue data in some experiences, such as issue view. We will share updates here in one hour or as more information becomes available.

3. resolved Jan 28, 2026, 07:42 PM UTC

   On Jan 28, 2026, Jira, Jira Product Discovery, and Jira Service Management users in eu-west-1 region may have experienced delays in viewing recently submitted updates on the web page and/or mobile apps. Updates continued to process successfully during the incident. There are no actions needed from customers. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Jan 28, 2026, 06:12 PM UTC· resolved Jan 28, 2026, 07:42 PM UTC

1. identified Jan 28, 2026, 06:12 PM UTC

   We are actively investigating an issue affecting Jira, Jira Product Discovery, and Jira Service Management. Affected users may experience delayed issue data in some experiences, such as issue view. We will share updates here in one hour or as more information becomes available.

2. identified Jan 28, 2026, 06:50 PM UTC

   We are continuing to investigate an issue affecting Jira, Jira Product Discovery, and Jira Service Management. Affected users may experience delayed issue data in some experiences, such as issue view. We will share updates here in one hour or as more information becomes available.

3. resolved Jan 28, 2026, 07:42 PM UTC

   On Jan 28, 2026, Jira, Jira Product Discovery, and Jira Service Management users in eu-west-1 region may have experienced delays in viewing recently submitted updates on the web page and/or mobile apps. Updates continued to process successfully during the incident. There are no actions needed from customers. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Jan 28, 2026, 06:12 PM UTC· resolved Jan 28, 2026, 07:42 PM UTC

1. identified Jan 28, 2026, 06:12 PM UTC

   We are actively investigating an issue affecting Jira, Jira Product Discovery, and Jira Service Management. Affected users may experience delayed issue data in some experiences, such as issue view. We will share updates here in one hour or as more information becomes available.

2. identified Jan 28, 2026, 06:50 PM UTC

   We are continuing to investigate an issue affecting Jira, Jira Product Discovery, and Jira Service Management. Affected users may experience delayed issue data in some experiences, such as issue view. We will share updates here in one hour or as more information becomes available.

3. resolved Jan 28, 2026, 07:42 PM UTC

   On Jan 28, 2026, Jira, Jira Product Discovery, and Jira Service Management users in eu-west-1 region may have experienced delays in viewing recently submitted updates on the web page and/or mobile apps. Updates continued to process successfully during the incident. There are no actions needed from customers. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Jan 28, 2026, 06:12 PM UTC· resolved Jan 28, 2026, 07:42 PM UTC

1. identified Jan 28, 2026, 06:12 PM UTC

   We are actively investigating an issue affecting Jira, Jira Product Discovery, and Jira Service Management. Affected users may experience delayed issue data in some experiences, such as issue view. We will share updates here in one hour or as more information becomes available.

2. identified Jan 28, 2026, 06:50 PM UTC

   We are continuing to investigate an issue affecting Jira, Jira Product Discovery, and Jira Service Management. Affected users may experience delayed issue data in some experiences, such as issue view. We will share updates here in one hour or as more information becomes available.

3. resolved Jan 28, 2026, 07:42 PM UTC

   On Jan 28, 2026, Jira, Jira Product Discovery, and Jira Service Management users in eu-west-1 region may have experienced delays in viewing recently submitted updates on the web page and/or mobile apps. Updates continued to process successfully during the incident. There are no actions needed from customers. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Jan 28, 2026, 05:34 PM UTC· resolved Jan 28, 2026, 07:20 PM UTC

1. investigating Jan 28, 2026, 05:34 PM UTC

   We are actively investigating reports of a partial service disruption affecting Forge. We'll share updates here as more information is available.

2. investigating Jan 28, 2026, 06:33 PM UTC

   We continue to investigate the issue, and will share updates here as more information becomes available.

3. monitoring Jan 28, 2026, 07:02 PM UTC

   The issue has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor closely to confirm stability.

4. resolved Jan 28, 2026, 07:20 PM UTC

   On January 28, 2026, some customers may have experienced Forge function invocation availability disruption. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Jan 28, 2026, 04:49 PM UTC· resolved Jan 28, 2026, 08:00 PM UTC

1. monitoring Jan 28, 2026, 04:49 PM UTC

   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.

2. resolved Jan 28, 2026, 08:00 PM UTC

   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.

Read the full incident report →

Started Jan 27, 2026, 11:07 AM UTC· resolved Jan 27, 2026, 11:49 AM UTC

1. investigating Jan 27, 2026, 11:07 AM UTC

   We understand that some of our customers are facing intermittent issues with Assets. Our team is investigating the issue. We will update you on the progress within 60 minutes or sooner.

2. identified Jan 27, 2026, 11:33 AM UTC

   The incident has affected the Assets product, leading users encountering intermittent unavailability. Our team has identified the cause of the issue and deployed fix for the same. We see that the error rate has decreased, and the team is actively monitoring to ensure further stability. Further updates will follow in 60 minutes or upon significant progress.

3. resolved Jan 27, 2026, 11:49 AM UTC

   Deployment of the fix is completed and services are back to normal. This issue is resolved.

Read the full incident report →

Started Jan 27, 2026, 11:07 AM UTC· resolved Jan 27, 2026, 11:49 AM UTC

1. investigating Jan 27, 2026, 11:07 AM UTC

   We understand that some of our customers are facing intermittent issues with Assets. Our team is investigating the issue. We will update you on the progress within 60 minutes or sooner.

2. identified Jan 27, 2026, 11:33 AM UTC

   The incident has affected the Assets product, leading users encountering intermittent unavailability. Our team has identified the cause of the issue and deployed fix for the same. We see that the error rate has decreased, and the team is actively monitoring to ensure further stability. Further updates will follow in 60 minutes or upon significant progress.

3. resolved Jan 27, 2026, 11:49 AM UTC

   Deployment of the fix is completed and services are back to normal. This issue is resolved.

Read the full incident report →

Started Jan 22, 2026, 02:44 PM UTC· resolved Jan 22, 2026, 04:47 PM UTC

1. investigating Jan 22, 2026, 02:44 PM UTC

   Jira Service Management users are currently experiencing an issue where assets are not loading, affecting their interactions with service management functionality. We are currently investigating the issue, and the next update will be shared in 60 minutes or sooner

2. identified Jan 22, 2026, 03:41 PM UTC

   We have identified the cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience issue where assets are not loading, affecting their interactions with service management functionality. We will continue to share additional updates here as more information becomes available.

3. monitoring Jan 22, 2026, 04:32 PM UTC

   The issue has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor closely to confirm stability.

4. resolved Jan 22, 2026, 04:47 PM UTC

   On January 22, 2026, affected Jira Service Management users may have experienced some service disruption where assets were not loading, affecting their interactions with service management functionality. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Jan 22, 2026, 02:44 PM UTC· resolved Jan 22, 2026, 04:47 PM UTC

1. investigating Jan 22, 2026, 02:44 PM UTC

   Jira Service Management users are currently experiencing an issue where assets are not loading, affecting their interactions with service management functionality. We are currently investigating the issue, and the next update will be shared in 60 minutes or sooner

2. identified Jan 22, 2026, 03:41 PM UTC

   We have identified the cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience issue where assets are not loading, affecting their interactions with service management functionality. We will continue to share additional updates here as more information becomes available.

3. monitoring Jan 22, 2026, 04:32 PM UTC

   The issue has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor closely to confirm stability.

4. resolved Jan 22, 2026, 04:47 PM UTC

   On January 22, 2026, affected Jira Service Management users may have experienced some service disruption where assets were not loading, affecting their interactions with service management functionality. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Jan 20, 2026, 07:10 PM UTC· resolved Jan 20, 2026, 11:09 PM UTC

1. investigating Jan 20, 2026, 07:10 PM UTC

   Impact Users of the Assets product are experiencing intermittent accessibility issues, resulting in gateway timeouts and internal server errors. These technical disruptions are causing difficulties in performing queries, which may manifest as slow performance or failure to load certain pages, particularly those involving schemas. This issue affects related features that depend on the Assets product, such as specific custom fields and automation processes. Current Status The support teams are actively working to diagnose the issue and are focused on identifying the underlying problems causing the disruption. Efforts are ongoing to restore normal service levels and minimize any further inconvenience to users. Next Steps The incident team is continuing its investigation to determine the full extent of the impact and to identify effective resolutions. Further communications will be issued in 60 minutes or when significant progress is made.

2. investigating Jan 20, 2026, 08:08 PM UTC

   We continue to investigate the issue, and next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

3. monitoring Jan 20, 2026, 09:14 PM UTC

   The performance degradation of Assets has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

4. resolved Jan 20, 2026, 11:09 PM UTC

   On January 20, 2026, some customers may have experienced performance degradation of Assets. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Jan 20, 2026, 07:10 PM UTC· resolved Jan 20, 2026, 11:09 PM UTC

1. investigating Jan 20, 2026, 07:10 PM UTC

   Impact Users of the Assets product are experiencing intermittent accessibility issues, resulting in gateway timeouts and internal server errors. These technical disruptions are causing difficulties in performing queries, which may manifest as slow performance or failure to load certain pages, particularly those involving schemas. This issue affects related features that depend on the Assets product, such as specific custom fields and automation processes. Current Status The support teams are actively working to diagnose the issue and are focused on identifying the underlying problems causing the disruption. Efforts are ongoing to restore normal service levels and minimize any further inconvenience to users. Next Steps The incident team is continuing its investigation to determine the full extent of the impact and to identify effective resolutions. Further communications will be issued in 60 minutes or when significant progress is made.

2. investigating Jan 20, 2026, 08:08 PM UTC

   We continue to investigate the issue, and next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

3. monitoring Jan 20, 2026, 09:14 PM UTC

   The performance degradation of Assets has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

4. resolved Jan 20, 2026, 11:09 PM UTC

   On January 20, 2026, some customers may have experienced performance degradation of Assets. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Jan 20, 2026, 07:10 PM UTC· resolved Jan 20, 2026, 11:09 PM UTC

1. investigating Jan 20, 2026, 07:10 PM UTC

   Impact Users of the Assets product are experiencing intermittent accessibility issues, resulting in gateway timeouts and internal server errors. These technical disruptions are causing difficulties in performing queries, which may manifest as slow performance or failure to load certain pages, particularly those involving schemas. This issue affects related features that depend on the Assets product, such as specific custom fields and automation processes. Current Status The support teams are actively working to diagnose the issue and are focused on identifying the underlying problems causing the disruption. Efforts are ongoing to restore normal service levels and minimize any further inconvenience to users. Next Steps The incident team is continuing its investigation to determine the full extent of the impact and to identify effective resolutions. Further communications will be issued in 60 minutes or when significant progress is made.

2. investigating Jan 20, 2026, 08:08 PM UTC

   We continue to investigate the issue, and next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

3. monitoring Jan 20, 2026, 09:14 PM UTC

   The performance degradation of Assets has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

4. resolved Jan 20, 2026, 11:09 PM UTC

   On January 20, 2026, some customers may have experienced performance degradation of Assets. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Jan 14, 2026, 02:26 PM UTC· resolved Jan 14, 2026, 11:09 PM UTC

1. investigating Jan 14, 2026, 02:26 PM UTC

   We are investigating an incident that is intermittently affecting Jira Align cloud customers. Due to this issue, customers might observe loss of some feature functionality. We shall keep you informed on the progress in 60 mins or sooner.

2. identified Jan 14, 2026, 03:26 PM UTC

   We have identified the cause of the issue and our teams are diligently working on a mitigation. Affected users may experience some loss of functionality. We'll continue to share additional updates here in one hour or as more information is available.

3. identified Jan 14, 2026, 04:30 PM UTC

   Our teams are continuing to diligently work on applying mitigations. Affected users may experience some loss of functionality. We'll continue to share additional updates here in one hour or as more information is available.

4. identified Jan 14, 2026, 05:25 PM UTC

   Our teams are continuing to diligently work on applying mitigations. Affected users may experience some loss of functionality. We'll continue to share additional updates here in one hour or as more information is available.

5. monitoring Jan 14, 2026, 06:30 PM UTC

   Our teams have deployed a fix and we are currently confirming service restorations. We'll continue to monitor closely to confirm stability. We'll continue to share additional updates here in one hour or as more information is available.

6. monitoring Jan 14, 2026, 07:25 PM UTC

   Our teams have deployed a fix and we are continuing confirmations of service restorations. We'll continue to monitor closely to confirm stability. We'll continue to share additional updates here in one hour or as more information is available.

7. monitoring Jan 14, 2026, 08:06 PM UTC

   Our teams have deployed a fix and we are continuing confirmations of service restorations. We'll continue to monitor closely to confirm stability. We'll continue to share additional updates here in two hours or as more information is available.

8. monitoring Jan 14, 2026, 10:02 PM UTC

   Our teams have deployed a fix and our internal analysis has confirmed of service restorations. We are now deploying the fix to Preview sites. We expect that deployment to complete in approximately one hour. We'll continue to share additional updates here in one hour or as more information is available.

9. resolved Jan 14, 2026, 11:09 PM UTC

   On January 14, 2026, some Jira Align Cloud users may have experienced service disruption. The issue has now been resolved and the service is operating normally for all affected customers.

Read the full incident report →

Started Jan 12, 2026, 06:23 PM UTC· resolved Jan 12, 2026, 11:45 PM UTC

1. investigating Jan 12, 2026, 06:23 PM UTC

   We are actively investigating reports of a partial service disruption affecting Jira create, view, view board, and edit issue for some customers. We'll share updates here as more information is available.

2. investigating Jan 12, 2026, 06:23 PM UTC

   We are continuing to actively investigate reports of a partial service disruption affecting Jira create issue, issue view, view board, and edit issue for some customers. We'll share updates here in one hour or as more information is available.

3. investigating Jan 12, 2026, 06:23 PM UTC

   Our teams are continuing to actively investigate reports of a partial service disruption affecting Jira create issue, issue view, view board, and edit issue for some customers. We'll share updates here in one hour or as more information is available.

4. investigating Jan 12, 2026, 07:26 PM UTC

   Our teams are continuing to actively investigate reports of a partial service disruption affecting Jira create issue, issue view, view board, and edit issue for some customers. We'll share updates here in one hour or as more information is available.

5. monitoring Jan 12, 2026, 07:26 PM UTC

   The issue has been resolved and services are now operating normally for all affected customers. We'll continue to monitor closely to confirm stability.

6. resolved Jan 12, 2026, 11:45 PM UTC

   The service disruption has been fully resolved, and services are now operating normally for all impacted customers.

Read the full incident report →

Started Jan 08, 2026, 03:27 PM UTC· resolved Jan 08, 2026, 07:09 PM UTC

1. investigating Jan 08, 2026, 03:27 PM UTC

   We are actively investigating reports of a partial service disruption affecting Confluence Cloud for some customers. We'll share updates here in an hour or as more information is available.

2. monitoring Jan 08, 2026, 04:35 PM UTC

   The issue has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor closely to confirm stability.

3. monitoring Jan 08, 2026, 04:36 PM UTC

   The issue has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor closely to confirm stability.

4. resolved Jan 08, 2026, 07:09 PM UTC

   On Thursday, January 8, 2026, affected Confluence Cloud users in us-east-1 region may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.

5. postmortem Jan 28, 2026, 01:49 AM UTC

   ### Summary On Jan 08, 2026 between 14:54 UTC and 16:30 UTC, Atlassian customers using Confluence Cloud product\(s\) experienced degraded service with view/edit page experiences. The event was triggered by database overload due to an unexpected large burst of traffic. The database overload was the result of a configuration change, which led to a sudden spike in database connections, which impacted a subset of customers in a single partition in the us-east region. The incident was detected within 1 minute by by automated monitoring systems and mitigated by reducing the number of web server hosts connecting to the database layer, which put Atlassian systems into a known good state. The total time to resolution was about 1 hour and 26 minutes. ### **IMPACT** The overall impact was between Jan 08, 2026, 14:54 UTC and 16:30 UTC on Confluence Cloud products. The incident caused service disruption to customers in a single partition in the us-east region impacting the ability to view and edit pages. We observed partition-wide database saturation due to an unexpected large burst of traffic. Confluence Cloud components impacted during this window were: Login, View / Edit Page, Publish Page, Add Page, Comment. ### **ROOT CAUSE** A change was introduced that caused cross-region traffic routing for customers instead of routing to the same region. Some caches processing customer data were stale, which heavily loaded the databases and caused them to restart. As a result, the users of the product above could not login, view or edit pages, and the users received HTTP 500 and 504 errors. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. While we have a number of testing and preventative processes in place, this specific issue wasn’t identified due to a specific set of factors which resulted in this condition. We are prioritizing the following improvement actions to help avoid repeating this type of incident: * Fix the routing issue that resulted in cross-regional traffic * Decrease maximum number of connections per database instance, to allow for sufficient memory capacity to handle a surge in connections Furthermore, we deploy our changes progressively \(by cloud region\) to avoid broad impact but in this case, the impact was larger than desired. To minimize the impact of breaking changes to our environments, we will implement additional preventative measures such as enabling automatic vertical scaling when database clusters are running low on memory. We apologize to customers whose services were impacted during this incident; we are taking steps to help improve the platform’s performance and availability. Thanks, Atlassian Customer Support

Read the full incident report →

Started Jan 07, 2026, 04:23 PM UTC· resolved Jan 07, 2026, 06:53 PM UTC

1. investigating Jan 07, 2026, 04:23 PM UTC

   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.

2. investigating Jan 07, 2026, 04:38 PM UTC

   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.

3. monitoring Jan 07, 2026, 05:49 PM UTC

   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.

4. resolved Jan 07, 2026, 06:53 PM UTC

   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.

5. postmortem Jan 30, 2026, 04:02 PM UTC

   ### Summary On Jan 7, 2026, between 15:28 UTC and 17:04 UTC, Atlassian customers using Bitbucket Cloud could not load the dashboard landing page. Users also faced degraded performance and intermittent failures navigating other parts of the application or using public REST APIs. The event was caused by an unexpected load on a public API, causing long-running queries on a database which resulted in failed web and api requests. The incident was detected within three minutes by automated monitoring systems and mitigated by introducing stricter limits on the API for certain traffic, while taking manual actions on the impacted database, restoring Bitbucket to a healthy state. ### **IMPACT** Occurring on Bitbucket Cloud on Jan 7, 2026, between 15:28 UTC and 17:04 UTC, the incident caused degraded performance and intermittent failures to a subset of customers interacting with the Bitbucket web application and public APIs. Git operations over SSH and HTTPS were not impacted. ### **ROOT CAUSE** The event was caused by an unexpected load on a public API. The request volume during this period resulted in high resource utilization our central database’s read replicas, impacting website and our API performance and reliability. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know outages reduce your productivity. Although we have several testing and prevention processes, this issue went undetected because a specific request pattern on a public API was not tested against the traffic volume seen during the incident. We prioritized the following actions to prevent repeating this type of incident: * Improve rate limiting and caching capabilities at multiple points in our networking and application layers. * Apply stricter rate limits for specific public APIs to protect infrastructure health and shared application resources. * Optimize performance of specific queries and codepaths on these APIs to handle high request loads. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support

Read the full incident report →

Started Jan 07, 2026, 06:05 AM UTC· resolved Jan 07, 2026, 06:40 AM UTC

1. identified Jan 07, 2026, 06:05 AM UTC

   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.

2. resolved Jan 07, 2026, 06:40 AM UTC

   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.

Read the full incident report →

Started Jan 06, 2026, 05:18 AM UTC· resolved Jan 07, 2026, 11:32 AM UTC

1. investigating Jan 06, 2026, 05:18 AM UTC

   We are investigating an incident impacting Automation for Jira across Jira and Jira Service Management. Some automation rules that use specific triggers may fail to execute. Our team is working to identify the cause and restore normal service. We will provide the next update within 60 minutes.

2. identified Jan 06, 2026, 06:17 AM UTC

   We have identified the cause of the issue, and our teams are diligently working on a mitigation. We will continue to share additional updates here as more information becomes available.

3. identified Jan 06, 2026, 07:58 AM UTC

   Our engineers are continuing work toward the resolution of the incident impacting Automation for Jira. There are no new updates to share at this time. We will provide the next update within 2 hours.

4. identified Jan 06, 2026, 10:11 AM UTC

   Customers using Jira and Jira Service Management in Asia Pacific and South East regions have faced issues with Automation for Jira. Other regions are not impacted. Some automation rules using specific triggers failed to execute, causing rules to appear unresponsive. We have identified the cause and we continue working on restoring the operations back to normal as soon as possible. In the meantime, workaround to manage business critical rules is to disable and then re-enable each automation rule. This action triggers the rule and must be done for every critical rule. We will provide the next update in about two hours or sooner.

5. identified Jan 06, 2026, 12:19 PM UTC

   Some automation rules using specific triggers failed to execute, causing rules to appear unresponsive. Customers using Jira and Jira Service Management in Asia Pacific and South East regions have faced issues with Automation for Jira. Other regions are not impacted. The cause has been identified, and the team is actively working on restoring the operations back to normal as soon as possible. Workaround to manage critical rules, disable and re-enable each automation rule. This triggers the rule and must be done for every critical rule. We will provide the next update in about two hours or sooner.

6. monitoring Jan 06, 2026, 02:04 PM UTC

   Issue has been fixed for all new events - we are waiting for confirmation from some customers when they come online. Customers using Jira and Jira Service Management in Asia Pacific and South East regions had faced issues with Automation for Jira. Other regions not impacted. During Asia Pacific hours tomorrow, the team plans to replay historical events. Team will continue monitoring. Next update will tomorrow.

7. monitoring Jan 07, 2026, 04:43 AM UTC

   We are currently replaying historical events for affected customers to rerun Automation for Jira rules that failed to execute earlier. Our teams are closely monitoring the results of this replay to confirm that all affected automations are running as expected. We will provide the next update in about two hours or sooner.

8. monitoring Jan 07, 2026, 08:37 AM UTC

   We have replayed about 7 hours of historical events for affected customers to rerun Automation for Jira rules that previously failed. This covers most of the APAC business hours. Based on customer feedback, our team continues monitoring the situation and plans to complete rerunning the remaining Automation for Jira rules that failed earlier. We will provide the next update once replaying the historical events is complete.

9. resolved Jan 07, 2026, 11:32 AM UTC

   Rerunning the remaining Automation for Jira rules that failed for affected customers is complete. This update resolves the issue.

Read the full incident report →

Started Jan 06, 2026, 05:18 AM UTC· resolved Jan 07, 2026, 11:32 AM UTC

1. investigating Jan 06, 2026, 05:18 AM UTC

   We are investigating an incident impacting Automation for Jira across Jira and Jira Service Management. Some automation rules that use specific triggers may fail to execute. Our team is working to identify the cause and restore normal service. We will provide the next update within 60 minutes.

2. identified Jan 06, 2026, 06:17 AM UTC

   We have identified the cause of the issue, and our teams are diligently working on a mitigation. We will continue to share additional updates here as more information becomes available.

3. identified Jan 06, 2026, 07:58 AM UTC

   Our engineers are continuing work toward the resolution of the incident impacting Automation for Jira. There are no new updates to share at this time. We will provide the next update within 2 hours.

4. identified Jan 06, 2026, 10:11 AM UTC

   Customers using Jira and Jira Service Management in Asia Pacific and South East regions have faced issues with Automation for Jira. Other regions are not impacted. Some automation rules using specific triggers failed to execute, causing rules to appear unresponsive. We have identified the cause and we continue working on restoring the operations back to normal as soon as possible. In the meantime, workaround to manage business critical rules is to disable and then re-enable each automation rule. This action triggers the rule and must be done for every critical rule. We will provide the next update in about two hours or sooner.

5. identified Jan 06, 2026, 12:19 PM UTC

   Some automation rules using specific triggers failed to execute, causing rules to appear unresponsive. Customers using Jira and Jira Service Management in Asia Pacific and South East regions have faced issues with Automation for Jira. Other regions are not impacted. The cause has been identified, and the team is actively working on restoring the operations back to normal as soon as possible. Workaround to manage critical rules, disable and re-enable each automation rule. This triggers the rule and must be done for every critical rule. We will provide the next update in about two hours or sooner.

6. monitoring Jan 06, 2026, 02:04 PM UTC

   Issue has been fixed for all new events - we are waiting for confirmation from some customers when they come online. Customers using Jira and Jira Service Management in Asia Pacific and South East regions had faced issues with Automation for Jira. Other regions not impacted. During Asia Pacific hours tomorrow, the team plans to replay historical events. Team will continue monitoring. Next update will tomorrow.

7. monitoring Jan 07, 2026, 04:43 AM UTC

   We are currently replaying historical events for affected customers to rerun Automation for Jira rules that failed to execute earlier. Our teams are closely monitoring the results of this replay to confirm that all affected automations are running as expected. We will provide the next update in about two hours or sooner.

8. monitoring Jan 07, 2026, 08:37 AM UTC

   We have replayed about 7 hours of historical events for affected customers to rerun Automation for Jira rules that previously failed. This covers most of the APAC business hours. Based on customer feedback, our team continues monitoring the situation and plans to complete rerunning the remaining Automation for Jira rules that failed earlier. We will provide the next update once replaying the historical events is complete.

9. resolved Jan 07, 2026, 11:32 AM UTC

   Rerunning the remaining Automation for Jira rules that failed for affected customers is complete. This update resolves the issue.

Read the full incident report →

Started Jan 06, 2026, 05:18 AM UTC· resolved Jan 07, 2026, 11:32 AM UTC

1. investigating Jan 06, 2026, 05:18 AM UTC

   We are investigating an incident impacting Automation for Jira across Jira and Jira Service Management. Some automation rules that use specific triggers may fail to execute. Our team is working to identify the cause and restore normal service. We will provide the next update within 60 minutes.

2. identified Jan 06, 2026, 06:17 AM UTC

   We have identified the cause of the issue, and our teams are diligently working on a mitigation. We will continue to share additional updates here as more information becomes available.

3. identified Jan 06, 2026, 07:58 AM UTC

   Our engineers are continuing work toward the resolution of the incident impacting Automation for Jira. There are no new updates to share at this time. We will provide the next update within 2 hours.

4. identified Jan 06, 2026, 10:11 AM UTC

   Customers using Jira and Jira Service Management in Asia Pacific and South East regions have faced issues with Automation for Jira. Other regions are not impacted. Some automation rules using specific triggers failed to execute, causing rules to appear unresponsive. We have identified the cause and we continue working on restoring the operations back to normal as soon as possible. In the meantime, workaround to manage business critical rules is to disable and then re-enable each automation rule. This action triggers the rule and must be done for every critical rule. We will provide the next update in about two hours or sooner.

5. identified Jan 06, 2026, 12:19 PM UTC

   Some automation rules using specific triggers failed to execute, causing rules to appear unresponsive. Customers using Jira and Jira Service Management in Asia Pacific and South East regions have faced issues with Automation for Jira. Other regions are not impacted. The cause has been identified, and the team is actively working on restoring the operations back to normal as soon as possible. Workaround to manage critical rules, disable and re-enable each automation rule. This triggers the rule and must be done for every critical rule. We will provide the next update in about two hours or sooner.

6. monitoring Jan 06, 2026, 02:04 PM UTC

   Issue has been fixed for all new events - we are waiting for confirmation from some customers when they come online. Customers using Jira and Jira Service Management in Asia Pacific and South East regions had faced issues with Automation for Jira. Other regions not impacted. During Asia Pacific hours tomorrow, the team plans to replay historical events. Team will continue monitoring. Next update will tomorrow.

7. monitoring Jan 07, 2026, 04:43 AM UTC

   We are currently replaying historical events for affected customers to rerun Automation for Jira rules that failed to execute earlier. Our teams are closely monitoring the results of this replay to confirm that all affected automations are running as expected. We will provide the next update in about two hours or sooner.

8. monitoring Jan 07, 2026, 08:37 AM UTC

   We have replayed about 7 hours of historical events for affected customers to rerun Automation for Jira rules that previously failed. This covers most of the APAC business hours. Based on customer feedback, our team continues monitoring the situation and plans to complete rerunning the remaining Automation for Jira rules that failed earlier. We will provide the next update once replaying the historical events is complete.

9. resolved Jan 07, 2026, 11:32 AM UTC

   Rerunning the remaining Automation for Jira rules that failed for affected customers is complete. This update resolves the issue.

Read the full incident report →