Checkly

If your team already writes Playwright tests, you're closer to production-grade synthetic monitoring than you think. At KubeCon EU next week, we're showing how Checkly turns your existing Playwright scripts into always-on monitors: running from 20+ locations, alerting on failures, integrated straight into your CI pipeline. 📍 Booth 1185, Amsterdam, March 23–26. 👉 All the info here: hubs.ly/Q04690Bv0

Your next prompt when using Checkly in the IDE? Create an ICMP monitor in Checkly for [your-hostname-or-ip]. Ping every minute from us-east-1 and eu-west-1. Set a degraded alert at 10% packet loss and a failure alert at 20% packet loss or average latency over 200ms. Ping any host. Track packet loss & latency across regions. Same CLI/Terraform/Pulumi you already use. Shipped last week 👇 hubs.ly/Q046g72b0

"Monitoring is something you add later, once the product is bigger." This one comes up a lot. And it gets the tradeoff backwards. When you have one critical user flow, that's the easiest time to add monitoring. One check, done in seconds. The cost of adding it later (more flows, more complexity, more fire drills) is always higher. @Stefan Judis is covering this and other Playwright myths on March 31. Short, to-the-point, live, with code to back every answer. Register now: hubs.ly/Q046v-KF0

Recording is up: Daniel Paulus set up DNS, TCP, and ICMP monitors live and deployed them as code from the terminal. 30 min, no slides. Check it out: hubs.ly/Q047hFKh0

Heading to Amsterdam for KubeCon EU? Come find us off the expo floor too. On 24.03, we're at The Boat House for a laid-back harbour evening to close out the week with the right crowd. If you've been wanting to connect but the booth isn't the right setting, this is it. 👉 Register → hubs.ly/Q046fPDc0

In Amsterdam for KubeCon EU? We are co-hosting a kickoff party with Rootly, Cloudsmith, Embrace, Kusari & Pulumi: retro gaming, karaoke, and conversations that actually happen when you take people off the expo floor. If you're landing before the conference starts, this is where to be: hubs.ly/Q046g5s30

We shipped ICMP monitoring in Checkly last week. Ping any host. Measure latency, packet loss, reachability, across 20+ regions. Define it as code (CLI, Terraform, Pulumi). Set assertions. Done. Changelog doc 👇 hubs.ly/Q046gjtd0

If you're going to KubeCon EU, here's how to make the most of the week: 🎮 Pre-conference: gaming + karaoke kickoff with Rootly AI, Cloudsmith, Embrace, Kusari & Pulumi → hubs.ly/Q04691Zl0 🌊 Post-conference: wind down at The Boat House with Rootly AI, Cloudsmith, MetalBear & Spotify for Backstage → hubs.ly/Q0468--N0 👉 All the info here: hubs.ly/Q04690MN0

Still manually triaging Playwright failures at 3 AM? Rocky AI now does it for you. Automatically. Failed check → AI root cause analysis → delivered to Slack/email/Teams. In seconds. Two toggles to enable. All plans. Live now: hubs.ly/Q045JQyM0

Tomorrow at 10AM PDT / 1PM EDT / 6 PM CET, Paulus is setting up DNS, TCP, and ICMP monitors live in less than 30 minutes. If you've ever written "root cause: networking" in a retro and then done nothing about it, this one's for you. Live attendees get our MaC prompt library + a Q&A that won't be on the recording. Register: hubs.ly/Q046T82l0

Quick one for your week planning: Daniel Paulus is running a shortlive session on Tuesday where he sets up DNS, TCP, and ICMP monitors from scratch and deploys them as code. If "root cause: networking" keeps showing up in your retros with zero follow-up, block 20 minutes on Tuesday. Live attendees get our MaC prompt library + a Q&A that won't be in the recording. --> hubs.ly/Q046k0QJ0

"E2E tests are flaky." "E2E tests are slow." "E2E tests are QA's job." "Monitoring comes later." Stefan Judis has heard every version of these: in conference Q&As, YouTube comments, Slack threads... The same myths keep circulating. On March 31, Stefan is running a live session to tackle Playwright and E2E testing myths head-on. Not "it depends" answers. Direct ones, with code. Register now: hubs.ly/Q046v-cN0

Last October, a DNS race condition took down Netflix, Slack, and 2,500 other companies for hours. The root cause? Not an attack. Just a networking layer nobody was watching closely enough. Most teams have solid application monitoring. But the layer between your infrastructure and your users - DNS propagation, TCP handshakes, packet loss - that's still the thing that shows up in retros as "root cause: networking" with no follow-up action. Next Tuesday (March 17), @Daniel Paulus is running a 22-minute live session on how to actually set up network monitoring — DNS, TCP, ICMP — and manage it all as code. No slide deck. Just live setup, real patterns, and the MaC prompts we use internally. Register here --> hubs.ly/Q046k0qx0

Are you going to Amsterdam for KubeCon EU? 🇳🇱 Before the conference kicks off, we're co-hosting a warm-up night with Rootly, Cloudsmith, Embrace, Kusari and Pulumi. Retro gaming, karaoke, and good company at a venue in the city. Best way to start the week: meet the people you'll be running into on the expo floor, except in a setting where no one's wearing a lanyard. Register here: hubs.ly/Q046k3G50

Next Tuesday we're spending 30 minutes on the protocols underneath: DNS, TCP, and ICMP. What you'll see: → DNS monitors that verify record propagation across nameservers → TCP checks for port connectivity and handshake validation → ICMP ping monitors for reachability, latency, and packet loss across regions → All three running inside private networks with Checkly private locations 🧠 Live demos, real config. Daniel Paulus (VP Engineering) walks through the setup. 📆 March 17 · 9 AM PST / 12 PM EDT / 6 PM CET · 30 min 🔗 hubs.ly/Q045K5GD0

We're heading to KubeCon + CloudNativeCon Europe 🎉 March 23–26 in Amsterdam - and Checkly will be there as a sponsor. If you're building, deploying, or operating cloud-native apps and want to talk monitoring as code, Playwright-based synthetic testing, or just what production reliability looks like in 2026, come find us at our booth. Drop a comment or DM if you'll be there. Would love to connect. 👉 More info here: hubs.ly/Q046k0h30

ICMP monitors are now live in Checkly 🎉 When something breaks: is the machine down, or is the service down? ICMP answers that in your first alert. Ping any host or IP. Measure reachability, latency, and packet loss. No extra tool needed. URL ✓ TCP ✓ DNS ✓ Heartbeat ✓ ICMP ✓ hubs.ly/Q046bsk_0

We're heading to KubeCon EU 🇳🇱 Find us at booth 1185in Amsterdam, March 23–26. We'll be showing how uptime monitoring and Playwright-based synthetic checks work together in a single platform, written in code, versioned with your stack. Come by for a live demo and a real conversation. 👉 More info here: hubs.ly/Q04690-D0

How do you monitor the network layer underneath your apps today? If the answer is "we don't, really", we're hosting a short session on March 17 to walk through exactly how to set low-level protocol checks up with Checkly's Monitoring as Code workflow. DNS, TCP, and our brand-new ICMP monitors. Plus private locations for internal hosts. Register (or grab the recording) here: hubs.ly/Q045K6qZ0

We codified our best engineer's debugging brain into an AI agent. Rocky AI now automatically runs root cause analysis the moment a check fails — and sends it to your Slack/email before you even wake up. Traces, screenshots, logs, code. All analyzed in seconds. Live today on all Checkly plans 👇 hubs.ly/Q045JG220