Service healthchecks

Cronitor healthchecks provide a powerful service healthcheck solution for APIs, websites and services including:

  • HTTP, TCP and UDP healthchecks
  • Multi-region downtime verification
  • Intermittent downtime detection
  • Configurable request intervals
  • Flexible outbound requests supporting custom headers, cookies, etc
  • Powerful assertions to create custom healthchecks.

Defining Healthcheck Assertions

Combine multiple service health assertions with our built-in checks for total and intermittent downtime to create the right healthcheck solutions for your services. Available assertions include:

  • Maximum response time
  • Mean response time
  • Response code
  • Response body

Configurable operators for these rules include eq lt gt gte lte not contains

Creating a Healthcheck monitor

  1. From your dashboard, click the button to create a new monitor and select Healthcheck
  2. Select a request method. You can choose among HTTP methods like GET and POST, as well as simple socket healthchecks using TCP or UDP.
  3. Provide a healthcheck endpoint and define request details as desired.
  4. Add custom assertions like mean response time < 3 seconds
  5. Give the monitor a descriptive name like Single sign on service endpoint and add optional tags or notes
  6. After saving the monitor healthchecks will begin within a few moments.

Request Quotas

Healthchecks can be configured to ping your endpoint as often as once every 30 seconds, however each plan has a maximum number of allowed healthcheck requests each calendar month. If this quota cannot accommodate your use case, please reach out to support@cronitor.io for assistance.

Cronitor for Business:
3,000,000 Healthcheck requests per month

Cronitor for Teams:
1,000,000 Healthcheck requests per month

Solo Cronitor:
250,000 Healthcheck requests per month

Request Details

All health check requests will be made with the User Agent Monibot from our monitors in California, Oregon, Ohio, Virginia, Ireland and Tokyo. Outages are verified across multiple regions to determine failure scope.