Jira Software Outage History

Jira Software experienced a cloud outage that prevented users from opening Jira cloud products, affecting 11 core components across the Jira Cloud suite, including Mobile, Viewing content, Create and edit, Administration, Search, Authentication and User Management, Notifications, Marketplace, Purchasing & Licensing, Signup, and Automation for Jira. Users attempting to access Jira Cloud features likely experienced failures or delays.

According to Jira's status page, the incident began at Jun 24, 2025 12:04 PM UTC and was resolved by Jun 24, 2025 1:39 PM UTC, lasting about 1 hour 35 minutes. The provider issued two status updates during the incident as they investigated and restored services. The outage appeared global, with widespread impact across Jira Cloud products and features.

During the incident, Jira Software experienced a brief outage affecting the ability to attach files to work items. Users saw errors such as 'The following files have failed to upload' when uploading attachments, while attaching files in a comment remained functional. The issue affected two components, Viewing content and Create and edit, and lasted about 50 minutes, starting at 3:09 AM UTC and ending at 3:59 AM UTC. The Jira Software team published two status updates during the incident, including an initial investigation notice at 3:05 AM UTC and a follow-up confirming resolution. No user-facing work items were permanently disrupted after recovery.

From 8:09 AM UTC to 12:40 PM UTC, Jira Software reported intermittent failures loading the child work item panel for Jira Work Management, Jira Service Management, and Jira Cloud customers. Users attempting to view or expand related child items could experience delays or errors, impacting navigation and visibility of related work items. The issue concerned the Viewing content component and prompted engineers to investigate the root cause. The incident lasted about 4 hours and 31 minutes and included two status updates from Jira.

Jira Software experienced delays in delivering emails from Jira Automation, JWM, and JSM automations, affecting automated email notifications for some users. The incident began at Jun 13, 2025 5:44 AM UTC and was resolved by Jun 13, 2025 7:14 AM UTC, lasting roughly 1 hour and 30 minutes. The issue was associated with the Automation for Jira component, which showed email delivery delays during this period.

The provider issued two official status updates during the incident, with the Automation for Jira component moving from up to warn and then back to up as the issue was resolved. No broad regional pattern was reported, and the outage did not indicate a system-wide failure.

Jira Software experienced a brief disruption affecting Jira search pages due to timeouts in the Search component. The incident began around 11:50 PM UTC with investigators flagging timeouts, and the status page updated to warn at Jun 11, 2025 11:54 PM UTC. The issue lasted about 30 minutes and was resolved by Jun 12, 2025 12:24 AM UTC when the Search component returned to normal. The Jira status page published two updates during the incident, outlining the investigation and restoration.

Jira Software users in the Singapore region were affected by Forge invocation errors that impacted a subset of Marketplace apps for Confluence, Jira Service Management, and Jira, as well as Atlassian Developer Cloud customers. The outage began on 9:44 PM UTC and was resolved by 10:39 PM UTC, lasting about 55 minutes. The issue degraded Marketplace functionality and Forge invocations for affected instances.

The Atlassian status page indicated the problem as a marketplace issue with investigation ongoing, then moved back to normal as the service recovered. The incident involved the Marketplace component and was geographically confined to the Singapore region, with no broad global impact reported. The provider issued two status updates during the incident.

An outage in Jira Software's outbound email system caused delays and failures in receiving email notifications across Atlassian products, including Confluence, Jira Work Management, Jira Service Management, Jira, Opsgenie, Trello, Bitbucket, Jira Align, Jira Product Discovery, Atlas, Compass, Loom Cloud, and more. The Notifications component entered a degraded state starting at 5:19 PM UTC, with mail processing reported as normal by 4:45 PM UTC; the incident was resolved by 5:59 PM UTC. The provider issued 2 status updates during the event, noting degraded email delivery and later restoration. The outage lasted about 40 minutes and affected email-based notifications across Atlassian services.

Jira Software experienced a brief outage affecting the Administration area, with users seeing 403 errors when attempting to reach Administration. Administrative access was unavailable during the incident, impacting Jira admins and workflows relying on admin controls. The issue began at 6:54 AM UTC and was resolved by 7:34 AM UTC, lasting roughly 40 minutes. The Jira status page posted two updates during the event, first noting the Administration issue and later confirming restoration as the component returned to normal operation.

Jira Software experienced a brief authentication outage that prevented users from signing in and produced 503 gateway error messages. The Authentication and User Management component was affected, causing login interruptions across Jira Software services.

The outage began on May 26, 2025 5:19 AM UTC and was resolved by May 26, 2025 6:00 AM UTC, lasting 41 minutes. The provider issued 2 status updates during the incident, and authentication services returned to normal after the outage.

Jira Software and Jira Cloud products were degraded across all services, affecting Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. Users likely faced slower responses, timeouts, or intermittent access issues as the incident unfolded. The outage began on 2:14 PM UTC and was resolved by 12:44 AM UTC, lasting approximately 10 hours and 30 minutes.

According to Atlassian's Jira status page, the incident started with an investigation into degraded performance across all Jira products and impacted 12 components, including Administration, Viewing content, Create and edit, Marketplace, Notifications, Automation for Jira, Authentication and User Management, Search, Mobile, Purchasing & Licensing, and Signup. The status returned to Up on May 21, 2025 12:44 AM UTC after two updates were issued during the incident.