Build trust during downtime by keeping customers informed from the first failure through recovery. Monitors can open and resolve incidents automatically.
No active incidents.
Add any Cronitor uptime check, cron job, heartbeat, or group. Its current status and uptime history appear automatically, so monitor changes update the page without extra work.
Group related monitors under one component and let customers expand the details. For third-party services outside Cronitor, add a component you update by hand or through the API.
Let customers view the last 24 hours, 7 days, 30 days, or 90 days. Scheduled maintenance is left out, and long-running incidents stay in the calculation even when they began before the selected window.
Publish a page for everyone, protect it with a password, or limit it to approved IPs. Readers can subscribe by email, RSS, or webhook, and each page keeps its own access and notification settings.
Webhook subscriptions are confirmed by email before the first update is sent.
Monitors can report that a service failed and recovered. Your team can explain what happened, what is affected, and what customers should expect next.
Create or edit incidents by hand, backdate updates, and move an incident from investigating through resolved. Schedule maintenance ahead of time, and manage the same workflow through the API.
missing_dataoperationalmaintenancedegraded_performanceminor_outageoutage
# the same update, over the API $ curl -X PUT https://cronitor.io/api/issues/9f2b4c7ae10d6835 \ -H "Authorization: Bearer $CRONITOR_API_KEY" \ -d '{ "severity": "minor_outage", "state": "identified", "updates": [{ "state": "identified", "message": "A certificate expired inside an upstream provider at 02:14 UTC.", // backdate the update, not the incident "timestamp": "2026-08-11T02:31:00Z" }] }' # everything else on the page is scriptable too # /api/statuspages /api/statuspage_components # /api/issues /api/maintenance_windows
Every incident has a shareable link, so support can send customers to the same source of truth.
Start with a name and one component. Cronitor hosts the page for you, or you can connect your own domain with HTTPS included.
A failing monitor opens an incident. Recovery resolves it.
When a service flaps, repeated failures stay in one incident and the timeline stays readable.
Let readers switch between the last 24 hours, 7 days, 30 days, and 90 days.
Schedule work ahead of time and keep it out of your uptime calculation.
Group related services into one row, with details available when customers need them.
Use your own domain. Cronitor handles HTTPS and warns you when DNS is misconfigured.
Publish publicly, require a password, or restrict access by IP address or range.
Let customers subscribe by email or webhook, with confirmation before updates begin.
Send updates to Slack, Teams, Discord, or any feed reader.
Embed current status in a README or website with SVG or JSON.
Keep production and staging pages separate without duplicating monitors.
Add the checks, cron jobs, and heartbeats you already monitor. When a monitor changes state, the status page updates with it — without a second tool or custom integration.