Jira Software Outage History

Jira Software and Jira Service Management experienced a brief outage, with some users seeing a "Something went wrong" message when performing common actions such as viewing boards, issues, and creating issues. The incident affected the Create and edit and Viewing content components, causing intermittent failures for a subset of users.

The outage began at Oct 27, 2025 3:04 AM UTC and was resolved by Oct 27, 2025 3:24 AM UTC, lasting approximately 20 minutes. The Jira Software status page posted two updates during the incident: first noting an investigation into the issues, and later confirming resolution as services returned to normal.

Jira Software experienced a degradation in the Automation for Jira component, causing delays in executing automation rules and impacting automated workflows. The issue was described as a follow-on effect of the recent AWS outage. The outage began on 6:24 AM UTC and was resolved by 11:44 AM UTC, lasting roughly 5 hours and 20 minutes.

During the incident, Jira posted two official updates describing ongoing investigation and eventual restoration, with Automation for Jira moving from a degraded state back to normal as AWS-related issues were addressed.

Jira Software's cloud services experienced broad degradation, impacting 11 components including Notifications, Mobile, Purchasing & Licensing, Signup, Automation for Jira, Administration, Marketplace, Search, Viewing content, Create and edit, and Authentication and User Management. Users could encounter degraded performance or partial outages across Jira features such as creating and editing issues, searching, and signing in. The outage began at Oct 20, 2025 7:59 AM UTC and lasted about 16 hours 5 minutes, with service returning to normal by Oct 21, 2025 12:04 AM UTC.

The Atlassian Cloud Services status page documented an investigation at the outset and two official updates as the incident progressed. Report volume rose during the event, with a noticeable uptick in user reports between Oct 20, 2025 7:30 AM UTC and Oct 20, 2025 9:45 AM UTC, indicating broad impact. By Oct 21, 2025 12:04 AM UTC the issues were resolved and Jira Software components returned to normal.

The Jira Software outage began at 7:12 AM UTC and was resolved by 7:45 AM UTC, lasting 33 minutes. The incident affected Jira Software users across Europe, with login and project access issues reported from multiple countries including France, Germany, Spain and Poland.

Jira Software experienced degraded UI operations that affected UI-based customer interactions. The issue was centered on the Automation for Jira component, with users potentially encountering errors or delays when performing UI tasks. The outage began on 1:44 PM UTC and was resolved by 4:19 PM UTC, lasting about 2 hours and 35 minutes.

The Jira Software status page posted 2 official updates during the incident as teams investigated and worked toward a fix. By 16:19 UTC the status had returned to normal and UI operations were restored.

Jira Software users experienced error messages when working on issues, disrupting viewing and editing issue content. The incident began at Oct 3, 2025 9:24 AM UTC and Jira indicated an error code Hash 4G7N40 during initial investigation. It appeared to be limited to the Viewing content component.

The provider posted 2 status updates during the incident, and the service was restored by Oct 3, 2025 11:29 AM UTC. The outage lasted about 2 hours and 5 minutes, from Oct 3, 2025 9:24 AM UTC to Oct 3, 2025 11:29 AM UTC.

An incident on 4:39 AM UTC to 4:52 AM UTC caused degraded performance for Jira and Confluence cloud products due to an erroneous TLS certificate. User reports began around 4:45 AM UTC, indicating widespread impact across regions and features. Multiple components were affected, including viewing content, notifications, create and edit, search, authentication and user management, administration, mobile, purchasing and licensing, signup, and automation for Jira. The issue was acknowledged with a status update at 5:14 AM UTC and continued monitoring, with user reports and activity peaking in the early window of the incident. Recovery progressed and full restoration was reported by 6:59 AM UTC. There were two official status updates during the event.

Jira Software experienced a brief degradation caused by a code change that led to duplicate issues being created in Jira Service Management and Jira. This could have caused confusion as duplicates appeared across projects, and it affected the Viewing content component. The incident lasted about 5 minutes, from 6:49 AM UTC to 6:54 AM UTC. Atlassian reverted the code change and is preparing steps to remove the duplicates and prevent recurrence.

The issue began on Sep 9, 2025 10:23 AM UTC with degraded performance for Microsoft Edge users of Jira Software and Confluence, affecting create/edit and viewing content workflows across two components: Create and edit and Viewing content. Users experienced slower interactions and reliability issues when working with Jira Cloud and Confluence content on Edge.

An outage affected Jira Software users relying on the Tempo integration, with the Tempo 'account' field disappearing from the edit screen. This primarily impacted the Create and edit workflow, hindering users from viewing or selecting the Tempo account when editing issues. The incident began at Sep 8, 2025 10:54 AM UTC and was resolved by Sep 8, 2025 11:59 PM UTC, lasting approximately 13 hours and 5 minutes. The disruption was confined to the Tempo-related editing path while other Jira workflows remained available.