Is Jira Work Management Down Right Now? Check if there is a current outage ongoing.

We are aware of some customers having delays receiving emails from their Jira, JWM and JSM automations. Our team is looking into this issue with urgency and will provide further update when available.

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

### Summary On May 20, 2025, between 13:10 UTC and 22:12 UTC, a small subset of Atlassian customers using Jira Software and Jira Service Management products were unable to access certain functionality, such as creating, viewing, or editing boards, issues, filters, and Jira Service Management requests. The root cause was data duplication in our software related to upgrades of \(non-faulty\) third party apps. The incident was detected within 4 minutes by Automated Monitoring, and mitigated through the subsequent 8 hours and 58 mins. Factors that prolonged the impact of the incident included: * An attempt to mitigate the issue by disabling the \(non-faulty\) apps was ineffective because the disablement mechanism was not integrated with the affected data source * Attempts to manually rectify the data in the database were hampered by the binary storage format used for the data \(necessary for performance reasons\) ### **IMPACT** During the impact period stated above, Jira Software and Jira Service Desk sites that had a specific version of the third party apps installed were impacted. For the duration of the incident, functionality such as creating, viewing, or editing of boards, issues, filters, and Jira Service Management requests was unavailable on those sites. ### **ROOT CAUSE** During the process of version upgrade for the third party apps with dynamic modules, duplicated data was left behind due to a bug in Atlassian systems triggered during a prior upgrade. ### **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 during development because of the specific sequence of events required to trigger the latent duplicate data to impact the product’s functioning. We are prioritizing the following improvement actions to avoid repeating this type of incident: * Detecting and repairing duplicated data at the source * Updating the faulty “write” subsystem to prevent further duplication of data Furthermore, we are taking steps to enable swifter mitigation should such an incident occur in the future. We are: * Enhancing app disablement tooling \(and its documentation\) to make it simple and effective to deploy against this class of issue * Enhancing validation of the app upgrade process * Developing an affordance for viewing, repairing, and modifying specific app data 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

Deployment of the fix for this issue has now completed rolling out and this should be resolved for all users.

We are continuing to investigate an issue that is disrupting access to core Jira functionality for a limited number of Jira customers. We will provide an update when we have identified a fix.

We are continuing to investigate issues with the Jira degradation and will provide updates as we learn more.

We are investigating cases of degraded performance for all Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. We will provide more details within the next hour.

The issue with the Administration accessibility has now been resolved, and the service is operating normally for all affected customers.

The issues causing access problems to Administration have been resolved, and services are now functioning normally for all affected customers. We will monitor it closely for the next 30 minutes to ensure stability.

We are aware of an issue where users are receiving a 403 error when attempting to reach Administration. Our team is looking into this issue with urgency and will provide an update as soon as possible.

We are aware of an issue where users are receiving a 403 error when attempting to reach Administration. Our team is looking into this issue with urgency and will provide an update as soon as possible.

We are investigating cases of degraded performance for all Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. We will provide more details within the next hour.

Between 10:55 AM UTC to 13:15 PM UTC on April 28, 2025, we experienced partial unavailability in managing Forge apps; Such as lifecycle developer console usage, and the creation and deployment of Forge apps for Atlassian Partners, Jira Work Management, Jira, Atlassian Developer, Jira Product Discovery, Compass, and Atlassian Migrations. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The conditions that cause the bug have been addressed and we're actively working on a permanent fix. The issue has been resolved and the service is operating normally.

The issues causing the unavailability of related Forge apps capabilities on multiple Atlassian platforms have been resolved, and services are now operating normally for all impacted customers. We will continue to closely monitor for stability.

We are currently experiencing partial unavailability in managing Forge apps on different Atlassian platforms, such as apps lifecycle (installation, removals), developer console usage (including tunneling), and the creation and deployment of Forge apps. We have identified the root cause and are in the process of mitigating the impact. We'll keep you posted with further updates. Next updates in 1 hour.

