惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

The Register - Security
The Register - Security
云风的 BLOG
云风的 BLOG
U
Unit 42
F
Fortinet All Blogs
The GitHub Blog
The GitHub Blog
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
D
Docker
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
S
Secure Thoughts
Hacker News: Ask HN
Hacker News: Ask HN
Vercel News
Vercel News
S
Security @ Cisco Blogs
GbyAI
GbyAI
Stack Overflow Blog
Stack Overflow Blog
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
I
Intezer
MongoDB | Blog
MongoDB | Blog
AI
AI
MyScale Blog
MyScale Blog
Engineering at Meta
Engineering at Meta
Y
Y Combinator Blog
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
P
Proofpoint News Feed
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
W
WeLiveSecurity
博客园 - 叶小钗
S
SegmentFault 最新的问题
N
News | PayPal Newsroom
WordPress大学
WordPress大学
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
D
DataBreaches.Net
小众软件
小众软件
Microsoft Azure Blog
Microsoft Azure Blog
Spread Privacy
Spread Privacy
H
Help Net Security
美团技术团队
博客园 - 司徒正美
T
Threat Research - Cisco Blogs
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
K
Kaspersky official blog
Application and Cybersecurity Blog
Application and Cybersecurity Blog
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
V
Vulnerabilities – Threatpost
TaoSecurity Blog
TaoSecurity Blog
N
Netflix TechBlog - Medium
L
Lohrmann on Cybersecurity
J
Java Code Geeks
量子位
Martin Fowler
Martin Fowler
博客园_首页

Catchpoint Blog

SRE Report: AI optimism and the economics of effort SRE Report: Why fast is what users trust SRE Report 2026: What surprised us, what didn't, and why the gaps matter most The SRE Report 2026: Defensible Ns Why Synthetic Tracing Delivers Better Data, Not Just More Data A New Chapter: LogicMonitor + Catchpoint – A Personal Note from Mehdi Mezmo + Catchpoint deliver observability SREs can rely on The four pillars holding up your digital business, and what happens when they crumble When payments pause: lessons from a global payments outage Observability 2025 Decoded: What the DZone Report Means for SLO-Driven Ops The next evolution of WebPageTest has arrived, and it’s a game-changer The Monitoring Blind Spot That Could Cost You Black Friday Powering Mexico’s Digital Future: Expanded Internet Observability with Catchpoint The Next Chapter of WebPageTest: Your New Experience Starts Soon SRE Report Retrospectives — Have AIOps Predictions Held Up? When BGP becomes UX: The inside story of a SaaS routing decision gone wrong (or right) Session Replay explained: A guide to seeing digital experience through your user’s eyes Making the invisible visible: Are your cloud firewalls and DDoS protection really working? Why it’s time to move beyond APM: Monitoring from the user’s perspective When metrics mislead: Inside the 2025 Retail Web Performance Benchmark The vendor trap: why your next outage won’t be your fault—but will be your problem LLMs don’t stand still: How to monitor and trust the models powering your AI Semantic Caching: What We Measured, Why It Matters The Annual SRE Survey Is Open—We Want to Hear from You Observability isn’t about the tool. It’s about the truth Invisible dependencies, visible impact: Lessons from the Google Cloud outage Real-time detection of BGP blackholing and prefix hijacks Leading analyst firm reveals the real cost of internet disruptions The Power of Over 3000 Intelligent Observability Agents Monitoring in the Age of Complexity: 5 Assumptions CIOs Need to Rethink Why Intelligent Traffic Steering is Critical for Performance and Cost Optimization Retail digital performance event recap: Key insights from IBM & Catchpoint Zendesk outage: A case for proactive monitoring and faster incident response Silence during chaos: Why the X outage is a call to arms for proactive monitoring The $1 Million Lesson: Building a Culture of Quality Through SLAs When AI tools fail: How to map your AI dependencies for proactive visibility Why Super Bowl 2025 was a triumph for Internet Resilience Why Internet Performance Monitoring is the new health check for IT organizations Why use Playwright in Catchpoint for synthetic monitoring Introducing WebPageTest Expert Plan: Real-Time Insights, Synthetic + RUM together in One Platform The shift to digital: How businesses are reshaping their priorities for 2025 The SRE Report 2025's Call to Action Monitoring in the Age of the Internet: DEM, IPM, and APM—What You Need to Know SSL Monitoring, Trust, and McLOVIN Performing for the holidays: Look beyond uptime for season sales success Lessons from Microsoft’s office 365 Outage: The Importance of third-party monitoring Web Performance Experts Look into the Future of Web Performance The hidden challenges of Internet Resilience: Key insights from 2024 report When SSL Issues aren’t just about SSL: A deep dive into the TIBCO Mashery outage The curious case of Marriott and the untold impact of web performance on revenue Preparing for the unexpected: Lessons from the AJIO and Jio Outage It’s time to stop neglecting the elephant in the room: Performance Matters! The Need for Speed: Highlights from IBM and Catchpoint’s Global DNS Performance Study Learnings from ServiceNow’s Proactive Response to a Network Breakdown Webinar Recap: Taking Web Performance to the Next Level Use the Catchpoint Terraform Provider in your CI/CD workflows Is the Internet ready for L4S? Takeaways from the CrowdStrike outage: third-parties can pose risk July 19th global IT outage reminds us of digital complexity 5 Actions you can take to improve digital performance 2024: A banner year for Internet Resilience APM vs Observability: Both-and, not either-or AppAssure: Ensuring the resilience of your Tier-1 applications just became easier APM vs observability: why your definitions are broken APM vs Observability: What comes next? APM vs Observability: Observing beyond APM Achieving stability with agility in your CI/CD pipeline AWS Outage: How do you prepare for the failure of your own safety net? Catch frustration before it costs you: New tools for a better user experience Catchpoint Expands Observability Network to Barcelona: A Growing Internet Hub Catchpoint Peak Performance Summit 2025: Redefining Observability for the Outcome Economy Catchpoint named a leader in the 2024 Gartner® Magic Quadrant™ for Digital Experience Monitoring Consolidation and Modernization in Enterprise Observability Connected Devices: Unlocking the next frontier of Internet Performance Monitoring Cloud Monitoring's Blind Spot: The User Perspective Cloudflare’s Resolver Outage: More Than Just DNS Cloudflare outage: another wake-up call for resilience planning Demystifying API Monitoring and Testing with IPM Creating the IPM Category: Catchpoint’s Journey to Leadership and the LogicMonitor Era Critical Requirements for Modern API Monitoring Customer Survey 2024: Unveiling insights and impact Did Delta's slow web performance signal trouble before CrowdStrike? Diagnosing Wi-Fi failures that traditional tools miss: a case study DNS misconfiguration can happen to anyone - the question is how fast can you detect it? ECN explained: Navigate congestion for faster, smoother data delivery Don’t get caught in the dark: Lessons from a Lumen & AWS micro-outage Escalating risk, shrinking margins: The 2025 Internet Resilience Report From refresh to results: the metrics that shaped Election Day 2024 coverage Fast and furious: The importance of performance in the digital age Getting Started with Traceroute From the source to the edge: the six agent types you can’t ignore From SEO to AEO: Why Web Performance Is the Key to AI Search Success Going for gold: Testing the resilience of Olympic websites Here’s the proof: What the fastest sites on the web have in common Google’s Agent-to-Agent (A2A) Protocol is here—Now Let’s Make it Observable How IPM helped a top tech brand catch an OpenAI outage before it became a crisis How AI Turns Monitoring From “What Now?” Into “What’s Next?” How SAP achieved world-class uptime through modern observability How to Monitor AI Agents in Commerce Systems
Agentic AI: Powerful But Fragile—What You Need to Know
2026-05-31 · via Catchpoint Blog

