Loading full navigation.

Autonomous IT is here. The alert loop ends now. LEARN MORE

Partners

Docs

LM Academy

LM Community

Pricing

Platform
Solution
Industry
Role
There is no result.

LOGICMONITOR BLOG

Catchpoint Is Now LogicMonitor Digital Experience

Catchpoint is now LogicMonitor Digital Experience. Co-founder Mehdi Daoudi reflects on the work connecting Internet and user experience visibility with LogicMonitor’s infrastructure insights, and how that progress advances the company’s Autonomous IT vision.

5–8 minutes
Mehdi Daoudi

NEWSLETTER

Subscribe to our newsletter

Get the latest blogs, whitepapers, eGuides, and more straight into your inbox.

SHARE

The quick download:

Catchpoint is now LogicMonitor Digital Experience

  • Nearly a year after the acquisition closed, the Catchpoint products carry the LogicMonitor name: one company, one platform, and the integrated experience we showed at Elevate Community Conference 2026.

  • Internal dashboards can look healthy while support tickets mount, which is why you need an outside view too.

  • That outside view comes from LogicMonitor Digital Experience’s four products, Synthetics, Real User Monitoring, Endpoint Monitoring and Internet Sonar, each showing a different angle on the same experience.

  • What’s next: LogicMonitor Digital Experience becomes the experience and Internet-context elements of our Autonomous IT platform, with Edwin AI connecting what users see to what is happening in the infrastructure, applications, and AI services behind it, so teams spend less time finding problems and more time fixing them.

Catchpoint is now LogicMonitor Digital Experience.

I’ve written the word Catchpoint on whiteboards, contracts, and slides for 17 years, and watching it change is not nothing. The name was never the point, though. Behind it was a question our customers kept asking, one CIOs still ask: what are my users experiencing right now, and why?

That question is why we joined LogicMonitor in December 2025. Since then, we’ve made progress connecting what users experience across the Internet with what LogicMonitor sees inside the infrastructure and applications that serve them. Digital Experience alerts can now feed into Edwin AI for correlation, and we’ve introduced no-code transaction testing to help teams more easily monitor critical journeys such as login and checkout. 

The LogicMonitor Digital Experience name reflects that work and our place within the broader LogicMonitor platform. Our mission carries forward: helping teams understand what their users are experiencing, why it is happening, and where to act.

Experience Extends Beyond Your Systems

When we started, teams already depended on networks and providers they didn’t own, but the list was shorter. Today a single login or checkout depends on DNS providers, CDNs, cloud regions, third-party APIs, SaaS platforms, ISPs, the model providers and inference endpoints behind every new AI feature, and the Wi-Fi in somebody’s kitchen. You own few of these dependencies, and visibility into them is limited. The median page on the 1,000 most popular sites makes 129 third-party requests, according to the 2025 Web Almanac.

That’s why application and infrastructure monitoring, as essential as they are, only tell part of the story. They tell you how the things you run are behaving. They don’t tell you what happened to the request on its way to the user, or what the user saw when it got there.

Internal monitoring shows the systems you run. Users experience the whole delivery chain.

I’ve watched versions of this play out in different ways over the years. In 2018, Box experienced broad service issues. Before it started testing from the customer’s side, it had a good view of its web app but little visibility into what customers experienced through its APIs. For a company that handles three to five billion public API calls per day, that’s a problem. 

A recent example went the other way: a global payments platform’s internal dashboards looked fine, but synthetic tests showed performance degradation in several regions. The outside view caught what the inside view missed. Many incidents need both. 

Connecting “our systems are up” to “our users are fine” has guided our work for 17 years. Since joining LogicMonitor, we’ve continued that work for longtime customers and extended it to more teams. Catchpoint is exceeding its targets year to date in 2026, reflecting continued demand for visibility into how Internet performance affects the experiences teams deliver.

Four Problems Customers Bring Us

LogicMonitor Digital Experience is the experience and Internet-context layer of the LogicMonitor platform. But customers don’t come to us for specific products or features. They come with a problem. Four show up again and again: 

  • Application resilience. Will checkout, login, and payment work right now, from everywhere our customers are, and what did real users actually experience when they got there?
  • Workforce productivity. Why is the workforce slow in Salesforce or M365 this morning, and is it the laptop, the corporate network, or the provider?
  • Internet performance. When something breaks between us and our users, is it us or them, and can we prove it to the ISP, CDN, or cloud provider we are paying? This is Internet Performance Monitoring, the use case Catchpoint helped define, and it continues as a core use case within Digital Experience.
  • AI service reliability. Are the model endpoints, inference APIs, and agent workflows our AI features depend on available and performing, from the places they are actually called?

All four rest on the same fact that IPM was built on: the Internet is a dependency of your production environment, and so, increasingly, are the AI services running on it. What carries forward is the way we see that dependency, from thousands of public and private vantage points, now connected to what LogicMonitor sees inside the environment.  

Four Views of the Same User Experience

