Source
Features page (uptime monitoring) — Cronitor
Checked for Cronitor on 1 Nov 2026
- Page
- https://cronitor.io/uptime-monitoring
- Checked
- 1 Nov 2026, 10:36 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:3976a5e1395abafac9fcdc98170354dfe65ea6e680f9f6a826b655c46de70cad
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Check interval Report an error
“30-second checks from 12+ locations worldwide.”
-
Locations Report an error
“Pick up to 12 regions across 5 continents and check as often as every 30 seconds.”
-
History retention Report an error
“Uptime and response time are retained for 12 months, globally and by region”
-
Verified downtime Report an error
“Cronitor verifies downtime from at least one additional region before alerting, so a single bad probe does not page anybody.”
-
Assertions Report an error
“Set assertions for status code, page content, response time, and certificate expiry.”
-
Javascript checks Report an error
“Checks that need JavaScript run in a real Chrome browser.”
-
Status pages Report an error
“Any check can publish to a public or private status page, so customers and internal teams read the same uptime data you do.”
-
Alert integrations Report an error
“Route alerts through 10+ integrations.”
-
Failure modes Report an error
“01 HOST UNREACHABLE DNS doesn't resolve, the connection is refused, or nothing answers at all. 02 CERTIFICATE EXPIRING Your SSL certificate is about to expire — with days of warning, not a browser interstitial. 03 500 INTERNAL SERVER ERROR The status code isn't the one the check asked for. 04 REQUEST TIMES OUT The response takes longer than the budget you set for it. 05 CONTENT MISSING The page loads, returns 200, and no longer contains your expected content.”
-
Coverage Report an error
“Add checks for websites, APIs, servers, firewalls, and other endpoints — including SSH bastions, mail servers, and VPNs.”
-
Check interval range Report an error
“CHECK INTERVAL 30s — 24h”
-
Config methods Report an error
“CONFIGURED BY dashboard · API · YAML”
-
Config as code Report an error
“Provision and version-control checks with YAML and the Cronitor CLI.”
-
Custom requests Report an error
“You can send custom methods, headers, and request bodies to test real API behavior, not just reachability.”
-
Mcp monitoring Report an error
“Configure a POST with a stateless JSON-RPC tools/list request and assert the status and JSON response.”
-
Platform modules Report an error
“01 Jobs Monitor cron jobs and scheduled agents. 02 Checks Check uptime, performance, and SSL. 03 Heartbeats Monitor any source with a heartbeat. 04 Status Pages Share uptime on a public or private status page. 05 Analytics Track website traffic, errors, and performance.”
-
Per region latency Report an error
“Per-region latency, measured against that region's own median.”
-
SSO docs Report an error
“Configure SAML SSO”
-
Free tier hint Report an error
“Start for free”
Scores citing this record
- The Agency Developer Checks, locations & failure confirmation
- The Agency Developer Uptime reports, data & the vendor's own reliability
- The Customer Support Lead Checks, locations & failure confirmation
- The Customer Support Lead Uptime reports, data & the vendor's own reliability
- The E-Commerce Operations Manager Checks, locations & failure confirmation
- The E-Commerce Operations Manager Uptime reports, data & the vendor's own reliability
- The SaaS Platform Engineer Checks, locations & failure confirmation
- The SaaS Platform Engineer Uptime reports, data & the vendor's own reliability
- The Information Security Officer Checks, locations & failure confirmation
- The Information Security Officer Uptime reports, data & the vendor's own reliability
- The Skeptic Checks, locations & failure confirmation
- The Skeptic Uptime reports, data & the vendor's own reliability