Murtaza Doctor

we can detect config issues happening in real time.

And the idea is to correlate cloud paths, routing and user experience.

So we all know that the biggest issues happen when you start changing your config or fat fingering config files.

so this particular product actually allows you to simulate changes before your deployment and auto detect any drifts in configuration right and if you think about a multi-domain assurance across cloud and routing and other things this becomes a real thing right so

Just to highlight, one of our customers actually had an intermittent purchase failure in a multi-API workflow.

And Cloud Insights, which is one of our products, it correlated the user impact.

It went ahead and figured out the path degradation.

You know, it looked at a routing change which was made, a config push, and then produced the root cause in under two minutes, right?

And a human team would take hours figuring it out.

And this would be like a toss call happening or an escalation call where every team would come on board and we're trying to figure out.

And look at the root cause here.

The root cause started with just a configuration change.

Yeah.

And look at the example we had.

So on November 18th, we had a major cloudflare outage.

And what we observed from a ThousandEyes perspective is

We actually saw the network paths to Cloudflare's front end were clean.

There were no spikes in latency.

There was no packet loss.

The internet paths look all green, but the application traffic was failing with timeouts and 500s.