Changelog

We're thrilled to announce that we're a launch partner in Vercel's new Observability Marketplace! You can now effortlessly create and manage Checkly accounts directly within Vercel, simplifying how you monitor your deployments and projects.

Ensure that no faulty code reaches production with Checkly's new Vercel native integration:

• Manage billing, your team's access to Checkly, and your usage directly from your Vercel account.

• Add Checkly scheduled and pre-deployment monitors to your code, using our monitoring-as-code workflow.

With Checkly, you can easily set up pre-deployment tests to run as part of your CI pipeline through GitHub Actions. With monitoring-as-code, you ensure that your monitoring is always up to date with the latest production deployments.

Whenever you push a new commit, and a deployment is triggered, Checkly will automatically run the checks for you in a test session, allowing you to block the deployment if checks are failing, and expose those issues for your team to resolve quickly.

If your team is already using Vercel and you want to improve your applications' reliability with a scheduled monitoring setup, creating a new Checkly account is now one click away.

New Checkly users will also have a tailored onboarding experience, helping you set up your monitoring as code workflow and quickly get started with the Checkly CLI.

For more information, look at the Checkly <> Vercel integration docs. You can learn more about Vercel’s native integrations here.

Happy monitoring!

Questions or feedback? Join our Slack community.

We’re excited to announce that Dark Mode is now live in Checkly! One of the most requested features on our public roadmap, it’s here for everyone who prefers a darker look — especially when getting paged in the middle of the night. No more reaching for sunglasses 😎

By default, Dark Mode follows your OS theme preference, but you can override this anytime in your user settings to manually toggle between light and dark themes.

We’re excited to hear what you think!

Dark Mode is now live across the Checkly UI — and we’re excited to share it with everyone.

If you spot anything that could use a little extra polish, drop a comment on the roadmap item or let us know in the Checkly community Slack.

Happy monitoring!

We are excited to announce that Checkly status pages are now available, unifying monitoring and customer communications for your services and applications!

Status pages are an essential tool for increasing customer trust and keeping your users in the know whenever you are dealing with an incident.

With Checkly status pages your customers can be notified within seconds of a check alerting, maintaining confidence that your team is aware and working to solve any issues.

With status pages, you can:

• Show the health and uptime of the critical services of your product or business.

• Connect services to synthetic checks, automatically opening incidents when checks fail.

• Automatically notify subscribed users whenever an incident is published or resolved.

• Customize the look and feel with theming, a logo, and a custom domain.

Incident notifications

Whenever you post an incident update to a status page, subscribed users will receive email notifications, helping them to stay up to date with ongoing work.

Incident notifications reduce the need for manual customer communication and allow your team to focus on problem solving.

Automatic incident creation

Connect your synthetic checks directly to a status page and automatically open and resolve incidents based on check failures and recoveries.

Automatic incident creation speeds up the time to customers being notified and reduces cognitive load for your engineers, freeing up more focus on solving ongoing issues.

Getting started with status pages

Check out the status page documentation to start and learn how to configure pages and manage incidents manually and automatically.

Status pages can be managed through the web UI or with Checkly’s Monitoring as Code (MaC) workflow and are available in the CLI starting with v5.2.0.

Status pages are available for Checkly users on the Enterprise plan. Reach out to our support team or your account executive for access.

Happy monitoring!

Questions or feedback? Join our Slack community.

Here are the most exciting changes from the last month.

⚡TCP Checks Generally Available

We’re excited to announce that TCP checks are now available in Checkly across all plan types! After a successful beta phase, we’ve expanded functionality, improved documentation, and refined features to make TCP checks a reliable tool for monitoring your infrastructure.

Some use cases include:

• Mail servers – Ensure IMAPS or SMTP connections are available.

• Custom TCP services – Verify internal or external TCP-based applications.

• Firewalls – Confirm that specific ports are open or intentionally blocked.

