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

Apr 4, 2025

No incidents reported today.

Apr 3, 2025

No incidents reported.

Apr 2, 2025

No incidents reported.

Apr 1, 2025

No incidents reported.

Mar 31, 2025

No incidents reported.

Mar 30, 2025

No incidents reported.

Mar 29, 2025

No incidents reported.

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