Jira Service Management Status

Maintenance Notification for Jira and Confluence Platforms (Singapore and Northern California Only)

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 18, 2025 - 00:00 UTC

Scheduled - 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
Mar 18, 2025 00:00 - Jun 1, 2025 00:00 UTC

About This Site

Here we will post updates about Jira Service Management's availability. For status information about other Atlassian products or services, please visit the Atlassian status page.

Jira Service Management Web Operational

Service Portal Operational

Opsgenie Incident Flow Operational

Opsgenie Alert Flow Operational

Opsgenie Incident Flow Operational

Opsgenie Alert Flow Operational

Jira Service Management Email Requests Operational

Authentication and User Management Operational

Purchasing & Licensing Operational

Signup Operational

Automation for Jira Operational

Assist Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Past Incidents

Mar 29, 2025

No incidents reported today.

Mar 28, 2025

No incidents reported.

Mar 27, 2025

No incidents reported.

Mar 26, 2025

No incidents reported.

Mar 25, 2025

Users receiving a 502 Bad Gateway error when attempting to open JSM Customer Portal

Resolved - We have confirmed that this issue is now resolved.
Mar 25, 05:48 UTC

Monitoring - 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.
Mar 25, 05:34 UTC

Investigating - 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
Mar 25, 05:06 UTC

Mar 24, 2025

Some customers are experiencing an issue viewing Team field in Jira issue view

Resolved - 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.
Mar 24, 17:56 UTC

Investigating - 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.
Mar 24, 17:07 UTC

Mar 23, 2025

No incidents reported.

Mar 22, 2025

No incidents reported.

Mar 21, 2025

Intermittent issues with customer upgrades and adding new Assets in JSM in ap-south region

Resolved - 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.
Mar 21, 10:55 UTC

Update - 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.
Mar 21, 06:19 UTC

Investigating - 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.
Mar 21, 02:05 UTC

Mar 20, 2025

No incidents reported.

Mar 19, 2025

Some customers are experiencing an issue viewing Team field in Jira

Resolved - 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.
Mar 19, 22:58 UTC

Investigating - 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.
Mar 19, 22:06 UTC

Users Encountering a Site Maintenance Message on APAC-Based Jira Sites

Resolved - 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.
Mar 19, 19:12 UTC

Identified - 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.
Mar 19, 15:11 UTC

Update - 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.
Mar 19, 12:39 UTC

Update - 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.
Mar 19, 09:08 UTC

Update - 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.
Mar 19, 08:22 UTC

Investigating - 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.
Mar 19, 07:45 UTC

Performance degradation for Jira and Confluence User

Resolved - 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.
Mar 19, 16:22 UTC

Investigating - 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.
Mar 19, 15:07 UTC

Mar 18, 2025

Automation rule execution are delayed

Resolved - 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.
Mar 18, 17:28 UTC

Update - 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.
Mar 18, 17:15 UTC

Monitoring - The delayed execution of automation rules is mitigated and recovery is in progress. We are now monitoring closely.
Mar 18, 16:51 UTC

Update - 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.
Mar 18, 16:09 UTC

Investigating - 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.
Mar 18, 15:04 UTC

Users may experience performance degradation when loading the issue view

Resolved - 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.
Mar 18, 16:42 UTC

Investigating - 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.
Mar 18, 16:24 UTC

Mar 17, 2025

Service Slowness in Multiple Products

Resolved - 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.
Mar 17, 22:33 UTC

Monitoring - 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.
Mar 17, 16:36 UTC

Investigating - 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.
Mar 17, 14:19 UTC

Monitoring - 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.
Mar 17, 12:43 UTC

Mar 16, 2025

No incidents reported.

Mar 15, 2025

No incidents reported.