Skip to main content

The Network Data Problem Slowing Down Enterprise AIOps

Daren Fulwell
IP Fabric

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.

Most organizations rely on institutional knowledge to bridge the gap between what their tools are showing them and how the network is actually behaving. 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. This leaves AI systems with a view of the network that’s riddled with gaps that it doesn’t know about. And when this is the case, how can any enterprise confidently act on what their AI is telling them?

Why AI Fails on Fragmented Data

While much of the AI discussion focuses on models and frameworks, NetOps teams are finding that the more difficult problem has less to do with the AI system itself and more to do with the quality and reliability of the data used to train it.

AI systems inherit many of the same limitations as human operators; like humans, AI systems can only reason from the information that’s available to them. If infrastructure data is outdated or missing critical dependencies, the resulting analysis will only reflect a fragment of the operational reality. These systemic gaps may result in an AI agent taking actions without considering the effect it’ll have on network behavior as a whole, which can put operations, security, and compliance at risk.

The Rise of Network Digital Twins

Given the hype around AIOps — and the desire to solve this data problem — enterprises are looking for a way to maintain a complete, contextualized view of the network. Rather than relying on fragmented operational views stitched together from diagrams, spreadsheets and disconnected systems, teams are exploring approaches that create a more unified understanding of configurations, connectivity, routing behavior and dependencies.

This is where network digital twins are gaining traction. Network digital twins provide an interactive model of the network at a given point in time, giving both human engineers and AI systems access to a normalized, end-to-end understanding of the network’s state and behavior. This shared context becomes especially valuable in enterprise environments, where teams are pushing dozens of changes per day, and any one of those changes carries the potential for downstream risk.

Building a Foundation for Network Autonomy

In today's complex environments, there is no shortage of information; the real difficulty lies in trying to piece fragments of the network together. Most network data is trapped in engineers’ heads, and until organizations find a way to document and validate that data, AIOps will be forever out of reach.

While many organizations are chomping at the bit to automate, the key to long-term success is simple: go back to basics. While it’s important to understand the configuration and state data for each device, it’s even more important to understand the relationships between the devices, which determine how the network actually behaves.

In other words: focus on the data first. Then when you’re confident that your data is an accurate representation of network behavior, you’ll be ready to take the first step towards automation, AIOps, and eventually, autonomy.

Daren Fulwell is Field CTO at IP Fabric

Hot Topics

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

The Network Data Problem Slowing Down Enterprise AIOps

Daren Fulwell
IP Fabric

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.

Most organizations rely on institutional knowledge to bridge the gap between what their tools are showing them and how the network is actually behaving. 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. This leaves AI systems with a view of the network that’s riddled with gaps that it doesn’t know about. And when this is the case, how can any enterprise confidently act on what their AI is telling them?

Why AI Fails on Fragmented Data

While much of the AI discussion focuses on models and frameworks, NetOps teams are finding that the more difficult problem has less to do with the AI system itself and more to do with the quality and reliability of the data used to train it.

AI systems inherit many of the same limitations as human operators; like humans, AI systems can only reason from the information that’s available to them. If infrastructure data is outdated or missing critical dependencies, the resulting analysis will only reflect a fragment of the operational reality. These systemic gaps may result in an AI agent taking actions without considering the effect it’ll have on network behavior as a whole, which can put operations, security, and compliance at risk.

The Rise of Network Digital Twins

Given the hype around AIOps — and the desire to solve this data problem — enterprises are looking for a way to maintain a complete, contextualized view of the network. Rather than relying on fragmented operational views stitched together from diagrams, spreadsheets and disconnected systems, teams are exploring approaches that create a more unified understanding of configurations, connectivity, routing behavior and dependencies.

This is where network digital twins are gaining traction. Network digital twins provide an interactive model of the network at a given point in time, giving both human engineers and AI systems access to a normalized, end-to-end understanding of the network’s state and behavior. This shared context becomes especially valuable in enterprise environments, where teams are pushing dozens of changes per day, and any one of those changes carries the potential for downstream risk.

Building a Foundation for Network Autonomy

In today's complex environments, there is no shortage of information; the real difficulty lies in trying to piece fragments of the network together. Most network data is trapped in engineers’ heads, and until organizations find a way to document and validate that data, AIOps will be forever out of reach.

While many organizations are chomping at the bit to automate, the key to long-term success is simple: go back to basics. While it’s important to understand the configuration and state data for each device, it’s even more important to understand the relationships between the devices, which determine how the network actually behaves.

In other words: focus on the data first. Then when you’re confident that your data is an accurate representation of network behavior, you’ll be ready to take the first step towards automation, AIOps, and eventually, autonomy.

Daren Fulwell is Field CTO at IP Fabric

Hot Topics

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