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

推荐订阅源

让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
人人都是产品经理
人人都是产品经理
Cisco Talos Blog
Cisco Talos Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
V
V2EX
博客园 - 三生石上(FineUI控件)
Martin Fowler
Martin Fowler
WordPress大学
WordPress大学
D
Docker
S
SegmentFault 最新的问题
博客园 - 聂微东
美团技术团队
Apple Machine Learning Research
Apple Machine Learning Research
月光博客
月光博客
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Last Week in AI
Last Week in AI
M
MIT News - Artificial intelligence
F
Fortinet All Blogs
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
The GitHub Blog
The GitHub Blog
GbyAI
GbyAI
L
LangChain Blog
Vercel News
Vercel News
博客园 - 叶小钗
MongoDB | Blog
MongoDB | Blog
Stack Overflow Blog
Stack Overflow Blog
H
Help Net Security
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
The Cloudflare Blog
Engineering at Meta
Engineering at Meta
T
Threat Research - Cisco Blogs
T
Threatpost
Scott Helme
Scott Helme
T
Tailwind CSS Blog
Latest news
Latest news
Stack Overflow Blog
Stack Overflow Blog
Blog — PlanetScale
Blog — PlanetScale
The Register - Security
The Register - Security
罗磊的独立博客
P
Proofpoint News Feed
腾讯CDC
S
Schneier on Security
雷峰网
雷峰网
A
About on SuperTechFans
T
Tenable Blog
F
Full Disclosure
Cyberwarzone
Cyberwarzone
博客园_首页
有赞技术团队
有赞技术团队
K
Kaspersky official blog

Catchpoint Blog

SRE Report: AI optimism and the economics of effort SRE Report: Why fast is what users trust The SRE Report 2026: Defensible Ns SRE Report 2026: What surprised us, what didn't, and why the gaps matter most 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 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 Agentic AI: Powerful But Fragile—What You Need to Know Demystifying API Monitoring and Testing with IPM Cloudflare outage: another wake-up call for resilience planning Cloudflare’s Resolver Outage: More Than Just DNS Cloud Monitoring's Blind Spot: The User Perspective Connected Devices: Unlocking the next frontier of Internet Performance Monitoring Consolidation and Modernization in Enterprise Observability Catchpoint named a leader in the 2024 Gartner® Magic Quadrant™ for Digital Experience Monitoring Catchpoint Peak Performance Summit 2025: Redefining Observability for the Outcome Economy Catchpoint Expands Observability Network to Barcelona: A Growing Internet Hub Catch frustration before it costs you: New tools for a better user experience Creating the IPM Category: Catchpoint’s Journey to Leadership and the LogicMonitor Era AWS Outage: How do you prepare for the failure of your own safety net? Achieving stability with agility in your CI/CD pipeline APM vs Observability: Observing beyond APM APM vs Observability: What comes next? APM vs observability: why your definitions are broken AppAssure: Ensuring the resilience of your Tier-1 applications just became easier APM vs Observability: Both-and, not either-or 2024: A banner year for Internet Resilience 5 Actions you can take to improve digital performance Fast and furious: The importance of performance in the digital age How SAP achieved world-class uptime through modern observability How AI Turns Monitoring From “What Now?” Into “What’s Next?” How IPM helped a top tech brand catch an OpenAI outage before it became a crisis Google’s Agent-to-Agent (A2A) Protocol is here—Now Let’s Make it Observable Here’s the proof: What the fastest sites on the web have in common Going for gold: Testing the resilience of Olympic websites From SEO to AEO: Why Web Performance Is the Key to AI Search Success From the source to the edge: the six agent types you can’t ignore Getting Started with Traceroute How to Monitor AI Agents in Commerce Systems From refresh to results: the metrics that shaped Election Day 2024 coverage Escalating risk, shrinking margins: The 2025 Internet Resilience Report Don’t get caught in the dark: Lessons from a Lumen & AWS micro-outage ECN explained: Navigate congestion for faster, smoother data delivery DNS misconfiguration can happen to anyone - the question is how fast can you detect it? Diagnosing Wi-Fi failures that traditional tools miss: a case study Did Delta's slow web performance signal trouble before CrowdStrike? Customer Survey 2024: Unveiling insights and impact Critical Requirements for Modern API Monitoring
When AI tools fail: How to map your AI dependencies for proactive visibility
2025-03-04 · via Catchpoint Blog

