Is Jira Service 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 are investigating an issue impacting a subset of market place apps for some Confluence, Jira Service Management, and Jira, and Atlassian Developer Cloud customers in the Singapore region. We will provide more details within the next hour.

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.

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 problematic change that caused this issue has now been rolled back and service has now been restored.

Our team is continuing to investigate this issue with urgency, and will provide an update as soon as possible when available.

We are continuing to investigate this issue.

We are investigating cases of degraded performance for Jira and Jira Service Management Outlook Plugin. We will provide more details within the next hour.

Our team has now mitigated this issue and product performance has been restored.

We have identified the root cause of the failure and have mitigated the issue, but we are investigating the root cause of the traffic increase in JSM. We continue to monitor closely.

We have identified the root cause of the JSM Request experience degraded performance and are actively mitigating the problem. We are now monitoring closely.

We are investigating cases of degraded performance and reduced access for raising certain JSM request types in Jira Service Management Cloud customers. We will provide more details within the next hour.

We are investigating cases of degraded performance for Jira and Jira Service Management Outlook Plugin. We will provide more details within the next hour.

We are investigating cases of degraded performance and reduced access for raising certain JSM request types in Jira Service Management Cloud customers. We will provide more details within the next hour.

All search functionality is operational without any latency. Thank you for your patience.

The problem is mitigated, and we are now monitoring closely.

We identified degraded performance at alert search functionality for some Jira Service Management and Opsgenie Cloud customers due to the infrastructure issue from cloud provider. No impact has been observed at alert critical flows like notification. The team has taken actions to mitigate the issue and minimize the impact to search functionality

We identified degraded performance at alert search functionality for some Jira Service Management and Opsgenie Cloud customers due to the infrastructure issue from cloud provider. No impact has been observed at alert critical flows like notification. The team has taken actions to mitigate the issue and minimize the impact to search functionality

Between 7:37 and 8:06 UTC, Confluence, Jira, and JSM were unavailable or experienced degraded performance for some users in the European region. The issue has now been resolved, and the services are operating normally for all impacted customers.

From 7:37 to 8:06 UTC, we experienced issues that made Confluence, JIRA, and JSM unavailable or degraded the experience of some users in the European region. The issue has been mitigated, and services operate normally for all impacted customers. We will continue to monitor it closely for stability.

From 7:37 to 8:06 UTC, we experienced issues that made Confluence, JIRA, and JSM unavailable or degraded the experience of some users in the European region. The issue has been mitigated, and services operate normally for all impacted customers.We will continue to monitor it closely for stability.

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.

Our team has identified the issue causing problems with Assets loading within JSM and Jira and applied a fix. Assets are now functioning as expected across our products.

We are aware of some users experiencing an error such as 'there is a problem loading the objects' when attempting to view Assets in JSM and Jira. Our team is looking into this issue with urgency.

We are aware of some users experiencing an error such as 'there is a problem loading the objects' when attempting to view Assets in JSM and Jira. Our team is looking into this issue with urgency.

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.

A fix has been put into place for the issue relating to Assets not appearing correctly in the customer portal. This should now be resolved.

We are aware of an issue currently impacting the customer portal view of JSM, where Assets are not appearing correctly. Our team is looking into this issue with urgency and we will provide an update when available.

We are aware of an issue currently impacting the customer portal view of JSM, where Assets are not appearing correctly. Our team is looking into this issue with urgency and we will provide an update when available.

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.

### Summary Jira, Confluence and JSM Automation rules triggered or scheduled to run between 10am and 5pm UTC on March 17, 2025, and between 1pm UTC on March 18 and 12:30am UTC on March 19 were delayed on average by 1.5 hours and up to 12 hours maximum. The incident was triggered by the deployment of a monitoring library upgrade, which slowed the execution of all rules. This reduced the throughput of rule processing which resulted in rules being backed up and delayed. The change manifested in poor rule performance only during periods of high traffic. This incident occurred over two time windows. For the first incident window, backed-up rule executions began to reduce 4 hours 15 minutes after the first alert, and all rules had caught up 7 hours after the first alert. For the second incident window, backed-up rule executions began to reduce 1 hour, 50 minutes after the first alert, and all rules had caught up 10 hours after the first alert. The root cause of both incidents was identified and a change to address it was deployed by 10am UTC on March 19, 2025. ### **IMPACT** The customer’s rules were delayed on average by 1.5 hours and up to 12 hours during both incident windows. A very small number of rules encountered the following error: “_The rule actor doesn't have permission to view the event that triggered this rule_.” This error occurred because of rate limiting implemented by an internal Atlassian service due to increased throughput resulting from our mitigation efforts. These rules failed to complete successfully. All other rules eventually ran successfully. ### **ROOT CAUSE** The issue was caused by a change introduced to an Atlassian monitoring library, which significantly degraded the Automation rule engine's performance. The performance degradation prevented Automation's system from keeping pace with processing throughput, causing a back-up of executions and subsequent customer rule delays. ### **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 didn’t manifest itself until our systems were at peak load. The change to the Atlassian monitoring library that was the root cause of the incident has been fixed. We are prioritizing the following improvement actions that are designed to avoid a repeat of this type of incident: * Deploying the fixed monitoring library after thorough testing * Implementing additional monitoring and alerting to the area of our system affected with performance degradation * Introducing additional pre-deployment testing designed to identify performance degradations before they impact customers * Increasing rate limits of certain downstream Atlassian systems to reduce the likelihood of the rule failures that occurred in this incident * Increasing the processing capacity of parts of our system to reduce the impact of backed up rule executions We apologize to customers whose automation rules were impacted during this incident; we are taking immediate steps designed to improve the platform’s performance and availability. Thanks, Atlassian Customer Support

Between 13:00 UTC to 16:30 UTC, we experienced delays in automation processing across Confluence, Jira Service Management, and Jira, which was causing rules to appear stuck. The issue has been resolved and we expect new automations to continue processing without delay. For automation processes initiated before 16:30 UTC, they may take until 08:00 UTC March 19th, 2025, however, we anticipate processing to be completed quicker. No action is required from users for these automations to be completed.

We have successfully identified and mitigated the issue affecting all automation customers, which was causing rules to appear stuck. New automations should now process as expected without delay. For automation processes initiated from 13:00 UTC to 16:30 UTC on March 18th, 2025, in Jira, Jira Service Management, and Confluence, execution will continue but may experience delays of up to one day. No action is required from users for these automations to be completed. We are closely monitoring the situation and will provide further updates as more information becomes available.

The delayed execution of automation rules is mitigated and recovery is in progress. We are now monitoring closely.

We are investigating cases of degraded performance regarding automation rules execution for Confluence, Jira Service Management, and Jira Cloud customers. We are applying mitigation to speed up rule execution. We will provide more details within the next hour.

We are investigating cases of degraded performance w.r.t automation rules execution for Confluence, Jira Service Management, and Jira Cloud customers. We will provide more details within the next hour.

We have confirmed that this issue is now resolved.

Our team has now identified the cause of this problem and has reverted a recent change that is expected to have caused this error. Our team is continuing to monitor to ensure resolution of this issue at this time.

We are aware of some users currently receiving a 502 Bad Gateway error message when attempting to access their JSM Customer Portals. Our team is currently investigating an an update will be provided when available

We have confirmed that this issue is now resolved.

Our team has now identified the cause of this problem and has reverted a recent change that is expected to have caused this error. Our team is continuing to monitor to ensure resolution of this issue at this time.

We are aware of some users currently receiving a 502 Bad Gateway error message when attempting to access their JSM Customer Portals. Our team is currently investigating an an update will be provided when available

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.

Between 00:13 UTC to 10:00 UTC, on 21st March, we experienced provisioning failures for Jira Service Management. During this time, customers were unable to add/update their Assets in JSM. The issue has been resolved and the service is operating normally.

We are aware of some customers having a degraded experience when attempting to upgrade or adding new Assets to JSM products. Our team is currently investigating this issue and will post new updates as they become available.

We are aware of some customers having a slower than expected experience when attempting to upgrade or activate JSM products. Our team is investigating this issue.

Between 00:13 UTC to 10:00 UTC, on 21st March, we experienced provisioning failures for Jira Service Management. During this time, customers were unable to add/update their Assets in JSM. The issue has been resolved and the service is operating normally.

We are aware of some customers having a degraded experience when attempting to upgrade or adding new Assets to JSM products. Our team is currently investigating this issue and will post new updates as they become available.

We are aware of some customers having a slower than expected experience when attempting to upgrade or activate JSM products. Our team is investigating this issue.

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.

Between 13:00 UTC to 16:30 UTC, we experienced delays in automation processing across Confluence, Jira Service Management, and Jira, which was causing rules to appear stuck.The issue has been resolved and we expect new automations to continue processing without delay.For automation processes initiated before 16:30 UTC, they may take until 08:00 UTC March 19th, 2025, however, we anticipate processing to be completed quicker. No action is required from users for these automations to be completed.

