# Usage and check runs - Checkly Docs

> What counts as a check run, how uptime monitors are billed, and where to see your usage.

Source: https://www.checklyhq.com/docs/admin/usage/

---

Back to top
- What counts as a check run
- Uptime monitors
- Seeing your usage
- Usage emails

Admin

# Usage and check runs

What counts as a check run, how uptime monitors are billed, and where to see your usage.

Synthetic checks, such as API, Browser and Multistep checks and Playwright Check Suites, use check runs from your plan. Uptime monitors don’t use check runs: they’re billed by the number of monitors. See [pricing](https://www.checklyhq.com/pricing/) for what your plan includes.

## ​ What counts as a check run

Each run of a check uses check runs, wherever it starts: scheduled runs, runs you start with **Schedule now**, test runs from the check editor, and test sessions from the CLI, such as `npx checkly test` and `npx checkly trigger`. On top of that:

- **Locations:** each location counts. A check that runs from three locations in parallel uses three check runs each time it’s scheduled.

- **Retries:** each retry is another check run. A flaky check that often retries uses noticeably more.

- **Multistep checks:** each HTTP request the check makes counts as one API check run, with at least one per run.

- **Playwright Check Suites:** each started 30 seconds of run time counts as one Browser check run.

For example, an API check that runs every hour from two locations in parallel uses 48 check runs a day. Each retry adds one more.
To use fewer check runs, lower the frequency of checks that don’t need it, run from fewer locations, or use round-robin instead of [parallel scheduling](https://www.checklyhq.com/docs/concepts/scheduling), and fix flaky checks so they retry less.

## ​ Uptime monitors

URL, TCP, DNS, ICMP, SSL, traceroute and gRPC monitors are billed by how many monitors you have, not by how often they run. Their runs don’t use check runs.

## ​ Seeing your usage

Open **Settings** and, under **Account**, select [Billing & usage](https://app.checklyhq.com/settings/account/billing), then the **Usage** tab. It shows the usage for the whole account in the current billing period.

## ​ Usage emails

On Starter and Team plans, users who can manage billing (Owners and Admins by default) get an email when the account has used more than 90% of its included API or Browser check runs, and another one when it goes over and starts incurring overages. API and Browser check runs each get their own emails.
On the Hobby plan, checks stop running when the included check runs are used up. All members get an email at 80% and at 100% of the included check runs.

Was this page helpful?

[Suggest edits](https://github.com/checkly/docs/edit/main/admin/usage.mdx)[Raise issue](https://github.com/checkly/docs/issues/new?title=Issue%20on%20docs&body=Path:%20/admin/usage)

[Creating an API key in Checkly Previous](https://www.checklyhq.com/docs/admin/creating-api-key)[Admin Overview Next](https://www.checklyhq.com/docs/admin/team-management/overview)

[x](https://x.com/checklyhq)[github](https://github.com/checkly)[linkedin](https://linkedin.com/company/checkly)

[Powered by This documentation is built and hosted on Mintlify, a developer documentation platform](https://www.mintlify.com/?utm_campaign=poweredBy&utm_medium=referral&utm_source=checkly-422f444a)