AI platforms have experienced several service interruptions over the past few months.

A screenshot of a social media postAI-generated content may be incorrect.

We’ve all seen the memes fly when ChatGPT, Gemini or Perplexity go down. They’re funny at first, but then reality hits: if you rely on AI tools for work or business, these outages can grind your day to a halt. And it’s not just a glitch here or there— there’s a clear pattern of AI services failing across different platforms:

  • February 5-6, 2025: Google’s Gemini experienced a 23-hour disruption that affected the "Add File" and "Link File" functionalities within Gems. The outage prevented users from attaching files to their AI-driven workflows. Users had no workaround, leading to productivity loss for businesses relying on Gemini’s file-processing capabilities.
  • January 23, 2025: ChatGPT and several OpenAI APIs suffered elevated error rates, with users encountering "bad gateway" errors. Businesses relying on ChatGPT for automation, customer service, and content generation were left scrambling
  • January 23, 2025: Perplexity’s API experienced a major outage, causing timeouts and disruptions for applications relying on its AI capabilities.  
  • December 26, 2024: A host of OpenAI services (ChatGPT, Sora video creation, plus agents, realtime speech, batch, and DALL-E APIs) suffered error rates north of 90%.
  • June 4, 2024: On this day, multiple AI platforms, including OpenAI's ChatGPT, Anthropic's Claude, and Perplexity, experienced simultaneous outages. Users worldwide reported disruptions, leading to widespread discussions on social media platforms.

We’ve officially hit a point where our dependence on AI is no longer just a possibility; it’s an absolute. When these systems fail, we’re left scrambling. The real question is: how do you stay ahead of the next failure?

The revenue impact of AI outages

The numbers are big and growing bigger: in 2025, global AI investments are set to exceed $500 billion. For many companies, AI apps like ChatGPT aren’t optional anymore—they’re mission-critical. Gartner reports that 70% of enterprises now use large language models (LLMs) for everyday tasks like automated customer service, marketing personalization, and real-time data crunching.

When these AI systems go offline, it’s not just a minor inconvenience. In finance, a few hours of AI downtime could mean millions lost due to missed trades or undetected fraud. In eCommerce, chatbots and recommendation engines going dark mean abandoned shopping carts and fewer conversions, which translates to real money left on the table.

But the damage doesn’t stop at lost revenue. Companies increasingly rely on AI-powered automation to streamline workflows, meaning that outages force employees to revert to manual processes, significantly slowing down productivity. This is particularly evident in customer support, where AI chatbots handle vast volumes of inquiries. If an outage forces companies to fall back on human agents, call center queues expand, increasing response times and leading to diminished customer satisfaction.

If you’re concerned about the impact of AI outages on your business, now is the time to evaluate your AI dependencies and invest in tools that can help you stay ahead of disruptions.

The need for visibility: Mapping your AI dependencies  

Even with the best monitoring strategies in place, AI outages present a unique challenge: You may know something is broken, but not necessarily where or why. To accurately pinpoint issues, you need tools that enable you to get actionable insights into your AI dependencies—whether they originate in the application layer or the underlying Internet Stack.  

eCommerce AI dependencies: A case study

Consider an eCommerce company relying on an AI-powered chatbot for customer support. It relies on several key components to deliver a seamless shopping experience:

  • Front-end CDN: Ensures fast content delivery to users.
  • Distributed Hyperscaler: Acts as the origin server for dynamic content.
  • Search and Seller APIs: Retrieve relevant product data for users.
  • Chatbot Powered by OpenAI API: Handles customer inquiries and provides real-time support.

The chatbot is a critical part of the customer support workflow. When a shopper interacts with the chatbot, their request is forwarded to an external API, which then interacts with the OpenAI API to generate a response. This means the chatbot’s functionality is entirely dependent on the OpenAI API.

A white rectangular sign with black textAI-generated content may be incorrect.