Check out the TCP checks documentation to get started and learn more about usage, reporting and billing. TCP checks are fully integrated into Checkly’s Monitoring as Code (MaC) workflows and available in the CLI starting v4.19.1.

</> Developer Experience

Pulumi Provider Update

The Checkly Pulumi provider has gotten a very much overdue update, including checkly test and checkly trigger retries, especially useful for CI workflows.

If you have any issues or feature requests, please report them in the checkly/pulumi-checkly repo directly!

Checkly CLI 5.0.1

Checkly CLI 5.0.1 is here!

• Requires Node.js 17 or a later version.

• Added support for alert channel constructs to define Incident.io, Microsoft Teams and Telegram alerts as code!

• Fixed the command line reporters to include the degraded status.

  

UX Improvements

Search for users by name or email in the members list

Reviewing and editing your team’s access to Checkly just got easier with search. Head over to members to check it out.

We’ve made further UX improvements based on your input:

• Date pickers now support time (hh:mm:ss) selection alongside the date. Making specific timeframes shareable as well.

• 6 decimal digits precision is now available on hover over the availability metric on the check results page.

• Individual check results are now clickable in Checkly dashboards, providing quick access to each check’s run details.

• The test sessions page has a new search box to help you find the one you’re looking for faster.

Private Location metrics

The endpoint private-locations/{id}/ metric now receives updates once a minute. The Prometheus export also gets updates every minute now.

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!

P.S. Thanks for reading this far! As a gift, we’d like to invite you to our private alpha for Playwright Native checks, where you can use Projects StorageState , @tags, custom dependencies, and all playwright features 🎭 — if you’re interested, reach out, and we’ll get you on the list!

At Checkly, we’re always keen to hear from users and learn how we can improve—whether through the public feedback board, Slack, or direct conversations. We’ve made a few UX improvements based on your input and are excited to share what’s new.

Check them out below—and keep the suggestions coming! 🚀

Date picker now supports time selection

All date pickers across the UI now allow specifying time (hh:mm:ss) alongside the date. This ensures more precise filtering and is also reflected in the URL, making it easier to share results with your colleagues for a specific timeframe.

6 decimal digits precision in check availability

Hovering over the availability metric on the check results page now displays availability to the 6th decimal place, along with the total number of checks in the selected time period and the failed checks count.

Clickable check results in dashboards

Both the check name and individual check results are now clickable in Checkly dashboards, providing quick access to each check’s run details.

Search added to test session results

Find checks easily with the new search box on the test sessions page. Both test names and test paths are now searchable.

We hope these updates improve your experience with Checkly! If you have any questions or feedback don’t hesitate to reach out via Slack or join the discussions on the feedback board.

Happy monitoring! 🚀

We’re excited to announce that TCP checks are now fully available in Checkly across all plan types! After a successful beta phase, we’ve expanded functionality, improved documentation, and refined features to make TCP checks a reliable tool for monitoring your infrastructure.

TCP checks allow you to monitor critical infrastructure like databases, messaging queues or mail servers, ensuring they are reachable and responsive. Simply specify a hostname and TCP port to start monitoring.

🔎 Example Use Cases

• Mail servers (e.g. mail.example.org:993): Ensure your mail server is online and accepting IMAPS connections. Set assertions on the response time to spot slowdowns and provide reliable email services for your users.

• Custom TCP Services (e.g. service.example.org:5000): Monitor internal services that use custom TCP-based protocols. Send a simple command like ‘HEALTHCHECK‘ and assert that the response contains ‘OK‘ to verify that the service is running and responsive.

🚀 Get started with TCP Checks

Check out the TCP checks documentation to get started and learn more about usage, reporting and billing. TCP checks are fully integrated into Checkly’s Monitoring as Code (MaC) workflows and available in the CLI starting v4.19.1.

The Terraform provider supports TCP checks from v1.9.0, and the Pulumi provider from v2.0.0.

