Jira Software Outage History

APAC-based Jira Cloud and Confluence sites displayed a site maintenance banner affecting Confluence, Jira Work Management, Jira Service Management, and Jira Cloud customers. The outage began on Mar 19, 2025 7:49 AM UTC and was resolved by Mar 19, 2025 7:14 PM UTC, lasting about 11 hours and 25 minutes. The incident impacted 11 components across Jira Cloud offerings and Confluence.

Jira Software experienced degraded performance across multiple features, including Forge app installations via Marketplace, automation rule execution, and loading of the issue view. Users on Jira Cloud and Jira Service Management reported slower experiences and intermittent errors when installing Forge apps or running automation. The issues affected three components: Marketplace, Automation for Jira, and Viewing content. The incident began at 8:45 AM UTC and continued with degraded performance until restoration.

Timeline and response: The Jira Software status page issued four updates during the incident, describing ongoing degradation and eventual restoration. The affected components returned to normal by 5:29 PM UTC. The outage lasted approximately 8 hours and 44 minutes, from 8:45 AM UTC to 5:29 PM UTC.

Atlassian Jira automation processing experienced delays across Jira, Jira Service Management, and Confluence due to unusually high traffic. The Automation for Jira component entered a degraded state at 12:44 PM UTC, with automation rules firing but execution slowed. New events were expected to process later, potentially taking up to a day. Adjustments were made at 12:13 PM UTC to prioritize incoming events.

The incident lasted approximately 3 hours and 55 minutes, during which two official status updates were issued. The automation delays subsided and the Automation for Jira component returned to normal at 4:39 PM UTC.

Some users encountered errors when creating new Jira and Confluence sites. The Jira Software Signup component transitioned to a degraded state at Mar 14, 2025 6:54 PM UTC and was restored by Mar 14, 2025 8:49 PM UTC, with an outage duration of about 1 hour and 55 minutes. The service issued two status updates during the incident, first announcing an investigation and later confirming signup restoration. The impact was limited to new site creation, while other functionality remained available.

Jira Software users experienced degraded performance and intermittent errors affecting the Issue View across Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud. The incident began on Mar 6, 2025 4:29 PM UTC when the Jira status page first reported intermittent issues, and it persisted until Mar 7, 2025 2:49 PM UTC. During this period, users attempting to view or interact with issues faced slow loads, partial data, and failed operations within the Issue View and related content.

The Jira status page documented the event as Jira Platform Connection Errors with subsequent updates noting degraded performance in the Issue View. The outage affected 11 components, including Notifications, Mobile, Purchasing & Licensing, Administration, Marketplace, Automation for Jira, Viewing content, Authentication and User Management, Create and edit, Search, and Signup. The incident prompted three status updates as investigations progressed, and normal service resumed by Mar 7, 2025 2:49 PM UTC. The outage lasted approximately 22 hours and 20 minutes.

Jira Software users experienced intermittent failures when loading Jira reports. The issue affected the Viewing content component and disrupted reporting workflows for a subset of users.

The incident began at Mar 5, 2025 11:24 PM UTC and was resolved by Mar 6, 2025 12:10 AM UTC, lasting about 46 minutes. The Jira Software status page issued 2 updates during the outage as teams investigated and then confirmed resolution.

Jira Software experienced an outage affecting iOS users who encountered 403 errors when both IP Allowlist and App Trust Mobile Bypass were enabled. This prevented access to Jira pages on iOS devices, while Android devices could still access Jira as a workaround. A fix has been submitted to the App Store for review and is expected to become available before the end of the week.

The Jira Software status page reported a brief incident affecting iOS users where pages returned 403 errors when IP Allowlist and App Trust Mobile Bypass were both enabled. The issue began at Feb 26, 2025 5:04 AM UTC and was resolved by Feb 26, 2025 5:09 AM UTC. A fix has been submitted to the App Store and is expected to be available before the end of the week. As a workaround, users could access Jira Software from Android devices until the release is available.

The incident was short, with two official status updates posted during the event, and access returned to normal after the fix was released. The Mobile component was affected.

A broad degradation affected Jira Work Management, Jira Service Management, Jira Cloud, and Confluence, with users experiencing slower responses and intermittent issues. The incident began at 5:49 PM UTC and lasted about 1 hour and 40 minutes, with full recovery reported by 7:29 PM UTC. The initial update cited degraded performance for Jira Work Management, Jira Service Management, and Jira Cloud, and a subsequent update expanded the scope to Confluence.

Jira Cloud experienced a brief degradation, with some users reporting slow or inaccessible Jira across Jira Work Management, Jira Service Management, Jira Software, and Jira Product Discovery. The issue impacted 11 Jira Cloud 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 10:44 AM UTC and was resolved by 11:14 AM UTC, lasting approximately 30 minutes. During the incident, Jira's status page described ongoing investigation and intermittent errors, with the status page publishing two updates and services returning to full operation by the final update.