Do Son 
On the morning of April 16, Atlassian users began experiencing significant disruptions across several Jira products. The widely used project management tools—including Jira, Jira Service Management, Jira Work Management, and Jira Product Discovery—started generating errors and exhibiting erratic behavior. The root cause was identified as instability within Atlassian’s backend services, which the company itself classified as an “active incident.”
The outage commenced around 06:59 UTC (09:59 MSK). At that time, it was 2:59 a.m. on the U.S. East Coast, but by the time American employees began their workday, the issue had escalated into a widespread disruption. The affected products failed to load user interfaces and dashboards properly. Numerous widgets either failed to display altogether or triggered timeouts when users attempted to access core platform features.
Atlassian promptly confirmed that it had received a surge of user reports citing inability to access Jira dashboards and widgets. The company’s internal incident response team was immediately mobilized to investigate and resolve the malfunction. Status updates were regularly posted on Atlassian’s monitoring page, detailing progress across all impacted services.
The brunt of the disruption was borne by users of Jira Work Management, Jira Service Management, and Jira Product Discovery—three essential tools widely relied upon for task tracking, technical support, and ideation workflows. The outage was particularly disruptive for Agile teams, for whom uninterrupted access to task trackers is vital to daily operations.
By 12:48 p.m. Eastern Time, Atlassian reported that it had identified the root cause of the issue. However, despite the swift diagnosis, restoring full functionality took time. The company anticipated that dashboard performance would return to normal closer to 19:00 UTC.
Though some functionality has gradually been restored, users continue to report slow interface response times and unstable dashboard loading. The platform remains in a state of partial degradation, and Atlassian has yet to disclose the precise technical specifics behind the incident.
Widespread failures in Jira’s cloud services are rare, but they inevitably draw attention given the critical role these tools play in the IT infrastructure of thousands of organizations. Atlassian products are utilized not only in software development but also across marketing, operations, and customer support. As such, even a partial performance decline can have an immediate and far-reaching impact on entire departments.
At the time of publication, Atlassian had not confirmed whether a detailed postmortem would be conducted. However, the company has historically shared comprehensive analyses following the resolution of major outages.
