Jira Software Outage History

Jira Software experienced a 13-hour major incident where some users encountered intermittent errors and degraded performance when viewing boards and work items in Jira Service Management and Jira Cloud. The team identified the root cause and applied a progressive fix that restored normal operations for all affected customers. The service was fully resolved and returned to normal functionality.

Jira Software experienced performance degradation affecting front-end experiences including view board, navigation, and backlog functionality across multiple regions for 1.1 hours. The incident impacted core components including viewing content, create/edit functions, authentication, search, and administration features. Engineering teams identified the root cause and worked on a resolution while the service was classified as having minor impact.

Jira Software experienced a major incident where users in some regions were unable to load work items across Atlassian products. The issue affected viewing content and create/edit functionality. The incident lasted 9 minutes and was resolved while the team was actively investigating the problem.

Jira and Jira Service Management customers in the US-East region experienced performance degradation with automation rule executions, causing delays in rule processing. The incident affected the Automation for Jira component and lasted 1.3 hours before being resolved. Previously delayed automation rules were expected to complete within 12 hours of the resolution.

Jira Software experienced a 5.8-hour major incident affecting users in the EU region, with degraded performance across multiple components including issue viewing, boards, authentication, search, and mobile access. Users encountered 5XX errors when trying to access issues, boards, and navigation features. The engineering team deployed a fix to resolve the performance issues and prevent recurrence.

Jira Software experienced an issue where Forge custom fields were not getting created on work items pages after deploying applications. The problem affected only new deployments with Forge custom fields, while existing deployments continued to function normally. The root cause was identified and a fix was deployed, restoring full service after 5 hours.

A major incident affected multiple Atlassian products including Jira and Confluence Cloud, impacting users' ability to access and use core functionality such as viewing content, authentication, search, notifications, and administration features. The outage lasted 1.9 hours, with Atlassian identifying the root cause and implementing a mitigation that restored service across all affected products. All services were fully recovered and the incident was resolved after a monitoring period to ensure stability.

Jira Software experienced an 8.4-hour incident where automation events in Jira, Jira Service Management, and JSM Assist were delayed by multiple hours for some users. The incident response team identified the root cause and implemented a fix, first restoring normal processing for new automation events, then working through the backlog of delayed historical events. All services were fully restored and all delayed automation events were successfully processed.

Multiple Atlassian services experienced elevated error rates and degraded performance for 18.3 hours due to a public cloud provider infrastructure outage. The incident affected core functionality including content viewing, editing, authentication, search, notifications, administration, marketplace, mobile access, purchasing, and automation features across Atlassian products. The underlying infrastructure issue was mitigated and services were restored, with teams subsequently clearing backlogs of queued events for notifications, automation triggers, and data syncs.

Jira Software experienced a major incident where users were unable to log time while on business boards, affecting the create and edit functionality. The engineering team identified the root cause and deployed a fix to resolve the issue. The incident lasted 3.4 hours and service was restored to normal operation for all affected customers.