Operations | Monitoring | ITSM | DevOps | Cloud

Join, Ankit and Leon as they explore recent articles about: The current state of the AI bubble; the compelling evidence for a 4-day workweek; the enduring legacy of and nostalgia for CDs;

However, your customers still expect a flawless experience, every time. The complexity of modern architectures (CDNs, DNS, APIs, cloud platforms) means that even “simple” applications can break in ways you don’t see coming. So how do you stay ahead of issues you don’t even own? By monitoring the digital delivery chain as your users experience it, across networks, geographies, and third-party dependencies, and catching performance degradations before they become business problems.

When a site disruption hits, businesses face immediate and visible fallout: customer churn spikes, and revenue takes a direct hit. If customers can’t transact, your bottom line suffers, plain and simple. This insight comes from a recent Forrester survey commissioned by Catchpoint, where respondents revealed the real business impacts of Internet disruptions.

Join, Payal, Denton, and Leon as they explore recent articles about AOL Dialup services, AI agents, ISP throttling, and what the heck is McDonald’s “Grimace” anyway?

Not from your data center. Not from your internal network. Not from your controlled environments. Real users are on hotel Wi-Fi, public LTE, spotty networks, global cloud providers. To understand their experience, your monitoring needs to reflect their reality: location, device, network, context.

Users are mobile. Apps are elastic. Traffic shifts constantly across clouds, ISPs, and geographies. Monitoring needs to adapt to that reality. You need visibility that moves with your users and your applications, wherever they go, however they connect. The Internet is now your application fabric. And your monitoring strategy should reflect that!

What do you do if your monitoring, APM, and synthetic tools tell you an application is up, but the users say it’s not? A good first question is to ask where your monitoring tools are located relative to both the users and the application itself. In this episode Mursi helps Leon identify his “red-light, green light” issue and adjust his monitoring to do a better job showing the REAL user’s experience.

This month, Leon breaks down the new Internet Resilience Report, enhancements to Catchpoint’s API monitoring suite, and some of the reasons for replacing selenium with Playwright and Puppeteer as Catchpoint’s web test scripting tool. In the “New to You” segment, he reviews SSL certificate monitoring.

Behind the Dashboard is an ongoing series where we look under the hood of a specific Catchpoint feature. Each episode breaks down the technology itself, what’s challenging about using it for monitoring, and how we removed friction and toil to make it a valuable part of the Catchpoint platform. In this episode Leon, Brandon, and Sergey take a look at “traceroute” tests – a feature that may seem humble and unassuming, but has unexpected power and utility when it comes to identifying performance issues with your site, service, or application.

When a website stops working all of a sudden, it could be down, or it could be something more complex. In this episode Sheldon jumps in to help Leon figure out what’s going wrong with his livestream, where they discover an unexpected black hole.