in this blog post

Just when you’d finally wrapped your head around AI, here comes its autonomous cousin, Agentic AI. Think of it as AI that doesn’t just assist, but acts. It makes decisions, handles tasks, and communicates with other systems on its own. While it’s revolutionizing supply chains and customer experiences, there’s a catch. These autonomous agents rely on a plethora of third-party services, and when one fails, everything stops.

A study of eCommerce companies revealed that 88% of respondents lost more than $100,000 in a month due to Internet disruptions. The risk grows as Agentic AI expands, with each dependency multiplying the chance of downtime. When AI fails, operations halt, revenues drop, and reputations suffer.

So, how do you harness the power of agentic AI without the risk of it all crumbling when one link in the chain breaks? The answer is simple: visibility. Let’s break down why knowing what’s happening behind the scenes is crucial.

The promise of autonomy

Traditional AI systems often rely on human oversight for decision-making. Agentic AI goes a step further—these autonomous agents handle tasks, make decisions, and interact with external systems on their own. From automating supply chains to personalizing customer service, the potential is huge. But here's the catch: these agents depend on a network of external services, and even a small disruption in one service can bring everything to a halt. When the chain breaks, the fallout is immediate and far-reaching.

The hidden pitfalls of Agentic AI

Recent AI outages have shown us just how fragile interconnected technology can be. Agentic AI agents pull data from multiple external services, each of which introduces a new point of failure. When something goes wrong, pinpointing the issue isn’t simple—it requires end-to-end visibility, which most monitoring tools simply can’t provide. Without it, you’re left in the dark, trying to diagnose the problem as everything grinds to a halt.

Here’s where teams get stuck:

  • They know their AI-driven service is failing or running slowly.
  • They don’t know whether the problem is internal, with the AI provider, or buried somewhere in the network path.

