Jira Software Outage History

Jira Software experienced degraded performance across a broad set of Atlassian cloud services beginning at 4:19 PM UTC, affecting Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo. Users likely encountered slower load times and reduced responsiveness across these apps and dashboards. The incident lasted about 2 hours and 45 minutes, with the status returning to normal by 7:04 PM UTC. The Jira status page issued two updates during the incident, noting ongoing investigation and eventual recovery for the affected Create and edit component, with overall service resumed to the up state.

Jira Software experienced degraded performance affecting Jira Work Management, Jira, and Jira Service Management, with users reporting slow access when viewing issues and boards. The degradation began at Dec 1, 2025 5:24 PM UTC and was resolved by Dec 1, 2025 6:29 PM UTC after Atlassian posted two updates indicating investigation and restoration of normal operation. The Viewing content component across these Jira products was affected.

An outage affected Jira Software and multiple Atlassian services, impacting 12 components including Notifications, Viewing content, Search, Create and edit, Authentication and User Management, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, and Automation for Jira. Users could have experienced degraded performance across projects, notifications, content access, search results, and authentication during the incident. The outage began at 2:59 PM UTC and was resolved by 4:14 PM UTC, lasting about 1 hour and 15 minutes. Atlassian issued two status updates during the incident as they investigated and worked to restore services.

Jira Software experienced a degraded issue affecting Forge Custom Fields on the Issue Create Screen, causing selected field values to be lost after submission. This disrupted creating or editing issues and could require re-entering data. The issue affected the Create and edit component.

The incident began at Nov 20, 2025 7:00 AM UTC and was fully resolved by Nov 20, 2025 9:49 PM UTC, spanning roughly 14 hours and 49 minutes. A degraded period started at Nov 20, 2025 8:34 PM UTC when Jira's status page listed the issue and issued 2 updates before recovery. The status page indicated that the root cause had been identified and a fix was being deployed.

Jira Software experienced an intermittent NO SUCH TRACK error when opening Jira issues, degrading the ability to view and edit issues and impacting multiple related features. The issue affected 12 components, including Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, and Automation for Jira. The outage began at 2:44 PM UTC and lasted until 5:29 PM UTC, a duration of approximately 2 hours and 45 minutes. The Jira Software status page issued two updates during the incident to communicate the investigation and subsequent recovery.

During the incident, the status transitioned from a normal state to degraded and then returned to normal as services were restored. The two official updates summarized the investigation and confirmation of recovery, and all affected components were brought back online following the resolution.

Jira Software experienced a partial outage affecting the email notification subsystem. Some users were unable to send emails due to timeouts when refreshing OAuth tokens from Microsoft, which impacted authentication for a subset of accounts and delayed email delivery. The incident began at Nov 15, 2025 4:29 PM UTC and was resolved by Nov 15, 2025 9:39 PM UTC, lasting 5 hours and 10 minutes. The Notifications component moved from a normal state to degraded during the event and then returned to normal as the issues subsided.

Degraded performance and intermittent errors affected some Confluence, Jira Service Management, and Jira Cloud customers. The incident began at 4:14 PM UTC when the Jira Software status moved to degraded performance and teams began investigating. Two components were affected: Viewing content and Automation for Jira. The issue persisted for about 1 hour 55 minutes and was resolved by 6:09 PM UTC, with the status returning to normal. The provider issued 2 updates during the incident.

An issue affected the Automation for Jira component, causing some automation rule conditions to not function as expected across Jira Software and Jira Service Management. Customers relying on automated workflows may have seen certain rules not fire or behave correctly. The incident began at Oct 31, 2025 2:14 AM UTC and was resolved by 4:29 AM UTC, lasting about 2 hours and 15 minutes. The Jira status page described an ongoing investigation into automation functionality and its impact on customers.

An incident caused degraded performance for Jira Software users in Australia beginning at Oct 29, 2025 6:49 AM UTC as Atlassian reported an ongoing investigation into degraded Atlassian cloud performance. The issue affected 11 Jira Software components, including Search, Signup, Automation for Jira, Notifications, Administration, Mobile, Purchasing & Licensing, Authentication and User Management, Viewing content, Create and edit, and Marketplace, resulting in slower responses and intermittent access for several hours. The regional outage lasted about 19 hours and 20 minutes, with services returning to normal by Oct 30, 2025 2:09 AM UTC.

Jira Software experienced degraded functionality affecting issue viewing (viewIssue) and creating (createIssue) across multiple regions. Users could not reliably view or create issues, with potential knock-on effects for Jira Service Management and Jira Work Management. The incident began on 4:34 PM UTC and was resolved by 5:54 PM UTC, lasting about 1 hour and 20 minutes. The affected components were Create and edit, and Viewing content.

The Jira status page described a Jira Platform Incident and ongoing investigation, and the team posted two updates during the incident as they investigated the disruption. Reporting volume from users was limited, indicating a relatively contained impact while the issue was active. The service returned to normal after the updates, with functionality restored for creating and viewing issues across regions.