194 years of downtime: looking back on incident data from 2018

[#1]

Statuspage customers logged more than 194 years of collective incidents in 2018. That’s a whopping 87% increase from the 104 years logged in 2017, and we aren’t even through December yet.

Open incident communication is becoming more and more important to companies and their customers. This is underlined by the big names who have set up a public Statuspage this year like Github, LinkedIn, and Yelp. With more focus on incident communication comes more focus on incident management in general. Companies are spending more time and resources preparing for downtime, as we learned from a handful of customers we profiled on how they prepare for high traffic days.

We dug deeper into our 2018 data to get a better idea of when and how our customers communicated around downtime this year. The data represents all reported incidents – from small blips in service to large-scale outages – plus any planned downtime logged through scheduled maintenance.

📚Read the full report on the Atlassian Blog

🗣Comment with something your team learned from an incident in 2018 and we'll send you a free #HugOps poster to display in your workspace in 2019. 

[Gonchik Tsymzhitov]

Hi!

Thanks for wonderful report!

Just curious, how many customer status pages have been used for a report?
Just interesting avg of the downtime, avg maintenance of the period for a per system in one year.

Cheers,
Gonchik Tsymzhitov

[Shannon Winter]

Thanks @Gonchik Tsymzhitov! So glad you like it. We have thousands of customers and it's holistic view of incidents and scheduled maintenance across all of their pages.