Tell your users what's down before they ask

A public or private web page that shows the current status and 90-day uptime history of each part of your product, plus open incidents and planned maintenance. You build it from components (a service like "API" or "Checkout", or a group that nests services under a heading), host it on a checkly-status-page.com subdomain or your own domain, and let users subscribe for incident updates by email, RSS, Atom, or a Slack feed.

You create an automation rule on the status page with one or more tags, the components it should impact, the impact each gets (degraded performance, partial outage, major outage, or under maintenance), and the first and last update messages. When a check carrying one of those tags fails and triggers an alert, Checkly opens one incident, updates the components, and notifies subscribers if you chose to. When the check recovers, the rule posts the last update and resolves the incident. Rules can also be defined in code with the StatusPageV3AutomationRule construct. Incident automation is available on the Communicate Team and Enterprise plans.

Every plan, including the free Hobby plan, includes one status page with up to 20 services and 250 subscribers. Communicate Starter raises that to 25 services and 500 subscribers and adds a custom domain. Communicate Team adds incident automation, maintenance windows on the page, password protection, theme customization, 50 services, and 1,000 subscribers. Enterprise adds white labeling, 100 services, 2,000 subscribers, and a custom number of pages. Full details are on the pricing page.

Per component, over the last 90 days, from incident impacts. Time under a major outage counts as 100% downtime, partial outage counts as 30%, and degraded performance or maintenance count as 0%. Overlapping incidents on the same component never double-count. Uptime is driven by incidents, not raw check results: without an automation rule or a manually opened incident, a failing check does not lower the number, so the page shows what you have actually communicated.

Yes, on Communicate Starter and above. Add the domain to your status page, create a CNAME record pointing at your page's checkly-status-page.com address (set to DNS only if you use Cloudflare), and add the TXT records Checkly shows you to verify ownership. Verification is also what lets search engines index the page.

Visitors click "Get updates" on the page and enter their email. After they confirm a verification email, they receive a message for every incident update, including the one that resolves it, unless you opt out of notifying subscribers on a specific update. Anyone can also follow the page anonymously through its RSS or Atom feed, or run /feed subscribe against the Slack feed URL in a channel. Feed followers do not count toward your subscriber limit.

Yes. StatusPageV3 defines the page, StatusPageV3Component defines each service or group, and StatusPageV3AutomationRule defines the rules that open incidents. All three are TypeScript constructs in the Checkly CLI, so they are versioned in git, reviewed in pull requests, and deployed with your checks. Already built a page in the app? Run checkly import status-page:<id> to pull it, its components, and its rules into your project, or reference it with StatusPageV3.fromId() and manage only the parts you want in code.