Flow diagram depicting the interaction between a user, an external API, and OpenAI's API in an e-commerce chatbot system

If the OpenAI API experiences an outage, the chatbot fails, leaving customers without support. This not only frustrates users but can also lead to lost sales and damaged customer relationships.

How to map AI dependencies and stay ahead of outages

In the eCommerce example above, the chatbot’s dependency on the OpenAI API highlights the importance of mapping AI dependencies. When outages occur, knowing exactly where the failure lies can mean the difference between minutes of downtime and hours of lost revenue. By mapping your AI dependencies, you can quickly identify the root cause of outages, reducing downtime and minimizing revenue loss. Here's how:

#1 Visualize your AI dependencies

Start by creating a map of all the services and APIs your AI tools rely on. For example, if your chatbot depends on OpenAI’s API, you need to include it in your dependency map. Tools like Internet Stack Map can help you visualize these connections, making it easier to pinpoint where failures occur when an outage happens.

Internet Stack Map view

In the example above, the Internet Stack Map view of our eCommerce case study shows all other services are working as expected, except for the OpenAI API (highlighted in red), which impacts chatbot interactions.

#2 Customize your workflow

Every AI system is unique, so your dependency map should reflect your specific architecture. Identify key components like CDNs, DNS providers, and origin servers, and ensure they’re included in your map. This customization ensures you’re prepared to troubleshoot issues that are specific to your setup.

#3 Correlate data for faster insights

Use monitoring tools that combine synthetic testing with real-time outage data. By correlating this data, you can quickly determine whether an issue is with your AI provider (e.g., OpenAI) or your own infrastructure. This reduces the time spent diagnosing problems, helps you avoid unnecessary war rooms and saves you money.

Faster resolution, fewer disruptions

AI outages remind us how vulnerable we are in this interconnected world. When these systems fail, every minute counts—particularly if you’re losing revenue or driving customers away. That’s why Internet Stack Map, recently updated with a groundbreaking user interface, is a game-changer for incident response. It offers immediate clarity about what broke and where, shrinking your Mean Time to Identify (MTTI) and Mean Time to Resolve (MTTR).  

See how Internet Stack Map can help you stay ahead of disruptions—schedule a demo today.

Learn more

Summary

AI platforms have experienced several service interruptions over the past few months.

A screenshot of a social media postAI-generated content may be incorrect.

We’ve all seen the memes fly when ChatGPT, Gemini or Perplexity go down. They’re funny at first, but then reality hits: if you rely on AI tools for work or business, these outages can grind your day to a halt. And it’s not just a glitch here or there— there’s a clear pattern of AI services failing across different platforms:

  • February 5-6, 2025: Google’s Gemini experienced a 23-hour disruption that affected the "Add File" and "Link File" functionalities within Gems. The outage prevented users from attaching files to their AI-driven workflows. Users had no workaround, leading to productivity loss for businesses relying on Gemini’s file-processing capabilities.
  • January 23, 2025: ChatGPT and several OpenAI APIs suffered elevated error rates, with users encountering "bad gateway" errors. Businesses relying on ChatGPT for automation, customer service, and content generation were left scrambling
  • January 23, 2025: Perplexity’s API experienced a major outage, causing timeouts and disruptions for applications relying on its AI capabilities.  
  • December 26, 2024: A host of OpenAI services (ChatGPT, Sora video creation, plus agents, realtime speech, batch, and DALL-E APIs) suffered error rates north of 90%.
  • June 4, 2024: On this day, multiple AI platforms, including OpenAI's ChatGPT, Anthropic's Claude, and Perplexity, experienced simultaneous outages. Users worldwide reported disruptions, leading to widespread discussions on social media platforms.

We’ve officially hit a point where our dependence on AI is no longer just a possibility; it’s an absolute. When these systems fail, we’re left scrambling. The real question is: how do you stay ahead of the next failure?

The revenue impact of AI outages

The numbers are big and growing bigger: in 2025, global AI investments are set to exceed $500 billion. For many companies, AI apps like ChatGPT aren’t optional anymore—they’re mission-critical. Gartner reports that 70% of enterprises now use large language models (LLMs) for everyday tasks like automated customer service, marketing personalization, and real-time data crunching.

