Checkly changelog
Checkly changelog

Run checks on deployment in any location




You can now select a specific location where we should run your checks when they are triggered by a deployment through GitHub, Vercel or using our command line triggers.

This option is now available on the CI/CD Triggers tab for all checks and check groups.


Just select any location from the drop down.

For command line triggers, you add the optional runLocation to trigger you check in that location. Note, we use the shorter notation here.


Overview of bug fixes last weeks





Hope you're doing great! We are working on some larger product initiatives, but always squeeze in some bug fixes reported by our customers or discovered by our team. Here are some of the highlights from the last weeks.

Home dashboard

  • Empty groups on the home dashboard no longer show up when filtering by name, tag or any of the other filters.
  • Sometimes, the home dashboard (and the Reporting pages) didn't show any tags, or had tags missing. This is fixed!


  • Duplicating an API check in a Group created a Browser check instead. Yeah, that was silly.
  • Also, duplicating an API check could throw an error when the check had no locations selected.

Alerting & Alerting channels

  • The Webhook editor always loaded the placeholder code in the user interface, instead of the user supplied code. This is fixed. The actual webhooks did execute user supplied code BTW.

Deployment & integrations

  • We addressed a timeout issue in our queueing system that reran checks in a loop when triggered by a GitHub, Vercel or command line trigger.

Extra special thanks to our customers for helping us with reporting these!

Run the latest Playwright, Puppeteer and Node with Versioned Runtimes





You can now upgrade your JavaScript-powered checks to the latest and greatest Playwright versions, Node.js version and other dependencies with just one click on the new "Runtimes" tab!


This feature give you full control over when and how you want to update all Javascript functionality for your Browser checks the setup & teardown scripts for API checks.

To kick it off, we shipped a new runtime named 2021.06 which includes

  • Playwright 1.12.2
  • Puppeteer 10.0.0
  • Node.js 14.x

We plan to release a new runtime every quarter with new major and minor versions of the supported packages.

If you want to test the waters a bit before flipping your whole account to a new runtime, you can override just for a single check or a groups of checks.

Read more about how to use versioned runtimes in our docs

P.S. you can also manage your runtimes through our public API and with our Terraform provider in the latest release candidate.

DNS module is now available in all runtimes





We just added the dns module to our allow-list for all script runtimes. Some customers expressed interest in using a DNS lookup or some other DNS operation in their API setup scripts and / or in their Playwright browser checks.

We recommend using the .promises API. This works as follows:

const resolver = require('dns').promises
const res = await resolver.lookup('')
// this prints: { address: '', family: 4 }

Full docs are here for the Nodejs 12 runtime

New code editor for Browser checks





We just released a major overhaul of our browser check editor.


  • It's based on Visual Studio Code / Monaco.
  • It has better code completion on all supported frameworks.
  • It's has a way more efficient screen layout for a quicker debug cycle.
  • Snippets and process.env are now autocompleted and preview in the editor.
  • You can run and stop check runs with the CMD + SHIFT + K short cut.

This is live for everyone now, check it out in your account.

Subscribe to our status page or Twitter handle for all updates on incidents





We recently changed our "default" status page to an externally hosted status page at


Click the "Subscribe to updates" button to receive timely updates whenever we hit a snag. You can also follow our dedicated Twitter handle @checklyHQStatus

Of course, we still dog food Checkly heavily and we have our own dashboards, but to cover all cases — what if our own dashboards are down? — we need to have a 3rd party to keep us in "check"

New integration: FireHydrant





We just launched a new integration with FireHydrant!


You can use this integration to create and resolve incidents on FireHydrant automatically as your checks fail and recover, potentially kicking off FireHydrant Runbooks in the process.

Read all about how to install and use the Checkly FireHydrant integration on our docs/integrations page or just head over to your alert settings to add it as an alert channel.

Sub second degradation and failure limits in UI





Small update to start the week! You can now set response time limits shorter than 1 second directly in our web app. image.png Before, this was only available through our API.

Run checks up to every 10 seconds





We just released a big change on how often you can schedule your API and Browser checks.

  • You can now run API checks up to every 10 seconds. Previously this was every 1 minute.
  • You can now run Browser checks every 60 seconds. Previously this was every 5 minutes.

This feature is available to all customers on our metered pricing plan introduced this January and is visible in the Checkly app right now.

Read more about why this matters in our blog post

Filtering events is now live





You can now filter events on the global and per check event timelines.


This is super useful when you have a busy account with multiple outages or degradations overlapping each other, or you just want to look at your deployment events.

You can filter by: