Jira Service Management Incident History

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 aware of users experiencing issues attempting to load Jira Dashboard widgets. Our team is investigating this issue with priority.

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

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.

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.