Jira Service Management Outage History

Impact Users of the Assets product are experiencing intermittent accessibility issues, resulting in gateway timeouts and internal server errors. These technical disruptions are causing difficulties in performing queries, which may manifest as slow performance or failure to load certain pages, particularly those involving schemas. This issue affects related features that depend on the Assets product, such as specific custom fields and automation processes. Current Status The support teams are actively working to diagnose the issue and are focused on identifying the underlying problems causing the disruption. Efforts are ongoing to restore normal service levels and minimize any further inconvenience to users. Next Steps The incident team is continuing its investigation to determine the full extent of the impact and to identify effective resolutions. Further communications will be issued in 60 minutes or when significant progress is made.

We continue to investigate the issue, and next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

We are investigating an incident affecting Jira Work Management, Jira, and Jira Service Management. We will provide updates via Statuspage shortly. The ability to view issues and boards is experiencing degraded performance for some users. Customers may notice a slowdown in accessing these functionalities.

We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

We are aware that customers are receiving message NO SUCH TRACK intermittently when opening Jira issues. Our team is investigating this issue and we will share next update in 60 mins if not sooner.

We are investigating reports of degraded performance and intermittent errors for some Confluence, Jira Service Management, and Jira Cloud customers. We will provide more details in one hour, if not sooner.

We are continuing to investigate the cause of degraded performance and intermittent errors impacting Automations and the Automation UI for some Confluence, Jira Service Management, and Jira Cloud customers. We will provide more details in one hour, if not sooner.

Jira Service Management and Jira products are currently experiencing an issue with their Automation functionality. Customers may find that some rule conditions within Automation are not functioning as expected. Our team is working diligently to identify the cause and implement a resolution. Updates with further information will be sent in 60 minutes.

We have reports of some users in Australia seeing degraded performance of Atlassian cloud. Our team is investigating this and we shall keep you informed in next 60 minutes or sooner.

Considering the complexity and intermittent nature of this issue. Atlassian team believes that further investigation of this issue is required and we will reach out to some of the impacted customers for specific information. Based on the above, we shall be able to provide further update in next 24 hours, if not sooner

Considering the complexity and intermittent nature of this issue. Atlassian team believes that further investigation of this issue is required and we will reach out to some of the impacted customers for specific information. Based on the above, we shall be able to provide further update in next 24 hours, if not sooner.

Working with our infrastructure provider, our team has been able to identify specific CDN hardware changes that were rolling out this week, and are expected to be correlated to the performance issues some customers have seen loading pages in Jira and Confluence in specific countries, including Australia, Japan, Germany, Spain, Brazil and the USA. Our provider has indicated that this rollout has now been halted indefinitely and the rollout reverted, to restore expected levels of service across all impacted countries. Our network error logging from browser data shows that this mitigation was successful, and we've now received multiple confirmations from previously impacted customers following this change that services have restored. We sincerely apologize for any inconvenience this has caused. If you are continuing to experience any issues please reach out to Atlassian Support.

Impact Jira Software users are experiencing service degradation in viewIssue and createIssue. This issue affects multiple regions, with noticeable impacts on user functionalities across these experiences. This is potentially affecting Jira Service Management and Jira Work Management. Next Steps - The team is investigating and further communications will be provided in 60 minutes.

We are aware that some customers using Jira Software or Jira Service Management are experiencing issues including 'something went wrong' errors with various functionalities such as viewing boards, issues, and creating issues. Our team is investigating with urgency and we will provide an update within an hour.

UI based Customer interactions are currently degraded and our team is actively investigating the same. We shall keep you informed of the progress in next 2 hours.

Atlassian team is actively investigating the issue with UI based Customer interactions. Existing automation rules continue to run without any issue. Accessing automation rules and creating new automation rules could lead to intermittent failures. We shall keep you informed of the progress in next 2 hours, if not sooner.

We are observing delays in Opsgenie, JSM ops and Compass ops notification flows. No alert has been lost and our team is actively working on it to mitigate the delays. We'll keep you posted with further updates.

We are investigating reports of intermittent errors on Jira Service Management Cloud customers' Organizations page. Once we identify the root cause, we will provide more details.

We are investigating cases of disappearing 'account' while trying to edit it. Account field is Tempo(Vendor) field. We are investigating the case and provide further informations

All affected fields originate from Tempo(Vendor), we are consulting it now with them.

We are continuing to investigate this issue

We are investigating cases of degraded performance for automation triggers in Jira Service Management and Jira Cloud customers. We will provide more details within the next hour.