Skip to main content

Customer-Facing Incidents Increased by 43% During the Past Year

The average customer-facing incident takes nearly three hours to resolve (175 minutes) while the estimated cost of downtime is $4,537 per minute, meaning each incident can cost nearly $794,000, according to new research from PagerDuty.

As respondents' organizations saw an average of 25 high-priority/priority incidents in the last 12 months, the cumulative costs add up to just under $20 million per year, per organization.


Source: PagerDuty

"PagerDuty's global survey found that incidents have been driven by increased complexity, rapid expansion of digital services and insufficient investment in IT infrastructure maintenance," said Eric Johnson, CIO at PagerDuty. "The costs of these incidents are significant both financially and in lost consumer trust, which is why companies need to invest in automation to mitigate the risk and shorten the time an incident lasts. Investing in automation needs to be at the top of IT leaders' priority lists."

Other key findings of the data include:

■ Over half (59%) of IT leaders say that customer-impacting incidents have increased, growing by an average of 43% in the last 12 months.

■ 78% of IT leaders in travel say customer-impacting incidents have increased.

■ 68% of IT leaders in finance say customer-impacting incidents have increased.

■ Organizations with at least five manual processes in incident response incurred $30.4 million in annual costs of customer-facing outages vs. $16.8 million for those with at least five processes fully automated.

■ 69% of IT leaders say the board and management are failing to invest in protecting customer trust when outages occur.

■ Nearly a quarter (24%) of IT leaders reported outages negatively impacting share prices.

■ More than ⅓ (35%) of IT leaders have seen higher levels of employee burnout.

■ More than 70% of IT leaders report that remediation, mobilizing responders, collaboration between teams and internal communications with stakeholders are yet to be fully automated.

Digital incidents continue to rise in number, last longer and cost more, but organizations are also understanding the critical role automation can play. 86% of IT leaders surveyed say that their organization is making strides towards fully automating the end-to-end incident response process.

"Digital incidents occur, and front-line responders are too often hindered in their ability to resolve incidents quickly due to fragmented IT environments, inadequate processes and inability to identify the right responders," said Jeffrey Hausman, Chief Product Development Officer at PagerDuty. "Automation can be a key enabler in achieving resilience in these increasingly complex environments."

Methodology: The survey — of 500 IT leaders and decision-makers of companies with more than 1,000 employees responsible for IT operations from the US, UK and Australia — was conducted online between May 31, 2024 and June 6, 2024 by Censuswide on behalf of PagerDuty.

The Latest

Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...

AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...

Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...

Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...

Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...

In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ... 

Virtual Private Networks became a cornerstone of enterprise security at a time when corporate infrastructure looked very different from today ... For years, this model worked well. But the architecture behind VPNs assumed a centralized corporate environment—one where the network itself was the hub of activity. In a cloud — first world, that assumption no longer holds ...

Website outages get resolved just as fast in August as they do in November. I went looking for the opposite: the summer slowdown everyone assumes is there once the people who fix things are away. It isn't in the data we collected, covering 1.8 million confirmed outages across tens of thousands of websites ...

This year, many of the cloud infrastructure contracts signed in the early days of the AI boom will come up for renewal. As the year goes on, I anticipate we'll see a significant amount of cloud vendor swapouts and multi-cloud adoption, and the reason isn't just GPU depreciation. It's because they're tired of their current cloud providers ...

There's a moment the many observability teams have experienced days into bringing a new service into production: you realize that the vendor's claims of "intelligent" behavior included a large serving of hype. Their dashboards look nice until they don't, the failure modes are a black box, and no one on the team can confidently explain why the system did what it did at 2 am. Agentic AI is about to force every Ops team to relive that moment at web-scale until they start treating these systems as the dependencies they actually are ...

Customer-Facing Incidents Increased by 43% During the Past Year

The average customer-facing incident takes nearly three hours to resolve (175 minutes) while the estimated cost of downtime is $4,537 per minute, meaning each incident can cost nearly $794,000, according to new research from PagerDuty.

As respondents' organizations saw an average of 25 high-priority/priority incidents in the last 12 months, the cumulative costs add up to just under $20 million per year, per organization.


Source: PagerDuty

"PagerDuty's global survey found that incidents have been driven by increased complexity, rapid expansion of digital services and insufficient investment in IT infrastructure maintenance," said Eric Johnson, CIO at PagerDuty. "The costs of these incidents are significant both financially and in lost consumer trust, which is why companies need to invest in automation to mitigate the risk and shorten the time an incident lasts. Investing in automation needs to be at the top of IT leaders' priority lists."

Other key findings of the data include:

■ Over half (59%) of IT leaders say that customer-impacting incidents have increased, growing by an average of 43% in the last 12 months.

■ 78% of IT leaders in travel say customer-impacting incidents have increased.

■ 68% of IT leaders in finance say customer-impacting incidents have increased.

■ Organizations with at least five manual processes in incident response incurred $30.4 million in annual costs of customer-facing outages vs. $16.8 million for those with at least five processes fully automated.

■ 69% of IT leaders say the board and management are failing to invest in protecting customer trust when outages occur.

■ Nearly a quarter (24%) of IT leaders reported outages negatively impacting share prices.

■ More than ⅓ (35%) of IT leaders have seen higher levels of employee burnout.

■ More than 70% of IT leaders report that remediation, mobilizing responders, collaboration between teams and internal communications with stakeholders are yet to be fully automated.

Digital incidents continue to rise in number, last longer and cost more, but organizations are also understanding the critical role automation can play. 86% of IT leaders surveyed say that their organization is making strides towards fully automating the end-to-end incident response process.

"Digital incidents occur, and front-line responders are too often hindered in their ability to resolve incidents quickly due to fragmented IT environments, inadequate processes and inability to identify the right responders," said Jeffrey Hausman, Chief Product Development Officer at PagerDuty. "Automation can be a key enabler in achieving resilience in these increasingly complex environments."

Methodology: The survey — of 500 IT leaders and decision-makers of companies with more than 1,000 employees responsible for IT operations from the US, UK and Australia — was conducted online between May 31, 2024 and June 6, 2024 by Censuswide on behalf of PagerDuty.

The Latest

Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...

AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...

Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...

Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...

Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...

In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ... 

Virtual Private Networks became a cornerstone of enterprise security at a time when corporate infrastructure looked very different from today ... For years, this model worked well. But the architecture behind VPNs assumed a centralized corporate environment—one where the network itself was the hub of activity. In a cloud — first world, that assumption no longer holds ...

Website outages get resolved just as fast in August as they do in November. I went looking for the opposite: the summer slowdown everyone assumes is there once the people who fix things are away. It isn't in the data we collected, covering 1.8 million confirmed outages across tens of thousands of websites ...

This year, many of the cloud infrastructure contracts signed in the early days of the AI boom will come up for renewal. As the year goes on, I anticipate we'll see a significant amount of cloud vendor swapouts and multi-cloud adoption, and the reason isn't just GPU depreciation. It's because they're tired of their current cloud providers ...

There's a moment the many observability teams have experienced days into bringing a new service into production: you realize that the vendor's claims of "intelligent" behavior included a large serving of hype. Their dashboards look nice until they don't, the failure modes are a black box, and no one on the team can confidently explain why the system did what it did at 2 am. Agentic AI is about to force every Ops team to relive that moment at web-scale until they start treating these systems as the dependencies they actually are ...