We have successfully identified and mitigated the issue affecting all automation customers, which was causing rules to appear stuck. New automations should now process as expected without delay.For automation processes initiated from 13:00 UTC to 16:30 UTC on March 18th, 2025, in Jira, Jira Service Management, and Confluence, execution will continue but may experience delays of up to one day. No action is required from users for these automations to be completed. We are closely monitoring the situation and will provide further updates as more information becomes available.

The delayed execution of automation rules is mitigated and recovery is in progress. We are now monitoring closely.

We are investigating cases of degraded performance regarding automation rules execution for Confluence, Jira Service Management, and Jira Cloud customers. We are applying mitigation to speed up rule execution. We will provide more details within the next hour.

We are investigating cases of degraded performance w.r.t automation rules execution for Confluence, Jira Service Management, and Jira Cloud customers. We will provide more details within the next hour.

Between 14:22 UTC to 16:41 UTC, we experienced performance degradation for 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 Jira Service Management and Jira Cloud customers. We will provide more details within the next hour.

Between 14:22 UTC to 16:41 UTC, we experienced performance degradation for 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 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.

Between 09:43 UTC to 15:55 UTC, we experienced delays in automation processing across Confluence, Jira Service Management, and Jira, which was causing rules to appear stuck. The issue has been resolved and we expect new automations to continue processing without delay. For automation processes initiated before 15:55 UTC, we anticipate processing to be completed by 08:00 UTC March 18th, 2025. No action is required from users for these automations to be completed.

We have successfully identified and mitigated the issue affecting all automation customers, which was causing rules to appear stuck. New automations should now process as expected without delay. For automation processes initiated before 15:55 UTC on March 17th, 2025, in Jira, Jira Service Management, and Confluence, execution will continue but may experience delays of up to one day. No action is required from users for these automations to be completed. We are closely monitoring the situation and will provide further updates as more information becomes available.

Following our previous update, we continue to experience delays in automation processing across Jira, Jira Service Management, and Confluence. The issue persists, affecting all automation customers and causing rules to appear stuck. Our team is actively working to resolve the situation and restore normal service levels as quickly as possible. We appreciate your patience and will provide further updates as more information becomes available.

We are currently experiencing delays in automation processing across Jira, Jira Service Management, and Confluence due to high traffic. While rules are firing, execution is delayed. Rules triggered in the last 2.5 hours will be processed, but this may take up to a day. New events should process normally following adjustments made at 12:13 PM UTC to prioritize them. We will provide an update in the next hour. Thank you for your patience.

Between 09:43 UTC to 15:55 UTC, we experienced delays in automation processing across Confluence, Jira Service Management, and Jira, which was causing rules to appear stuck. The issue has been resolved and we expect new automations to continue processing without delay.For automation processes initiated before 15:55 UTC, we anticipate processing to be completed by 08:00 UTC March 18th, 2025. No action is required from users for these automations to be completed.

We have successfully identified and mitigated the issue affecting all automation customers, which was causing rules to appear stuck. New automations should now process as expected without delay.For automation processes initiated before 15:55 UTC on March 17th, 2025, in Jira, Jira Service Management, and Confluence, execution will continue but may experience delays of up to one day. No action is required from users for these automations to be completed. We are closely monitoring the situation and will provide further updates as more information becomes available.

Following our previous update, we continue to experience delays in automation processing across Jira, Jira Service Management, and Confluence. The issue persists, affecting all automation customers and causing rules to appear stuck. Our team is actively working to resolve the situation and restore normal service levels as quickly as possible. We appreciate your patience and will provide further updates as more information becomes available.

We are currently experiencing delays in automation processing across Jira, Jira Service Management, and Confluence due to high traffic. While rules are firing, execution is delayed. Rules triggered in the last 2.5 hours will be processed, but this may take up to a day. New events should process normally following adjustments made at 12:13 PM UTC to prioritize them. We will provide an update in the next hour. Thank you for your patience.

On March 14th, 2025, between 09:00 and 19:14 UTC, some customers experienced issues creating new sites. The errors occurring for some users during new site creation should now be resolved.

We are investigating cases of errors for some users creating new sites. We will provide more details within the next hour.

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.

JSM and JIRA mail puller services have recovered and are back in normal operating status. For more information, please check Microsoft status updates at this link: https://portal.office.com/servicestatus

Microsoft has resolved the issue and we are currently monitoring performance for Jira and JSM.

We are currently experiencing degraded performance with Microsoft mail services. We are investigating the issue with Microsoft

On February 26, 2025 14:45 UTC a temporary Slack outage began which affected JSM automations within Slack. On February 27, 2025 08:05 UTC we observed new Slack events being processed within JSM successfully. We have confirmed with the Slack team that this outage is resolved. Slack has advised on their Status page that they do not plan to replay events that were buffered from this incident. For more information on Slack’s update please refer to Slack's status page: https://slack-status.com/2025-02/1b757d1d0f444c34 If you have any further questions please contact our support team.