We are currently experiencing partial unavailability in managing Forge apps on different Atlassian platforms. Such as apps lifecycle (installation, removals), developer console usage (including tunnelling), and the creation and deployment of Forge apps. Our team is working diligently to resolve this issue and restore services quickly. We are in the process of identifying the root cause and implementing the necessary fixes. Next updates in 1 hour.

We are currently experiencing partial unavailability in managing Forge apps on different Atlassian platforms. Such as apps lifecycle (installation, removals), developer console usage (including tunnelling), and the creation and deployment of Forge apps. Our team is working diligently to resolve this issue and restore services quickly. We are in the process of identifying the root cause and implementing the necessary fixes.Next updates in 1 hour.

Between 13:00 UTC to 23:00 UTC on April 23, 2025, we experienced automation rule execution delays for Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. The issue has been resolved and the service is operating normally. For some high volume customers who regularly have rule throttling, there may be an extended period to clear full backlogs. For those high volume customers we expect any extended period rule throttling to be resolved by 07:00 UTC on April 24, 2025.

New executions are continuing to run without delay. Remaining delayed executions will complete in approximately one hour. We will continue to monitor the progress and provide an update within the next hour.

New executions are running without delay. Remaining delayed executions will complete in the next 2 hours. We will continue to monitor the progress and provide an update within the next hour.

A majority of new automation executions are running without delay. Remaining delayed automation executions should be completed within 3 hours. We will continue to monitor the progress and provide an update within the next hour.

We have applied significant mitigations and the majority of delayed automation executions should be completed within 2 hours. Some customers may experience some delay in some executions during the 2 hours following. Rule execution delays should be mitigated in 4 hours. We will continue to monitor the progress and provide an update within the next hour.

We are still investigating automation rule delays that is impacting some Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. The backlog of previous mitigations has decreased and continues to decrease, however some customers may be still be experiencing delays. The backlog of automations is being processed as we continue to apply mitigations and will provide more details within the next hour.

We are still investigating automation rule delays that is impacting some Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. Previous mitigations have decreased the average delays across executions, however some customers may be still be experiencing delays. We are applying more mitigations and will provide more details within the next hour.

We are investigating automation rule execution delays that are impacting some Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. We have applied a temporary mitigation and are continuing to investigate for root cause. We will provide more details within the next hour.

We are investigating cases of degraded performance for automation rules for Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. We will provide more details within the next hour.

We are investigating cases of degraded performance for automation rules for Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. We will provide more details within the next hour.

Between 3:30 UTC to 23:00 UTC April 16, 2025, we experienced an issue with loading certain Jira Dashboard widgets for Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. The issue has been resolved and the service is operating normally.

We continue to work on resolving the issue with loading certain Jira Dashboard widgets for for Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. We have identified the root cause and are currently deploying fixes. We expect to complete the deployments by 23:00 UTC.

We continue to work on resolving the issue with loading certain Jira Dashboard widgets for for Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. We have identified the root cause and expect recovery shortly. We will provide another update at 22:00 UTC.

We continue to work on resolving the issue with loading certain Jira Dashboard widgets for Jira Work Management, Jira Service Management, and Jira Product Discovery. We have identified the root cause and expect recovery shortly. We will provide another update at 19:00 UTC.

We are aware of users experiencing issues attempting to load Jira Dashboard widgets. Our team is investigating this issue with priority.

We are aware of users experiencing issues attempting to load Jira Dashboard widgets. Our team is investigating this issue with priority.

Between 00:00 UTC to 01:05 UTC 14 April, users attempting to load the Administration page for Atlassian products. The issue has been resolved and the service is operating normally.

We are aware of an issue where users attempting to load the Administration page are instead seeing a blank page. Our team is investigating with urgency and will provide further update as soon as possible.

We are aware of an issue where users attempting to load the Administration page are instead seeing a blank page. Our team is investigating with urgency and will provide further update as soon as possible.

