Skip to main content

The Leading Causes of IT Outages - and How to Prevent Them

Mark Banfield
LogicMonitor

IT outages happen to companies across the globe, regardless of location, annual revenue or size. Even the most mammoth companies are at risk of downtime. Increasingly over the past few years, high-profile IT outages — defined as when the services or systems a business provides suddenly become unavailable — have ended up splashed across national news headlines.

In March 2019, Facebook and Instagram each experienced 14 hours of downtime. A second IT outage struck both — along with WhatsApp — in April 2019, taking all three platforms offline. And in July 2019, all three platforms experienced availability problems that impacted users. British Airways has also faced a series of high-profile IT outages in the past, including one in April that resulted in 100 canceled flights and 200 delayed flights. An outage back in May 2017 also affected more than 1,000 flights, call centers, BA's website and BA's mobile app.

Given all of these recent disruptive and costly outages, LogicMonitor decided to investigate the causes behind downtime, commissioning an independent study investigating the major causes of downtime, the business impact of outages on organizations, and ways to avoid IT outages and brownouts. The IT Outage Impact Study involved surveying 300 IT decision-makers across the United States, Canada, the United Kingdom, Australia and New Zealand.

Outages Lead to Compliance Failures and High Costs

The number one and number two issues were concerns about performance and availability

Among other insights, the survey revealed the top 5 issues keeping IT decision makers up at night. The number one and number two issues were concerns about performance and availability, beating out security and cost-effectiveness worries.

Unfortunately, those self-reported fears about IT teams' ability to maintain availability are well-founded. In fact, 96% of global survey respondents reported that their organizations had suffered at least one IT outage over the past three years. Such outages can have serious implications, including steep costs and low customer satisfaction scores. Heavily regulated industries, such as healthcare and finance, face another dire consequence beyond service disruptions and costs as a result of outages: compliance failure.

"One of our clients is a radiology company, and they need to be up 24/7," said a service desk support engineer for a solution provider. "If they have more than an hour of downtime a year, probably less than that, that's a serious issue. These guys can never go down, for legal reasons."


Human Error is #1 Cause of IT Outages in the US and Canada

The study found that human error was the #1 cause of IT outages in the United States and Canada, and the #3 cause globally. Given this finding, it was no surprise that Network World covered the story of British Airways' May 2017 outage under the headline, "British Airways' outage, like most data center outages, was caused by humans."

The Network World article describes how an engineer working onsite at a data center near the Heathrow airport disconnected a power supply. When the power supply was reconnected, a surge of power caused the outage. The article also cites a 2016 Ponemon Institute study, which found that human error accounted for 11 percent of outages, more than weather (10%), generator failures (6%) or IT equipment malfunction (4%).

Faced with findings like this, it's no wonder that global IT decision makers said 51% of IT outages are avoidable. As a result, more and more teams worldwide are transitioning to monitoring tools that incorporate AIOps and automation to minimize human error and maximize early warning opportunities.

Monitoring Helps Prevent Outages Through Early Warning Systems

Comprehensive monitoring provides visibility into IT infrastructure and can help organizations get ahead of trends that indicate an outage may be rapidly approaching. The top two causes of outages, according to survey respondents, are declining hardware/software performance and IT teams' failure to notice when usage reaches a dangerous level. Artificial intelligence for IT operations (AIOps) and intelligent monitoring offer an effective solution to both of these outage factors.

To minimize your organizations' outage risk, look for monitoring solutions with the following capabilities:

■ A platform that offers a holistic view of your IT systems via a single pane of glass and integrates with all your technologies

■ A tool that builds in a high level of redundancy to eliminate single points of failure

■ A platform that provides early visibility via an early warning system into trends that could indicate future trouble

■ A solution that is able to scale with your business as it grows, making sure your current and future monitoring needs are met.

Mark Banfield is CRO at LogicMonitor

The Latest

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

40% of organizations deploying AI will implement dedicated AI observability tools by 2028 to monitor model performance, bias and outputs, according to Gartner ...

Until AI-powered engineering tools have live visibility of how code behaves at runtime, they cannot be trusted to autonomously ensure reliable systems, according to the State of AI-Powered Engineering Report 2026 report from Lightrun. The report reveals that a major volume of manual work is required when AI-generated code is deployed: 43% of AI-generated code requires manual debugging in production, even after passing QA or staging tests. Furthermore, an average of three manual redeploy cycles are required to verify a single AI-suggested code fix in production ...

Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...

Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...

