What it does
OpenStatus combines managed uptime checks with status pages and incident response. Monitors can send configurable HTTP requests, evaluate response assertions and latency thresholds, and report results by region. Teams can route alerts to notification services and connect an incident to customer-facing status updates. The hosted dashboard is one way to manage the service; its API, CLI, Terraform provider, and MCP server offer automation paths. OpenStatus also publishes an AGPL-3.0 self-hostable project.
Start with an endpoint
The official monitor tutorial lists an OpenStatus account and a public URL as prerequisites. Create a monitor, give it a name and URL, then choose request details such as method, headers, or body when a basic check is not enough. Assertions can check response status, headers, or body; latency thresholds can distinguish a slow response from an outright failure. The service reports timing phases as well as total response time. For example, a checkout API monitor could assert that a POST returns the expected status and that its response stays under a chosen latency threshold.
Checks run from selected regions, with per-region results to help distinguish a broad outage from a localized problem. A monitor can send notifications to services such as Slack, PagerDuty, email, or a webhook. Teams can also publish status pages and maintain an incident timeline, linking detection to customer communication; the monitoring service does not itself repair the endpoint.
Plans and operating choices
The site shows a $0 Hobby plan with one monitor and one status page, with checks every 10 minutes. Starter is shown at $30 per month, and the pricing page describes a 14-day Starter trial without a card. Paid-plan limits for check frequency, regions, and response-log retention vary. The public URL checker is available without an account, but the monitor tutorial requires an account for persistent monitoring. The project is self-hostable under AGPL-3.0; operating the self-hosted stack is separate from the hosted plan prices.
Strengths
- Checks endpoints from multiple regions and exposes individual regional results rather than only a single aggregate.
- HTTP checks can assert on status codes, headers, response bodies, and latency.
- Monitoring can connect to notification channels, status pages, and an incident timeline.
- The API, CLI, Terraform provider, and MCP server provide several ways to automate workspace changes.
Watch out for
- The $0 Hobby plan is limited to one monitor and one status page, with checks every 10 minutes.
- Monitoring a service on a private network requires deploying a private probe in that network.
Best for
- Checking public websites and API endpoints from more than one geographic region
- Teams that want uptime alerts and customer-facing status updates in one workflow
- Managing monitors and status pages through an API, CLI, Terraform, or MCP client
Sources
- Open Source Status Page, Uptime Monitoring & Incident Response (Oct 25, 2026)
- Website & API Uptime Monitoring from 28 Regions (Oct 25, 2026)
- openstatus documentation | openstatus (Oct 25, 2026)
- Create an Uptime Monitor in 5 Minutes | openstatus (Oct 25, 2026)
- Pricing — Free Status Page and Uptime Monitoring Plans (Oct 25, 2026)
- Status Page and Uptime Monitoring API — openstatus (Oct 25, 2026)
- openstatus/LICENSE at main · openstatusHQ/openstatus · GitHub (Oct 25, 2026)