If you aren't recording and publishing incidents because you want to look good, then you are more likely to have a much bigger failure. This report raises some interesting questions, how can we measure near-misses, and can we find a better metric than Mean Time To Repair (MTTR) given the complex partial failure modes we see? I encourage everyone to publish more, include near misses in your incident reports, and to help everyone else build a safer world as a result.

The VOID report marks a remarkable advancement in how our community will look at and fix incidents moving forward. Upon seeing the emerging key findings of the report, Jeli was excited to support this research across these large datasets. Through extrapolating the key findings of the report, we are all able to build more resilient systems with greater collaboration.

The VOID Report is one of those rare and delightful moments of active thought. It takes a given subject matter, in this case claims about incidents in software, as serious and worthy of in-depth consideration. And through a close examination it finds that something doesn't quite make sense. That critique provides an opening for thought, and the sloughing off of received dogma. It's a wonderful example of critical thinking.

As SREs we spend a lot of time thinking about incidents, trying to learn from them and understand our world better. The VOID report gives us well-researched data so we can see clearer, and help our organizations learn from our peers across the industry.

The VOID report represents a great step forward for the IT industry. It is both a demonstration that numerous organizations are transforming their approach to post-incident learning, and an inspiring call for others to recognize the importance of this New Way of looking at incidents. I love the rigorous critique of MTTR, as well as the practical alternatives suggested by the report.

Reading that companies are ditching Root Cause Analysis in the same report as we get a fantastic analysis of MTTR fallacies really gave me, a professional pessimist, optimism for the future.

If you loved Accelerate and the DORA Report, this will be right up your alley: a long-overdue, open-sourced data dump of real outages. Yours. Ours. Companies big and small have contributed their outage reports to seed this repo of what really happens when things goes sideways.

The VOID report is the first industry-wide analysis of the state of software reliability today—in fact, it is the closest thing we have to a 'State of the Union' address. Everyone who designs and operates software systems should read it.

The VOID project is one of the most significant steps we can take as an industry to improve our operations and safety. This report sets up solid bases for many organizations and practitioners to turn their outage review practices towards more impactful and learning-centric views.

The VOID report is an outstanding broad view of patterns in incidents across many organizations. I'm looking forward to the database growing and lending itself to even more research and insights.

The VOID report challenges the “Old View” in what many technology organizations deem as the gold standard for incidents, such as: duration of incidents, MTTR, and Root Cause Analysis. Instead, we can embrace a “New View” that includes learning from incidents beyond just fixing them, deeper and broader incident analysis, humans as the superpower of systems, and an increased focus on successes versus failures when analyzing incidents.