Atlassian has admitted that restoring all of the services that were mistakenly disabled during recent script maintenance could take another two weeks. On April 5, 9:03 UTC, Atlassian first recognized the outage on its Status Page.
Impacted services include Jira Software, Jira Work Management, Jira Service Management, Confluence, Opsgenie Cloud, Statuspage, and Atlassian Access.
The downtime has impacted around 400 Atlassian customers or 0.18 percent of the company's 226,000 customers. Even though this only affects a tiny number of consumers, those who are affected continue to be unable to access their data.
According to them, they are trying to fix the issue but given the complexity of the rebuild process for each customer site, they cannot release exact ETA of the restoration.
Atlassian has mobilized hundreds of engineers to work around the clock to repair the outage, according to a company representative.
As fresh information becomes available, the company updates its status page every three hours. Atlassian said on April 11 that approximately 35 percent of users affected by the service outage had their functionality restored, with no data loss recorded.
Atlassian has also recommended affected customers contact support with any queries or concerns.