Checkly changelog
Checkly changelog

HTTP Proxy for Private Locations




You can now proxy all check traffic through any HTTP proxy you might have in your internal network or private cloud when using Checkly's Private Locations.

Note: please update your Checkly Agent containers to version 1.0.5


Make sure to check our docs on how to effectively use HTTP proxies across your full Checkly setup.

Private Location Health




Private Location health is now shown in the private locations list under account settings. The health indicators let you know whether all of your checks are running in the private location or if the location has capacity issues or failures causing checks to be delayed or fail to run.


Private location queue health metrics are also available in the REST API and the Prometheus integration so you can monitor and act on them from your own systems.

`require` snippets in Browser checks




You can now use the standard Node.js require() syntax to import code snippets into your Browser checks, where we first only supported Handlebars templates.

Here's an example:

  1. Create a login routine you want to reuse in Browser check scripts. Export it as a function


  1. Now require the snippet from the ./snippets directory — just like JS file — and call the function passing in the relevant parameters.

CleanShot 2022-06-10 at 14.45.09@2x.png

Read more in our docs on how to use this new syntax.

This is now the recommended way to DRY up your code. The legacy Handlebars notations is still usable till further notice.

Status Badges




Status badges are now available for your checks. You can share the status badges anywhere, such as code repository READMEs or other websites. The badges can show check status and check response times. Badges need to be enabled for your account in the Account Settings page.


Once enabled, they can be accessed via the Checkly public API. Badges are publicly accessible and do not require API key authentication.


Run Checks in Private Locations




Checkly Private Locations are now available for everyone.

You can already test your public apps from various locations using Checkly, but what if you want to monitor and test segregated applications and APIs that aren’t publicly available? Your internal APIs deserve the same care as the public ones.

Many of you asked us how to approach the testing of internal applications, and we’re excited to tell you that you can now test your internal APIs and applications using Checkly, too!

Private locations use the Checkly Agent, a container-based tool, to run API and browser checks right in your infrastructure. It’s based on the code we run in production packaged into an OCI-compliant container so that you can use it with Docker, Kubernetes, Podman, etc.


Learn more in this blog post.

Read the documentation to get started.

Runtime 2022.02 with Playwright 1.20.2 now available




We just released Runtime 2022.02 with Playwright 1.20.2 and Puppeteer 13.7.0 among other NPM package updates and additions.


Runtime 2022.02 is the new default for all new users, existing users should upgrade in due time. You can do this upgrade in a controlled fashion. Read more on how runtimes work and how you can gradually upgrade your account in our documentation. — It's just one click.

Get to the right insights, faster 🏃‍♀️




The revamped Check Overview page now gives you more ways to dive into data that matters for your checks, and your business.


Here’s what you can do now:

  • Easily access a timeline of all individual check runs.
  • Constraints-free: see alerts, check runs and other data for any time interval you need.
  • Integrating Checkly with your CI/CD – as you should? Access those check runs more easily than before.
  • There’s more… 👇

Read more on our blog.

Tags are now propagated to Opsgenie




All tags you set on Checks and Check Groups are now propagated to your Opsgenie integration.


Use tags to route alerts to specific teams or trigger specific actions. This feature enhancement came from our Public Roadmap.

Checkly API now generally available




We moved our public API to General Available. What does this mean?

  • Updated documentation and API playground.
  • New, non-polymorphic endpoints for creating checks
  • Two deprecated endpoints (see below)
  • A million — well, *checks bug tracker* 38 actually — fixes to docs, schema's, default values, and response bodies.
  • Rate limiting on endpoints to prevent abuse.


Hundreds of devs are already using our API daily through our Terraform provider, Pulumi provider (in preview) or directly from their codebase.

P.S. the auto-generated OpenAPI / Swagger docs are still available at

Deprecated endpoints

We deprecated two endpoints on our public API as part of making the public API Generally Available.

  • GET /check-results-rolled-up. This endpoint was a stop-gap for longer-range data. You can now use the regular /check-results endpoint

  • POST /checks. This endpoint was polymorphic. We now have dedicated endpoints for API and Browser check creation on /checks/api and /checks/browser

We will remove these endpoints on Monday 4 July 2022. We will follow up with emails to alert you as we near that date.

Pulumi provider tech preview




We just started a tech preview of our Pulumi provider. This provider allows you to use your favourite programming language to manage your monitoring setup from your code base!


This integration is now in preview and we are actively looking for early adopters. Just drop a short email to if you want to be involved in the preview and we will gladly help you get started.