Murtaza Doctor

And this is a classic backend service failure, not a routing.

or a path issue, right?

Now, imagine this outage in an agentic-driven world.

Cloudflare sits between users and APIs for everything, right?

Whether you're talking about, you know, OpenAI, you know, X, Anthropic, dozens of more things, right?

So when Cloudflare's back and broke,

entire agent workflows would have failed.

They would have retried, they would have cascaded, the load would have multiplied.

And that's, I think, brings back to your original thing, which we just discussed that that's why our SLEs matter.

And that's why ThousandEyes is so relevant because we focus on SLEs to drive

those experiences for our customers.

And that's what really matters, right?

So it doesn't really matter.

And in this case, right, the path was green, you know, and the workflow was catastrophically failing.

So you can see the impact of some of these outages happening and

Obviously, we as ThousandEyes, we love to shed light on some of these things.

We actually submit our reports around these outages as well.

And if you actually go to thousandeyes.com slash outages, you'll actually be able to see a global map of all of the outages on the application and network sites happening in real time.

I mean, I think, you know, the idea is that think about it as like, you know, something which is on your network operations, you know, control, right?

You have it on your not, you have your dashboard of all the outages happening.