Skip to main content

Millions Lost to Internet Outages: Could a C-Suite Role Help Stem the Tide?

Mehdi Daoudi
Catchpoint

The consequences of outages have become a pressing issue as the largest IT outage in history continues to rock the world with severe ramifications. It has been estimated that this latest outage cost Fortune 500 companies as much as $5.4 billion in revenues and gross profit with Delta most recently confirming $380 million in revenue alone. According to the Catchpoint Internet Resilience Report, these types of disruptions, internet outages in particular, can have severe financial and reputational impacts and enterprises should strongly consider their resilience.

This isn't just an issue impacting companies using CrowdStrike's software, but is one that is costing companies millions across the board. The Internet Resilience Report revealed that 43% of surveyed businesses in sectors including finance, e-commerce, cloud, and healthcare estimated losses of over $1 million due to internet outages or degradations in the month prior to the 2024 survey.

In today's interconnected world, a single point of failure in internet infrastructure can translate directly into substantial revenue losses. Thus, a top-down approach to internet resilience is needed. Companies should consider the establishment of a chief resilience officer (CRO) within the C-suite. This role is akin to that of a Chief Security Officer, emphasizing the importance of resilience alongside security. One of the primary causes of frequent outages is the lack of centralized and unified monitoring tools, resulting in a fragmented IT landscape reminiscent of the Balkans. The CRO should be responsible for driving the standardization of telemetry across the organization to enhance resilience. As the report highlights, the financial and reputational consequences of inadequate resilience are as severe as those of security breaches. Therefore, it is imperative that companies prioritize resilience at the highest levels of their organization.

In fact, Fortune 2000 companies are leading the charge in the new trend and increasingly recognizing the value of the CRO role. These executives are tasked with driving resilience planning, identifying single points of failure, and devising strategies to mitigate potential disruptions. The extensive Adobe Experience Cloud outage last year, which lasted 18 hours (in addition to the recent CrowdStrike outage), serves as a stark example of the type of service disruption that a CRO could help manage and prevent.

However, the creation of a CRO position is not the only path to achieving resilience. Organizations should also foster a culture of resilience by learning from their mistakes by documenting and studying failures within the product delivery chain and encouraging a mindset of continuous improvement. Companies should conduct preemptive exercises to test their systems, identifying weaknesses and refining their responses to potential outages.

Moreover, it is crucial for businesses to work with reliable vendors who demonstrate a commitment to resilience. While everyone is allowed to make mistakes, repeated failures or a lack of accountability should prompt companies to reconsider their partnerships. Learning from each incident and ensuring that vendors do the same is key to maintaining a resilient internet infrastructure.

As we navigate our increasingly digital-first world, the importance of internet resilience cannot be overstated. It should be an integral part of any disaster recovery or business continuity program, discussed at the highest organizational levels and tested regularly. While we can't simulate every possible outage scenario, planning for the unexpected has become a crucial business practice.

Prioritizing internet resilience and taking resiliency into consideration from the c-suite down is essential for any business aiming to thrive amidst the complexities of our connected landscape.

Mehdi Daoudi is CEO and Co-Founder of Catchpoint

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 ...

Millions Lost to Internet Outages: Could a C-Suite Role Help Stem the Tide?

Mehdi Daoudi
Catchpoint

The consequences of outages have become a pressing issue as the largest IT outage in history continues to rock the world with severe ramifications. It has been estimated that this latest outage cost Fortune 500 companies as much as $5.4 billion in revenues and gross profit with Delta most recently confirming $380 million in revenue alone. According to the Catchpoint Internet Resilience Report, these types of disruptions, internet outages in particular, can have severe financial and reputational impacts and enterprises should strongly consider their resilience.

This isn't just an issue impacting companies using CrowdStrike's software, but is one that is costing companies millions across the board. The Internet Resilience Report revealed that 43% of surveyed businesses in sectors including finance, e-commerce, cloud, and healthcare estimated losses of over $1 million due to internet outages or degradations in the month prior to the 2024 survey.

In today's interconnected world, a single point of failure in internet infrastructure can translate directly into substantial revenue losses. Thus, a top-down approach to internet resilience is needed. Companies should consider the establishment of a chief resilience officer (CRO) within the C-suite. This role is akin to that of a Chief Security Officer, emphasizing the importance of resilience alongside security. One of the primary causes of frequent outages is the lack of centralized and unified monitoring tools, resulting in a fragmented IT landscape reminiscent of the Balkans. The CRO should be responsible for driving the standardization of telemetry across the organization to enhance resilience. As the report highlights, the financial and reputational consequences of inadequate resilience are as severe as those of security breaches. Therefore, it is imperative that companies prioritize resilience at the highest levels of their organization.

In fact, Fortune 2000 companies are leading the charge in the new trend and increasingly recognizing the value of the CRO role. These executives are tasked with driving resilience planning, identifying single points of failure, and devising strategies to mitigate potential disruptions. The extensive Adobe Experience Cloud outage last year, which lasted 18 hours (in addition to the recent CrowdStrike outage), serves as a stark example of the type of service disruption that a CRO could help manage and prevent.

However, the creation of a CRO position is not the only path to achieving resilience. Organizations should also foster a culture of resilience by learning from their mistakes by documenting and studying failures within the product delivery chain and encouraging a mindset of continuous improvement. Companies should conduct preemptive exercises to test their systems, identifying weaknesses and refining their responses to potential outages.

Moreover, it is crucial for businesses to work with reliable vendors who demonstrate a commitment to resilience. While everyone is allowed to make mistakes, repeated failures or a lack of accountability should prompt companies to reconsider their partnerships. Learning from each incident and ensuring that vendors do the same is key to maintaining a resilient internet infrastructure.

As we navigate our increasingly digital-first world, the importance of internet resilience cannot be overstated. It should be an integral part of any disaster recovery or business continuity program, discussed at the highest organizational levels and tested regularly. While we can't simulate every possible outage scenario, planning for the unexpected has become a crucial business practice.

Prioritizing internet resilience and taking resiliency into consideration from the c-suite down is essential for any business aiming to thrive amidst the complexities of our connected landscape.

Mehdi Daoudi is CEO and Co-Founder of Catchpoint

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 ...