Six Months In: The Next Chapter of Internet Performance Monitoring at LogicMonitor

Just over six months ago, LogicMonitor and Catchpoint came together with a vision of building a better together self-healing enterprise. A slow checkout page doesn’t feel like an infrastructure issue to the shopper trying to complete a purchase. A SaaS application that freezes during the workday doesn’t arrive with a clean explanation of whether the issue started in the application, the network, a cloud service, a third party, or the user’s connection. Essentially, when performance drops, teams need to understand what’s happening inside the environment and what users are actually experiencing outside of it. 

That was the core reason LogicMonitor acquired Catchpoint. 

Six months later, that same customer pain is still guiding the work: helping IT teams connect infrastructure health with real-world internet and digital experience performance, so they can troubleshoot faster, reduce risk, and protect the digital services their businesses rely on.

Internet Performance Monitoring Momentum Since The Acquisition

Since the acquisition, LogicMonitor and Catchpoint integration has swiftly moved forward on two key tracks.

The first is a more connected customer experience. Today, customers who use both platforms can move between the two portals through a more seamless authentication experience. Catchpoint alert data can be sent to Edwin AI via REST APIs and webhooks for correlation. 

The second is continued product development across Catchpoint’s Internet Performance Monitoring capabilities.  Four 2026 releases delivered updates to IPM customers across synthetic testing, RUM, endpoint visibility, streaming, APIs, security, and administration.

Making Digital Experience Testing Easier to Scale

Internet Performance Monitoring only creates value when teams can test the journeys that matter. For many organizations, those journeys are getting more complex. A single transaction may cross internal systems, third-party APIs, identity providers, payment services, cloud infrastructure, and public internet routes before the user sees a result.

Recent Catchpoint releases have focused on making that testing easier to create and manage. The No-Code Transaction Test gives teams a browser-based recorder for critical user journeys. 

Teams can capture workflows without writing scripts, refine the journey in a visual editor, and export to Playwright when they need more control. That combination is critical because digital experience monitoring often needs both speed and depth. Some teams need to create coverage quickly, while others need the flexibility to adapt tests for more complex flows.

WebPageTest Instant Test improvements also help teams move faster. Updates make it easier to configure tests, choose device and connection combinations, review location capacity, manage security settings, and run tests in bulk. For authenticated workflows, WebPageTest credential script variables let teams store credentials separately and reference them as variables instead of hardcoding them into scripts.

The outcome is faster setup, safer authenticated testing, and a clearer path to coverage for the journeys that affect revenue, productivity, and customer trust.

Giving Teams Clearer Web Performance Signals

Performance data can get noisy quickly. Teams need enough detail to understand what’s happening, but they also need signals that help them prioritize.

That’s why we’re really excited about the recent change to Experience Score, which brings Lighthouse metrics into supported web tests, including Total Blocking Time, Largest Contentful Paint, Cumulative Layout Shift, First Contentful Paint, and Apdex. This update delivers something our customers have been asking for:  a clearer score that reflects both technical performance and user experience.

Web performance conversations often cross teams. Engineering may care about browser metrics, while operations may care about availability and response time. On the business side, leaders may care more about conversion, customer satisfaction, and risk. A clearer experience score gives those groups a more practical way to discuss the same problem.

Domain Breakdown in WebPageTest adds another layer of visibility by helping teams analyze the third-party domains involved in page load performance. For modern digital services, third-party dependencies can shape the user experience as much as owned infrastructure. 

Catchpoint has also added Core Web Vitals alerting across nodes, giving teams another way to track user-impacting performance patterns across a broader set of test results.

Expanding Visibility Across Users, Endpoints, and Streaming

User experience doesn’t stop at the web page. It includes the network path, the endpoint, the browser, the user’s location, and the type of digital service being delivered.

Catchpoint’s recent releases expand visibility across several of those areas. RUM Network Score helps teams distinguish application performance from the quality of the user’s network, making it easier to understand whether a poor experience came from the application itself or from conditions around the user.

Browser crash logging adds visibility into crashes that can disrupt the user experience, including cases where monitoring scripts may not fully load. Endpoint TCP Traceroute gives teams another way to analyze endpoint paths when ICMP is blocked, which is common in many enterprise environments.

Catchpoint has also added Streaming Test capabilities for HLS, DASH, and MP4 playback. Teams can monitor startup delay, play time, buffer time, and buffering events. For companies that depend on streaming media, training content, digital events, or video-based customer experiences, those metrics help teams understand whether playback quality is meeting expectations.

Together, these updates reflect a wider view of digital experience. Teams need to know whether services are reachable, whether pages are fast, whether transactions complete, whether endpoints have a clean path, and whether media experiences perform as expected.

Strengthening the Operational Foundation

Mature monitoring programs depend on security, automation, scale, and administration. Several recent Catchpoint updates strengthen that foundation.

Catchpoint CLI v1 and REST API v4 support gives teams a command-line way to work with REST API v4, currently in preview.

Rotational API keys improve API access management for teams embedding monitoring data and configuration into operational workflows.

Test-level proxy support with PAC files gives teams more control over how specific tests route traffic, which matters for complex network architectures, internal applications, and enterprise testing requirements.

Point Allocation redesign gives administrators clearer visibility into allocation health, usage trends, projected consumption, and contract capacity.

Native macOS Endpoint support for Intel and Apple Silicon, plus ARM support for Enterprise Node in preview, broadens deployment flexibility across modern environments.

These changes may read operational on paper, but they address real customer needs. Monitoring programs need to scale securely, integrate with automation workflows, support varied environments, and give administrators enough control to manage coverage responsibly.

Continued Investment In Internet Performance Monitoring

Six months after the acquisition, LogicMonitor is continuing to invest in Internet Performance Monitoring in tangible ways. The integration work is specific and active: seamless authentication between LogicMonitor and Catchpoint today, with deeper product alignment underway.

The IPM roadmap has also kept moving, with updates across test creation, authenticated workflows, web performance analysis, RUM, endpoint visibility, streaming coverage, APIs, and administration. For IT operations, SRE, network, and digital experience teams that means faster testing, clearer signals, broader visibility, and fewer blind spots when performance issues affect users and the business.