← All changelogs

Changelog

What's new in September 2026

Published

Create and manage checks from your AI agent

The Checkly MCP server can now create, update, and delete checks, monitors, and check groups. Tell your agent what to monitor, and it sets up the check.

Here’s an example: Create a URL monitor for checklyhq.com that runs every minute from Europe and the US. Alert me if it goes down. If you dreamt about feeding your agent CSV files or OpenAPI specs to start monitoring all the things, now’s the time to send it to work!

Playwright Check Suites aren't supported yet because they need access to local files.

A URL monitor for checklyhq.com created from an MCP prompt in a coding agent, passing and running every minute from the US and Germany, with its creation logged in the Activity panel

Automatic check repair for Browser and Multistep checks (Beta)

As mentioned above, setting up new checks is only one prompt away, but what do you do when checks fail? How can you evaluate and, in the ideal case, fix them?

Rocky AI can now repair browser and multistep checks for you if the root cause analysis finds a repairable mistake like an outdated selector. In that case, Rocky proposes a fix, tests it, and updates the check if it still matches the initial intent. It's off by default.

A finished Rocky AI check repair, labelled Beta, for a Playwright code error: the summary shows a link locator updated to match the page text, a passing test session, and the fix saved to the check

Track contract usage and credit budgets

Contract customers can now see consumed and remaining credits, usage trends, and projected consumption, broken down by account and check type, including AI invocations. Spot a projected overage early, without asking us for a report. The same data is available through the API, CLI, and MCP server.

The Budget consumption card showing 247.50M of 500M credits used, a usage bar split by check type with a projection to contract end, and an on-track badge

Status pages, rebuilt around components

We rebuilt our status pages (say hello to StatusPageV3) and introduced components. The new component-based status pages make it easy for you to group your services and properties in the way your users will understand. Check them out!

And if you're on Team and Enterprise plans, automation rules can open and resolve incidents for you.

A public status page with an open DB outage incident, the Website and Notifications components at partial outage, the App at degraded performance, a collapsed Regions group, and 90-day uptime bars per component

Also shipped

  • Status Pages: manage status pages through the MCP server, get an email when certificate provisioning for your custom domain fails, and get reminders when an incident has been open for more than two hours.
  • GitHub pull requests from the UI: with the Checkly GitHub App installed, Export to Code and UI edits to supported code-managed checks open a pull request against the file that defines the check.
  • Client certificates: scope certificates to a URL path, so one host can use different mTLS identities for different routes.
  • gRPC and SSL checks: gRPC checks keep their selected locations across deploys and report clearer errors. SSL checks show certificate expiry details when chain verification fails.
  • Fixes: retries of API checks outside a group now run their setup and teardown scripts, and the cursor-paginated check results API no longer skips results.