Atlassian Jira Service Management Outage History

57 incidents recorded over the last 365 days, 57 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Atlassian Jira Service Management status92.37% uptime history

Every Recorded Atlassian Jira Service Management Incident

Atlassian Jira Service Management incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 7, 2026Performance and access related issues with JiraOn August 7th - 2026, between 10:27 UTC to 11:49 UTC, some users in the Central European region may have experienced service access issues. The issue has now been resolved and the service is operating normally for all…1h 21mResolved
Aug 7, 2026Degraded performance of JIRAOn August 7, 2026, JIRA, JWM, and JSM users may have experienced performance degradation when viewing issues and boards. The issue has now been resolved, and the service is operating normally for all affected customers.13 minResolved
Jul 21, 2026Voice call failures for some India based numbersOur notification provider has identified the root of the issue that is causing voice call failures to some India-based mobile numbers. We understand the inconvenience this may cause and appreciate your patience while…75h 18mResolved
Jul 20, 2026Degraded performance of Jira Automation rulesOur team has been able to validate that all rule executions are performing normally and this issue is now resolved.28h 37mResolved
Jul 20, 2026Degraded performance of Jira Automation rulesOn July 20, 2026, some Jira and Jira Service Management users may have experienced performance degradation of automation rule executions. The issue has now been resolved, and the service is operating normally for all…1h 19mResolved
Jul 6, 2026Reliability issues with Jira and Confluence## Summary On Jul 6, 2026, between 06:51 and 20:17 UTC, Atlassian customers using cloud products in European (EU) regions experienced service disruptions affecting automation rule execution, user search, user picker…3h 40mResolved
Jun 19, 2026Jira : Incoming emails partial outageOur team has proactively reached out to all impacted organizations providing the below instructions to re-authorize their Microsoft mail server. If you are still experiencing this issue, please attempt to complete the…150h 26mResolved
Jun 10, 2026Unable to load Assets pageOn June 10 2026, between 08:10 and 09:08 UTC, users experienced degraded performance and inability to load the Assets page, which is impacting the ability to create, update, and delete assets. We have implemented a…17 minResolved
Jun 10, 2026Delays in processing incoming Emails, Work Item notifications, and Scheduled Triggers in Marketplace AppsWe are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.1h 35mResolved
Jun 9, 2026Some users experiencing issues viewing boards and work itemsThe issue has now been resolved, and the service is operating normally for all affected customers.12h 58mResolved
Jun 8, 2026Users experiencing issues loading work items in Jira and JSMOn June 08 2026, between 01:30 and 02:40 UTC, users experienced degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions. We have implemented…1h 2mResolved
Jun 2, 2026Degraded performance of Jira and JSM automations in US EastOn June 2, 2026, some Jira and Jira Service Management users in the US-East region may have experienced performance degradation of automation rule executions. The issue has now been resolved, and the service is…1h 18mResolved
Jun 1, 2026For Jira-software viewIssues and viewBoard are degraded**SUMMARY** On June 01, 2026, between 06:54 and 08:28 UTC, Atlassian customers using Jira, Jira Service Management, and Jira Work Management were unable to view issues, boards, and backlogs, and experienced errors…5h 17mResolved
May 14, 2026Users experiencing issues accessing multiple Atlassian products### Summary On May 14, 2026, between 04:30 and 05:26 UTC, Atlassian customers experienced widespread service disruption across multiple Atlassian Cloud products. The issue was caused by a race condition in our internal…1h 44mResolved
May 14, 2026Excessive notifications being received by some Jira Service Management usersThis incident has been resolved. During the incident window, some customers using Atlassian Assist experienced excessive notifications as our team replayed delayed events caused by this prior…8h 26mResolved
May 13, 2026Automations within Jira, Jira Service Management and JSM Assist experiencing delays for some users### Summary ### On May 12, 2026 between 19:01 and 20:46 UTC, a subset of Atlassian customers may have experienced delays in background operations and automation processes. Some background operations, such as…8h 21mResolved
May 8, 2026Multiple Atlassian services are experiencing issuesAll dates and times below are in UTC unless stated otherwise. ### Summary On May 8, 2026 between 00:22 and 06:08, one of our hosting providers suffered a significant incident in a specific availability zone in…18h 13mResolved
May 6, 2026Lookup Objects in Automation for Jira Service Management are not functioningThe 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.1h 41mResolved
May 2, 2026The Work Item view experience of Jira is restored### SUMMARY ### Between May 1, 2026 at 23:34 UTC and May 2, 2026 at 02:53 UTC Atlassian customers using Jira and Jira Service Management (JSM) across all Cloud tenants received an error page when attempting to open…1h 52mResolved
Apr 14, 2026Disrupted Rovo availability for Automation rulesOn April 14, 2026, affected users may have experienced some service disruption with automation rules that use Rovo agents. The issue has now been resolved, and the service is operating normally for all affected…3h 58mResolved
Apr 13, 2026Users experiencing issues with login across Atlassian products### Summary On April 13, 2026, between 05:49 and 06:29 UTC, customers experienced failures when attempting to log in, sign up, reset passwords, and complete multi-factor authentication flows across Atlassian cloud…2h 47mResolved
Apr 8, 2026Multiple products impacted by search failures### Summary On April 8, 2026, between 04:46 UTC and 12:09 UTC, search functionality was unavailable or degraded across several Atlassian Cloud products, including Jira, Confluence, Jira Service Management, Rovo, Rovo…5h 18mResolved
Mar 18, 2026Automations aren't triggering on work item creation, field updates, or comment additions### Summary On March 18, 2026, between 10:06 and 13:47 UTC, customers experienced delays in Automation rules executing when triggered by Jira events such as Work Item creation, Work Item updates, and comments…16h 35mResolved
Mar 10, 2026Automation events delayed for some customers in the APAC regionOn 9 March UTC, Automation users in the APAC region may have experienced performance degradation within Jira, Jira Product Discovery, Jira Service Management, Jira Work Management, Confluence. The issue has now been…52 minResolved
Feb 26, 2026Atlassian Assist in Jira Service Management is currently unavailable.On February 26, 2026, JSM experienced a disruption, and Atlassian Assist service was unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.5h 33mResolved
Feb 20, 2026Degraded performance of Cloud Products when selecting users or teamsThis issue has been resolved and all services are functional.9h 33mResolved
Feb 6, 2026Disrupted JIRA and JSM availabilityOn February 6, 2026, JIRA and JSM experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.9h 13mResolved
Feb 6, 2026Users incorrectly moved from Free to Standard Service Collection Trial accountThe team has verified that the fix has successfully propagated to all accounts. Impacted customers will receive an email follow-up containing additional information.18h 14mResolved
Feb 5, 2026Some users in us-east-1 region unable to access Jira and JSM.On February 5, 2026, JIRA and JIRA Service Management experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected…7h 25mResolved
Jan 28, 2026Degraded performance of Jira, JPD, and JSM in eu-west-1On Jan 28, 2026, Jira, Jira Product Discovery, and Jira Service Management users in eu-west-1 region may have experienced delays in viewing recently submitted updates on the web page and/or mobile apps. Updates…1h 30mResolved
Jan 27, 2026Assets intermittently unavailableDeployment of the fix is completed and services are back to normal. This issue is resolved.42 minResolved
Jan 22, 2026JSM Asset not loadingOn January 22, 2026, affected Jira Service Management users may have experienced some service disruption where assets were not loading, affecting their interactions with service management functionality. The issue has…2h 2mResolved
Jan 20, 2026Issue affecting AssetsOn January 20, 2026, some customers may have experienced performance degradation of Assets. The issue has now been resolved, and the service is operating normally for all affected customers.3h 58mResolved
Jan 6, 2026Disrupted Automation for Jira triggers not running for some customersRerunning the remaining Automation for Jira rules that failed for affected customers is complete. This update resolves the issue.30h 14mResolved
Dec 27, 2025Outbound Email, Mobile Push Notifications, and Support Ticket Delivery Impacting All Cloud Products### Summary On **December 27, 2025**, between **02:48 UTC and 05:20 UTC**, some Atlassian cloud customers experienced failures in sending and receiving emails and mobile notifications. Core Jira and Confluence…2h 32mResolved
Dec 15, 2025Degraded performance of Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, and RovoOn December 15th, 2025, Admin Hub, Atlassian Analytics, Confluence Cloud, Ecosystem, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo users in the prod-us-east region may have experienced…2h 45mResolved
Dec 5, 2025Linked worked item functionality is broken, if the work item contains an attachment.On December 5th, 2025, Jira Service Management users may have experienced an error when creating linked work items that included an attachment. The issue has now been resolved, and the service is operating normally for…2h 16mResolved
Dec 1, 2025Degraded Performance for Some Jira UsersImpact Jira Software users experienced degraded performance affecting their ability to view issues and boards. Users may have encountered an error or slowdown during this time. Current Status The situation is…1h 0mResolved
Nov 21, 2025Multiple Atlassian services experiencing degraded performance### Summary On November 21, 2025, between 13:44 and 15:16 UTC, Trello customers were intermittently unable to view and update data on their boards. Customers also may have experienced issues authenticating with…1h 54mResolved
Nov 18, 2025Customers are receiving message NO SUCH TRACK intermittently when opening Jira issuesOn November 18, 2025, some Jira Service Management users may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.2h 45mResolved
Nov 15, 2025Some users are unable to send emails from JiraThe issue has been resolved. All systems are healthy and fully operational, with no further problems observed in sending emails from Jira.43h 20mResolved
Nov 3, 2025Degraded performance and intermittent errorsOn November 3, 2025, some Confluence, Jira Service Management, and Jira Cloud users may have experienced performance degradation and errors in the Global Automation UI page. Automation executions were not impacted by…1h 57mResolved
Oct 31, 2025Automation rule conditions order change is affecting customersConfirmed that the incident has been resolved and the automation rules are executing as expected.2h 14mResolved
Oct 29, 2025Degraded performance of Atlassian cloud sites for some customersIncident has been resolved.19h 22mResolved
Oct 27, 2025Jira Platform Incident - viewIssue and createIssue Service DisruptionBetween 15:09 UTC to 17:16 UTC, some customers experienced partial outage for Jira Work Management, Jira Service Management, and Jira viewIssue, createIssue and editIssue caused by a faulty code rollout. We have…1h 16mResolved
Oct 27, 2025Some users experiencing 'Something went wrong error' message in Jira and JSMOur team identified a problematic feature release that was causing the 'something went wrong' errors to appear within Jira and Jira Service Management. We disabled the feature that was causing this issue and normal…22 minResolved
Oct 22, 2025Delay in execution of Automation rulesOur teams have identified and fixed the root cause of the issue that caused delay in executing Automation rules. This was caused due to scaling issues following on from the recent AWS outage. This issue is marked as…0 minResolved
Oct 20, 2025Atlassian Cloud Services impacted### Postmortem publish date: Nov 19th, 2025 ### Summary All dates and times below are in UTC unless stated otherwise. Customers utilizing Atlassian products experienced elevated error rates and degraded performance…21h 28mResolved
Oct 15, 2025Unable to perform UI OperationsBetween 14:00 UTC to 16:00 UTC, we experienced automation rule functionality degradation for Confluence, Jira Work Management, Jira Service Management, and Jira. Impact Some customers using Jira, Confluence, and Jira…2h 32mResolved
Sep 30, 2025Delays in Opsgenie, JSM Ops and Compass Ops notificationsBetween 13:10 UTC to 14:00 UTC, we experienced notification delay for Jira Service Management, Opsgenie, and Compass in only EU-region. The issue has been resolved and the service is operating normally.25 minResolved
Sep 22, 2025Degraded performance to multiple Atlassian experiences### **SUMMARY** On September 22, 2025, between 04:38 and 04:48 UTC, Atlassian customers experienced connection errors preventing access to their [atlassian.net](http://atlassian.net/) sites. Some customers observed…1h 38mResolved
Sep 19, 2025JSM Customer Organizations Page is throwing errorsWe've rolled out a fix, and Organizations page is back to normal operations now.74h 8mResolved
Sep 11, 2025Duplicate issues being created in Jira Service Management and JiraOur team has completed restoration of customer environments for the vast majority of those impacted by this issue. We will continue working with the final impacted customers to ensure we reach a full resolution. If you…301h 41mResolved
Sep 11, 2025Duplicate issues being created in Jira Service Management and JiraDuplicated message. Please refer to the updates from this incident: https://jira-software.status.atlassian.com/incidents/knx11cj542ks3 minResolved
Sep 10, 2025Delays observed at JSM, Opsgenie and Compass alert search functionality in US Region### **SUMMARY** Between September 10, 2025, at 13:56 UTC and September 11, 2025, at 14:40 UTC, Jira Service Management, Compass Cloud Operations, and Opsgenie customers in the U.S. region experienced degraded…27h 21mResolved
Sep 9, 2025Degraded performance in Confluence and Jira for Microsoft Edge usersAn update has been released by Microsoft to resolve this issue for users of the Edge browser. To verify that you are running the required version of Edge, you can navigate to edge://components/ in the address bar, click…140h 16mResolved
Sep 8, 2025Disappearing 'account' filed for Tempo usersOur team is now satisfied that the issues relating to these missing fields are now resolved.13h 44mResolved

How to Read This Atlassian Jira Service Management Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Atlassian Jira Service Management acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Atlassian Jira Service Management outage in this window ran 12d 13h, against a mean recovery of 19h 25m. If you depend on Atlassian Jira Service Management in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.