Over the past month, we’ve been building …

1-Second API Check Frequency is Now Available Upon Request to Enterprise Customers

Need to monitor an API with strict SLOs or high availability requirements? You can now run API checks every second—reach out to us to learn more or request access.

Checkly AI: Playwright Impact Analysis & Error Explainer in beta

We just released Checkly’s first two AI-assisted features in beta!

First up is Playwright Impact Analysis. This feature generates a concise summary for every failing Playwright test focusing on end-user impact, answering questions like “Who is impacted?”, “Which features are broken?” and “What steps led to this failure?”

If your failed Playwright test has a trace file, you will find an Analyze with AI button that kicks off the analysis.

The second is the Explain Error button, displayed above every Playwright error message. Clicking this button uses AI to explain why a script failed and how to fix it with a snippet of example code and displays any best practices and links to helpful documentation, like the official Playwright docs.

Both features are now in beta and free for all users during this phase, as we’re testing them and gathering feedback. For more information on access, how it works, and how to provide feedback, please check our changelog entry.

💻 Developer Experience

🖱️A Sidebar that scales with us (and with you), finally!

We’ve been shipping fast — Traces, Status Pages, Dark mode, TCP checks… But our old sidebar was not keeping up with the pace. So we rebuilt it. The new layout is developer-first and introduces logical groupings and cleaner information architecture, making it faster for you to locate the different product sections, create new resources and configure your setup. It’s now ready to scale with everything we’re building (and that you’re monitoring with us!)

Runtime 2025.04 is here

Our latest runtime 2025.04 is now generally available, and uses Playwright 1.51.1 and Node.js v22.11.0.

A new release of the Checkly agent featuring this runtime has also been released; the version number is 6.0.0. Checkly agent 6.0.0 comes with both runtime 2024.09 and 2025.04 making upgrading easier.

You can check out the full specs for the new runtime here, and learn more about Checkly runtimes and how to use private locations for your monitoring in our documentation.

Playwright Check Suites Alpha

Promote any playwright tests to synthetic monitors straight from your codebase. Use pwTags and pwProjects to pick the ones you care about. Drop in custom Frequency and Locations, and they’ll run globally as often as you need —no UI clicks, just code-driven monitoring in your checkly.config.ts file. Includes:

• Custom code dependencies, read directly from your package.json file and cached between runs when there are no changes.

• Multiple browsers and viewports support - Firefox, Webkit, Chromium, you name it.

• Dependencies between tests or projects, if you use a shared login step, we’ve got you!

• Support for npm, pnpm and yarn based repositories.

Give them a try, and happy monitoring!

🐛 Fixes:

• The Analytics API (/v1/analytics/* endpoints) now exposes retry data for each check. The following fields are included:

  • totalCheckRuns – Total number of check runs within the selected time window

  • checkRunsWithRetries – Number of check runs that included at least one retry

  • checksWithRetriesPercentage – Percentage of check runs with retries, relative to the total check runs

• Several code editors in the app (e.g. for configuring a webhook alert channel) are now resizable: You can drag the corner to expand the editor and get more space when working with larger code snippets.

• OS-based DNS resolution for TCP checks in private locations: We released a new version of the Checkly agent (v5.0.0.) that introduces the USE_OS_DNS_RESOLVER environment variable. When When set to true, TCP checks will resolve DNS using getaddrinfo C function, instead of using the network. This enables easier DNS resolution for internal services e.g. services running in the same Kubernetes cluster.

• Alert notifications are sent correctly on check degradations: Until recently we sent alert notifications as soon as a check degraded, even if the alert configuration was set to notify only after 2 or more failures. Degraded notifications now respect the check alert configuration correctly.

• Private location failover logic updated: If a private location becomes unavailable, assigned checks will no longer fall back to a public location. Instead, they’ll be paused to avoid false alerts. We’re also exploring improvements to increase visibility into private location failures and give users more control over fallback behavior.

Got feedback? We’d love to hear from you!

You can share your feedback on our feedback hub or connect via the Checkly community Slack.

Happy monitoring!