Skip to main content

Lack of Automation Hinders Speed of Response to IT Outages and Incidents

Vincent Geffray

It's an eye opener to see that while companies have implemented service management for the most part — more than 90 percent of companies reporting that they have an IT Service Management system (ITSM) — only 11 percent of companies stated that they have automated the process for organizing their response to IT outages and incidents, according to Everbridge's 2016 State of IT Incident Management report.

This finding is significant because 47 percent of the companies reported having a major IT incident at least 6 times a year, the average cost of downtime is $8,662 per minute, and companies take 27 minutes on average to assemble an IT response team. Automated solutions can reduce this average time to 5 minutes or less. Considering the average cost of $8,662 per minute, the savings realized could be higher than $190,000 per major IT incident.

Key findings from the research include:

Most Companies Have an ITSM or Ticketing System

Over 90 percent of companies reported using an ITSM or ticketing system.

Major IT Outages or Incidents Occur Quite Frequently

47 percent of companies experience a major IT outage or incident six times or more a year.

36 percent experience them close to monthly (11 or more times per year).

More than a quarter of respondents reported that their companies experienced more than 21 incidents last year — that's close to two per month.

Only 9 percent of respondents reported that their organization did not report a major IT outage or incident in the past year.

The most common sources of incidents are network outages (experienced by 61 percent of companies), hardware failure or capacity issues (58 percent), internal business application issues (51 percent ), and unplanned maintenance (41 percent).

Responding to IT Outages and Incidents is Complicated and Too Manual

Two thirds (66 percent) of companies have distributed IT organizations with people spread among multiple locations and multiple time zones.

39 percent have more than 25 people included in their IT response teams. 29 percent have more than 50 people who need to be coordinated to respond to an incident. 16 percent more than 100 people.

43 percent of respondents reported that at least part of their process relies on manually calling and reaching out to people to activate the incident response team. Only 11 percent reported using an IT alerting tool to automate the process. These systems can improve response by reaching people through multiple modalities; use schedules to see who is available; automatically escalate to additional people if designated primary contacts do not respond; automatically organize conference bridges; and provide an audit trail of performance.

Response Times Could be Significantly Reduced by Automation

The mean time to activate and assemble a response team was cited as 27 minutes. Automated solutions can reduce this response time to 5 minutes or less.

IT downtime is expensive and hurts productivity

The average cost of IT downtime was reported as $8,662 per minute.

63 percent of respondents stated that IT incidents or outages hurt employee productivity, 60 percent that it caused IT team disruption or distraction, and 34 percent that it decreased customer satisfaction.

13 percent reported that their organization had experienced bad press or publicity due to an IT incident or outage.

Methodology: The sample for the research was 152 IT professionals, including 86% of respondents from companies of 1000 employees or more, and 45% from companies with more than 10,000 employees.

The Latest

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ... 

Most production autonomous agents do not run in a vacuum. They run inside cloud infrastructure: virtual machines, containers, pods, managed clusters or private servers. That is where most operations teams start monitoring. Is the VM alive? Is the container running? Did the pod restart? Is memory stable? Is CPU too high? Did the health check pass? Those signals are useful. They tell you whether the shell around the agent is alive. They do not tell you whether the agent inside is actually operational ...

Enterprise IT environments have never been more observable ... Yet many organizations still grapple with outages, lengthy incident resolution cycles, and increasing complexity. Most teams do not suffer from a shortage of data. They struggle to determine what deserves attention and what action to take next ... Enterprise IT operations must move beyond monitoring and visibility. The next stage of maturity is decision operations, an approach that helps teams make faster, better-informed decisions ...

Lack of Automation Hinders Speed of Response to IT Outages and Incidents

Vincent Geffray

It's an eye opener to see that while companies have implemented service management for the most part — more than 90 percent of companies reporting that they have an IT Service Management system (ITSM) — only 11 percent of companies stated that they have automated the process for organizing their response to IT outages and incidents, according to Everbridge's 2016 State of IT Incident Management report.

This finding is significant because 47 percent of the companies reported having a major IT incident at least 6 times a year, the average cost of downtime is $8,662 per minute, and companies take 27 minutes on average to assemble an IT response team. Automated solutions can reduce this average time to 5 minutes or less. Considering the average cost of $8,662 per minute, the savings realized could be higher than $190,000 per major IT incident.

Key findings from the research include:

Most Companies Have an ITSM or Ticketing System

Over 90 percent of companies reported using an ITSM or ticketing system.

Major IT Outages or Incidents Occur Quite Frequently

47 percent of companies experience a major IT outage or incident six times or more a year.

36 percent experience them close to monthly (11 or more times per year).

More than a quarter of respondents reported that their companies experienced more than 21 incidents last year — that's close to two per month.

Only 9 percent of respondents reported that their organization did not report a major IT outage or incident in the past year.

The most common sources of incidents are network outages (experienced by 61 percent of companies), hardware failure or capacity issues (58 percent), internal business application issues (51 percent ), and unplanned maintenance (41 percent).

Responding to IT Outages and Incidents is Complicated and Too Manual

Two thirds (66 percent) of companies have distributed IT organizations with people spread among multiple locations and multiple time zones.

39 percent have more than 25 people included in their IT response teams. 29 percent have more than 50 people who need to be coordinated to respond to an incident. 16 percent more than 100 people.

43 percent of respondents reported that at least part of their process relies on manually calling and reaching out to people to activate the incident response team. Only 11 percent reported using an IT alerting tool to automate the process. These systems can improve response by reaching people through multiple modalities; use schedules to see who is available; automatically escalate to additional people if designated primary contacts do not respond; automatically organize conference bridges; and provide an audit trail of performance.

Response Times Could be Significantly Reduced by Automation

The mean time to activate and assemble a response team was cited as 27 minutes. Automated solutions can reduce this response time to 5 minutes or less.

IT downtime is expensive and hurts productivity

The average cost of IT downtime was reported as $8,662 per minute.

63 percent of respondents stated that IT incidents or outages hurt employee productivity, 60 percent that it caused IT team disruption or distraction, and 34 percent that it decreased customer satisfaction.

13 percent reported that their organization had experienced bad press or publicity due to an IT incident or outage.

Methodology: The sample for the research was 152 IT professionals, including 86% of respondents from companies of 1000 employees or more, and 45% from companies with more than 10,000 employees.

The Latest

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ... 

Most production autonomous agents do not run in a vacuum. They run inside cloud infrastructure: virtual machines, containers, pods, managed clusters or private servers. That is where most operations teams start monitoring. Is the VM alive? Is the container running? Did the pod restart? Is memory stable? Is CPU too high? Did the health check pass? Those signals are useful. They tell you whether the shell around the agent is alive. They do not tell you whether the agent inside is actually operational ...

Enterprise IT environments have never been more observable ... Yet many organizations still grapple with outages, lengthy incident resolution cycles, and increasing complexity. Most teams do not suffer from a shortage of data. They struggle to determine what deserves attention and what action to take next ... Enterprise IT operations must move beyond monitoring and visibility. The next stage of maturity is decision operations, an approach that helps teams make faster, better-informed decisions ...