The Leading Causes of IT Outages - and How to Prevent Them

Mark Banfield
LogicMonitor

IT outages happen to companies across the globe, regardless of location, annual revenue or size. Even the most mammoth companies are at risk of downtime. Increasingly over the past few years, high-profile IT outages — defined as when the services or systems a business provides suddenly become unavailable — have ended up splashed across national news headlines.

In March 2019, Facebook and Instagram each experienced 14 hours of downtime. A second IT outage struck both — along with WhatsApp — in April 2019, taking all three platforms offline. And in July 2019, all three platforms experienced availability problems that impacted users. British Airways has also faced a series of high-profile IT outages in the past, including one in April that resulted in 100 canceled flights and 200 delayed flights. An outage back in May 2017 also affected more than 1,000 flights, call centers, BA's website and BA's mobile app.

Given all of these recent disruptive and costly outages, LogicMonitor decided to investigate the causes behind downtime, commissioning an independent study investigating the major causes of downtime, the business impact of outages on organizations, and ways to avoid IT outages and brownouts. The IT Outage Impact Study involved surveying 300 IT decision-makers across the United States, Canada, the United Kingdom, Australia and New Zealand.

Outages Lead to Compliance Failures and High Costs

The number one and number two issues were concerns about performance and availability

Among other insights, the survey revealed the top 5 issues keeping IT decision makers up at night. The number one and number two issues were concerns about performance and availability, beating out security and cost-effectiveness worries.

Unfortunately, those self-reported fears about IT teams' ability to maintain availability are well-founded. In fact, 96% of global survey respondents reported that their organizations had suffered at least one IT outage over the past three years. Such outages can have serious implications, including steep costs and low customer satisfaction scores. Heavily regulated industries, such as healthcare and finance, face another dire consequence beyond service disruptions and costs as a result of outages: compliance failure.

"One of our clients is a radiology company, and they need to be up 24/7," said a service desk support engineer for a solution provider. "If they have more than an hour of downtime a year, probably less than that, that's a serious issue. These guys can never go down, for legal reasons."


Human Error is #1 Cause of IT Outages in the US and Canada

The study found that human error was the #1 cause of IT outages in the United States and Canada, and the #3 cause globally. Given this finding, it was no surprise that Network World covered the story of British Airways' May 2017 outage under the headline, "British Airways' outage, like most data center outages, was caused by humans."

The Network World article describes how an engineer working onsite at a data center near the Heathrow airport disconnected a power supply. When the power supply was reconnected, a surge of power caused the outage. The article also cites a 2016 Ponemon Institute study, which found that human error accounted for 11 percent of outages, more than weather (10%), generator failures (6%) or IT equipment malfunction (4%).

Faced with findings like this, it's no wonder that global IT decision makers said 51% of IT outages are avoidable. As a result, more and more teams worldwide are transitioning to monitoring tools that incorporate AIOps and automation to minimize human error and maximize early warning opportunities.

Monitoring Helps Prevent Outages Through Early Warning Systems

Comprehensive monitoring provides visibility into IT infrastructure and can help organizations get ahead of trends that indicate an outage may be rapidly approaching. The top two causes of outages, according to survey respondents, are declining hardware/software performance and IT teams' failure to notice when usage reaches a dangerous level. Artificial intelligence for IT operations (AIOps) and intelligent monitoring offer an effective solution to both of these outage factors.

To minimize your organizations' outage risk, look for monitoring solutions with the following capabilities:

■ A platform that offers a holistic view of your IT systems via a single pane of glass and integrates with all your technologies

■ A tool that builds in a high level of redundancy to eliminate single points of failure

■ A platform that provides early visibility via an early warning system into trends that could indicate future trouble

■ A solution that is able to scale with your business as it grows, making sure your current and future monitoring needs are met.

Mark Banfield is CRO at LogicMonitor

The Latest

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

40% of organizations deploying AI will implement dedicated AI observability tools by 2028 to monitor model performance, bias and outputs, according to Gartner ...

Until AI-powered engineering tools have live visibility of how code behaves at runtime, they cannot be trusted to autonomously ensure reliable systems, according to the State of AI-Powered Engineering Report 2026 report from Lightrun. The report reveals that a major volume of manual work is required when AI-generated code is deployed: 43% of AI-generated code requires manual debugging in production, even after passing QA or staging tests. Furthermore, an average of three manual redeploy cycles are required to verify a single AI-suggested code fix in production ...

Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...

Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...