Jira Software Outage History

An outage affected Jira Software Marketplace, causing error messages such as 'something went wrong' or 'Hash MHHY91' when users tried to access third-party apps. The issue disrupted access to app integrations and affected workflows relying on Marketplace functionality. The outage began at Sep 4, 2025 12:54 AM UTC and was resolved by Sep 4, 2025 3:14 PM UTC, lasting about 14 hours and 20 minutes. The Jira Software team issued two status updates during the incident, outlining ongoing investigation and eventual restoration of Marketplace services.

Jira Software Kanban boards loading issues briefly disrupted board access for some users, with errors such as 'Something went wrong' when loading Kanban boards. The problem affected two components—Create and edit and Viewing content—causing degraded experience while loading boards. The incident began around 4:17 AM UTC and Jira raised a warning at 4:19 AM UTC; the status returned to normal by 4:49 AM UTC. The provider posted two status updates during the event.

Jira Software experienced a data handling issue on the Global Issue Create Screen where values typed into Forge app-created custom fields could disappear when focus moved away. Although the UI sometimes showed the field as blank, the data was still stored in the backend, which caused confusion during issue creation. The Create and edit component was the primary area affected, and the status page provided a workaround to proceed with Create by ignoring the missing visible data and submitting anyway. The incident began on 10:30 PM UTC and progressed toward remediation.

The incident began on 10:30 PM UTC and was resolved by 12:19 PM UTC, lasting about 13 hours and 49 minutes, during which the Jira Software status page issued 2 updates detailing investigation and remediation steps. The impact was limited to the Create and edit component and Forge app custom fields on the Global Issue Create Screen.

Jira Software experienced a brief issue where product invitation emails were not delivered to users. In-product invitations remained functional and other Jira features were unaffected. The incident began at Aug 5, 2025 4:24 AM UTC and was resolved by Aug 5, 2025 4:29 AM UTC, lasting about 5 minutes. The impact was isolated to email delivery for invitations and affected the Administration component.

Jira Software reported an issue where product invitation emails were not being correctly sent to users. Invitations within the product still succeed, but email notifications for invitations were impacted. The outage began at 11:45 PM UTC and was resolved by 4:19 AM UTC, lasting about 4 hours and 34 minutes. The Administration component showed a degraded state during the incident and returned to normal after resolution. The status page issued 2 updates during the incident.

This primarily affected email delivery for invitations; users relying on email invitations may have experienced delays or missing emails, while in-app invitations remained functional.

Jira Software users experienced a degraded experience when attaching files or accessing existing media content in issues, affecting two components: Viewing content and Create and edit. The incident was first acknowledged as under investigation at Jul 30, 2025 7:02 AM UTC and transitioned to a degraded state at Jul 30, 2025 7:04 AM UTC. The outage lasted for about 1 hour and 16 minutes, with service returning to normal by Jul 30, 2025 8:20 AM UTC.

The Jira Software status page outlined the investigation and subsequent restoration as the issue progressed, noting that attachments and media access were degraded and that affected components returned to normal with the resolution.

Jira Automation for Jira experienced degraded performance affecting automation rule execution for Jira Service Management and Jira Cloud customers. The issue began at 3:34 PM UTC when the Automation for Jira component was listed as degraded, with the status page noting investigation into delays in automation rule execution.

The problem was resolved by 6:44 PM UTC, lasting about 3 hours and 10 minutes. The Jira Software status page later returned the Automation for Jira component to the normal state, with updates communicating recovery progress and the incident affecting a single component.

Jira Software experienced a brief partial outage that prevented some users from loading Jira pages such as Your Work, Projects and Settings. The incident began on 1:29 AM UTC and was resolved by 2:05 AM UTC, lasting roughly 36 minutes, with the Viewing content component listed as degraded during the outage. The Jira Software status page indicated an investigation and posted updates as the situation developed.

An incident involving Forge app invocation caused intermittent errors for Jira Cloud customers, affecting Confluence, Jira Work Management, Jira Service Management, Jira, and Compass Cloud. Users may have seen errors in app functionality and some scheduled triggers or smart links not executing during the affected window. The issue was observed from 5:44 AM UTC to 7:44 AM UTC and mitigations were put in place as investigations continued, with errors receding over time. The service was monitored for resolution and were restored in due course.

Jira Software experienced brief degraded performance in Atlassian Administration when the Administration component moved to a degraded state at 9:39 AM UTC. Users encountered errors loading Users and Groups pages in Atlassian Administration, and there were problems with user IDP syncing. The incident affected admin workflows and identity-related configuration, and the status returned to normal at 11:04 AM UTC.

The Jira Software status page issued 2 updates during the event, first acknowledging the investigation and degraded functionality and later confirming restoration. The outage lasted approximately 1 hour 25 minutes.