New Slack events are continuing to get processed within JSM successfully. We are continuing to monitor the situation closely. We are still awaiting confirmation on when the historical events from the start of the incident will be processed. For ongoing updates, please refer to Slack's status page: https://slack-status.com/2025-02/d41e4bfd1ccae26a

New Slack events are continuing to get processed within JSM successfully. We are continuing to monitor the situation closely. We are still awaiting confirmation on when the historical events from the start of the incident will be processed. For ongoing updates, please refer to Slack's status page: https://slack-status.com/2025-02/d41e4bfd1ccae26a

We have confirmed with Slack that new events are now being processed successfully, and we have validated this within JSM. We continue to monitor the situation closely. We are still awaiting confirmation on whether historical events from the start of the incident will be processed. For ongoing updates, please refer to Slack's status page: https://slack-status.com/2025-02/d41e4bfd1ccae26a

An issue has occurred where JSM Automations within Slack are not currently triggering actions as expected. Slack is aware of this issue and is working through their backlog of events. Atlassian has received a small number of events from this backlog and is monitoring for incoming alerts to be processed. Slack are providing updates on this issue on their status page here: https://slack-status.com/2025-02/d41e4bfd1ccae26a

We are aware of an issue where JSM Automations within Slack are not currently triggering actions as expected. Slack is aware of this issue and is working through their backlog of events that need to be processed. We are pending Atlassian system events to be processed at this time. Slack are providing updates on this issue on their status page here: https://slack-status.com/2025-02/d41e4bfd1ccae26a

We are aware of an issue with JSM Automations within Slack are not currently triggering actions as expected. We believe that this is related to a current incident that Slack is experiencing with Events API. Slack is providing updates on this issue on their status page here: https://slack-status.com/2025-02/d41e4bfd1ccae26a

### 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.

This incident has been resolved.

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

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

We're experiencing an elevated level of API errors in Asset services and are currently looking into the issue.

The issue with Jira Service Management Assets has been resolved, and the service is now functioning normally.

We are investigating an issue with Jira Service Management Assets that is affecting our Jira Service Management Cloud customers in the European region. We will provide more details within the next hour.

We are investigating an issue with JSM Assets that is impacting customers in Jira Service Management Cloud customers in Europe . We will provide more details within the next hour.

This incident has been resolved.

We have identified a fix and we are monitoring the results

We are investigating an issue with email processing failing for Jira/Jira Service Management customers. We will update on the progress of the investigation

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.

Between 30 January 2025, 23:05 UTC, and 31 January 2025, 01:40 UTC, some customers for Confluence and Jira Service Management experienced errors viewing Confluence content either directly on Confluence or on Jira Service Management Portal as Knowledge base articles. The root cause was the custom domain configured for Confluence, which caused a 'Forbidden Client' error. We have deployed a fix to mitigate the issue and verified that the services have recovered. The issue has been resolved and the service is operating normally.

We have identified the root cause of the Confluence pages that can't be accessed and are not loaded in JIRA Service Management knowledge-based. We have mitigated the problem, and now we are monitoring it closely.

We are investigating an issue with being unable to access Confluence pages that are impacting Confluence and JIRA Service Management Cloud customers. We will provide more details within the next hour.

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 13 Jan, 11:45 PM UTC to 14 Jan 07:10 AM UTC, we experienced intermittent login failures for Confluence, Jira Service Management, and Jira. The issue has been resolved and the service is operating normally.

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

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.

Between 10:00pm UTC on 09/Jan/25 to 3:00am UTC on 10/Jan/25, the Automation drop down menu for Jira Service Management and Jira was not rendering correctly. The issue has been resolved and the service is operating normally.

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

Between 11:28:00 UTC on 22/Dec/24 to 16:41:00 UTC on 23/Dec/24, we experienced a problem when running Automation rules for Confluence, Jira Service Management, and Jira that prevented rules that contained a Send Web Request action with Smart Values from completing successfully. The issue has been resolved and the service is operating normally.

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

Between 12:19 UTC to 02:27 UTC we experienced degradation of assets experiences and customer and organisation profile information for some customers in the Asia Pacific region. The issue has now been resolved and the service is operating normally.

We are monitoring traffic to confirm resolution.

We have identified the fault in the system and are addressing the issue.

We notice customers getting impacted by Internal Server Errors across Asia Pacific region for Assets powered experiences. Jira Service Management and Assets experiences are partially unavailable.

