Atlassian Outage History
Atlassian is up right nowPingoru has recorded 1,025 incidents for Atlassian: 401 in the last 12 months and 71 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 37 | 65 of 720 (9%) |
| May 2026 | 83 | 286 of 744 (38%) |
| June 2026 | 34 | 267 of 720 (37%) |
| July 2026 | 17 | 130 of 744 (17%) |
| August 2026 | 27 | 131 of 744 (18%) |
| September 2026 | 25 | 77 of 720 (11%) |
| October 2026 | 18 | 17 of 587 (3%) |
Incidents, newest first
Major August 25, 2026 Notifications are delayed 5h 51m via Confluence· View Content, iOS App, Create and Edit, Android App and 11 more
Started Aug 25, 2026, 08:42 AM UTC· resolved Aug 25, 2026, 02:33 PM UTC
- investigating Aug 25, 2026, 08:42 AM UTC
We are actively investigating reports of performance degradation resulting in increased latency for email, mobile, and slack notifications for Jira, JSM and Confluence. Our teams are investigating the issue and more information will be shared within the next 1 hour.
- investigating Aug 25, 2026, 09:44 AM UTC
Our teams have identified the impacted regions and are actively working to mitigate the issue. We will provide further updates within an hour, or sooner if we have significant progress to share.
- investigating Aug 25, 2026, 10:49 AM UTC
Our teams have taken few corrective measures to mitigate the issue in one of the impacted regions and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered. We will provide further updates within next two hours, or sooner if we have significant progress to share.
- monitoring Aug 25, 2026, 01:01 PM UTC
Our teams continue to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered. We will provide further updates within next two hours, or sooner if we have significant progress to share.
- resolved Aug 25, 2026, 02:33 PM UTC
On 25th Aug 2026, some users may have experienced increased latency in email, mobile and slack notifications. The issue has now been resolved, and the service is operating normally for all customers.
Minor August 25, 2026 Notifications are delayed 5h 51m via Jira Service Desk· Jira Service Management Web, Service Portal, Opsgenie Incident Flow, Opsgenie Alert Flow and 9 more
Started Aug 25, 2026, 08:42 AM UTC· resolved Aug 25, 2026, 02:33 PM UTC
- investigating Aug 25, 2026, 08:42 AM UTC
We are actively investigating reports of performance degradation resulting in increased latency for email, mobile, and slack notifications for Jira, JSM and Confluence. Our teams are investigating the issue and more information will be shared within the next 1 hour.
- investigating Aug 25, 2026, 09:44 AM UTC
Our teams have identified the impacted regions and are actively working to mitigate the issue. We will provide further updates within an hour, or sooner if we have significant progress to share.
- investigating Aug 25, 2026, 10:49 AM UTC
Our teams have taken few corrective measures to mitigate the issue in one of the impacted regions and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered. We will provide further updates within next two hours, or sooner if we have significant progress to share.
- monitoring Aug 25, 2026, 01:01 PM UTC
Our teams continue to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered. We will provide further updates within next two hours, or sooner if we have significant progress to share.
- resolved Aug 25, 2026, 02:33 PM UTC
On 25th Aug 2026, some users may have experienced increased latency in email, mobile and slack notifications. The issue has now been resolved, and the service is operating normally for all customers.
Minor August 25, 2026 Notifications are delayed 5h 51m via Jira Service Management· Jira Service Management Web, Service Portal, Opsgenie Incident Flow, Opsgenie Alert Flow and 9 more
Started Aug 25, 2026, 08:42 AM UTC· resolved Aug 25, 2026, 02:33 PM UTC
- investigating Aug 25, 2026, 08:42 AM UTC
We are actively investigating reports of performance degradation resulting in increased latency for email, mobile, and slack notifications for Jira, JSM and Confluence. Our teams are investigating the issue and more information will be shared within the next 1 hour.
- investigating Aug 25, 2026, 09:44 AM UTC
Our teams have identified the impacted regions and are actively working to mitigate the issue. We will provide further updates within an hour, or sooner if we have significant progress to share.
- investigating Aug 25, 2026, 10:49 AM UTC
Our teams have taken few corrective measures to mitigate the issue in one of the impacted regions and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered. We will provide further updates within next two hours, or sooner if we have significant progress to share.
- monitoring Aug 25, 2026, 01:01 PM UTC
Our teams continue to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered. We will provide further updates within next two hours, or sooner if we have significant progress to share.
- resolved Aug 25, 2026, 02:33 PM UTC
On 25th Aug 2026, some users may have experienced increased latency in email, mobile and slack notifications. The issue has now been resolved, and the service is operating normally for all customers.
Major August 25, 2026 Notifications are delayed 5h 51m via Jira Software· Viewing content, Create and edit, Authentication and User Management, Search and 7 more
Started Aug 25, 2026, 08:42 AM UTC· resolved Aug 25, 2026, 02:33 PM UTC
- investigating Aug 25, 2026, 08:42 AM UTC
We are actively investigating reports of performance degradation resulting in increased latency for email, mobile, and slack notifications for Jira, JSM and Confluence. Our teams are investigating the issue and more information will be shared within the next 1 hour.
- investigating Aug 25, 2026, 09:44 AM UTC
Our teams have identified the impacted regions and are actively working to mitigate the issue. We will provide further updates within an hour, or sooner if we have significant progress to share.
- investigating Aug 25, 2026, 10:49 AM UTC
Our teams have taken few corrective measures to mitigate the issue in one of the impacted regions and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered. We will provide further updates within next two hours, or sooner if we have significant progress to share.
- monitoring Aug 25, 2026, 01:01 PM UTC
Our teams continue to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered. We will provide further updates within next two hours, or sooner if we have significant progress to share.
- resolved Aug 25, 2026, 02:33 PM UTC
On 25th Aug 2026, some users may have experienced increased latency in email, mobile and slack notifications. The issue has now been resolved, and the service is operating normally for all customers.
Minor August 24, 2026 Degraded performance of Notifications 3h 52m via Jira Software· Viewing content, Create and edit, Authentication and User Management, Search and 7 more
Started Aug 24, 2026, 07:22 PM UTC· resolved Aug 24, 2026, 11:15 PM UTC
- investigating Aug 24, 2026, 07:22 PM UTC
We are actively investigating reports of performance degradation resulting in increased latency for email, mobile, and Slack notifications for JIRA, JSM, and Confluence. We will share updates here as more information is available.
- investigating Aug 24, 2026, 08:25 PM UTC
Our teams have identified three impacted regions, and continue to investigate the increased latency affecting email, mobile, and Slack notifications for JIRA, JSM, and Confluence.
- identified Aug 24, 2026, 09:30 PM UTC
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience increased latency in email, mobile, and Slack notifications for JIRA, JSM, and Confluence. We will continue to share additional updates here as more information is available.
- resolved Aug 24, 2026, 11:15 PM UTC
On August 24, 2026, some JIRA, JSM, and Confluence users may have experienced performance degradation resulting in increased latency in email, mobile, and Slack notifications. The issue has been resolved for newly created notifications, and service is operating normally. There may be older notifications that are being processed, and we expect them to be completed in next few hours.
Minor August 24, 2026 Degraded performance of Notifications 3h 52m via Jira Service Desk· Jira Service Management Web, Service Portal, Opsgenie Incident Flow, Opsgenie Alert Flow and 9 more
Started Aug 24, 2026, 07:22 PM UTC· resolved Aug 24, 2026, 11:15 PM UTC
- investigating Aug 24, 2026, 07:22 PM UTC
We are actively investigating reports of performance degradation resulting in increased latency for email, mobile, and Slack notifications for JIRA, JSM, and Confluence. We will share updates here as more information is available.
- investigating Aug 24, 2026, 08:25 PM UTC
Our teams have identified three impacted regions, and continue to investigate the increased latency affecting email, mobile, and Slack notifications for JIRA, JSM, and Confluence.
- identified Aug 24, 2026, 09:30 PM UTC
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience increased latency in email, mobile, and Slack notifications for JIRA, JSM, and Confluence. We will continue to share additional updates here as more information is available.
- resolved Aug 24, 2026, 11:15 PM UTC
On August 24, 2026, some JIRA, JSM, and Confluence users may have experienced performance degradation resulting in increased latency in email, mobile, and Slack notifications. The issue has been resolved for newly created notifications, and service is operating normally. There may be older notifications that are being processed, and we expect them to be completed in next few hours.
Minor August 24, 2026 Degraded performance of Notifications 3h 52m via Jira Service Management· Jira Service Management Web, Service Portal, Opsgenie Incident Flow, Opsgenie Alert Flow and 9 more
Started Aug 24, 2026, 07:22 PM UTC· resolved Aug 24, 2026, 11:15 PM UTC
- investigating Aug 24, 2026, 07:22 PM UTC
We are actively investigating reports of performance degradation resulting in increased latency for email, mobile, and Slack notifications for JIRA, JSM, and Confluence. We will share updates here as more information is available.
- investigating Aug 24, 2026, 08:25 PM UTC
Our teams have identified three impacted regions, and continue to investigate the increased latency affecting email, mobile, and Slack notifications for JIRA, JSM, and Confluence.
- identified Aug 24, 2026, 09:30 PM UTC
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience increased latency in email, mobile, and Slack notifications for JIRA, JSM, and Confluence. We will continue to share additional updates here as more information is available.
- resolved Aug 24, 2026, 11:15 PM UTC
On August 24, 2026, some JIRA, JSM, and Confluence users may have experienced performance degradation resulting in increased latency in email, mobile, and Slack notifications. The issue has been resolved for newly created notifications, and service is operating normally. There may be older notifications that are being processed, and we expect them to be completed in next few hours.
Minor August 24, 2026 Degraded performance of Notifications 3h 52m via Confluence· View Content, iOS App, Create and Edit, Android App and 11 more
Started Aug 24, 2026, 07:22 PM UTC· resolved Aug 24, 2026, 11:15 PM UTC
- investigating Aug 24, 2026, 07:22 PM UTC
We are actively investigating reports of performance degradation resulting in increased latency for email, mobile, and Slack notifications for JIRA, JSM, and Confluence. We will share updates here as more information is available.
- investigating Aug 24, 2026, 08:25 PM UTC
Our teams have identified three impacted regions, and continue to investigate the increased latency affecting email, mobile, and Slack notifications for JIRA, JSM, and Confluence.
- identified Aug 24, 2026, 09:30 PM UTC
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience increased latency in email, mobile, and Slack notifications for JIRA, JSM, and Confluence. We will continue to share additional updates here as more information is available.
- resolved Aug 24, 2026, 11:15 PM UTC
On August 24, 2026, some JIRA, JSM, and Confluence users may have experienced performance degradation resulting in increased latency in email, mobile, and Slack notifications. The issue has been resolved for newly created notifications, and service is operating normally. There may be older notifications that are being processed, and we expect them to be completed in next few hours.
Minor August 21, 2026 Marketplace App Macros Not Rendering in Confluence 2h 53m via Confluence· View Content, iOS App, Create and Edit, Android App and 11 more
Started Aug 21, 2026, 07:16 AM UTC· resolved Aug 21, 2026, 10:10 AM UTC
- identified Aug 21, 2026, 07:16 AM UTC
We have identified the root cause of an issue impacting Marketplace App macros in Confluence. Users may experience macros not rendering correctly or displaying errors. Our engineering team has identified the root cause and remediation is underway. We will provide further updates in the next 60 minutes.
- identified Aug 21, 2026, 08:15 AM UTC
A fix has been identified and is currently being deployed. Users should begin to see the impacted MarketPlace App - Connect macros to start rendering correctly, once the fix has been fully propagated. We will provide further updates within the next 2 hours.
- resolved Aug 21, 2026, 10:10 AM UTC
On 21st Aug 2026, between 04:26 UTC and 09:33 UTC, some users may have experienced issues with macros not rendering correctly in Confluence. The issue has now been resolved and the service is operating normally for all customers.
Minor August 18, 2026 Degraded performance with Rovo 3h 41m via Atlassian Rovo· Knowledge Discovery, Search, 3P Connectors, Chat and 6 more
Started Aug 18, 2026, 07:11 AM UTC· resolved Aug 18, 2026, 10:52 AM UTC
- investigating Aug 18, 2026, 07:11 AM UTC
Rovo is experiencing reduced reliability, with streamed message responses failing for some requests. This is affecting the Rovo product and related internal services that depend on the same path. Affected individuals may see errors, failed responses, or delayed replies when using Rovo Chat. Our teams are investigating the issue and more information will be shared within the next 1 hour.
- identified Aug 18, 2026, 08:09 AM UTC
Rovo continues to experience degraded performance and this also affects connected Rovo experiences such as agents and other features that rely on the same request path. Affected users may see errors, failed responses, delayed replies, or permission-related failures. Our teams have identified the root cause of this incident and is now actively working on mitigating the issue. We will provide further updates within an hour or sooner if we have any significant progress to share.
- identified Aug 18, 2026, 09:05 AM UTC
Our teams have taken corrective steps to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered. We will provide further updates within an hour, or sooner if we have significant progress to share.
- identified Aug 18, 2026, 10:13 AM UTC
Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates within an hour, or sooner if we have significant progress to share.
- resolved Aug 18, 2026, 10:52 AM UTC
We have now implemented a fix and services have been restored to normal operation for affected customers. On August 18 2026, users experienced reduced reliability, with streamed message responses failing for some requests. This also affected the Rovo product and related internal services that depend on the same path. Affected users also observed errors, failed responses, or delayed replies when using Rovo Chat.
- postmortem Aug 31, 2026, 06:21 AM UTC
**SUMMARY** On August 18, 2026 between 06:16 and 10:48 UTC, Rovo Chat and connected AI experiences suffered significant degradation. A configuration change inadvertently activated an experimental, resource-intensive AI capability across a much larger share of traffic than intended. This triggered a cascading failure in our shared caching infrastructure, leading to widespread request failures across multiple AI-powered surfaces. **IMPACT** During the impact period, customers experienced failed or unresponsive interactions when sending messages to Rovo Chat and Agents, as well as issues with select AI features across Jira and JSM. Requests either failed outright or returned intermittent errors or access-denied responses. **ROOT CAUSE** A configuration cleanup update contained an unintended change that inadvertently enabled a new Atlassian experimental agent - Marathon Agents - designed for limited and controlled rollout, for nearly all incoming requests. You can learn more about the rollout of Marathon Agents here: [https://community.atlassian.com/forums/Rovo-articles/What-s-New-in-Rovo-Agents-Your-Bi-Monthly-Update/ba-p/3242351](https://community.atlassian.com/forums/Rovo-articles/What-s-New-in-Rovo-Agents-Your-Bi-Monthly-Update/ba-p/3242351). This capability places significantly higher demand on our shared caching infrastructure than standard workloads. The sudden load on the caching infra led to a series of cascading failures in our systems which took some time to recover. **REMEDIAL ACTION PLAN & NEXT STEPS** The incident was resolved by rolling back the configuration change, disabling the experimental capability for all users, and scaling up infrastructure to absorb residual load. To help prevent recurrence, we are taking the following actions: - **Cache isolation:** Introducing dedicated, isolated caching instances for critical operational flows (such as permission checks and session state) and high-intensity AI features, to limit blast radius from any single component - **Improved pre-production validation:** Strengthening our staged rollout and soak-testing processes to catch resource-intensive changes before they reach production at scale - **Architectural hardening:** Reviewing the design of resource-intensive AI capabilities to ensure they are resilient to infrastructure pressure and safe for broader rollout We sincerely apologize for the disruption this caused. We are committed to the reliability of Rovo and our AI experiences, and these improvements will be prioritized accordingly. Thanks, Atlassian Customer Support
Minor August 12, 2026 Confluence intermittent errors 2h 1m via Confluence· View Content, iOS App, Create and Edit, Android App and 11 more
Started Aug 12, 2026, 08:11 PM UTC· resolved Aug 12, 2026, 10:13 PM UTC
- identified Aug 12, 2026, 08:11 PM UTC
Impact Some Confluence Cloud users visiting public links saw a Something went wrong error page. The issue affected anonymous access paths for public links, and some related Confluence areas could also show the same error message. Current Status A problematic recent change was identified and a revert was prepared. The team is using the revert path to restore the affected experience while checking that service returns to normal. Next Steps The incident team is completing the revert and monitoring the affected experience. Further updates will be sent in 60 minutes, or sooner if there is a material change.
- resolved Aug 12, 2026, 10:13 PM UTC
On August 12, 2026 some Confluence users utilizing anonymous access via public links, may have experienced a 'Something went wrong' error message. The issue has now been resolved, and the service is operating normally for all affected customers.
Critical August 7, 2026 Performance and access related issues with Jira 1h 21m via Jira Service Desk· Jira Service Management Web, Service Portal, Opsgenie Incident Flow, Opsgenie Alert Flow and 9 more
Started Aug 07, 2026, 11:30 AM UTC· resolved Aug 07, 2026, 12:52 PM UTC
- investigating Aug 07, 2026, 11:30 AM UTC
We are investigating issues affecting your services. We are actively working to identify the cause and resolve the issue. We will provide further updates within one hour.
- monitoring Aug 07, 2026, 12:22 PM UTC
Some customers experienced issues accessing affected services in the Central European region. We have been able to apply the fix to mitigate the issues and we are seeing recovery. We continue to monitor the situation and should be fully recovered soon. We should be able to provide more updates in the next one hour or earlier.
- resolved Aug 07, 2026, 12:52 PM UTC
On August 7th - 2026, between 10:27 UTC to 11:49 UTC, some users in the Central European region may have experienced service access issues. The issue has now been resolved and the service is operating normally for all the customers.
Critical August 7, 2026 Performance and access related issues with Jira 1h 21m via Jira Service Management· Jira Service Management Web, Service Portal, Opsgenie Incident Flow, Opsgenie Alert Flow and 9 more
Started Aug 07, 2026, 11:30 AM UTC· resolved Aug 07, 2026, 12:52 PM UTC
- investigating Aug 07, 2026, 11:30 AM UTC
We are investigating issues affecting your services. We are actively working to identify the cause and resolve the issue. We will provide further updates within one hour.
- monitoring Aug 07, 2026, 12:22 PM UTC
Some customers experienced issues accessing affected services in the Central European region. We have been able to apply the fix to mitigate the issues and we are seeing recovery. We continue to monitor the situation and should be fully recovered soon. We should be able to provide more updates in the next one hour or earlier.
- resolved Aug 07, 2026, 12:52 PM UTC
On August 7th - 2026, between 10:27 UTC to 11:49 UTC, some users in the Central European region may have experienced service access issues. The issue has now been resolved and the service is operating normally for all the customers.
Critical August 7, 2026 Performance and access related issues with Jira 1h 21m via Jira Software· Viewing content, Create and edit, Authentication and User Management, Search and 7 more
Started Aug 07, 2026, 11:30 AM UTC· resolved Aug 07, 2026, 12:52 PM UTC
- investigating Aug 07, 2026, 11:30 AM UTC
We are investigating issues affecting your services. We are actively working to identify the cause and resolve the issue. We will provide further updates within one hour.
- monitoring Aug 07, 2026, 12:22 PM UTC
Some customers experienced issues accessing affected services in the Central European region. We have been able to apply the fix to mitigate the issues and we are seeing recovery. We continue to monitor the situation and should be fully recovered soon. We should be able to provide more updates in the next one hour or earlier.
- resolved Aug 07, 2026, 12:52 PM UTC
On August 7th - 2026, between 10:27 UTC to 11:49 UTC, some users in the Central European region may have experienced service access issues. The issue has now been resolved and the service is operating normally for all the customers.
Minor August 7, 2026 Degraded performance of JIRA 13m via Jira Service Desk· Jira Service Management Web, Service Portal, Opsgenie Incident Flow, Opsgenie Alert Flow and 9 more
Started Aug 07, 2026, 01:33 AM UTC· resolved Aug 07, 2026, 01:46 AM UTC
- investigating Aug 07, 2026, 01:33 AM UTC
We are actively investigating reports of performance degradation affecting JIRA and JSM. Affected users may experience errors viewing issues and boards. We will share updates here as more information is available.
- monitoring Aug 07, 2026, 01:39 AM UTC
The performance degradation of JIRA has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.
- resolved Aug 07, 2026, 01:46 AM UTC
On August 7, 2026, JIRA, JWM, and JSM users may have experienced performance degradation when viewing issues and boards. The issue has now been resolved, and the service is operating normally for all affected customers.
Minor August 7, 2026 Degraded performance of JIRA 13m via Jira Service Management· Jira Service Management Web, Service Portal, Opsgenie Incident Flow, Opsgenie Alert Flow and 9 more
Started Aug 07, 2026, 01:33 AM UTC· resolved Aug 07, 2026, 01:46 AM UTC
- investigating Aug 07, 2026, 01:33 AM UTC
We are actively investigating reports of performance degradation affecting JIRA and JSM. Affected users may experience errors viewing issues and boards. We will share updates here as more information is available.
- monitoring Aug 07, 2026, 01:39 AM UTC
The performance degradation of JIRA has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.
- resolved Aug 07, 2026, 01:46 AM UTC
On August 7, 2026, JIRA, JWM, and JSM users may have experienced performance degradation when viewing issues and boards. The issue has now been resolved, and the service is operating normally for all affected customers.
Minor August 7, 2026 Degraded performance of JIRA 19m via Jira Core· Viewing content, Create and edit, Authentication and User Management, Search and 7 more
Started Aug 07, 2026, 01:26 AM UTC· resolved Aug 07, 2026, 01:46 AM UTC
- investigating Aug 07, 2026, 01:26 AM UTC
We are actively investigating reports of performance degradation affecting JIRA and JSM. Affected users may experience errors viewing issues and boards. We will share updates here as more information is available.
- investigating Aug 07, 2026, 01:33 AM UTC
We are actively investigating reports of performance degradation affecting JIRA and JSM. Affected users may experience errors viewing issues and boards. We will share updates here as more information is available.
- monitoring Aug 07, 2026, 01:39 AM UTC
The performance degradation of JIRA has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.
- resolved Aug 07, 2026, 01:46 AM UTC
On August 7, 2026, JIRA, JWM, and JSM users may have experienced performance degradation when viewing issues and boards. The issue has now been resolved, and the service is operating normally for all affected customers.
Minor August 7, 2026 Degraded performance of JIRA 19m via Jira Work Management· Viewing content, Create and edit, Authentication and User Management, Search and 7 more
Started Aug 07, 2026, 01:26 AM UTC· resolved Aug 07, 2026, 01:46 AM UTC
- investigating Aug 07, 2026, 01:26 AM UTC
We are actively investigating reports of performance degradation affecting JIRA and JSM. Affected users may experience errors viewing issues and boards. We will share updates here as more information is available.
- investigating Aug 07, 2026, 01:33 AM UTC
We are actively investigating reports of performance degradation affecting JIRA and JSM. Affected users may experience errors viewing issues and boards. We will share updates here as more information is available.
- monitoring Aug 07, 2026, 01:39 AM UTC
The performance degradation of JIRA has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.
- resolved Aug 07, 2026, 01:46 AM UTC
On August 7, 2026, JIRA, JWM, and JSM users may have experienced performance degradation when viewing issues and boards. The issue has now been resolved, and the service is operating normally for all affected customers.
Critical August 3, 2026 Issues installing, uninstalling and managing Forge or OAuth 2.0 apps 11m via Atlassian Developer· Bitbucket Cloud APIs, App listing management, App Deployment, App listings and 45 more
Started Aug 03, 2026, 03:26 AM UTC· resolved Aug 03, 2026, 03:37 AM UTC
- investigating Aug 03, 2026, 03:26 AM UTC
Our team is aware of an issue that was impacting the ability to install, uninstall or manage Forge and OAuth 2.0 integrated apps between 2026-08-03 01:47 UTC and 02:29 UTC. Apps that were already installed should have continued to run as normal during this impact window. We believe we have now rectified this issue and are monitoring for ongoing impact. We apologize for any inconvenience this may have caused.
- resolved Aug 03, 2026, 03:37 AM UTC
We have confirmed that the issues relating to installing, uninstalling and managing Forge and OAuth 2.0 apps should now be fully resolved.
Notice July 31, 2026 BitBucket Site fails to Load 2h 28m via Bitbucket· Website, API, Git via SSH, Authentication and user management and 9 more
Started Jul 31, 2026, 01:09 PM UTC· resolved Jul 31, 2026, 03:38 PM UTC
- monitoring Jul 31, 2026, 01:09 PM UTC
Some customers experienced intermittent errors when accessing Bitbucket Cloud, including failures loading the site and associated impacts to Pipelines. We have been able to apply the fix to mitigate the issues and we are seeing recovery. We continue to monitor the situation and should be fully recovered soon. We should be able to provide more updates in the next one hour or earlier.
- monitoring Jul 31, 2026, 02:28 PM UTC
A fix has been implemented and services are operating normally for all affected customers. We are continuing to monitor to confirm stability. We will provide a further update within 60 minutes.
- resolved Jul 31, 2026, 03:38 PM UTC
On July 31, 2026, affected Bitbucket Cloud users for some customers may have experienced failures loading the site and impacts to associated pipelines. The issue has now been resolved, and the service is operating normally for all affected customers.
Minor July 21, 2026 Voice call failures for some India based numbers 3d 3h via Jira Service Desk· Jira Service Management Web, Service Portal, Opsgenie Incident Flow, Opsgenie Alert Flow and 9 more
Started Jul 21, 2026, 09:48 AM UTC· resolved Jul 24, 2026, 01:07 PM UTC
- identified Jul 21, 2026, 09:48 AM UTC
We are working with our notification provider to resolve the issue. We will provide another update in 24 hours or as soon as more information becomes available.
- identified Jul 22, 2026, 06:59 AM UTC
A small number of voice notifications for Jira Service Management and Opsgenie customers using India based mobile numbers may fail. Customers may see failed voice call logs and not receive the expected paging call. Our 3rd party notification provider is actively working towards restoring the voice notification delivery and we will provide updates once the issue is resolved. If you need any further support or information, please reach out to our support team.
- resolved Jul 24, 2026, 01:07 PM UTC
Our notification provider has identified the root of the issue that is causing voice call failures to some India-based mobile numbers. We understand the inconvenience this may cause and appreciate your patience while our provider works on restoring the service. If you have experienced any issues with voice notifications, please contact our Support for assistance.
Minor July 21, 2026 Voice call failures for some India based numbers 3d 3h via Jira Service Management· Jira Service Management Web, Service Portal, Opsgenie Incident Flow, Opsgenie Alert Flow and 9 more
Started Jul 21, 2026, 09:48 AM UTC· resolved Jul 24, 2026, 01:07 PM UTC
- identified Jul 21, 2026, 09:48 AM UTC
We are working with our notification provider to resolve the issue. We will provide another update in 24 hours or as soon as more information becomes available.
- identified Jul 22, 2026, 06:59 AM UTC
A small number of voice notifications for Jira Service Management and Opsgenie customers using India based mobile numbers may fail. Customers may see failed voice call logs and not receive the expected paging call. Our 3rd party notification provider is actively working towards restoring the voice notification delivery and we will provide updates once the issue is resolved. If you need any further support or information, please reach out to our support team.
- resolved Jul 24, 2026, 01:07 PM UTC
Our notification provider has identified the root of the issue that is causing voice call failures to some India-based mobile numbers. We understand the inconvenience this may cause and appreciate your patience while our provider works on restoring the service. If you have experienced any issues with voice notifications, please contact our Support for assistance.
Minor July 21, 2026 Voice call failures for some India based numbers 3d 3h via OpsGenie· Incident Flow, Incident Flow, Alert Flow, Alert Flow and 41 more
Started Jul 21, 2026, 09:48 AM UTC· resolved Jul 24, 2026, 01:07 PM UTC
- identified Jul 21, 2026, 09:48 AM UTC
We are working with our notification provider to resolve the issue. We will provide another update in 24 hours or as soon as more information becomes available.
- identified Jul 22, 2026, 06:59 AM UTC
A small number of voice notifications for Jira Service Management and Opsgenie customers using India based mobile numbers may fail. Customers may see failed voice call logs and not receive the expected paging call. Our 3rd party notification provider is actively working towards restoring the voice notification delivery and we will provide updates once the issue is resolved. If you need any further support or information, please reach out to our support team.
- resolved Jul 24, 2026, 01:07 PM UTC
Our notification provider has identified the root of the issue that is causing voice call failures to some India-based mobile numbers. We understand the inconvenience this may cause and appreciate your patience while our provider works on restoring the service. If you have experienced any issues with voice notifications, please contact our Support for assistance.
Minor July 20, 2026 Degraded performance of Jira Automation rules 1d 4h via Jira Software· Viewing content, Create and edit, Authentication and User Management, Search and 7 more
Started Jul 20, 2026, 08:18 PM UTC· resolved Jul 22, 2026, 12:56 AM UTC
- investigating Jul 20, 2026, 08:18 PM UTC
We are actively investigating reports of performance degradation affecting Automation rules for Jira and Jira Service Management. We will share updates here as more information is available.
- investigating Jul 20, 2026, 09:27 PM UTC
Our teams are continuing to investigate delays in Jira and Jira Service Management automation rule executions for some customers. We are seeing signs of improvement, but affected users may still experience delays. We'll share updates here as more information is available.
- identified Jul 21, 2026, 04:53 AM UTC
The team has identified a root cause and after initial testing, is now enacting scaling changes to help to prevent these rule execution delays. We'll monitor performance over the next 24 hours and provide an update at that time or sooner if we can confirm the improvement is in place.
- resolved Jul 22, 2026, 12:56 AM UTC
Our team has been able to validate that all rule executions are performing normally and this issue is now resolved.
Minor July 20, 2026 Degraded performance of Jira Automation rules 1d 4h via Jira Service Desk· Jira Service Management Web, Service Portal, Opsgenie Incident Flow, Opsgenie Alert Flow and 9 more
Started Jul 20, 2026, 08:18 PM UTC· resolved Jul 22, 2026, 12:56 AM UTC
- investigating Jul 20, 2026, 08:18 PM UTC
We are actively investigating reports of performance degradation affecting Automation rules for Jira and Jira Service Management. We will share updates here as more information is available.
- investigating Jul 20, 2026, 09:27 PM UTC
Our teams are continuing to investigate delays in Jira and Jira Service Management automation rule executions for some customers. We are seeing signs of improvement, but affected users may still experience delays. We'll share updates here as more information is available.
- identified Jul 21, 2026, 04:53 AM UTC
The team has identified a root cause and after initial testing, is now enacting scaling changes to help to prevent these rule execution delays. We'll monitor performance over the next 24 hours and provide an update at that time or sooner if we can confirm the improvement is in place.
- resolved Jul 22, 2026, 12:56 AM UTC
Our team has been able to validate that all rule executions are performing normally and this issue is now resolved.