Skip to main content

One in Four Companies Never Test Their Disaster Recovery Plan

Nearly 30 percent of organizations lost business revenue due to an outage in the last 12 months

While 95 percent of organizations have a disaster recovery plan in place, 23 percent never test their plan, according to a new survey from Spiceworks.

A lack of testing and coverage gaps within disaster recovery plans may be leading to service outages in many organizations

Among those that don’t test their plan, 61 percent cited inadequate time, 53 percent cited inadequate resources, and 34 percent said disaster recovery is not a priority in their organization. The findings indicate a lack of testing and coverage gaps within disaster recovery plans may be leading to service outages in many organizations.

“Even the best laid disaster plans can go awry, especially if no one bothers to test them,” said Peter Tsai, Senior Technology Analyst at Spiceworks. “Ideally, a company’s disaster recovery plan should evolve and improve over time as weaknesses are exposed during testing and an organization’s needs change. However, the results show testing is often infrequent or not taking place at all, leaving many organizations vulnerable when disaster strikes.”

Larger Organizations Are More Likely to Experience Service Outages

In the last 12 months, 77 percent of organizations reported experiencing at least one outage (i.e. any interruption to normal levels of IT-related service). More specifically, 59 percent of organizations experienced one to three outages, 11 percent experienced four to six outages, and 7 percent experienced seven or more outages in the last 12 months.

Larger companies, which tend to rely on a greater number of services, experienced more outages than their smaller counterparts. 87 percent of large businesses large businesses with 1,000 or more employees experienced one or more outages in the last 12 months, compared to 79 percent of mid-size businesses with 100 to 999 employees, and 71 percent of small businesses with less than 100 employees.

Across all company sizes, 27 percent of organizations that experienced an outage reported losing business revenue as a result. Although 59 percent of organizations estimated losing less than $10,000 in revenue in the last 12 months, 31 percent estimated a loss of $10,000 to $100,000, and 10 percent reported losing $100,000 or more.

Power Outages and Internet Connectivity Issues Most Frequently Lead to Service Outages

The top causes leading to service outages in the last 12 months were power outages (56 percent), internet connectivity issues (48 percent), and hardware failure (32 percent), likely because less than half of organizations have backup power sources, redundant internet service providers, or high availability / failover systems in place.

Additionally, 27 percent of organizations experienced an outage due to service issues with a third-party vendor, while 21 percent experienced an outage due to human error and 13 percent due to natural disasters. Breaking down the types of natural disasters that led to outages, 29 percent were hurricanes, 16 percent were fires, 15 percent were floods, and 12 percent were due to either a tornado, animal-related incident, or blizzard.

Methodology: The survey was conducted in August 2018 and included 762 respondents from organizations across North America and Europe. Respondents are among the millions of IT professionals in Spiceworks and represent a variety of company sizes, including small-to-medium-sized businesses and enterprises. Respondents come from a variety of industries, including manufacturing, healthcare, nonprofits, education, government, and finance.

The Latest

Reliability is no longer proven by uptime alone, according to the The SRE Report 2026 from LogicMonitor. In the AI era, it is experienced through speed, consistency, and user trust, and increasingly judged by business impact. As digital services grow more complex and AI systems move into production, traditional monitoring approaches are struggling to keep pace, increasing the need for AI-first observability that spans applications, infrastructure, and the Internet ...

If AI is the engine of a modern organization, then data engineering is the road system beneath it. You can build the most powerful engine in the world, but without paved roads, traffic signals, and bridges that can support its weight, it will stall. In many enterprises, the engine is ready. The roads are not ...

In the world of digital-first business, there is no tolerance for service outages. Businesses know that outages are the quickest way to lose money and customers. For smaller organizations, unplanned downtime could even force the business to close ... A new study from PagerDuty, The State of AI-First Operations, reveals that companies actively incorporating AI into operations now view operational resilience as a growth driver rather than a cost center. But how are they achieving it? ...

