Source
Features page (status pages) — Checkly
Checked for Checkly on 1 Nov 2026
- Page
- https://www.checklyhq.com/product/status-pages/
- Checked
- 1 Nov 2026, 10:20 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:6492b3260c302dfc84dc8c5b8b1ecef3e46dcf2d39559ea064e29f4eb06a7c89
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Incident automation plans Report an error
“Incident automation is available on the Communicate Team and Enterprise plans.”
-
Hobby limits Report an error
“Every plan, including the free Hobby plan, includes one status page with up to 20 services and 250 subscribers.”
-
Communicate starter Report an error
“Communicate Starter raises that to 25 services and 500 subscribers and adds a custom domain.”
-
Communicate team Report an error
“Communicate Team adds incident automation, maintenance windows on the page, password protection, theme customization, 50 services, and 1,000 subscribers.”
-
Enterprise tier Report an error
“Enterprise adds white labeling, 100 services, 2,000 subscribers, and a custom number of pages.”
-
Automation rule behavior Report an error
“An automation rule matches failing checks by tag. When a check with that tag fails, Checkly opens one incident on the components you listed, posts your first update, and resolves it when the check recovers.”
-
Automation cool down Report an error
“cool down 5 min”
-
Uptime calculation Report an error
“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 requires incidents Report an error
“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”
-
Managed as code Report an error
“The page, its components, and its automation rules are TypeScript constructs in your repo. Import a page you built in the UI with one CLI command and keep it in version control from then on.”
-
Constructs Report an error
“StatusPageV3 defines the page, StatusPageV3Component defines each service or group, and StatusPageV3AutomationRule defines the rules that open incidents.”
-
Cli import Report an error
“checkly import status-page:<id> pulls a page you built in the UI into code”
-
UI parity Report an error
“Prefer the UI? Everything here has full parity in the app.”
-
Custom domain Report an error
“Serve the page from status.yourcompany.com with a CNAME and a TXT record.”
-
Subdomain hosting Report an error
“host it on a checkly-status-page.com subdomain or your own domain”
-
Feeds Report an error
“RSS, Atom, and Slack feeds for anyone who would rather not hand over an email”
-
Password protection Report an error
“Password protection for internal pages; account members sign in with Checkly”
-
Planned maintenance Report an error
“Planned maintenance shown on the page, with reminders up to 7 days ahead”
-
Maintenance suppression Report an error
“Planned maintenance can suppress automated incidents on the components it covers.”
-
SEO indexing Report an error
“Custom domain with DNS verification, so search engines can index the page”
-
Feature gating Report an error
“Custom domains start on Communicate Starter. Password protection, maintenance on the page, and theme customization are on Team and Enterprise.”
-
Feed subscriber limit Report an error
“Feed followers do not count toward your subscriber limit.”
-
Manual updates Report an error
“Post extra updates by hand whenever you learn more.”
-
Manual incidents Report an error
“without an automation rule or a manually opened incident, a failing check does not lower the number”
-
Cloudflare cname note Report an error
“DNS only if proxied through Cloudflare”
-
Impact levels Report an error
“the impact each gets (degraded performance, partial outage, major outage, or under maintenance)”
-
Free tier no credit card Report an error
“One status page on every plan. No credit card required.”
3 facts read from this page are not shown because they could not be confirmed on the page as captured.
Scores citing this record
- The Agency Developer Status pages & incident communication
- The Agency Developer Pricing transparency
- The Customer Support Lead Status pages & incident communication
- The E-Commerce Operations Manager Status pages & incident communication
- The SaaS Platform Engineer Status pages & incident communication
- The Information Security Officer Status pages & incident communication
- The Information Security Officer Pricing transparency
- The Skeptic Status pages & incident communication