Jira Service Management Status

Excessive notifications being received by some Jira Service Management users

Update - Some of the users continue to experience an excessive number of notifications arriving from JSM (Assist) as our team replays delayed events experienced in this prior incident:

https://jira-service-management.status.atlassian.com/incidents/v307yb60q5g7

At this time we expect that these notifications will be arriving for the next few hours, until the recovery of the delayed events are processed which is taking longer than expected (ETA approx. 4 hours). We will provide further updates within 6 hours or sooner if the recovery occurs.
May 14, 2026 - 03:52 UTC

Investigating - We are aware that some users are experiencing an excessive number of notifications arriving from Jira Service Management (Assist) as our team replays delayed events experienced in this prior incident:

https://jira-service-management.status.atlassian.com/incidents/v307yb60q5g7

At this time we expect that the vast majority of these notifications will be arriving within the next two hours.
We will provide further update at that time or sooner if further information becomes available.
May 14, 2026 - 01:15 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

May 14, 2026

Users experiencing issues accessing multiple Atlassian products

Resolved - All products and services impacted by this incident should now be fully recovered, and this incident is resolved.
May 14, 06:48 UTC

Update - We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.
May 14, 06:41 UTC

Monitoring - Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products.
We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place.
May 14, 05:43 UTC

Update - Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products.

At this time, Atlassian customers should also be able to once again raise support requests with our team.

We will provide further update within an hour as we are able to progress mitigating this issue.
May 14, 05:34 UTC

Update - It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident.

We are continuing to receive reports about expanded product impact resulting from this incident.

While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information.

We will provide further update within one hour, or sooner as further information becomes available.
May 14, 05:24 UTC

Identified - Further confirmations of impacted products have now been added to the incident.

Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.
May 14, 05:11 UTC

Investigating - We are aware that the current issues with accessing Atlassian products are impacting additional products. We have now expanded the impact of the incident to cover the known impacted products at this time.
We will provide further update within one hour or sooner as information is available.
May 14, 05:03 UTC

May 13, 2026

Automations within Jira, Jira Service Management and JSM Assist experiencing delays for some users

Resolved - We appreciate your patience during this incident. Our services are now fully operational and all delayed automation events have been processed.
May 13, 09:59 UTC

Update - Our teams are actively processing events that were delayed during this incident. We will provide a further update once all delayed events have been processed.
May 13, 08:42 UTC

Update - While new automation events are being processed correctly, our teams continue working through the processing of historical events that were delayed by this incident.

We will provide an update on the progress within one hour.
May 13, 07:42 UTC

Update - Our team has been able to confirm that new automation events should now be processed correctly.

We are working through the processing of historical events that have been delayed by this incident and will provide an update on progress within one hour.
May 13, 06:38 UTC

Update - The root cause of this issue has now been confirmed by our incident response team.
We are working urgently to bring back normal automation processing to impacted users, and process historical events that were delayed by the impact of the incident.
We will provide further update within one hour or sooner if available.
May 13, 05:38 UTC

Identified - Our team has identified a likely root cause of this issue and is actively working on a fix.
At this point in time the required steps to mitigate this issue are expected to take approximately three hours.
We will provide further update within three hours or sooner if further information is available prior to that time.
May 13, 02:41 UTC

Investigating - At this time it is expected that impacted users may be experiencing delays for multiple hours on their automation events.
Our team is continuing to investigate this issue with urgency. We will provide further update within an hour.
May 13, 01:37 UTC

May 12, 2026

No incidents reported.

May 11, 2026

No incidents reported.

May 10, 2026

No incidents reported.

May 9, 2026

No incidents reported.

May 8, 2026

Multiple Atlassian services are experiencing issues

Resolved - On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.
May 8, 19:45 UTC

Update - Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team.

We apologise for the disruption and thank you for your patience.
May 8, 11:12 UTC

Update - We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.
May 8, 08:03 UTC

Monitoring - The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared.
May 8, 05:53 UTC

Update - We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each product page.
May 8, 04:10 UTC

Update - Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.
May 8, 04:10 UTC

Update - We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.
May 8, 04:10 UTC

Update - Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.
May 8, 03:00 UTC

Identified - We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.
May 8, 02:15 UTC

Investigating - We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.
May 8, 01:31 UTC

May 7, 2026

No incidents reported.

May 6, 2026

Lookup Objects in Automation for Jira Service Management are not functioning

Resolved - The issue causing failures in the lookup objects within JSM Automation has been resolved. A fix was implemented to address the problem and the service is now operating normally for all affected customers.
May 6, 11:17 UTC

Monitoring - A fix has been implemented to address the failures observed in the lookup objects within JSM Automation. We are actively monitoring the situation to ensure stability. We will share the final update within next 1 hour.
May 6, 10:18 UTC

Investigating - We are investigating reports of lookup objects in Automation for Jira Service Management are not functioning as expected. Our engineering teams are actively investigating and working to resolve the issue. We will provide further updates in next 1 hour.
May 6, 09:35 UTC

May 5, 2026

No incidents reported.

May 4, 2026

No incidents reported.

May 3, 2026

No incidents reported.

May 2, 2026

The Work Item view experience of Jira is restored

Resolved - The Jira Work Item View experience has been restored to normal service. Our teams are continuing to investigate the root cause affecting this issue.
We will provide more details once we identify the root cause
May 2, 02:48 UTC

Update - We are actively investigating reports of a service disruption affecting the Work Item viewing experience in Jira. This is also impacting the accessibility of support tickets.
We will share updates here as more information becomes available.
May 2, 02:00 UTC

Update - We are actively investigating reports of a service disruption affecting the issue viewing experience in Jira. This is also impacting the accessibility of support tickets.
We will share updates here as more information becomes available.
May 2, 01:38 UTC

Investigating - We are investigating an incident affecting Jira Software (viewBoard, viewIssue, createIssue). Our team is working to identify the cause and restore service to normal levels. We will provide the next update within 60 minutes.
May 2, 00:55 UTC

May 1, 2026

No incidents reported.

Apr 30, 2026

No incidents reported.