In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

One in Four Companies Never Test Their Disaster Recovery Plan

Nearly 30 percent of organizations lost business revenue due to an outage in the last 12 months

While 95 percent of organizations have a disaster recovery plan in place, 23 percent never test their plan, according to a new survey from Spiceworks.

A lack of testing and coverage gaps within disaster recovery plans may be leading to service outages in many organizations

Among those that don’t test their plan, 61 percent cited inadequate time, 53 percent cited inadequate resources, and 34 percent said disaster recovery is not a priority in their organization. The findings indicate a lack of testing and coverage gaps within disaster recovery plans may be leading to service outages in many organizations.

“Even the best laid disaster plans can go awry, especially if no one bothers to test them,” said Peter Tsai, Senior Technology Analyst at Spiceworks. “Ideally, a company’s disaster recovery plan should evolve and improve over time as weaknesses are exposed during testing and an organization’s needs change. However, the results show testing is often infrequent or not taking place at all, leaving many organizations vulnerable when disaster strikes.”

Larger Organizations Are More Likely to Experience Service Outages

In the last 12 months, 77 percent of organizations reported experiencing at least one outage (i.e. any interruption to normal levels of IT-related service). More specifically, 59 percent of organizations experienced one to three outages, 11 percent experienced four to six outages, and 7 percent experienced seven or more outages in the last 12 months.

Larger companies, which tend to rely on a greater number of services, experienced more outages than their smaller counterparts. 87 percent of large businesses large businesses with 1,000 or more employees experienced one or more outages in the last 12 months, compared to 79 percent of mid-size businesses with 100 to 999 employees, and 71 percent of small businesses with less than 100 employees.

Across all company sizes, 27 percent of organizations that experienced an outage reported losing business revenue as a result. Although 59 percent of organizations estimated losing less than $10,000 in revenue in the last 12 months, 31 percent estimated a loss of $10,000 to $100,000, and 10 percent reported losing $100,000 or more.

Power Outages and Internet Connectivity Issues Most Frequently Lead to Service Outages

The top causes leading to service outages in the last 12 months were power outages (56 percent), internet connectivity issues (48 percent), and hardware failure (32 percent), likely because less than half of organizations have backup power sources, redundant internet service providers, or high availability / failover systems in place.

Additionally, 27 percent of organizations experienced an outage due to service issues with a third-party vendor, while 21 percent experienced an outage due to human error and 13 percent due to natural disasters. Breaking down the types of natural disasters that led to outages, 29 percent were hurricanes, 16 percent were fires, 15 percent were floods, and 12 percent were due to either a tornado, animal-related incident, or blizzard.

Methodology: The survey was conducted in August 2018 and included 762 respondents from organizations across North America and Europe. Respondents are among the millions of IT professionals in Spiceworks and represent a variety of company sizes, including small-to-medium-sized businesses and enterprises. Respondents come from a variety of industries, including manufacturing, healthcare, nonprofits, education, government, and finance.

The Latest

Reliability is no longer proven by uptime alone, according to the The SRE Report 2026 from LogicMonitor. In the AI era, it is experienced through speed, consistency, and user trust, and increasingly judged by business impact. As digital services grow more complex and AI systems move into production, traditional monitoring approaches are struggling to keep pace, increasing the need for AI-first observability that spans applications, infrastructure, and the Internet ...

If AI is the engine of a modern organization, then data engineering is the road system beneath it. You can build the most powerful engine in the world, but without paved roads, traffic signals, and bridges that can support its weight, it will stall. In many enterprises, the engine is ready. The roads are not ...

In the world of digital-first business, there is no tolerance for service outages. Businesses know that outages are the quickest way to lose money and customers. For smaller organizations, unplanned downtime could even force the business to close ... A new study from PagerDuty, The State of AI-First Operations, reveals that companies actively incorporating AI into operations now view operational resilience as a growth driver rather than a cost center. But how are they achieving it? ...

In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...