Consider a financial services firm relying on AI-powered agents to handle customer inquiries about transactions and investments. These agents depend on several critical components, as shown in the diagram below.  

A diagram of a chatbotAI-generated content may be incorrect., Picture

A single user request triggers a complex chain of dependencies

When an agent requests data from an external service, it triggers a chain of events—each action between agents and systems increasing the complexity. If one of these services fails, the entire process can grind to a halt, leaving customers without support. For businesses, especially in sensitive industries like finance, this can quickly erode trust and push clients toward competitors.

This is why visibility matters: if you can't pinpoint where the failure occurred—whether inside your infrastructure, with the AI provider, or within the network path—you can't fix it quickly. And in industries like finance, every minute of downtime can result in lost revenue and significant reputational damage.

Without a unified view of AI agent dependencies, recovery is slow and costly, leading to inefficient war-room sessions and increasing frustration—both internally and among customers who rely on seamless service.

Building resilient Agentic AI: Key capabilities and practical steps

To protect your agentic AI systems from disruptions, it’s essential to have the right capabilities in place for proactive monitoring. This includes understanding your AI dependencies and being able to identify where failures might emerge across the entire technology stack. Without this visibility, teams may struggle to pinpoint the root cause of issues, leading to slower recovery times and greater customer impact.

Here’s how you can build these capabilities and put them into action:

  1. Map your AI dependencies
    Start by mapping all the dependencies your AI agents rely on. Ideally, you want to visualize every microservice, API, content delivery network (CDN), and DNS route in a simple, interactive, real-time map. This gives you a live view of the entire ecosystem your AI depends on, enabling you to immediately identify issues that impact performance. By having a comprehensive view of these external services, you can quickly diagnose problems, improving both Mean Time to Identify (MTTI) and Mean Time to Repair (MTTR).

A screenshot of a computerAI-generated content may be incorrect., Picture

Catchpoint’s Internet Stack Map
  1. Monitor continuously
    Ensure your AI systems perform seamlessly by implementing continuous internet performance monitoring. With real-time, proactive monitoring, you can simulate user journeys and detect anomalies before they escalate into major issues. This allows you to monitor every layer of your internet stack, ensuring uninterrupted performance.  

A blue and purple chart with iconsAI-generated content may be incorrect., Picture

The Internet Stack

By staying ahead of potential disruptions, you can quickly pinpoint problems and maintain optimal service availability, minimizing downtime and improving the user experience.

  1. Leverage automation tools for end-to-end workflow testing
    Use automation tools like Playwright to simulate real user interactions across complete workflows. This includes tasks such as adding products to the cart, checking out, and engaging with AI-powered agents. By scripting these processes, you can simulate user behavior, ensuring that the AI performs as expected. This capability allows you to identify friction points or performance issues before they impact the user experience, helping you address potential disruptions proactively.

Picture 1, Picture

End-to-end testing workflow with Playwright in Catchpoint
  1. Plan for Failover
    In case a critical AI service fails, do you have a fallback plan in place? Whether it’s switching to a backup model or queueing tasks until service is restored, having a well-defined failover strategy is essential for minimizing the impact of outages.
  1. Review Performance Data Regularly
    Don’t wait for an outage to force your hand. Schedule routine performance reviews of your AI dependencies to spot patterns or subtle issues—such as increasing response times or occasional timeouts—that may indicate underlying problems.

By combining these capabilities with actionable steps, you can ensure your Agentic AI systems remain resilient, proactive, and capable of minimizing downtime. With a clear understanding of your AI workflows and ongoing monitoring in place, you’ll be prepared to manage disruptions and keep your services running smoothly—staying ahead of the next AI meltdown.

Ready to safeguard your agentic AI?
Get a clear view of your AI dependencies with Internet Stack Map and start monitoring what matters.

Schedule a chat

Summary

Just when you’d finally wrapped your head around AI, here comes its autonomous cousin, Agentic AI. Think of it as AI that doesn’t just assist, but acts. It makes decisions, handles tasks, and communicates with other systems on its own. While it’s revolutionizing supply chains and customer experiences, there’s a catch. These autonomous agents rely on a plethora of third-party services, and when one fails, everything stops.

A study of eCommerce companies revealed that 88% of respondents lost more than $100,000 in a month due to Internet disruptions. The risk grows as Agentic AI expands, with each dependency multiplying the chance of downtime. When AI fails, operations halt, revenues drop, and reputations suffer.

So, how do you harness the power of agentic AI without the risk of it all crumbling when one link in the chain breaks? The answer is simple: visibility. Let’s break down why knowing what’s happening behind the scenes is crucial.

The promise of autonomy