This incident has been resolved.

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

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

Between 08:30 UTC and 22:19 UTC, we experienced an issue that caused "View Remaining XX comments" not to load for Jira Service Management and Jira. The issue has been resolved and the service is operating normally.

We are finalizing a fix and will deploy it soon. Workaround: Users can navigate to the All tab and then revisit the Comments tab. This resolves the issue, allowing the remaining comments to be viewed.

We are actively working on a hotfix for this incident. The update is taking longer than expected; we will provide an update in one hour. Workaround: Users can navigate to the All tab and then revisit the Comments tab. This resolves the issue, allowing the remaining comments to be viewed.

We are actively working on a hotfix for this incident. The process of building and progressively rolling out the fix is expected to take approximately 4 hours. We will update here if there are any changes in the timeline Workaround: Users can navigate to the All tab and then revisit the Comments tab. This resolves the issue, allowing the remaining comments to be viewed.

We continue to work on the HOT-fix for this incident. We will post another update in one hour.

We have identified the cause for the issue where users are not able to load more comments through View Remaining XX comments. A Hot-fix is being applied at the moment. This is currently affecting Jira Service Management, and Jira Cloud customers. As a workaround: users need to go to All tab and visit comments tab again. This resolves the issue and then remaining comments can be viewed We will provide more details within the next hour.

Between 3:16pm PST and 7:38pm PST, we experienced an outage for Rovo and all AI features across Atlassian Products. The issue has been resolved and the service is operating normally

We are witnessing significant recovery in the services. We will continue to monitor the situation closely.

We are actively communicating with the affected AI Service provider and closely monitoring the ongoing outage situation. While we have observed some signs of recovery, the majority of API calls are still resulting in errors. We have successfully restored the Smart Answers in Search feature by rerouting requests to an alternative model. All other Atlassian Intelligence capabilities and Rovo remain unavailable at this time due to the ongoing AI Service provider outage.

Between 12:13 AM UTC to 01:30 AM UTC, we experienced a degraded experience for AI features in Confluence, Jira Service Management, Jira, and Rovo. The issue has been resolved and the service is operating normally.

We are investigating an issue with AI features that is impacting all Rovo and Enterprise and Premium Confluence, Jira Service Management and Jira customers. We will provide more details within the next hour.

Between 09:00 UTC and 09:51 UTC, we experienced degraded performance for some Jira Service Management and Jira customers. The issue has been resolved, and the service is operating normally.

We have taken action to mitigate this issue and we will continue to monitor for the next hour before marking the incident as resolved.

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

Between 24/11/2024 09:46 PM UTC to 27/11/2024 5:58PM UTC, we experienced an issue where Automation match() smart values with regex are not working as expected for Confluence, Jira Service Management, and Jira. This issue has now been resolved, and automation rules are functioning as expected.

We have identified an issue with Automation match() smart values with regex that is impacting all Jira products and Confluence Cloud. We have identified the root cause and have stopped it from reoccurring.

All affected products are now back online and no further impact has been observed.

We have identified the root cause of the issue and have stopped it from reoccurring. We are currently working on a mitigation plan for the affected services.

We have identified an issue impacting some JSM customers where Compass components have been incorrectly sync'ed with JSM leading to unexpected services showing up in JSM. We are investigating the issue and will provide further updates shortly.

Between 15:29 UTC to 17:57 UTC, we experienced sync issues with Assist for Jira Service Management. The issue has been resolved and the service is operating normally.

We are investigating an issue with Assist that is impacting JSM Cloud customers. The issue is causing delays in synching information between Assist and Jira. We will provide more details within the next hour.

We are pleased to inform you that the recent issues affecting email processing for Microsoft accounts, which impacted our Jira and JSM Cloud customers, have been successfully resolved. This resolution follows Microsoft’s reversion of the changes that initially caused the disruption. We appreciate your patience and understanding as we worked closely with Microsoft to address this matter promptly.

Microsoft has identified the root cause of the API failures and provided an update that they are working on a solution. We are now monitoring this closely.

We are investigating an issue with email processing that is impacting some Jira and JSM Cloud customers. Multiple Microsoft APIs are failing, which is causing emails not to be marked as read and creating duplicate tickets, comments, and customer notifications for email requests in JSM, as well as internal notifications in Jira. The impact started at 7:00 UTC. This is a widespread issue on Microsoft's end, and we are currently awaiting their resolution

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.

We've noticed that Operations functionality on Jira Service Management Web UI was responding slowly or unavailable in US region between 07:00 PM and 07:35 PM UTC. Our engineering team has resolved this incident and brought back the Operations functionality up to speed.