When these AI systems go offline, it’s not just a minor inconvenience. In finance, a few hours of AI downtime could mean millions lost due to missed trades or undetected fraud. In eCommerce, chatbots and recommendation engines going dark mean abandoned shopping carts and fewer conversions, which translates to real money left on the table.

But the damage doesn’t stop at lost revenue. Companies increasingly rely on AI-powered automation to streamline workflows, meaning that outages force employees to revert to manual processes, significantly slowing down productivity. This is particularly evident in customer support, where AI chatbots handle vast volumes of inquiries. If an outage forces companies to fall back on human agents, call center queues expand, increasing response times and leading to diminished customer satisfaction.

If you’re concerned about the impact of AI outages on your business, now is the time to evaluate your AI dependencies and invest in tools that can help you stay ahead of disruptions.

The need for visibility: Mapping your AI dependencies  

Even with the best monitoring strategies in place, AI outages present a unique challenge: You may know something is broken, but not necessarily where or why. To accurately pinpoint issues, you need tools that enable you to get actionable insights into your AI dependencies—whether they originate in the application layer or the underlying Internet Stack.  

eCommerce AI dependencies: A case study

Consider an eCommerce company relying on an AI-powered chatbot for customer support. It relies on several key components to deliver a seamless shopping experience:

  • Front-end CDN: Ensures fast content delivery to users.
  • Distributed Hyperscaler: Acts as the origin server for dynamic content.
  • Search and Seller APIs: Retrieve relevant product data for users.
  • Chatbot Powered by OpenAI API: Handles customer inquiries and provides real-time support.

The chatbot is a critical part of the customer support workflow. When a shopper interacts with the chatbot, their request is forwarded to an external API, which then interacts with the OpenAI API to generate a response. This means the chatbot’s functionality is entirely dependent on the OpenAI API.

A white rectangular sign with black textAI-generated content may be incorrect.

Flow diagram depicting the interaction between a user, an external API, and OpenAI's API in an e-commerce chatbot system

If the OpenAI API experiences an outage, the chatbot fails, leaving customers without support. This not only frustrates users but can also lead to lost sales and damaged customer relationships.

How to map AI dependencies and stay ahead of outages

In the eCommerce example above, the chatbot’s dependency on the OpenAI API highlights the importance of mapping AI dependencies. When outages occur, knowing exactly where the failure lies can mean the difference between minutes of downtime and hours of lost revenue. By mapping your AI dependencies, you can quickly identify the root cause of outages, reducing downtime and minimizing revenue loss. Here's how:

#1 Visualize your AI dependencies

Start by creating a map of all the services and APIs your AI tools rely on. For example, if your chatbot depends on OpenAI’s API, you need to include it in your dependency map. Tools like Internet Stack Map can help you visualize these connections, making it easier to pinpoint where failures occur when an outage happens.

Internet Stack Map view

In the example above, the Internet Stack Map view of our eCommerce case study shows all other services are working as expected, except for the OpenAI API (highlighted in red), which impacts chatbot interactions.

#2 Customize your workflow

Every AI system is unique, so your dependency map should reflect your specific architecture. Identify key components like CDNs, DNS providers, and origin servers, and ensure they’re included in your map. This customization ensures you’re prepared to troubleshoot issues that are specific to your setup.

#3 Correlate data for faster insights

Use monitoring tools that combine synthetic testing with real-time outage data. By correlating this data, you can quickly determine whether an issue is with your AI provider (e.g., OpenAI) or your own infrastructure. This reduces the time spent diagnosing problems, helps you avoid unnecessary war rooms and saves you money.

Faster resolution, fewer disruptions

AI outages remind us how vulnerable we are in this interconnected world. When these systems fail, every minute counts—particularly if you’re losing revenue or driving customers away. That’s why Internet Stack Map, recently updated with a groundbreaking user interface, is a game-changer for incident response. It offers immediate clarity about what broke and where, shrinking your Mean Time to Identify (MTTI) and Mean Time to Resolve (MTTR).  

See how Internet Stack Map can help you stay ahead of disruptions—schedule a demo today.

Learn more

This is some text inside of a div block.