Uptime Monitoring & Status Pages
Cronitor
Rest of world Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Cronitor, Inc. · cronitor.io
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Cronitor at a glance
- Vendor
- Cronitor, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 1 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 1 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 1 Nov 2026
- Panel verdict
- The AI panel rates Cronitor 3/5, the mean of 6 judges. Cronitor, from Cronitor, Inc., founded in California, combines cron-job, heartbeat and website checks with hosted status pages. how scores are made
- As of
- Vendor pages captured 1 Nov 2026; evaluated by the panel 2 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Cronitor, from Cronitor, Inc., founded in California, combines cron-job, heartbeat and website checks with hosted status pages. The strongest uniform results are checks and locations and automation and teams, both at 7 with no spread, crediting intervals as fast as 30 seconds with downtime verified from at least one additional region before alerting, YAML version control through an open-source CLI against a documented REST API, and SAML single sign-on with SCIM provisioning. Pricing transparency scored 7 to 8 on public, computable unit pricing — Business at "$2 /mo per monitor + $5 /mo per user" and a worked "$55 /mo" example, no base fee — while we found no public information on VAT treatment or overage handling. Reports and reliability sits at a flat 6. The widest split is sovereignty, 0 to 2: data residency, hosting and a data processing agreement are recorded as unknown, and judges weighed that undocumented chain differently. Alerting and on-call (6 to 7) and status pages (6 to 7) diverge over native on-call rotations living in external tools.
Speaks for it
- Checks run as often as every 30 seconds, with downtime verified from at least one additional region before anyone is alerted.
- Monitors are managed as code — YAML import and export, an open-source CLI, and a REST API with a published OpenAPI description and scoped keys.
- Unit pricing is fully public with no base fee: Business at "$2 /mo per monitor + $5 /mo per user", with a worked example of "$55 /mo" for 20 monitors and 3 users, billed monthly with no contract.
- Status pages publish incidents automatically from monitors, on a custom domain with HTTPS, password protection and IP allow-lists.
- SAML single sign-on with SCIM provisioning and admin, user and read-only roles is documented.
Held against it
- Sovereignty scores run 0 to 2: data residency, hosting options and a data processing agreement are recorded as unknown, with no public information on the subprocessor chain; the contracting entity is Cronitor, Inc., founded in California.
- Escalation is documented through PagerDuty, OpsGenie, Splunk On-Call and Datadog On-Call, and we found no public information on native on-call schedules, rotations, or acknowledging and resolving from the app.
- We found no public information on VAT treatment, per-country SMS and phone-call costs, or overage handling.
- We found no public information on an SLA with credits, the vendor's own public status page, or a raw export of check results; the vendor's own figure shown is a self-reported 99.997 percent uptime over the last 12 months.
- The captured pages give different figures for the number of check locations — "12+ locations worldwide" beside a list of eleven named regions.
Best for
- You monitor cron jobs, heartbeats and public endpoints together and want one dashboard and alert pipeline reaching the same on-call team.
- You want monitors under version control as YAML, deployed through an open-source CLI and a documented REST API.
- You need a branded status page on your own domain that updates automatically when a monitor fails.
- You want to compute your bill from public pages before talking to sales.
Avoid if
- Your procurement requires documented data residency, hosting options or a data processing agreement before signing; all three are recorded as unknown.
- Your on-call rotations and overrides must live inside the monitoring tool — the documented model sends escalation to PagerDuty, OpsGenie, Splunk On-Call and Datadog On-Call.
- You need many separate status pages — Business includes one, with branded pages at "$25 /mo per page" and private pages at "$50 /mo per page".
- You need checks faster than every 5 minutes on the free tier — the free tier's fastest check frequency is 5 minutes, with 30-second checks from the Business plan.
The scores
| Criterion | Panel median |
|---|---|
| Checks, locations & failure confirmation | 3.5 of 5 |
| Alerting, escalation & on-call | 3.5 of 5 |
| Status pages & incident communication | 3.5 of 5 |
| API, monitoring as code & team administration | 3.5 of 5 |
| Uptime reports, data & the vendor's own reliability | 3 of 5 |
| European sovereignty | 0.5 of 5 |
| Pricing transparency | 3.5 of 5 |
Checks, locations & failure confirmation
Show reasoningHide reasoning
How this is scored
What can be monitored and how reliably a failure is detected: HTTP(S) with status code and keyword checks, TCP and port, ping, DNS records, SSL certificate and domain expiry, cron jobs and heartbeats, multi-step API checks with assertions, browser or transaction checks of a login or checkout, the shortest check interval, the number and regions of probe locations, the re-check from a second location before an alert, timeouts and response time thresholds, and private locations inside the customer's own network.
0 — Runs no checks of its own; a status page or alerting tool that only receives signals from other monitors.
3 — HTTP checks of a URL at a fixed interval with an up or down result; keyword, SSL, cron and the probe locations are basic or not described.
5 — HTTP(S), keyword, TCP or port, ping and SSL expiry checks, cron or heartbeat monitoring, an interval of one minute or less, several named probe locations, a failure confirmed from a second location before alerting, and response times recorded per check.
8 — Multi-step API checks with assertions on headers and body, browser or transaction checks of a user flow, DNS and domain expiry checks, sub-minute intervals, probe locations listed by city with the confirmation logic documented, private locations or agents for internal services, and maintenance windows that pause checks.
10 — Coverage and accuracy a reliability team runs on: every check type above with code-based checks (for example Playwright or scripted tests) in version control, location-specific thresholds, false-positive handling and probe health published, and the detection method documented so a result can be reproduced.
The Agency Developer
HTTP/HTTPS with custom methods and headers, TCP and UDP, browser checks in a real Chrome, keyword, response-time and SSL-expiry assertions, heartbeats, 30-second intervals, 12+ regions across 5 continents and downtime verified from a second region before alerting cover almost everything my client sites need. We found no public information on domain-expiry checks, DNS record checks, or private probes inside a client network, which keeps it below the top level. 1 3 9 15
The SaaS Platform Engineer
Thirty-second checks from selectable regions — eleven named regions across five continents — with downtime verified from at least one additional region before alerting is exactly the confirmation logic I want before anyone is paged. Assertions on status code, response body, JSON, headers and certificate expiry, browser checks in a real Chrome, and TCP and UDP probes with configurable timeouts are all documented. We found no public information on multi-step request chains, DNS or domain-expiry checks, or private probes inside our own network. 3 9 15
The Customer Support Lead
Uptime checks cover HTTP with assertions on status code, response body, JSON and headers, plus TCP, UDP and real-Chrome browser checks that run JavaScript, as often as every 30 seconds from up to 12 selectable regions across five continents, with downtime verified from at least one additional region before an alert and per-region latency measured against that region's own median. SSL expiry assertions with a configurable warning window, timeouts and maintenance windows are all documented. We found no public information on DNS record or domain expiry checks, multi-step transaction flows, or probe agents inside a customer's own network. 9 15 3 5
The E-Commerce Operations Manager
Checks run as often as every 30 seconds from eleven named regions, and downtime is verified from at least one additional region before anybody is paged — after a night when the homepage answered 200 while checkout errored, that confirmation logic is exactly what I want before waking someone up. Assertions cover status code, response body, headers, response time and certificate expiry, JavaScript pages run in a real Chrome browser, and maintenance windows and pause endpoints keep planned work out of the results. What holds it back for me: I found no public information on a multi-step checkout or payment flow, DNS or domain-expiry checks, or probes running inside our own network. 3 9 15
The Information Security Officer
The documentation covers HTTP, HTTPS, TCP and UDP checks, browser checks that run JavaScript in a real Chrome, and assertions on status code, body, JSON, headers, response time and certificate expiry, at intervals from 30 seconds to 24 hours from up to twelve selectable regions across five continents, with the regions named. A failure is verified from at least one additional region before anyone is alerted, timeouts are configurable, and static probe IP addresses are available in four regions for allow-listing. We found no public information on multi-step transaction checks, DNS record or domain expiry checks, or private probe locations inside our own network; internal services are covered instead by heartbeat pings that need no inbound access. 3 4 9 15
The Skeptic
Thirty-second checks, and — the part I always look for first — downtime is verified from at least one additional region before anyone is paged, stated in plain writing. Assertions cover status code, response body, JSON, headers, response time and certificate expiry, browser checks run in a real Chrome, and timeouts are configurable from 1 to 15 seconds. We found no public information on DNS or domain-expiry checks, multi-step transactions or private probes inside a customer's own network — and the captured pages give different figures for the probe count, "12+ locations worldwide" against a list of eleven named regions. 1 3 9 15
Alerting, escalation & on-call
Show reasoningHide reasoning
How this is scored
How the right person learns about a failure: alert channels (email, SMS, phone call, push app, Slack, Microsoft Teams, Telegram, webhooks), alerts to PagerDuty, Opsgenie or similar tools, escalation policies when an alert is not acknowledged, on-call schedules and rotations, acknowledge and resolve from the app, alert grouping and noise reduction, recovery notifications, maintenance windows that mute alerts, and whether SMS and calls are included or charged per message.
0 — No alerting at all; results can only be viewed in the dashboard.
3 — Email alerts and one or two chat integrations; escalation, phone calls and schedules are basic or not described.
5 — Email, SMS, a mobile push app, Slack, Microsoft Teams and webhooks, alerts forwarded to PagerDuty or Opsgenie, per-monitor alert contacts, recovery notifications, a delay or threshold before alerting, and maintenance windows that mute alerts.
8 — Phone call alerts, escalation policies with timeouts, on-call schedules and rotations with overrides, acknowledge and resolve from the app or chat, alert grouping, incident timelines with who did what, and the price of SMS and calls stated per country or included in the plan.
10 — On-call that replaces a separate incident tool: follow-the-sun schedules, escalation across teams, alert routing by service and severity, post-incident reviews generated from the timeline, and delivery of every alert channel monitored and reported.
The Agency Developer
Email, SMS, phone, Slack, Teams, Telegram and webhooks plus routing to PagerDuty, Opsgenie and Splunk On-Call, with failure tolerance, an 8-hour re-alert interval and flapping failures kept in one incident; SMS and on-call alerts are listed as included in the Business plan. We found no public information on native on-call schedules and rotations or per-country SMS and call prices. 1 5 8 11 15
The SaaS Platform Engineer
Phone and SMS sit among the listed channels alongside Slack, Teams, Telegram, PagerDuty and webhooks, with recovery notifications, failure tolerance ("page on the third consecutive miss instead of the first flake"), surge protection, incident dedup and maintenance windows doing real noise reduction. Escalation runs through the PagerDuty, OpsGenie, Splunk On-Call and Datadog On-Call integrations rather than native schedules — alerts "arrive wherever your on-call rotation already lives" — and SMS and on-call alerts are listed as Business plan inclusions. We found no public information on native on-call rotations with overrides, acknowledge-and-resolve in the app, or the per-country cost of SMS and calls. 1 2 4 8 11
The Customer Support Lead
Alerts go out through twelve or more channels including phone calls, SMS, Telegram and the chat platforms, with routing to PagerDuty, OpsGenie, Splunk On-Call and Datadog On-Call for escalation and on-call rotation, recovery notices, failure tolerance so a first flake does not page anyone, re-alert intervals, surge protection, and flapping failures collapsed into one incident with a timeline. We found no public information on native on-call schedules and rotations inside the product itself, on acknowledging and resolving from the app, or on per-country SMS and call costs. 1 11 10 9 5
The E-Commerce Operations Manager
SMS is listed as included in the Business plan and phone appears in the channel list, alerts carry issue context and recovery notices, and failure tolerance plus alert surge protection keep a flaky night from paging the whole shop — alerts even route into PagerDuty, Opsgenie or Datadog On-Call with escalation there, and escalation policies are referenced in the alert documentation. But the rotations themselves live in those external tools: I found no public information on native on-call schedules, overrides, or acknowledging and resolving from the app or chat. 1 8 9 10 11
The Information Security Officer
Email, SMS, phone, Slack, Microsoft Teams, Discord, Google Chat, Lark, Telegram and webhooks are all documented, alongside forwarding to PagerDuty, Opsgenie, Splunk On-Call and Datadog On-Call, and the Business plan states that SMS and on-call alerts are included. Flapping failures stay grouped in one incident with a timeline, recovery alerts are sent, and failure tolerance, grace periods, re-alert spacing and maintenance windows keep the noise down. We found no public information on native on-call schedules, rotations with overrides, or acknowledging and resolving from the app — the stated model is that alerts "arrive wherever your on-call rotation already lives", so escalation lives in the connected tools. 1 4 5 8 10 11 15
The Skeptic
The channels are broad — email, SMS, phone, Slack, Teams, Telegram, webhooks, and forwarding to PagerDuty, Opsgenie, Splunk On-Call and Datadog — and noise is handled with page-on-the-third-consecutive-miss, an eight-hour re-alert interval and flapping failures kept inside one incident. But the on-call machinery itself lives elsewhere: alerts "arrive wherever your on-call rotation already lives". We found no public information on native schedules and rotations, acknowledge-and-resolve from the app or chat, or what phone calls cost; SMS is only described as included on the Business plan. 1 4 8 11 15
Status pages & incident communication
Show reasoningHide reasoning
How this is scored
How customers and colleagues are told: public status pages on a custom domain with SSL, components and component groups fed automatically by monitors or set by hand, incident updates and scheduled maintenance announcements, subscribers notified by email, SMS, RSS or webhook, uptime history shown per component, private or password-protected pages for internal teams or single customers, branding and custom CSS, several languages, page templates, and how the status page itself stays online when the main product is down.
0 — No status page of any kind.
3 — A public status page listing monitors with their current state; custom domain, incident updates and subscribers are basic or not described.
5 — Public status pages on a custom domain, components linked to monitors, incident updates and scheduled maintenance, email subscribers, uptime history per component, the vendor's branding removable, and a password-protected or private page option.
8 — Component groups, SMS, RSS and webhook subscribers with per-component subscriptions, private pages with single sign-on or IP restriction, several languages, incident templates, embeddable status widgets, audience-specific pages for single customers, and the status page hosting kept separate from the main service and documented.
10 — Incident communication end to end: incidents drafted from monitor events and approved by a person, updates published to the page, subscribers, chat and social channels at once, a full incident archive with post-mortems, status page uptime published, and accessibility of the page stated.
The Agency Developer
Hosted pages on a custom domain with HTTPS included, components and component groups fed automatically by monitors, incident timelines through investigating to resolved, scheduled maintenance, password and IP-allowlist private pages, email, RSS and webhook subscribers, and SVG or JSON badges. We found no public information on per-component subscriptions, several languages, or how the status page stays online if the main service is down. 5 13 14
The SaaS Platform Engineer
Custom domain with HTTPS included, components fed automatically from monitors with 90-day uptime history, and incidents autopublished when a monitor fails — the page updates at 3 a.m. without a human logging in. Email, RSS and webhook subscribers, password-protected pages with IP allow-lists, component groups, scheduled maintenance and embeddable badges are all documented. We found no public information on SMS subscribers, per-component subscriptions, multiple languages, incident templates, or how the status page hosting is kept separate from the main service. 5 13 14
The Customer Support Lead
Pages sit on a custom domain with HTTPS, components appear automatically from uptime checks, cron jobs, heartbeats and groups, component groups are supported, incidents move from investigating through resolved with a timeline of updates, maintenance is announced ahead of time, readers subscribe by email, RSS or webhook, and private pages are protected by password and IP allowlist — close to everything my desk needs for the largest accounts. We found no public information on SMS subscribers, per-component subscriptions, incident templates, additional languages, or how the page's hosting is kept separate from the main service, and the page shows 90 days of uptime while data is retained for 12 months. 5 13 14 8
The E-Commerce Operations Manager
Custom domain with HTTPS handled for me, components fed automatically by monitors with groups and manual components, incident timelines from investigating through resolved, subscribers by email, RSS and webhook, password-protected or IP-restricted pages, and embeddable SVG or JSON badges. I found no public information on SMS subscribers or per-component subscriptions, several languages, incident templates, audience-specific pages for single customers, or how the page itself stays online when the main product is down. 5 13 14
The Information Security Officer
Pages run public or password-protected on a custom domain with HTTPS handled, components and component groups update automatically from uptime checks, cron jobs, heartbeats and monitor groups, and incidents move through investigating, identified, monitoring and resolved with a timeline, backdating and scheduled maintenance. Readers subscribe by email, RSS or webhook, uptime is shown per component for up to ninety days, access can be restricted to named IP addresses or networks, and SVG or JSON badges embed status elsewhere. We found no public information on SMS subscribers, several languages, incident templates, single sign-on for page viewers, or how the status page hosting is kept separate from the main service. 5 8 13 14
The Skeptic
Components feed automatically from monitors with uptime history, component groups exist, incidents move through investigating to resolved with a timeline and backdating, and the page can sit on a custom domain with HTTPS, password protection and IP allow-lists. Subscribers come by email, RSS and webhook with per-page settings. We found no public information on SMS subscribers, several languages, incident templates, or how the page itself stays online when the main service is down — the question I ask of every status page vendor. 5 13 14
API, monitoring as code & team administration
Show reasoningHide reasoning
How this is scored
How the tool fits a team and a deployment pipeline: a documented REST API to create and read monitors, status pages and incidents, a Terraform provider, CLI or monitoring-as-code workflow, checks run from CI/CD before a deploy, bulk import of monitors, integrations with ticketing and chat tools, team members with roles, single sign-on (SAML) and SCIM, audit logs, several teams or client accounts in one organisation, white-label or client reporting for agencies, and two-factor authentication.
0 — No API, no team accounts; one login per account and monitors are set up only by hand.
3 — A web dashboard with a few team members; the API, roles and multi-client set-up are basic or not described.
5 — A documented REST API covering monitors and status pages, webhooks, team members with roles, two-factor authentication, bulk import or a CSV upload of monitors, and several projects, teams or client groups in one account.
8 — A Terraform provider or monitoring-as-code CLI with checks kept in version control, checks triggered from CI/CD, single sign-on (SAML), SCIM provisioning, audit logs, sub-accounts for clients with their own logins, and white-label client reports.
10 — Administration that scales across many teams and clients: every setting reachable by API and code with parity stated, granular roles per resource, SSO enforced with SCIM, audit logs exportable to a SIEM, and agency or reseller accounts with separate billing.
The Agency Developer
A documented REST API with an OpenAPI spec and scoped keys covers monitors, status pages, issues and maintenance, and YAML import/export plus an open-source CLI put monitor configuration in version control; SAML single sign-on, SCIM provisioning and admin, user and read-only roles are all evidenced. For an agency the gaps hurt: we found no public information on client sub-accounts with their own logins, white-label client reports, or two-factor authentication. 6 7 8 15 16
The SaaS Platform Engineer
YAML import and export for version-controlled monitors plus an open-source CLI managing the same resources as a versioned REST API with a published OpenAPI spec and scoped keys is genuine monitoring-as-code, even if it is not Terraform. SAML single sign-on with role mapping, SCIM provisioning, and admin, user and read-only roles are documented. We found no public information on a Terraform provider, checks run from CI/CD, client sub-accounts, two-factor authentication, or audit logs beyond those created when a monitor is deleted. 6 7 15 16
The Customer Support Lead
A documented REST API with a published OpenAPI description covers monitors, status pages, components, incidents and maintenance windows, YAML import and export supports version control and bulk changes, and an open-source CLI manages the same resources including team and API keys; SAML single sign-on with role mapping and SCIM provisioning are documented alongside admin, user and read-only roles. We found no public information on a Terraform provider, two-factor authentication, client sub-accounts with their own logins, or white-label reports, and the audit logging described covers deleted monitors. 6 15 16 7
The E-Commerce Operations Manager
Monitors can live as YAML under version control with an open-source CLI, a published OpenAPI 3 specification, scoped API keys, bulk create, clone and delete, and SAML single sign-on with SCIM provisioning plus admin, user and read-only roles — the same resources are manageable through a CLI and even an MCP server for coding agents. I found no public information on a Terraform provider, client sub-accounts with their own logins, white-label agency reports or two-factor authentication, and the only audit logs described are created when a monitor is deleted. 6 7 8 15 16
The Information Security Officer
A REST API covers monitors, status pages and components, issues and maintenance windows, notification lists, groups, environments and API keys, published as an OpenAPI 3 description with request versioning and scoped keys, and an open-source CLI with YAML import and export manages the same resources so checks can live in version control. SAML single sign-on with Okta, Google Workspace and Microsoft Entra, SCIM provisioning, just-in-time user creation and admin, user and read-only roles are documented, with SAML priced at +$5/mo per user on the Business plan. The only audit-log statement we found covers deleted monitors, and we found no public information on two-factor authentication, client sub-accounts with their own logins, or white-label reporting. 4 6 7 8 15 16
The Skeptic
An open-source CLI and YAML import/export are documented explicitly for version control and infrastructure-as-code workflows, the REST API has a published OpenAPI spec with scoped keys and versioning, and SAML SSO comes with SCIM provisioning, just-in-time user creation and admin, user and read-only roles. Audit logs are evidenced only for deleted monitors. We found no public information on a Terraform provider, client sub-accounts with their own logins, white-label client reports, or exporting audit logs to a SIEM. 6 7 8 15 16
Uptime reports, data & the vendor's own reliability
Show reasoningHide reasoning
How this is scored
What the record is worth and whether the monitor itself can be trusted: uptime and SLA reports per monitor and period, response time charts and percentiles, scheduled reports by email, client-facing reports, how long check results and incident history are kept, export of results by CSV or API, the vendor's own public status page and incident history, its SLA, the probe IP addresses and user agent published for allow-listing, and an open-source or self-hosted edition.
0 — No history of any kind; only the current state is shown.
3 — An uptime percentage and a response time chart per monitor; retention, export and the vendor's own status are basic or not described.
5 — Uptime and response time reports per monitor and period, SLA reports, scheduled email reports, the retention period of check results stated, CSV or API export, the probe IPs published, and the vendor's own public status page.
8 — Response time percentiles and breakdowns (DNS, connect, TLS, first byte), client-ready branded reports, retention of a year or more stated per plan, a raw export of check results, the vendor's incident history and post-mortems public, and an SLA with credits published.
10 — A record that holds up in an audit: SLA calculations with their method stated, incident records suitable for ISO 27001, NIS2 or DORA evidence, full history exportable in an open format, a self-hosted or open-source edition with feature parity stated, and the vendor's own availability over several years published.
The Agency Developer
Uptime windows of a day to a quarter with the mean of 90 daily buckets stated and maintenance excluded, duration percentiles, scheduled daily, weekly and monthly email reports, 12 months of retention, and static probe IPs available in four regions are documented. We found no public information on branded client-ready reports, raw result export, the vendor's own public status page, or an SLA with credits. 2 3 4 5 8 9
The SaaS Platform Engineer
Twelve months of uptime and response-time retention globally and by region, scheduled daily, weekly and monthly email reports, duration percentiles with p50 through p99 aggregates, and a stated uptime formula (mean of 90 daily buckets, scheduled maintenance excluded) make the record defensible. Opt-in static probe IPs across US West, US East, EU West and EU Central help with allow-listing, and a metrics API retrieves performance data. We found no public information on an SLA with credits, the vendor's own status page or post-mortems, client-facing branded reports, or CSV export of raw check results. 3 4 5 9 15
The Customer Support Lead
Uptime and response time are retained for 12 months globally and by region, scheduled email reports go out daily, weekly or monthly, duration percentiles and p50 through p99 metric aggregates are charted, the published uptime figure is explained as a mean of 90 daily buckets with maintenance excluded, monitors export to YAML, static probe IPs are available in four regions, and the vendor states its own uptime as 99.997% over the last 12 months. We found no public information on an SLA with credits, client-ready branded reports, a raw export of check results, or the vendor's own public status page and incident history. 3 4 5 15 16
The E-Commerce Operations Manager
Uptime is shown per component for the last day, week, month or quarter with the calculation method published (mean of 90 daily buckets, scheduled maintenance excluded), uptime and response time retained for 12 months globally and by region, scheduled email reports go out daily, weekly or monthly, a Metrics API retrieves performance and reliability numbers, and static probe IPs in four regions can be allow-listed at our firewall. What I miss for the agency conversation: I found no public information on SLA reports with credits, client-ready branded reports, a raw export of check results, or the vendor's own status page and incident history beyond a 99.997 percent uptime claim over 12 months. 3 4 5 6 9 13
The Information Security Officer
Uptime and response time are retained for twelve months globally and by region, scheduled email reports go out daily, weekly and monthly, and the uptime calculation is documented — a mean of daily buckets with scheduled maintenance excluded and long incidents included — which is a method an auditor can actually re-perform. Metrics are retrievable through the API with p50 to p99 aggregates, and monitor configurations export as YAML. We found no public information on the vendor's own public status page and incident history, an SLA with credits, a raw export of check results, or response-time breakdowns by DNS, connect and TLS. 3 4 5 6 15
The Skeptic
Twelve months of uptime and response-time retention is stated globally and by region, scheduled daily, weekly and monthly email reports exist, percentiles run to p99, and the uptime number's method is published — a mean of 90 daily buckets with maintenance excluded and long incidents kept in. The vendor's own record is where I look hardest, and it is thin: a self-reported "99.997% UPTIME LAST 12 MONTHS" figure, while we found no public information on Cronitor's own public status page or incident history, an SLA with credits, a raw export of check results, or the actual probe IP addresses behind the static-IP feature. 3 4 5 9 15
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where account data, alert contacts (names and phone numbers of the people on call), status page subscribers and check results are stored and processed, and who the subprocessors are (hosting, SMS and phone gateways, email delivery, support and payment tools). Independently sourced by the sovereignty pipeline. Probe locations outside Europe are part of what the product does and are not counted against it; where the data is stored and who processes it is. A self-hosted or open-source edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (SMS and call gateways, email, support, payment) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every record on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, or a self-hosted open-source edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The Agency Developer
The contracting entity is Cronitor, Inc., a company founded and based in California, and we found no public information on where account data, alert contacts or check results are hosted, which subprocessors process them, or a data processing agreement. For hosting European client sites that chain is entirely undocumented on the captured pages. 4 5
The SaaS Platform Engineer
The contracting entity is Cronitor, Inc., founded in California, so the vendor sits outside Europe. We found no public information on where account data and alert contacts are stored, the subprocessor chain behind SMS, email and hosting, or a data processing agreement. The European probe regions are part of what the product does and are not weighed either way here. 4 5 8
The Customer Support Lead
The contracting entity is Cronitor, Inc, founded in California in 2014; we found no public information on where account data, alert contacts, status page subscribers and check results are stored or processed, who the subprocessors are, or whether a data processing agreement is offered. For a company whose customers are tax advisers and payroll offices, no European element of the chain can be confirmed from the public pages. 5 8 4
The E-Commerce Operations Manager
The contracting entity is Cronitor, Inc., founded and based in California, and the captured pages give no information on where account data, on-call phone numbers, status page subscribers or check results are stored, which subprocessors handle SMS, email or payments, or whether a data processing agreement is offered. For a shop selling across Germany, Austria and Switzerland this is the part I cannot assess at all from the public pages — only the company's seat is documented, and European probe regions do not tell me who processes the data. 4 5
The Information Security Officer
The contracting entity is Cronitor, Inc., a California company, and we found no public information in the captured pages on hosting location, data residency, the subprocessor list or a data processing agreement. For a tool that would hold our on-call staff's phone numbers and status page subscribers' email addresses, that leaves the entire processing chain undocumented; we found no public information on a self-hosted edition of the service — the open-source pieces are SDKs and a CLI, not the monitoring service itself. 4 5 8
The Skeptic
What is proven is that the contracting party is American: Cronitor, Inc., founded in California, © 2026 Cronitor, Inc. Beyond that the chain is dark — we found no public information on where account data, the names and phone numbers of the people on call, status page subscribers or check results are stored, on the subprocessors behind hosting, SMS, email and payments, or on a data processing agreement. For a European buyer this is the first question, and the captured pages do not answer it. 4 5 8
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per tier by number of monitors, check interval and status pages, team seats and on-call responders, what SMS and phone alerts cost, which features (multi-step or browser checks, SSO, longer retention, private locations, white-label) cost extra, the free tier and its limits, overage handling, minimum term and VAT.
0 — No public prices at all; every customer is a sales call.
3 — A starting price or a free tier exists, but how cost scales with monitors, intervals, seats or alerts is unclear.
5 — Tiers are public with their monitor count, interval and main inclusions, but at least one commonly needed piece (SMS or call alerts, extra seats, extra status pages, SSO, longer retention) is unpriced or "on request".
8 — Every tier priced publicly with its scaling rule (monitors, interval, seats, responders, status pages), SMS and call costs stated, add-ons priced, overage handling stated, minimum term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given number of monitors, interval, team size and alert volume, with every add-on, overage and support fee and the cancellation and data-return terms published.
The Agency Developer
Per-monitor and per-user pricing is public with a worked billing example, add-ons priced individually ("$1/mo per 1,000 checks" browser checks, "$25/mo per page" branded and "$50/mo per page" private status pages, "+$5/mo per user" SAML), SMS and on-call alerts listed as included, no base fee, and cancel-anytime monthly billing — I can compute a two-hundred-monitor annual bill from public pages alone. We found no public information on VAT treatment or overage handling. 2 8
The SaaS Platform Engineer
Unit pricing is public with no base fee — Business at "$2 /mo per monitor + $5 /mo per user", a free tier with five monitors, and priced add-ons: synthetic browser checks at "$1 /mo per 1,000 checks", branded status pages at "$25 /mo per page", private pages at "$50 /mo per page", and SAML SSO at "+$5/mo per user", with Enterprise "from $6,000/yr annual invoice billing". The pricing page even shows a worked example of $55 /mo for 20 monitors and 3 users, billed monthly with no contract. SMS and on-call alerts are listed among Business inclusions, but we found no public information on per-message or phone-call costs, VAT treatment, or overage handling. 8
The Customer Support Lead
The Business plan is priced at $2/mo per monitor + $5/mo per user with a worked example of $55/mo for 20 monitors and 3 users, no base fee and no contract; synthetic browser checks cost $1/mo per 1,000 checks, web analytics $10/mo per 100,000 events after 100,000 free, a branded status page $25/mo per page, a private page $50/mo per page, SAML SSO +$5/mo per user, and Enterprise starts from $6,000/yr annual invoice billing, with check frequency, subscriber and status page limits shown per tier. VAT treatment and per-country phone costs are the pieces we found no public information on. 8
The E-Commerce Operations Manager
The Business plan is "$2 /mo per monitor + $5 /mo per user" with a worked example of 20 monitors and 3 users totalling "$55 /mo", no base fee and no contract, and the add-ons are priced: single sign-on at "+$5/mo per user", branded status pages at "$25 /mo per page", private pages at "$50 /mo", synthetic browser checks at "$1 /mo per 1,000 checks" — and SMS and on-call alerts are included rather than per message, which is what I care about in peak season. I found no public information on VAT treatment, overage handling or per-call pricing, so the exact annual figure still needs one question to the vendor. 8
The Information Security Officer
Unit prices are fully public — $2/mo per monitor and $5/mo per user with a worked example bill, SAML at +$5/mo per user, branded pages at $25/mo per page, private pages at $50/mo per page and synthetic browser checks at $1/mo per 1,000 checks — alongside a free tier, a 14 day Business trial, monthly billing with no contract and Enterprise from $6,000/yr. SMS and on-call alerts are stated as included in the Business plan, and subscriber and status-page counts are listed per tier. We found no public information on VAT treatment or on what the Enterprise plan costs beyond its starting figure, so the annual total for a large deployment cannot be fully computed from public pages. 2 8
The Skeptic
Unusually computable from one page: "$2 /mo per monitor + $5 /mo per user", a worked bill (20 monitors, 3 users, "$55 /mo billed monthly, no contract"), a free tier of 5 monitors, browser checks at "$1 /mo per 1,000 checks", branded pages at "$25 /mo per page", private pages at "$50 /mo per page", SAML SSO at "+$5/mo per user", and cancel-anytime. We found no public information on VAT treatment, overage handling, or what phone alerts cost; SMS is only described as included on Business. Enterprise is quoted "from $6,000/yr" on annual invoice billing — a sales conversation above that floor. 8
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Cronitor
Is Cronitor European?
No. whats-best.ai classifies Cronitor as Rest of world.
Where does Cronitor store data?
Not stated on the vendor’s pages as of 1 Nov 2026.
Does Cronitor have a free plan?
Yes. Cronitor has a free plan, per the vendor’s page captured 1 Nov 2026.
What are the best alternatives to Cronitor?
As of 2 Nov 2026, the panel rates Hyperping (3.5/5), Checkly (3.5/5) and openstatus (3.5/5) highest among the other 14 Uptime Monitoring & Status Pages products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Hyperping (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Cronitor alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- We found no public information on compliance on the pages we read (cronitor.io, cronitor.io/cron-job-monitoring, cronitor.io/uptime-monitoring, cronitor.io/heartbeat-monitoring, cronitor.io/status-pages, cronitor.io/docs/api and 10 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 5 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 pricing fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (16)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage cronitor.io Checked 1 Nov 2026 Details →
- 2 Features page (cron job monitoring) cronitor.io Checked 1 Nov 2026 Details →
- 3 Features page (uptime monitoring) cronitor.io Checked 1 Nov 2026 Details →
- 4 Features page (heartbeat monitoring) cronitor.io Checked 1 Nov 2026 Details →
- 5 Features page (status pages) cronitor.io Checked 1 Nov 2026 Details →
- 6 API documentation cronitor.io Checked 1 Nov 2026 Details →
- 7 Documentation (SAML single sign-on) cronitor.io Checked 1 Nov 2026 Details →
- 8 Pricing page cronitor.io Checked 1 Nov 2026 Details →
- 9 Checks, locations & failure confirmation — found from sitemap cronitor.io Checked 1 Nov 2026 Details →
- 10 Checks, locations & failure confirmation — found from sitemap cronitor.io Checked 1 Nov 2026 Details →
- 11 Alerting, escalation & on-call — found from sitemap cronitor.io Checked 1 Nov 2026 Details →
- 12 Alerting, escalation & on-call — found from sitemap cronitor.io Checked 1 Nov 2026 Details →
- 13 Status pages & incident communication — found from sitemap cronitor.io Checked 1 Nov 2026 Details →
- 14 Status pages & incident communication — found from sitemap cronitor.io Checked 1 Nov 2026 Details →
- 15 API, monitoring as code & team administration — found from sitemap cronitor.io Checked 1 Nov 2026 Details →
- 16 API, monitoring as code & team administration — found from sitemap cronitor.io Checked 1 Nov 2026 Details →