Traditional AI systems often rely on human oversight for decision-making. Agentic AI goes a step further—these autonomous agents handle tasks, make decisions, and interact with external systems on their own. From automating supply chains to personalizing customer service, the potential is huge. But here's the catch: these agents depend on a network of external services, and even a small disruption in one service can bring everything to a halt. When the chain breaks, the fallout is immediate and far-reaching.

The hidden pitfalls of Agentic AI

Recent AI outages have shown us just how fragile interconnected technology can be. Agentic AI agents pull data from multiple external services, each of which introduces a new point of failure. When something goes wrong, pinpointing the issue isn’t simple—it requires end-to-end visibility, which most monitoring tools simply can’t provide. Without it, you’re left in the dark, trying to diagnose the problem as everything grinds to a halt.

Here’s where teams get stuck:

  • They know their AI-driven service is failing or running slowly.
  • They don’t know whether the problem is internal, with the AI provider, or buried somewhere in the network path.

Consider a financial services firm relying on AI-powered agents to handle customer inquiries about transactions and investments. These agents depend on several critical components, as shown in the diagram below.  

A diagram of a chatbotAI-generated content may be incorrect., Picture

A single user request triggers a complex chain of dependencies

When an agent requests data from an external service, it triggers a chain of events—each action between agents and systems increasing the complexity. If one of these services fails, the entire process can grind to a halt, leaving customers without support. For businesses, especially in sensitive industries like finance, this can quickly erode trust and push clients toward competitors.

This is why visibility matters: if you can't pinpoint where the failure occurred—whether inside your infrastructure, with the AI provider, or within the network path—you can't fix it quickly. And in industries like finance, every minute of downtime can result in lost revenue and significant reputational damage.

Without a unified view of AI agent dependencies, recovery is slow and costly, leading to inefficient war-room sessions and increasing frustration—both internally and among customers who rely on seamless service.

Building resilient Agentic AI: Key capabilities and practical steps

To protect your agentic AI systems from disruptions, it’s essential to have the right capabilities in place for proactive monitoring. This includes understanding your AI dependencies and being able to identify where failures might emerge across the entire technology stack. Without this visibility, teams may struggle to pinpoint the root cause of issues, leading to slower recovery times and greater customer impact.

Here’s how you can build these capabilities and put them into action:

  1. Map your AI dependencies
    Start by mapping all the dependencies your AI agents rely on. Ideally, you want to visualize every microservice, API, content delivery network (CDN), and DNS route in a simple, interactive, real-time map. This gives you a live view of the entire ecosystem your AI depends on, enabling you to immediately identify issues that impact performance. By having a comprehensive view of these external services, you can quickly diagnose problems, improving both Mean Time to Identify (MTTI) and Mean Time to Repair (MTTR).

A screenshot of a computerAI-generated content may be incorrect., Picture

Catchpoint’s Internet Stack Map
  1. Monitor continuously
    Ensure your AI systems perform seamlessly by implementing continuous internet performance monitoring. With real-time, proactive monitoring, you can simulate user journeys and detect anomalies before they escalate into major issues. This allows you to monitor every layer of your internet stack, ensuring uninterrupted performance.  

A blue and purple chart with iconsAI-generated content may be incorrect., Picture

The Internet Stack

By staying ahead of potential disruptions, you can quickly pinpoint problems and maintain optimal service availability, minimizing downtime and improving the user experience.

  1. Leverage automation tools for end-to-end workflow testing
    Use automation tools like Playwright to simulate real user interactions across complete workflows. This includes tasks such as adding products to the cart, checking out, and engaging with AI-powered agents. By scripting these processes, you can simulate user behavior, ensuring that the AI performs as expected. This capability allows you to identify friction points or performance issues before they impact the user experience, helping you address potential disruptions proactively.

Picture 1, Picture

End-to-end testing workflow with Playwright in Catchpoint
  1. Plan for Failover
    In case a critical AI service fails, do you have a fallback plan in place? Whether it’s switching to a backup model or queueing tasks until service is restored, having a well-defined failover strategy is essential for minimizing the impact of outages.
  1. Review Performance Data Regularly
    Don’t wait for an outage to force your hand. Schedule routine performance reviews of your AI dependencies to spot patterns or subtle issues—such as increasing response times or occasional timeouts—that may indicate underlying problems.

By combining these capabilities with actionable steps, you can ensure your Agentic AI systems remain resilient, proactive, and capable of minimizing downtime. With a clear understanding of your AI workflows and ongoing monitoring in place, you’ll be prepared to manage disruptions and keep your services running smoothly—staying ahead of the next AI meltdown.

Ready to safeguard your agentic AI?
Get a clear view of your AI dependencies with Internet Stack Map and start monitoring what matters.

Schedule a chat

This is some text inside of a div block.

You might also like

SRE Report 2026: What surprised us, what didn't, and why the gaps matter most

The SRE Report 2026: Defensible Ns

Why Synthetic Tracing Delivers Better Data, Not Just More Data