We identified a temporary access issue affecting some customers using several Atlassian Cloud products. All affected products are now back online, and no further impacts have been observed. We apologize for any inconvenience this may have caused.

We are aware that some customers experienced access issues with their sites. We identified the root cause and have mitigated the problem. Systems are now stable, and we are monitoring closely to ensure no further issues arise. For those still having trouble accessing their sites, adding /wiki/ to the site URL can serve as a temporary workaround (for example https://site.atlassian.net/wiki/). Further updates will be provided as needed.

We are aware that some customers experienced access issues with their sites. We identified the root cause and have mitigated the problem. Systems are now stable, and we are monitoring closely to ensure no further issues arise. For those still having trouble accessing their sites, adding /wiki/ to the site URL can serve as a temporary workaround (for example https://site.atlassian.net/wiki/). Further updates will be provided as needed.

Between March 21, 2025 17:00 UTC and March 24, 2025 17:39 UTC, some customers were not able to view and assign the team field value from the issue view in Jira Work Management, Jira Service Management, and Jira. The issue has been resolved and the service is operating normally.

We are investigating reports of users being unable to view and assign the team field value from the issue view for some Jira Work Management, Jira Service Management, and Jira customers.

Between March 21, 2025 17:00 UTC and March 24, 2025 17:39 UTC, some customers were not able to view and assign the team field value from the issue view in Jira Work Management, Jira Service Management, and Jira. The issue has been resolved and the service is operating normally.

We are investigating reports of users being unable to view and assign the team field value from the issue view for some Jira Work Management, Jira Service Management, and Jira customers.

On 20 March 2025, between 14:18 UTC and 22:43 UTC, some customers were not able to use the Team field to search and assign teams in Jira Work Management, Jira Service Management, and Jira. The issue has been resolved, and the service is operating normally.

We are investigating reports of customers being unable to see and assign teams from the team field dropdown for some Jira Work Management, Jira Service Management, and Jira customers. We will provide more details once we identify the root cause.

On 20 March 2025, between 14:18 UTC and 22:43 UTC, some customers were not able to use the Team field to search and assign teams in Jira Work Management, Jira Service Management, and Jira. The issue has been resolved, and the service is operating normally.

We are investigating reports of customers being unable to see and assign teams from the team field dropdown for some Jira Work Management, Jira Service Management, and Jira customers. We will provide more details once we identify the root cause.

Between 14:36 UTC to 16:15 UTC, we experienced performance degradation for Confluence, Jira Work Management, Jira Service Management, and Jira. The issue has been resolved and the service is operating normally.

We are investigating cases of degraded performance for some Confluence, Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within the next hour.

Between 07:45 UTC to 18:45 UTC, a very small number of customers for Confluence, Jira Work Management, Jira Service Management, and Jira in the APAC region experienced a site maintenance issue. The issue has now been resolved and the service is operating normally for all impacted customers.

We are actively addressing the site maintenance message affecting some customers using Jira Work Management, Jira Service Management, and Jira Cloud in the APAC region. While service has been restored for some users, others remain impacted as we collaborate with AWS to resolve the issue. We are working diligently to restore full functionality and will provide more updates as they become available. Thank you for your patience and understanding.

We have partially restored functionality to some of the affected Jira Work Management, Jira Service Management, and Jira Cloud customers. We will continue to work on the fix and share more information as it becomes available.

We continue to investigate the site maintenance issue impacting Jira Work Management, Jira Service Management, and Jira Cloud customers. We will share more information as it becomes available.

We are investigating the site maintenance' issue that is impacting Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within the next hour. The issue is fixed for Confluence customers.

We are investigating 'site maintenance' issue that is impacting some Confluence, Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within the next hour.

Between 07:45 UTC to 18:45 UTC, a very small number of customers for Confluence, Jira Work Management, Jira Service Management, and Jira in the APAC region experienced a site maintenance issue. The issue has now been resolved and the service is operating normally for all impacted customers.

We are actively addressing the site maintenance message affecting some customers using Jira Work Management, Jira Service Management, and Jira Cloud in the APAC region. While service has been restored for some users, others remain impacted as we collaborate with AWS to resolve the issue. We are working diligently to restore full functionality and will provide more updates as they become available. Thank you for your patience and understanding.

We have partially restored functionality to some of the affected Jira Work Management, Jira Service Management, and Jira Cloud customers. We will continue to work on the fix and share more information as it becomes available.

We continue to investigate the site maintenance issue impacting Jira Work Management, Jira Service Management, and Jira Cloud customers. We will share more information as it becomes available.

We are investigating the site maintenance' issue that is impacting Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within the next hour. The issue is fixed for Confluence customers.

We are investigating 'site maintenance' issue that is impacting some Confluence, Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within the next hour.

Between 14:36 UTC to 16:15 UTC, we experienced performance degradation for Confluence, Jira Work Management, Jira Service Management, and Jira. The issue has been resolved and the service is operating normally.

We are investigating cases of degraded performance for some Confluence, Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within the next hour.

Until the end of May 2025, Atlassian plans to perform maintenance on the infrastructure supporting the Jira and Confluence platforms.This maintenance will result in a temporary service outage for Free edition users located in Singapore and Northern California, with a total duration of no more than 120 minutes per customer. The maintenance will be performed during regular business hours in the specified regions.To learn more, please refer to this community post https://community.atlassian.com/forums/Announcement-articles/Upcoming-Maintenance-Notification-for-Jira-and-Confluence/ba-p/2973795#M6870

Scheduled maintenance is currently in progress. We will provide updates as necessary.

A mitigation for the performance issues has been implemented and this incident is now resolved.

We are continuing to investigate this issue.

We are aware of some users experiencing extended load times when attempting to view issues in Jira, Jira Work Management and Jira Service Management. Our team is investigating this issue.

Our team has been monitoring this issue and can confirm that the errors that were previously occurring have now been resolved.

Our team has implemented a fix for the connection errors that were being experienced across Jira Work Management, Jira Service Management, Jira and Jira Product Discovery Cloud products. We are continuing to monitor this change to ensure that the issue is mitigated.

Our team is continuing to investigate the issues relating to partial outage being experienced by some customers across Jira Work Management, Jira Service Management, Jira and Jira Product Discovery Cloud products. We will provide an update when more information relating to mitigating the issue is available.

We are continuing to investigate the root cause of the partial outage with that is impacting some Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. We are applying mitigation to affected customers. We will provide more details within the next hour.

We are investigating reports of intermittent errors for some Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. We will provide more details once we identify the root cause.

We are aware of an issue that was impacting user authentication to Atlassian services between 6:10AM Tuesday 4th March UTC and 6:35AM Tuesday 4th March UTC. Users that were already logged in would not have been impacted by this issue. A deployment suspected of causing this issue was rolled back and the problem was subsequently resolved.

### Summary On February 10, 2025, between 16:10 and 18:35 UTC, Atlassian customers in Brazil experienced intermittent failures accessing and using Jira and Confluence Cloud. This disruption was due to our Content Delivery Network \(CDN\) not having sufficient capacity in Brazil under a certain network configuration. Changes in the lead-up to the incident included enabling CDN for Jira and Confluence in Brazil between January 20th and February 6th to improve performance and security. Jira and Confluence experience success rate monitoring detected the incident within 50 minutes. The incident was mitigated by temporarily disabling CDN in Brazil, which put Atlassian systems into a known good state. The total time to resolution was two hours and 25 minutes. ### **IMPACT** The overall impact was on February 10, 2025, between 16:10 and 18:35 UTC to Jira and Confluence Cloud_._ The incident caused service disruption to Brazilian customers when they attempted to access or use any feature of those products. Customers observed a generic error page or “HTTP 500” error presented by our CDN provider for up to a third of all requests at peak. ### **ROOT CAUSE** Our CDN is configured to present Jira and Confluence Cloud from static IP ranges dedicated to Atlassian. This configuration limited the number of edge locations servicing customer requests, causing a high concentration of connections in the Brazilian region on one edge location in particular. When daily traffic volumes in Brazil peaked on February 10, connections through the edge location to our servers encountered a capacity limit and were rejected with a HTTP 500 error. ### **REMEDIAL ACTION PLAN & NEXT STEPS** We understand that outages impact your productivity. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Along with our CDN provider, we have already taken the following actions to avoid repeating this type of incident: * Our CDN provider has completed the rollout of the static, dedicated IP feature to all their edge locations and enabled Jira and Confluence Cloud to be served from all of them, thus moving to the intended configuration that will provide full network capacity. * We are working with our CDN provider to perform more rigorous checks of capacity and configuration for Jira and Confluence Cloud. * Our CDN provider increased the server connection limit for Jira and Confluence Cloud in all locations, further increasing capacity. * Based on the observed failure patterns, we have created additional monitoring and alerting configurations, so we will be alerted immediately if the issue reoccurs. Additionally, we are prioritizing actions to improve the detection of failures that affect a specific region. Thanks, Atlassian Customer Support

Between February 10, 2025, at 17:04 UTC and 18:32 UTC, some customers for Jira Work Management, Jira Service Management, Jira, Jira Product Discovery Cloud and Confluence experienced degraded performance and 500 errors. We found that cloud products in Brazil encountered an internal limit with our cloud service provider. We redistributed traffic to mitigate this issue and are working with our cloud provider to address this issue in the future. The issue has been resolved and all the services are operating normally.

We are investigating cases of degraded performance for Jira Work Management, Jira Service Management,Jira Cloud and confluence customers. We are currently investigating it and will provide more details within the next hour.

We are investigating cases of degraded performance for Jira Work Management, Jira Service Management, and Jira Cloud customers. We are currently investigating it and will provide more details within the next 30 minutes.

Between 05/Feb/25 2:30 PM UTC and 05/Feb/25 3:28 PM UTC some customers for Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud experienced intermittent errors. We have identified the root cause of the intermittent errors and have mitigated the problem. The issue has been resolved and the service is operating normally.

We continue to monitor the mitigation measures implemented to address the intermittent errors reported.

We have identified the root cause of the intermittent errors and have mitigated the problem. We are now monitoring this closely.

We are investigating reports of intermittent errors for some Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers.

This incident has been resolved.

We have mitigated the degraded performance of Jira Work Management, Jira Service Management, and Jira Cloud. We are now monitoring the situation closely.

We continue to work on resolving the degraded performance for Jira Work Management, Jira Service Management, and Jira. We have identified the root cause and expect recovery shortly.

We are investigating cases of degraded performance for Jira Work Management, Jira Service Management, and Jira Cloud customers in certain regions. We will provide more details within the next hour.

Between 11:30:00 UTC on 9/Jan/25 to 2:30:00 UTC on 10/Jan/25, we experienced a problem displaying the component values in Jira, Jira Work Management and Jira Service Management for some customers. The issue has been resolved and the service is operating normally.

We are continuing to investigate why components are not appearing for some users and will provide updates as we learn more.

We have identified an incident that caused the components to disappear from the field and affected our Jira, Jira work management, and Jira Service Desk Cloud customers. As of now, we do not have a root cause for the incident. We are investigating and will post updates within the next hour.

This incident has been resolved.

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

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

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

Between 07:50 UTC to 11:31 UTC, some customers experienced previews of attachments unavailable for Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The conditions that cause the bug have been addressed and we're actively working on a permanent fix. The issue has been resolved and the service is operating normally.

Between 04/Nov/24 11:30 PM UTC to 05/Nov/24 10:47 AM UTC, we experienced problems with the automation limits for some Cloud customers for Jira Work Management, Jira Service Management, and Jira. The issue has been resolved and the service is operating normally.

We are investigating issues with incorrectly set automation limits for some customers and will provide updates here soon.

Between 05:00 UTC to 11:20 UTC, we experienced problems with dashboards and gadgets not loading for Jira Work Management, Jira Service Management, and Jira. The issue has been resolved and the service is operating normally.

We are investigating issues with gadgets and pages not loading for some customers. We will provide updates here soon.

Between 08:30 - 12:00 UTC, we experienced 500 errors for Jira Work Management, Jira Service Management, and Jira for some customers. The issue has been resolved and the service is operating normally.

We continue to work on resolving the intermittent 500 error for Jira Cloud products. We have identified the root cause and expect full recovery shortly.

We are investigating <Jira responding with 500 error> errors for some Jira Cloud customers. Once we identify the root cause, we will provide more details.

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

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

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

Between 2024-10-23, 15:09 UTC and 2024-10-23, 17:06 UTC, we identified an issue that affected tenant provisioning and user management actions at Atlassian Cloud, causing a delay in performing actions related to these two topics. We have identified the root cause and the issue has been mitigated.

Between 22-Oct 09:00 AM UTC to 22-Oct 14:18 PM UTC, we experienced intermittent errors for Jira Cloud products. The issue has been resolved and the service is operating normally.

We continue to work on resolving the intermittent errors for Jira Cloud products. We have identified the root cause and expect full recovery shortly.

We are investigating reports of intermittent 'Too many requests or errors' messages showing up for some Jira Cloud customers. Once we identify the root cause, we will provide more details.

We experienced availability issues limited to a specific instance in AMER, resulting in Jira being temporarily unavailable. The issue began at 18:58 CET and was restored at 19:59 CET. All services are now fully operational

Between 2024-10-18 05:40 UTC-7 to 2024-10-18 08:40 UTC-7, we experienced an outage affecting user/group memberships in AdminHub for Confluence, Jira Work Management, Jira Service Management, Jira, and Guard. The issue has been resolved and the service is operating normally.

We have received reports of intermittent errors for some Cloud customers, specifically admins who are unable to see group memberships in AdminHub. We have identified the root cause and expect recovery shortly.

Between 2300 14 October to 0200 16 October, we experienced an outage affecting Team Managed Project creation for Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. The issue has been resolved and the service is operating normally.

Some customers are getting an error when trying to create team-managed Jira projects (Jira, Jira Work Management, Jira Service Management, Jira Product Discovery). We are currently investigating this and we will continue to share further updates.

This incident has been resolved.

We are observing a recovery on our monitoring dashboards. The affected rules will be executed in the next few hours, if they haven't been processed already. We will keep monitoring the situation during this time before marking the incident as 'Resolved'.

We identified that automation rules running between 6 AM UTC and 10 AM UTC may have been impacted by the incident. Additionally, all scheduled rules during this window were affected. We have taken action to mitigate this issue, and we are currently working on recovery. We know what the fix is and are implementing it now. The affected rules will run once the fix is applied.

We are investigating issues with scheduled automated rules and will provide updates here soon.

We have identified that the issue is related to a recent update on the Brave browser (https://brave.com/latest/), which is causing some cookie-related problems for users. As a temporary workaround, we recommend using one of our supported browsers: https://support.atlassian.com/atlassian-account/docs/supported-browsers-for-atlassian-cloud-products/. We understand that many users prefer Brave, and our engineering team will continue to investigate this issue and work towards a resolution on a best-effort basis.

We are investigating an issue with accessing Jira content that is impacting some Jira Cloud customers. We will provide more details within the next hour.

The issue has been resolved and the service is now operating normally.

Some customers may be experiencing an error showing on the project sidebar, which is impacting their ability to navigate within the project. We have started to investigate the issue and will provide further updates.

The issue causing "You don't have permissions to assign issues" errors for Jira users has been fully resolved. All systems are now operating normally, and users should no longer experience any permission-related problems.

We have identified the issue and applied a potential solution. The change will take approximately four hours to fully roll out, but improvements can be experienced sooner. We'll share more details in the coming hours.

We are investigating cases of Jira users getting "You don't have permissions to assign issues". We have identified the root cause of the issue. We will provide more details within the next hour.

Between 19/Sep/24 12:11 AM UTC to 19/Sep/24 2:39 AM UTC, we experienced left navigation panel not visible in the JIRA issue view. The issue has been resolved and the service is operating normally.

We have identified the root cause of the issue where left-hand navigation panel is not visible in JIRA issue view and have mitigated the problem. We are now monitoring this closely.

We have identified an issue where the left navigation panel is not visible in the JIRA issue view. We have started to investigate the issue and will provide further updates shortly.

Between 2024-09-18 14:01 UTC and 2024-09-18 15:25 UTC, we experienced an incident that caused errors in Jira Work Management, Jira Service Management, and Jira. The issue has been resolved, and the service is operating now.

We have an incident reported wherein the JWM is reporting errors. This is specific to EU region. We have started the investigation and would post further updates here.

The issue has been mitigated and JWM is operational now.

We are continuing to investigate this issue.

We have identified an issue wherein JWM is not loading or is loading very slow. We have started to investigate the issue and will provide further updates shortly.

Between 2024-09-09 11:06 UTC to 2024-09-12 10:24 UTC, we experienced elevated error rates for Jira issue creation for Jira Cloud. The issue has been resolved and the service is operating normally.

We continue to work on resolving the Jira issue creation function for Jira Cloud. We have identified the root cause and expect recovery shortly.

We are investigating an issue with creating Jira issues that is impacting some Jira Cloud customers. We will provide more details within the next hour.

This issue has been resolved.

Earlier today, we experienced issues with Automation. The issue has been resolved for Jira Service Management and Jira, we are working on fixing the issue for Confluence.

We are investigating an issue with Automation that is impacting Confluence, Jira, and Jira Service Management cloud customers. You might see the following issues: - Affected customers won't see any of the previously configured Automation rules - These automation rules are not executing at the moment We are actively working on this and will provide more details shortly.

This issue has been resolved.

We have identified the root cause and the issue appears to be resolved.

Users attempting to sign up are encountering reCaptcha errors that are preventing a successful signup.

This incident has been resolved.

We are seeing recovery and monitoring the situation

We are investigating cases of degraded performance and increased error rates for Atlassian products. We will provide more details within the next hour.

Between 15:00 UTC to 15:48 UTC, we experienced partial unavailability for Jira in the AMER region. The issue has been resolved, and the service is operating normally.

Between 02:35 UTC to 3:55 UTC on Aug 26, we experienced failing Identity sync for Jira Work Management, Jira Service Management, Jira, and Guard. The issue has been resolved and the service is operating normally. All affected Jira customers were synched with Identity and there is not need to wait 24h for a full sync.

The bug has been identified and fixed. However, it could take up to 24 hours since 03:55 UTC for the User and Group reflected correctly. As a workaround, you may need to perform a new User or Group change.

Between 02:35 UTC and 03:55 UTC, due to bugs in Identity, some changes in users' and group settings were not reflected in Jira.

Between 15 Aug 2024 - 10:30 UTC to 15 Aug 2024 - 22:40 UTC, editing of Jira Workflow Schemes were affected in Jira, Jira Service Management, Jira work management. The issue has been resolved and the service is operating normally. If you face any challenges please reach out to us via support ticket.

The team is still working towards a fix for the Jira Workflow Schemes.

Editing Jira Workflow Schemes is currently not possible and is resulting in the following error: The Jira server was contacted but has returned an error response. We are unsure of the result of this operation. The team is currently working on identifying the root cause and resolving it.

Between 12:00am 9th July to 08:00am 10th July, we experienced email deliverability issues for some recipient domains for Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, and Jira Product Discovery. The issue has been resolved and future emails will flow normally.

We continue to work on resolving the Email Notifications for Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, and Jira Product Discovery. We have identified the root cause.

We are investigating reports of intermittent errors whilst sending Email Notifications for Confluence, Jira Work Management, Jira Service Management, Jira, Trello, and Jira Product Discovery Cloud customers. We will provide more details once we identify the root cause.

Between 03-07-2024 20:08 UTC to 03-07-2024 20:31 UTC, we experienced issue creation and project for Jira Work Management. The issue has been resolved and the service is operating normally.

We have mitigated the problem and continue looking into the root cause. The outage was between 8:08pm 03/07 UTC - 08:31pm 03/07 UTC We are now monitoring closely.

We are investigating an issue with <FUNCTIONALITY IMPACTED> that is impacting <SOME/ALL> Atlassian, Atlassian Partners, Atlassian Support, Confluence, Jira Work Management, Jira Service Management, Jira, Opsgenie, Atlassian Developer, Atlassian (deprecated), Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas, Atlassian Analytics, and Rovo Cloud customers. We will provide more details within the next hour.

Between <01:15 UTC> to <08:03 UTC>, the copy production data to sandbox was unavailable for Confluence, Jira Work Management, Jira Service Management, and Jira. The issue has been resolved and the service is operating normally.

We are investigating reports that the option to copy production data to the sandbox is not available. We have identified the root cause and are rolling out the fix.

We have identified that this behavior existed for long time and is due to a bug triggered in edge scenario when following sequence of events happens: 1. First a paid app gets suspended due to lack of payment 2. Then administrator decides to uninstall app 3. Then administrator decides to (re)install app 4. Payment is issued for the app 5. App fails to reactivate (as a result of this bug) We are advising customers to raise a support ticket with Atlassian to restore app functionality when faced with such scenario. The app reactivates correctly when no re-installation was attempted after suspension. We haven't found any recent changes that could cause this scenario to be happening more frequently. We're going to work in the future on improving the reinstallation flow for the suspended apps which will reduce the possibility to leave apps in state whey they can't be reactivated.

We have identified that this behavior existed for long time and is due to a bug triggered in edge scenario when following sequence of events happens: 1. First a paid app gets suspended due to lack of payment 2. Then administrator decides to uninstall app 3. Then administrator decides to (re)install app 4. Payment is issued for the app 5. App fails to reactivate (as a result of this bug) We are advising customers to raise a support ticket with Atlassian to restore app functionality when faced with such scenario. The app reactivates correctly when no re-installation was attempted after suspension. We are working on a plan to fix this issue. We are continuing our investigation to understand if there is no recent change in system that could cause this scenario to be happening more frequently. We will post next update in 24 hours - by the 2024-06-13 9:30 UTC.

We are investigating an issue impacting paid apps after their license being suspended due to non-payment, and then reactivation fails even after making payment. We will provide more details once we identify the root cause.

Between 22:18 UTC to 22:56 UTC, we experienced errors for multiple Cloud products. The issue has been resolved and the service is operating normally.

We are investigating an issue with error responses for some Cloud customers across multiple products. We have identified the root cause and expect recovery shortly.

Some customer have experienced authorisation issues with Jira incoming mail Microsoft mail handlers when re-authorising or creating a new mail handler. The issue has been resolved and the service is operating normally now.

Some customers are experiencing an authorisation issue with Jira incoming mail Microsoft mail handlers when re-authorising or creating a new mail handler. We are working through this issue with Microsoft and expect some delays. When a fix is delivered, all the mail will be processed and issues subsequently created.