Understanding experience means looking at it from several angles at once. The four products in LogicMonitor Digital Experience each give you one.

  • Synthetics tests the journeys that matter, from where your users are, around the clock, so teams can find failures before users report them. 
  • Real User Monitoring (RUM) shows what real users experienced across browsers, devices, and networks, including where they dropped off.
  • Endpoint Monitoring covers the employee’s laptop, home network, VPN, and the SaaS apps they’re trying to reach, so IT can see whether a problem starts with the device, the corporate network, or a provider. 
  • Internet Sonar provides professionally curated internet health data to track major providers and services, so teams can understand widespread disruptions without monitoring each provider themselves.

Each product shows a different perspective on the same user experience, and each of the four problems above draws on more than one of them. Connecting those perspectives, and connecting them to what is happening inside your infrastructure, is where the LogicMonitor platform comes in. 

Where Digital Experience Fits in Autonomous IT

For most of my career, outside-in and inside-out monitoring lived in separate worlds: different tools, different teams, different budgets, and too many incidents spent arguing about whose data was right. 

LogicMonitor is building toward Autonomous IT: a closed loop in which unified telemetry, business-aware context, AI-driven reasoning, and governed action operate as one system, not a collection of tools. Digital Experience is the experience and Internet-context layer of that system. LM Envision is the infrastructure foundation underneath it. And Edwin AI, LogicMonitor’s AI operating layer for IT operations, is becoming the front door teams use to investigate, prioritize, and respond across it all. That is one platform, not three products sharing a logo.  

Here is what that means for the teams I talk to. When experience degrades, whether for a customer at checkout, an employee using a SaaS tool, or an application calling a model API, the investigation starts from what the user saw. It follows the request across the Internet and correlates it with what is happening inside the environment, with Edwin AI guiding the next step within the controls the team sets. Less time arguing about whose data is right. More time fixing. 

AI workloads make this more urgent. Many AI features a company ships depend on model providers, inference endpoints, and agent workflows it doesn’t own, with latency and availability that vary by region and by hour. Those are Internet dependencies in exactly the same sense as a CDN or a payments API, and they need the same outside-in view: tested from where they are called, measured against what the user actually experienced, and correlated with the infrastructure behind them. We’ve taken the 3100+ global observability endpoints developed at Catchpoint and enhanced them to deliver real-time AI workload reliability insights for our customers. And this is an area where we will continue to invest. 

Catchpoint started because I got tired of finding out about outages from customers. That motivation hasn’t changed, and I’m glad to pursue it now with a much larger team. 

The opportunity ahead is bigger than a new name. It is about connecting what we know about what users experience with what LogicMonitor knows about the systems and services behind it, so teams can understand problems sooner, find their causes faster, and act on them with confidence. That is how IT leaders move from managing incidents to protecting growth. 

See your service the way your users do.

Whether it is a customer at checkout, an employee in a SaaS app, or an AI feature calling a model API, see what they actually experience and why. Explore how Synthetics, Real User Monitoring, Endpoint Monitoring, and Internet Sonar extend LogicMonitor beyond your infrastructure.

By Mehdi Daoudi

General Manager, LM Digital Experience

Mehdi Daoudi is Digital Experience GM at LogicMonitor, previously having been co-founder and CEO of Catchpoint. His experience in IT inspired him to build the digital experience platform he envisioned as a user. He spent more than ten years at Google and DoubleClick, where he was responsible for quality of services, buying, building, deploying, and using internal and external monitoring solutions to keep an eye on the DART infrastructure, which delivers billions of transactions a day.

Disclaimer: The views expressed on this blog are those of the author and do not necessarily reflect the views of LogicMonitor or its affiliates.

© LogicMonitor 2026 | All rights reserved. | All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Related Blogs

Optimizing Website Performance: Harnessing the Power of Image Lazy Loading
Blog Digital Experience

Optimizing Website Performance: Harnessing the Power of Image Lazy Loading

Image lazy loading can speed up your site, or slow it down. Learn how to apply it selectively, protect Core Web Vitals, and measure the real-world impact.
October 30, 2026
Learn more
Outage Retrospective: What a Google Cloud Incident Revealed About Hidden Service Dependencies
Blog Internet Performance Monitoring

Outage Retrospective: What a Google Cloud Incident Revealed About Hidden Service Dependencies

See how a Google Cloud outage took major brands like Home Depot offline, and why digital experience monitoring spots failures before status pages update.
October 30, 2026
Learn more
Outage Retrospective: How the Adobe Experience Cloud Outage Exposed Third-Party Blind Spots
Blog DevOps & CI/CD

Outage Retrospective: How the Adobe Experience Cloud Outage Exposed Third-Party Blind Spots

See how Internet-health signals, synthetic tests, and Real User Monitoring exposed third-party failures during the 2023 Adobe Experience Cloud outage, and how LogicMonitor Digital Experience connects those perspectives to help teams identify user impact and incident ownership.
October 30, 2026
Learn more