Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

Day 7 of the great Atlassian outage: IT giant still struggling to restore access

Majority of affected users still wondering where their data went

The great Atlassian outage is stumbling into a new week, with the biz reporting it has "rebuilt functionality for over 35 percent of the users who are impacted by the service outage," meaning the majority of those afflicted remain unable to access their sites.

At this point it is fair to say the problem is severe. It kicked off on 5 April and the IT giant said that while it was "running a maintenance script, a small number of sites were disabled unintentionally".

Atlassian reported in a status update this morning that: "The rebuild stage is particularly complex due to several steps that are required to validate sites and verify data." This will be of little comfort to the 65 percent of affected customers wondering if signing up for Atlassian's cloud was such a good idea after all.

We suspect that the "dedicated team" Atlassian assigned to sorting out the problem has yet to take down the bunting from World Backup Day before the incident occurred.

Jira Software, Jira Work Management, Jira Service Management and Confluence are the biggest segments still affected at the time of publication. Confluence is a web-based corporate wiki and Jira is more about issue tracking. Jira Work Management is aimed at generic project management while Jira Service Management turned up last year as part of a vision to turn agile and DevOps principles to the IT service desk.

The irony of the latter collapsing into a heap due to an issue with a maintenance script will not have been lost on the affected users.

Also still on the broken list is IT incident-monitoring service, OpsGenie (acquired in 2018) and Atlassian's Statuspage incident communication service – again, the irony meter has gone off the scale.

To be clear, only a very small proportion of customers have been affected; on Friday we were told the figure was around the 400 mark. Still, we suppose being one of those 400 hasn't exactly been fun.

The Register contacted Atlassian to get more information and an ETA for when the rest of the data will be recovered. We will update should the company respond. ®

More about

More about

More about

TIP US OFF

Send us news


Other stories you might like