{"id":2734,"date":"2022-04-29T07:11:58","date_gmt":"2022-04-29T07:11:58","guid":{"rendered":"https:\/\/gitprotect.io\/blog\/?p=2734"},"modified":"2026-03-11T07:59:20","modified_gmt":"2026-03-11T07:59:20","slug":"was-the-jira-outage-the-last-atlassian-problem","status":"publish","type":"post","link":"https:\/\/gitprotect.io\/blog\/was-the-jira-outage-the-last-atlassian-problem\/","title":{"rendered":"Was the Jira Outage the Last Atlassian Problem?"},"content":{"rendered":"\n

A month ago it was impossible to imagine that hundreds of customers could lose access to such apps as Jira. What is more, it was absolutely unacceptable to think that the outage could last for almost three weeks. However, as the practice shows, everything can happen. So, let\u2019s look in detail at the problems which customers had to face when Atlassian was overcoming its greatest Jira outage<\/strong>. <\/p>\n\n\n\n\n\n\n\n\n\n

April\u2019s Jira outage – what was going on? <\/h2>\n\n\n\n

On the first day, when the Jira outage happened nobody knew for sure how long it could last and the Atlassian engineers had been releasing the same message on their Jira Software Status<\/a> \u201cWe continue to work on the defined processes to the resolution of the issues impacting some customers\u201d <\/em>with no explanations for almost eight days. On the ninth day, Atlassian finally sent emails to their customers that they weren\u2019t able to restore the services at that moment but they were working and they needed up to 2 more weeks to solve the problem. Let\u2019s repeat – 2 MORE WEEKS – how this will impact your team?<\/p>\n\n\n\n

The impact on customers. Was it disastrous? <\/h2>\n\n\n\n

But what about Jira customers? Did they suffer from the Atlassian outage? Unfortunately, yeap. About 400 customers lost their connection during this Jira outage while Atlassian engineers were trying to fix the problem<\/strong>. Companies had to put up with the consequences as many of them didn\u2019t back up their sites. Some of them were trying to use the Service Management tool for their helpdesk, which meant that their helpdesk wasn\u2019t working during this Jira outage. Moreover, some companies had nothing to do but delay, reschedule, and re-plan their projects, which, of course, brought them a lot of financial inconveniences and a reputation loss. <\/p>\n\n\n\n

<\/div>\n\n\n\n
\n\n\n\n

Jira down? Get your team back to tasks within minutes with the first professional backup for Jira<\/strong> Cloud, Jira Service Management, and Jira Work Management.<\/p>\n\n\n\n

\n
Sign up now<\/a><\/div>\n<\/div>\n\n\n\n
\n\n\n\n
<\/div>\n\n\n\n

What was the problem which lead to the longest Jira outage? <\/h2>\n\n\n\n

But let\u2019s get back to the problem of this Atlassian outage that lasted for almost two weeks<\/strong>. As it turned out, according to the Atlassian engineer, Sri Viswanath\u2019s explanation-post<\/a>, the Jira outage happened because of a human mistake. Well, we are all people and such a thing can happen, so it\u2019s always better to keep in mind a backup plan. While the engineers were updating the app with the code, something went wrong. As it turned out due to the lack of communication between the teams, which were in charge of the process \u201dThe script was executed with the wrong execution mode and the wrong list of IDs. The result was that sites for approximately 400 customers were improperly deleted\u201d<\/em> he explained. <\/p>\n\n\n\n

As it was hard to restore all the sites automatically in a bulk, the engineers had to make a number of steps which, obviously, took time. The restoration process was semi-automated and they needed to restore some customer data manually for each site. Once again, restore websites one by one manually!<\/p>\n\n\n

\n
\"Get<\/a><\/figure><\/div>\n\n\n

Are there any other threats? <\/h2>\n\n\n\n

After such a massive Atlassian outage customers probably started to think if there is any other threat to their websites<\/strong>. So, recently, according to the information taken from Bleeping Computer<\/a>, Atlassian has informed their Jira and Jira Service Management customers that a critical authentication bypass vulnerability in Seraph<\/strong>, which is a security framework for Atlassian web application, has affected their products.  It means that there is no proper protection for customers\u2019 login and logout requests and an attacker can remotely send a hack HTTP request to vulnerable computers and bypass authentication. That\u2019s why Atlassian advises their customers to update their products to the versions that include this security protection. <\/p>\n\n\n\n

Can situations like that be prevented? <\/h2>\n\n\n\n

Definitely, yes! The answer to this question is backup, as it is always the best solution to eliminate the negative effects of outages, security flaws, human errors, or cyberattacks. In the situation with the Jira outage, if users had a backup plan, they could continue their work almost without noticing the problem. All they needed to do is to restore their entire Jira environment to the new account, which would take them only a few minutes, and continue their work peacefully. <\/p>\n\n\n\n

\n