Built-in uptime monitoring and status pages for SaaS products, APIs and websites.
A status page is a public web page that shows whether a service and its components are working, lists active incidents and scheduled maintenance, and keeps a history of past uptime. Customers check it during an outage instead of opening support tickets, so one update reaches everyone at once.
Read the full guide: how status pages work and how to run oneUsers check one page during an outage instead of asking support if you're down.
Failed checks open the incident and update the page. Nobody copies status by hand.
Monitoring, incident response and your status page live in the tool you already use.
HTTP, TCP, TLS and SSH checks run from once a minute to once a day, mapped to components users recognize, like Checkout.
A component turns red only after 2 failed runs in a row, and green after 2 passes. One flaky probe never reaches customers.
Every check result is a stream. Pull the logs and traces behind a failed run without switching tools.
Post an incident or maintenance notice once. It appears on every page that shows the affected components.
Serve the page on status.yourcompany.com with your logo and colors. Domains are DNS-verified before they go live.
Open a page to everyone, password-protect it for key accounts, or embed a live badge and Atom feed in your app and docs.
Uptime is calculated from confirmed incident time, so the percentage always matches the bars. Maintenance never counts as downtime.
Visitors read a cached snapshot rebuilt every 60 seconds. A rush of users during an outage never touches your data.
Incidents, notices, branding, password protection and 90-day history included.
Enough for 5 checks every 5 minutes, or 1 check every minute.
Billed on Pay-as-you-go and Enterprise plans. Free and trial plans pause checks.
| Example page | Runs / month | Cost / month |
|---|---|---|
| 10 checks every 5 min | 86,400 | $10.80 |
| 20 checks every 5 min | 172,800 | $32.40 |
| 10 checks every minute | 432,000 | $97.20 |
Self-hosting? Open-source OpenObserve includes status pages.
See OpenObserve Cloud pricingWhat goes on one, public vs private pages, how uptime is calculated, and how to communicate during an incident. With a product walkthrough video.
Create a page, map components, publish, add a custom domain.
The API and browser checks behind your uptime monitoring.
Investigate and resolve what the status page reports.
Route alerts from your logs, metrics and traces to on-call.
Track the reliability targets behind your public uptime.
Synthetics, data ingestion and plan details.
Monitor your services, fix incidents with your team, and share your status with customers.
AI Observability by OpenObserve
OpenTelemetry-native observability for agents and LLMs.
