Checkly

Control who sees your status pages! 🔒 Checkly status pages now support password protection, so you can share service health with the right audience without exposing it publicly. Great for internal teams, partners, or select customers -> hubs.ly/Q04cjbZy0

50% of Checkly CLI users are agents. Stefan Judis just showed what that looks like: full monitoring setup + incident lifecycle, both handled by an agent through the terminal. Watch now: hubs.ly/Q04cj4k40

Same Playwright tests, same code — running locally, in CI, and as production monitors with `npx checkly deploy`. @stefanjudis showed how: hubs.ly/Q049pxg60

On Tuesday: Stefan Judis demos a full incident lifecycle handled by an agent through the Checkly CLI. No dashboards, no context switching — one agent conversation. Save your spot → hubs.ly/Q049_3yj0

Your agent deployed the code. Can it manage the monitoring too? Stefan Judis is demoing how the Checkly CLI became a first-class interface for AI agents, from onboarding a new Checkly setup in one conversation to resolving incidents end-to-end. Tuesday, April 14 — 6 PM CEST | 12 PM EST | 9 AM PST Register → hubs.ly/Q049_8xl0

When your website generates hundreds of millions a year, you can't afford blind spots. Use synthetic monitoring to catch errors before your users do. That's how Puma keeps running around the clock. 👉 hubs.ly/Q0493XbW0

One config for local, CI, and production Playwright environments. No duplication, no per-env config files. New guide covers the full pattern from simple toggles to fixture-based setups: hubs.ly/Q049qbqF0

Your agent deployed the code. Can it manage the monitoring? Next Tuesday: we'll demo how the Checkly CLI became a first-class agent interface. Save your spot → hubs.ly/Q049S4rW0

"E2E tests are flaky" — usually the app is. @stefanjudis showed three one-line fixes for the most common Playwright flake patterns: hubs.ly/Q049py-F0

Six Playwright myths, busted with live code. Flakiness, speed, production monitoring, AI test generation — @stefanjudis covered all of it. Recording is up: hubs.ly/Q049pxcm0

Puma is a 24/7 global revenue machine worth hundreds of millions a year. Every minute of downtime is expensive. Here's how Checkly helps keep it running. hubs.ly/Q0493Hb-0

Claude wrote a Checkly DNS monitor. The check failed. Rocky AI analyzed the trace route and found the root cause. Full loop from coding agent to AI debugging, live in 30 min: hubs.ly/Q047hFtw0

On March 31, Stefan is running a live session to tackle Playwright and E2E testing myths head-on. Direct answers, rapid-fire, with code. Link in the reply.

@rootlyhq @cloudsmith @PulumiCorp @embracemobile @TwingateHQ @kusaridev @jjrichardtang We had a great time, perfect kick-off for the KubeCon!

KubeCon, darts, DJs, and 300+ DevOps, SREs, and Platform Engineers! An evening where new people + new environment = ideas you won't find in any Slack thread. Big shoutout to @rootlyhq, @cloudsmith, @PulumiCorp, @embracemobile, @TwingateHQ, @checklyHQ, and @kusaridev for making this night as fun as it was!

Stefan Judis is myth-busting Playwright and E2E testing live next week: If you've ever debated whether E2E tests are "worth it" or whose job monitoring is, this is the session. 📆 March 31 🕙 6PM CEST - 12PM EDT - 9AM PDT 🔗 hubs.ly/Q046v_Fq0

A network check fails. Instead of digging through trace routes manually, Rocky AI reads the failure, explains what went wrong, and flags the broken assertion. Daniel Paulus demoed this live: AI that actually understands network diagnostics, not just summarizes logs. Full session: hubs.ly/Q047hHT-0

Amsterdam tomorrow 👋 KubeCon EU, booth 1185. Come say hi, we'll be demoing how teams ship monitoring the same way they ship code. Two events this week if you want to catch us off the expo floor: - Kick-off the week with us tomorrow: hubs.ly/Q0468_GL0 - Unwind after the show on Tuesday: hubs.ly/Q0468-Cn0 👉 All the info here: hubs.ly/Q046912y0

DNS monitoring in 60 seconds. Daniel Paulus creates a DNS monitor from scratch, picks a record type, fires a query, and reads the response in the Checkly UI. No YAML, no config files, no 30-page setup guide. Just point it at a domain and go. Next-up: configure it in code -> hubs.ly/Q047hGDs0

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