Pick up to 12 regions across 5 continents and check as often as every 30 seconds. See uptime and latency by region, with 12 months of history for spotting longer-term trends.
Set assertions for status code, page content, response time, and certificate expiry. When one fails, Cronitor shows which assertion failed and the response that caused it.
····
12mo retained
A website used to be one host and one hostname, either up or down. Problems were easier to spot, and one person often knew how everything was wired.
Now the same team may run a website, docs, a blog, a storefront, a status page, and a few legacy systems. Each has its own certificate, origin, and way of failing.
Cronitor Checks gives the developers supporting those systems one place to test availability, performance, certificates, and the response itself.
A check is a request we make on your behalf, on your schedule, from the regions you choose. Every response is evaluated against the assertions you define — not just whether the connection opened.
None of this needs anyone watching a dashboard. Cronitor runs the check, confirms the failure from a second region, and tells you — then tells you again when it recovers.
Set a performance assertion so a check fails when the page gets slow, not only when it stops answering. Uptime and response time are retained for 12 months, globally and by region, so you can compare current performance with last quarter.
Add checks for websites, APIs, servers, firewalls, and other endpoints — including SSH bastions, mail servers, and VPNs. Start with availability, then add assertions when you need to validate the response.
Alerts tell you what failed, where, and when. Cronitor verifies downtime from at least one additional region before alerting, so a single bad probe does not page anybody. Route alerts through 10+ integrations.
Keep everybody informed. Any check can publish to a public or private status page, so customers and internal teams read the same uptime data you do. Automatic email reports go out on a schedule. There is nothing extra to install.
Set up website and API checks in minutes, then add assertions, regions, and alerting as you need them.
Check availability around the world and get alerted when your site goes down.
Check API availability, performance, and response validity.
Set up checks for the SSH bastions, email servers and VPN endpoints you rely on.
Run your website checks using real Chrome browsers to test your JavaScript apps.
Test page content, status code, response time, certificate expiry, and more.
Select up to 12 locations for each check and focus monitoring where your users are located.
Frequent checks can spot small problems before they become big incidents.
Track SLAs with global and per-region performance metrics.
Cronitor confirms downtime from at least one additional region before alerting.
Provision and version-control checks with YAML and the Cronitor CLI.
See APIs, websites, and servers together, with status updates as checks run.
Checks share a dashboard, an alert pipeline and a status page with everything else Cronitor watches. The endpoint you check, the cron job that fills it, and the heartbeat from the worker behind it are all on one screen.
Uptime monitoring continuously probes your websites, APIs, and services from the outside to confirm they are up and responding correctly. Cronitor runs checks as often as every 30 seconds from 12+ locations across 5 continents and alerts you instantly when an endpoint is down, slow, or failing an assertion.
Downtime is always verified by at least one additional region before an alert is triggered, so a network blip near a single probe location does not page you. You choose the locations that matter for your users and the assertions that define a healthy response.
Beyond a simple up-or-down status, checks can assert status codes, response time, page content and JSON values, and SSL certificate expiration. You can send custom methods, headers, and request bodies to test real API behavior, not just reachability.
Use a Heartbeat monitor to verify that the agent itself keeps running, then add Uptime checks for the reachable services it depends on: its MCP server, gateway or health endpoint, webhooks, and TLS certificates. Together, the passive heartbeat and active checks show which layer failed.
Yes. Configure a POST with a stateless JSON-RPC tools/list request and assert the status and JSON response. The endpoint must be reachable from Cronitor's public probe regions. For an OAuth-protected server, an expected 401 response can still prove liveness.