Publish a clear status, not your private monitor configuration.
Keep your audience informed
Keep customers informed with your own status page. Publish selected components, incident updates and maintenance notices. Private settings stay private.
Free to use · view quotasTwo example series · solid and dashed
Two example series · solid and dashed
Two example series · solid and dashed
Last 30 days · gaps remain visible
Example service status
- WebsiteCurrent
- Public APIMaintenance
Data coverage: 90%
What you can monitor
Three ways to make the result useful
Connect results, incidents and status updates. Data gaps stay visible.
Choose what becomes public
Explain incidents and maintenance
Show honest availability
Understand your data
A consistent view across your services
Prepare privately, review sources and publish explicitly. Editors and publishers have separate permissions. History distinguishes outages, maintenance and gaps.
Two example series · solid and dashed
Two example series · solid and dashed
Two example series · solid and dashed
Last 30 days · gaps remain visible
Example service status
- WebsiteCurrent
- Public APIMaintenance
Data coverage: 90%
Your first steps
Your first steps
Connect your source in three steps.
- 01
Create a private draft
Choose a page name and the components your audience needs.
- 02
Review sources and content
Approve the source information and preview both language and theme.
- 03
Publish deliberately
Release the approved version and share its public link.
Good to know
Frequently asked questions
Answers and setup guides.
Does creating a page publish it?
Are internal alarm messages public?
Your next step
Make the next step clear
Choose your setup and connect your first source.