📌 Pricing & Billing

TCP checks are billed at $2 per 10k runs. They share the same quota as API checks, meaning they are included in your existing API check allocation. For more details on individual plan types, visit our pricing page.

💬 Connect with us

Got feedback or questions? We’d love to hear from you! Share your thoughts on our feedback hub or join the Checkly community Slack.

Happy monitoring!

We just released a new major 5.0.1 version of the Checkly CLI. You can also view the release note for 5.0.0 to check all PRs merged on GitHub.

Here’s what’s new.

Node.js 16.x is no longer supported

As Node.js 16.x was marked End-of-Life late 2023 we’ve released a new major CLI version and updated all relevant dependencies to a later Node.js major version.

New Alert Channel constructs

This release introduces CLI support for three existing alert channels. You can specify them with their corresponding constructs:

• Incident.io

• Microsoft Teams

• Telegram

Use these new constructs to define these alert channels, just like you would with any other alert channel construct:

import { IncidentioAlertChannel } from 'checkly/constructs'

export const incidentIoChannel = new IncidentioAlertChannel('my-channel-01', {
  name: 'ACME incident channel',
  url: 'https://api.incident.io/v2/alert_events/checkly/xxxx',
  apiKey: '1234abcd' // or use process.env.INCIDENT_API_KEY! and provide the key on the command line
  sendFailure: true,
  sendRecovery: true,
})

Learn more about using the new constructs in the CLI constructs reference docs.

Degraded state in reporters

We added the degraded state to all relevant reporters. Previously, Checkly reported degraded checks as passing, which was not great. On the default list reporter, the output for a degraded check will look as follows:

To get started with the Checkly CLI, run:

npm create checkly@latest 

Or upgrade to the latest Checkly CLI version with:

npm install -D checkly@latest

Happy monitoring!

Questions or feedback? Join our Slack community.

🚀 Try Checkly Traces today & Upgrade Your Monitoring!

We’re excited to announce that Checkly Traces is now generally available – delivering full end-to-end observability to your monitoring workflow.

Traces provide the right context to debug your failed and degraded checks, reducing your time to find the root cause!

What started as our OpenTelemetry Tracing integration in beta, has now grown to be a robust solution to complement your automatic checks.

Check out the integration docs for your codebase: Node.js, Next.js, Python, Ruby, Golang…

🔹 See exactly the underlying issues in your setup.

🔹 Identify trends in your underlying applications and services on the Check Overview page with the following:

• Services duration graph, which you can match to your check’s response times.

• The top 3-erroring spans, with a link to the latest check result that had this specific error.

  

🔹 See errors globally and identify trends in your services with the Traces Overview page

Your checks may target the same underlying applications and services, and that’s exactly what the Traces Overview page is for!

• Get a performance overview for those particular Spans selected

• Analyze duration and underlying issues for a particular Service in your backend

• View all spans and traces to see every event in your system while running your checks.

🛠 Start using Checkly Traces for free!

Checkly Traces are available on all plans. Get Started today and experience faster resolution with the immediate insights they provide:

• ｡🇯‌🇸‌ Node.js

• ｡🇯‌🇸‌ Next.js

• 🐍 Python: Django and Flask

• 🇬🇴 Golang

• 💎♦️ Ruby

• (and more!)

💼 Upgrading for more coverage

Checkly Traces are designed to scale with your team’s and business needs. To upgrade to the right plan that fits your organization:

1. Trial traces to explore all features

2. Contact our support team or your account executive for a personalized quote tailored to your usage and needs.

3. Enjoy Checkly Traces to debug with your team!

📊 Unlock Full Observability

Checkly Traces helps your teams diagnose issues faster, connect the dots across services, and ensure smooth application and services performance.

Don’t wait — start optimizing your monitoring today!

✨Happy monitoring!

Tell us what you think and what you’d love to see next! Leave a note in the feedback hub or connect with us in the Checkly community Slack.