Atlassian’s cloud outage which started on 5th April is set to go on for another 2 weeks.
The collaboration software solution experienced an outage of its Confluence and Jira products from 5th April which affected nearly 400 customers. Although the outage affected all customers, it arrived at a very tricky time.
It came when the company was hosting its Team’22 event in Las Vegas, where it was showcasing its new products.
What is Atlassian doing to fix the outage?
The recent outage has primarily affected the company’s Jira Software, OpsGenie, Work Management, Service Management, and Confluence services.
At the moment, the outage has had a knock-on effect on the Atlassian Developer service, making it impossible for users of the service to update the details of their account for five days as Atlassian’s entire focus is on fixing the outage.
Until today, the company has not been very vocal about the ongoing outage apart from a three-tweet thread that attributes the outage to a maintenance script. In the Twitter thread, the company also issues an apology and promises its customers that it is mobilizing hundreds of engineers.
The firm has gone public with a LinkedIn post after services for some customers were restored.
The post explained what was the root cause of the problem stating that the outage has affected around 400 customers.
It said that during the scheduled maintenance, the company’s team ran a script to get rid of legacy data from a deprecated service. However, things did not go according to plan as the script unexpectedly deleted websites, connected users, products, and third-party applications.
Atlassian clarified that the outage was not due to a cyber attack and there was no breach of customer data. Besides, since all the data was backed up, there was no loss of data.
The post also says that the outage is “unacceptable” and that the company is directly communicating with every customer with complete transparency on the length of the outage.
Atlassian has said that the issue which has been going on for a week will be fixed in the next couple of weeks.
Feature Image: Atlassian