openstatus

Openstatus is an open-source uptime monitoring and status page platform. It runs synthetic checks in parallel from 28 regions across Fly.io, Koyeb, and Railway, surfaces incidents on branded status pages, and exposes a REST API plus MCP server for programmatic control. Available as managed SaaS or self-hosted (AGPL-3.0). Bootstrapped, founded in 2023.

Who it's for

Development teams that want transparent incident communication
Companies that need multi-region uptime monitoring
Teams that prefer infrastructure-as-code workflows (monitoring as code via YAML)
Organizations that require self-hosted monitoring behind a firewall (private locations)
Open-source projects and startups looking for a free or affordable monitoring solution

Pricing

Hobby — $0/month: 1 monitor, 6 regions, 10m check interval, 1 status page, 3 page components, 14-day data retention
Starter — $30/month: 20 monitors, 28 regions, 1m check interval, 1 status page, 20 components, 3-month retention, subscribers, custom domain, WhatsApp/SMS/PagerDuty alerts
Pro — $100/month: 50 monitors, 28 regions, 30s check interval, 5 status pages, 50 components, 12-month retention, private locations, OTel exporter, 20 notification channels
Scale — $500/month: everything in Pro plus 10 status pages, 500 page components, and White Label, Magic Link auth, and IP Restriction included at no extra cost

Annual billing gives 2 months free (Starter $300/yr, Pro $1,000/yr, Scale $5,000/yr). Pricing is available in USD and EUR.

Key Features

28-region monitoring — Parallel checks across Europe, North America, South America, Asia, Africa, and Oceania; no round-robin, all selected regions fire simultaneously
Multi-cloud — Monitors run on Fly.io, Koyeb, and Railway for true cloud diversity
Status Pages — Branded public or password-protected pages with custom domains, themes, maintenance windows, and subscriber notifications (email, RSS, Slack)
API Monitoring — Assertions, thresholds, status code checks, header and body validation
Monitoring as Code — Define monitors in YAML, manage via CLI or GitHub Actions
Private Locations — 8.5MB Docker image for monitoring internal services behind firewalls
Alerting — Email, Slack, Discord, webhook, WhatsApp, SMS, PagerDuty, OpsGenie, Grafana OnCall
OpenTelemetry — Export synthetic check metrics to any OTLP endpoint
SDK — Node.js SDK on JSR (@openstatus/sdk-node)
MCP server — Streamable-HTTP MCP at https://api.openstatus.dev/mcp for status reports, maintenance windows, and monitor reads
Open-source — AGPL-3.0-licensed, self-hostable, 8k+ GitHub stars

Key Differentiators

Open-source and bootstrapped (no VC funding)
Parallel scheduling — all selected regions check simultaneously (vs. round-robin competitors)
Unlimited team members on paid plans
Status page subscribers included (not a paid add-on)
Private status pages included in the team plan (not an additional charge)
Self-hosting option with full feature parity

Product

Status Page: Turn transparency into trust with a dedicated status page. Keep users informed during downtime, so you can focus on the fix.
Uptime Monitoring: Monitor your websites and APIs from 28 regions across multiple cloud providers. Get instant alerts via Slack, Discord, email, and more. Open source with a free plan available.

Tooling

API: A typed JSON-over-HTTP API powered by ConnectRPC — every endpoint the dashboard uses, with a fully typed Node SDK on top.
CLI: Manage monitors, status pages, and incidents from your terminal — interactive for humans, scriptable for agents, and YAML-managed for monitoring as code.
MCP Server: Connect Claude, ChatGPT, Cursor, and any other Model Context Protocol client to your workspace — chat-shaped AI access with audit-logged mutations and explicit notify semantics.
Terraform: Manage monitors, notifications, and status pages as HCL — same plan-and-apply lifecycle as the rest of your infrastructure, with one command to bootstrap from an existing workspace.

Documentation

Building Trust with Status Pages: Understanding how to communicate effectively during incidents and build user trust through transparency.
Foundational Concepts: Understand uptime monitoring, latency vs response time, SLA calculations, and the design decisions behind openstatus.
Understanding Latency vs Response Time: Deep dive into the difference between latency and response time, and why both matter for monitoring
Understanding Private Locations: What a private location is, when to use one, how it talks to openstatus, and how it differs from a public probe.
Probes, Locations, and Regions: Three words that look interchangeable but aren't — what each one means in openstatus and how they fit together.
Uptime Calculation and Shared Values: Understand how openstatus calculates uptime — absolute (duration or requests) and manual modes — and choose which values to share on your status page.
Understanding Monitoring as Code: Why and how to manage monitoring configuration as code for GitOps workflows
Understanding Uptime Monitoring: A deep dive into uptime monitoring concepts, architecture, and best practices
How-to Guides: Practical guides for integrating openstatus with GitHub Actions, OTLP endpoints, Cloudflare, and more.
How to Deploy a Status Page to Cloudflare Pages: Learn how to use openstatus monitoring data to deploy a status page on Cloudflare Pages.
How to Add a Status Badge to a GitHub README: A step-by-step guide to adding a real-time SVG or PNG status badge to your GitHub repository.
Configure Your Status Page: A step-by-step tutorial to customize and configure your status page
Connect openstatus to Claude Code: Step-by-step tutorial to add the openstatus MCP server to Claude Code so the agent can read and manage your status pages from the terminal
Create a Private Location: Set up monitoring from your own infrastructure using Docker-based private probes
How to Deploy a Private Probe on Cloudflare Containers: A step-by-step guide to deploying an openstatus private monitoring probe on Cloudflare Containers.
How to Embed a Status Page in an Iframe: Embed a trimmed, chromeless version of your openstatus status page on any website using the ?embed query parameter.
How to Export Metrics to an OTLP Endpoint: A step-by-step guide to sending openstatus metrics to your observability platform via OTLP.
Import a Status Page from Another Provider: Import your existing status page setup from Atlassian Statuspage, Better Stack, or Instatus into openstatus
Manage Your openstatus Stack with Terraform and the CLI: Use Terraform to manage monitors, status pages, and notifications as code — and the openstatus CLI to handle incident status reports.
How to Monitor Your Model Context Provider (MCP) Server: Learn how to monitor your MCP server with openstatus using JSON-RPC ping checks
How to Run Synthetic Tests in GitHub Actions: Integrate openstatus synthetic monitoring into your CI/CD pipeline
Set Up the openstatus Slack Agent: A step-by-step tutorial to install the openstatus Slack agent and manage incidents directly from Slack
How to translate your status page: Enable multiple languages on your status page and contribute new translations.
How to Use openstatus React Widget: Add an openstatus status widget to your React or Next.js app with the @openstatus/react package, as a server or client component.
Self-Host the openstatus Status Page (Lightweight): Deploy only the openstatus status page and dashboard on your own infrastructure, without monitoring, analytics, or background services.
How to Self-Host openstatus: Complete guide to deploying openstatus on your own infrastructure
Need help?: We're always here to help.
CLI Reference: Complete reference for the openstatus CLI — manage status pages, monitors, and incidents from your terminal.
DNS Monitor Reference: Complete technical specification for DNS record monitoring
HTTP Monitor Reference: Complete technical specification for HTTP/HTTPS endpoint monitoring
Incident Reference: Technical specification for incident management and lifecycle
Location Reference: Complete technical specification for Location monitoring
Maintenance Reference: Technical specification for scheduled maintenance windows in openstatus.
MCP Server: Connect openstatus to AI assistants via the Model Context Protocol
Notification Channels Reference: Technical specification for openstatus notification channels and alert payloads.
Reference Overview: Technical specifications for openstatus monitors, status pages, notifications, locations, and the CLI, MCP, and Terraform integrations.
Page Components Reference: Complete specification for openstatus page components on status pages.
Private Location Reference: Technical specification for configuring and utilizing private monitoring locations.
Status Page Reference: Complete technical specification for openstatus status page configuration.
Status Report Reference: Technical specification for incident status updates within openstatus.
Subscriber Reference: Technical specification for managing status page subscribers and their notifications.
TCP Monitor Reference: Complete technical specification for TCP service monitoring.
Terraform Provider Reference: Technical specification for the openstatus Terraform Provider.
Authentication: Configure API key authentication for the openstatus Node.js SDK
Error Handling: Handle errors and implement retry strategies with the openstatus Node.js SDK
Getting Started: Install and start using the openstatus Node.js SDK
Health Service: Check the openstatus API health status using the Node.js SDK
Maintenance Service: Manage scheduled maintenance windows with the openstatus Node.js SDK
Monitor Service: Create and manage HTTP, TCP, and DNS monitors with the openstatus Node.js SDK
Notification Service: Manage notification channels and providers with the openstatus Node.js SDK
Node.js SDK: Interact with openstatus programmatically from your JavaScript and TypeScript applications
Reference: Complete reference for enums, regions, assertions, and TypeScript type exports in the openstatus Node.js SDK
Status Page Service: Manage status pages, components, groups, and subscribers with the openstatus Node.js SDK
Status Report Service: Manage incident reports and status updates with the openstatus Node.js SDK
TypeScript Tips: Tips for working with bigint fields, oneof types, and migrating clients in the openstatus Node.js SDK
PHP SDK: Interact with openstatus programmatically from your PHP applications
Python SDK: Interact with openstatus programmatically from your Python applications
Create an Uptime Monitor in 5 Minutes: Set up your first uptime monitor with openstatus — track response time, status codes, and availability from 28 global regions.
Create a Status Page: A step-by-step tutorial to create and publish your first status page
Get Started with openstatus CLI: Step-by-step tutorial to install and use the openstatus CLI for monitoring as code
Tutorials Overview: Step-by-step tutorials to create monitors, status pages, and private locations with openstatus.
Wire Up Your First Notification: Send your first alert from openstatus — create a notification channel, attach it to a monitor, and confirm an alert lands.
Publish Your First Status Report: Open, update, and resolve a status report from the openstatus dashboard — the four-state workflow your users will see during an incident.

Guides

API Service Disruption Template: Professional template for communicating API outages and third-party service failures to your users.
Best Open Source Status Page Tools in 2026: Compare the top open-source status page tools in 2026. We review openstatus, Cachet, Vigil, Statping-ng, and Upptime to help you pick the right one for your team.
Status Pages Should Be Boring: Your status page has one job: tell users if your service is down. Learn why the best status pages prioritize speed, reliability, and simplicity over flashy design and modern frameworks.
Connect Openstatus to Claude Code (MCP Setup Guide): Wire the openstatus MCP server into Claude Code so the agent can list status pages, draft incidents, and schedule maintenance from your terminal — with audit-logged mutations and explicit notify semantics.
Connect Openstatus to Claude Desktop (MCP Setup Guide): Add the openstatus MCP server to Claude Desktop so the assistant can list status pages, draft incidents, and schedule maintenance from chat — with audit-logged mutations and explicit notify semantics.
Database Performance Degradation Template: Technical template for communicating database latency and performance issues to your engineering-focused audience.
Deployment Rollback Template: Template for communicating deployment failures and rollback procedures during service disruptions.
Feature Degradation Template: Template for communicating partial service degradation where some features are impacted but the service remains available.
HTTP Headers Every Developer Should Know: A practical reference for common HTTP request and response headers, security headers, and the cloud provider-specific headers you'll encounter when monitoring APIs.
Incident Severity Matrix Template: Ready-to-use templates for classifying and communicating incidents by severity level. Covers status page message templates, postmortem requirements, and real-world examples for SEV0 through SEV3.
How to Migrate from Atlassian Statuspage to openstatus: Step-by-step guide to import your Atlassian Statuspage components, incidents, maintenances, and subscribers into openstatus.
How to Migrate from Better Stack to openstatus: Step-by-step guide to import your Better Stack monitors, status page, components, incidents, and maintenances into openstatus.
How to Migrate from Instatus to openstatus: Step-by-step guide to import your Instatus status page, components, incidents, maintenances, and subscribers into openstatus.
Network Connectivity Issues Template: Template for communicating network outages, CDN problems, and regional connectivity issues to affected users.
Public Postmortems are Underrated Marketing: Public incident postmortems build more trust than marketing campaigns. Learn why companies share detailed root cause analyses and how radical transparency during outages proves engineering maturity.
Public vs Private Status Pages: Learn the key differences between public and private status pages, when to use each, and how to match transparency to your audience - customers, teams, and partners.
Scheduled Maintenance Template: Proactive template for communicating planned maintenance windows, upgrades, and scheduled downtime to users.
Security Incident Response Template: Formal template for communicating security issues with professional, reassuring language that maintains user trust.
SLA vs SLO vs SLI Explained: Learn the critical differences between SLAs, SLOs, and SLIs. Understand how to measure service reliability, set internal targets, and make customer promises without over-committing or under-delivering.
Deliver Status Updates to Customer Slack Channels: Already share a Slack Connect channel with your enterprise customers? Route incident and maintenance updates into it, scoped to the components each customer depends on - no new channel, no integration code.
Top Five Atlassian Statuspage Alternatives: Explore the best alternatives to Atlassian Statuspage including OpenStatus, Status-io, Datadog Status Page, Instatus, and Betterstack.
What Is a Status Page?: A status page is a public web page that communicates the real-time health of your service - uptime, ongoing incidents, scheduled maintenance, and historical reliability. Here's what they include, why they matter, and how to build one that actually helps users.
What Is Incident Management?: Incident management is the process teams use to detect, respond to, resolve, and learn from service disruptions. Here's the lifecycle, the roles, the severity model, and what separates teams that handle incidents well from those who don't.
What Is MTTR? (And the Other MTT-Whatevers): MTTR is the average time it takes to recover from an incident. But there are four different MTT- metrics that get confused regularly. Here's what each one actually measures, how to calculate them, and how to actually move the numbers.
What Is Synthetic Monitoring?: Synthetic monitoring uses scripted, automated checks to simulate user behavior against your service from external locations. Here's how it differs from real user monitoring, the types of synthetic checks, and when each is worth running.
What Is Uptime Monitoring?: Uptime monitoring is the practice of continuously checking whether your service is reachable and responding correctly from outside your own network. Here's how it works, how uptime percentages are actually calculated, and what to monitor.
Why Every SaaS Needs a Status Page: Status pages aren't optional anymore. Learn why transparent service communication reduces support load, retains customers, and builds trust that marketing campaigns can't replicate.
Why Uptime Percentage Alone is Misleading: 99.9% uptime sounds impressive until you realize it tells you nothing about user experience. Learn why availability percentages hide the real story and what to measure instead.

Use Cases

Status Page for AI Agent: Let an AI agent run your status page. It receives openstatus webhooks, uses the openstatus MCP to investigate the failing monitor, files the status report, posts updates as it learns more, and resolves the report once the monitor recovers — all without waking anyone up.
Status Pages for API Infrastructure: Your API consumers expect transparency. Give them a branded status page with real-time uptime data, incident history, and subscription channels — powered by monitoring from 28 regions.
SOC 2-Ready Status Page in 2 Minutes: SOC 2 auditors expect documented incident communication. Openstatus gives you a branded status page with incident history, subscriber notifications, and audit-ready evidence — set up in minutes.
Status Pages for Crypto Exchanges and DeFi Protocols: Keep your traders and users informed during outages. Monitor exchange APIs, wallet services, and blockchain nodes from 28 global regions with a branded, trustworthy status page.
Status Pages for Enterprise Sales: Enterprise prospects expect a status page. When their security team sends a vendor questionnaire, a branded status page with uptime history and incident communication turns a blocker into a checkbox.
Status Pages for Open-Source Projects: Give your open-source community a transparent view of service health. Free status page with uptime monitoring, incident history, and community-friendly subscriptions.
Status Pages for Reducing Support Tickets: Every minute of downtime floods your inbox. A status page deflects support tickets by giving users a single source of truth — with real-time incident updates and subscriber notifications.
Status Pages for Startups: Early-stage startups need a status page before they think they do — for enterprise sales, SOC 2 audits, and SLA agreements. Openstatus gives you a branded, audit-ready status page in minutes with monitoring included.

Comparisons

Atlassian Statuspage vs openstatus: Looking for an Atlassian Statuspage alternative with built-in monitoring? openstatus includes 28-region uptime checks, flat pricing with no per-subscriber fees, and is fully open source.
BetterStack vs openstatus: openstatus vs BetterStack compared side-by-side. 28 regions (parallel) vs 4 (round-robin), open-source vs closed-source, and transparent pricing with no add-on fees for status pages or subscribers.
Checkly vs openstatus: Looking for a Checkly alternative focused on uptime monitoring and status pages? openstatus checks from 28 regions, includes public status pages, and is open source — starting free.
Incident.io vs openstatus: Looking for an incident.io alternative that combines monitoring with status pages? openstatus detects outages from 28 regions and communicates them to users — open source and starting free.
Instatus vs openstatus: Looking for an Instatus alternative with real uptime monitoring? openstatus monitors from 28 regions simultaneously, is fully open source, and includes status pages with subscriber notifications.
Status.io vs openstatus: Looking for a Status.io alternative with built-in monitoring? openstatus includes 28-region uptime checks, starts at $30/mo with unlimited team members, and is open source and self-hostable.
Uptime Kuma vs openstatus: openstatus vs Uptime Kuma compared side-by-side. Both open-source, but openstatus offers managed SaaS + 28-region global monitoring. Uptime Kuma is self-hosted only from 1 location.
UptimeRobot vs openstatus: Looking for an UptimeRobot alternative that checks from 28 regions at once? openstatus is open source, includes status pages and CI/CD integration, and supports OpenTelemetry export.

Playground

Global Speed Checker: Check the speed of your website from around the world.
cURL Builder: An online curl command line builder. Generate curl commands to test your API endpoints.
MCP Server Health Check: Free online MCP server health check. Test JSON-RPC initialize, ping, and tools/list handshake from your browser — no install, no signup.
Incident Severity Matrix Builder: Classify incidents with deterministic, auditable rules. Customize thresholds, test scenarios, and export a ready-to-use template for your runbook.
Uptime SLA Calculator - Convert Uptime % to Downtime: Free uptime SLA calculator. See how much downtime 99.9%, 99.99%, or 99.999% uptime allows per day, week, month, and year. Convert any uptime percentage to downtime instantly.

openstatus

openstatus

Who it's for

Pricing

Key Features

Key Differentiators

Product

Tooling

Documentation

Guides

Use Cases

Comparisons

Playground

Pages

Blog

Changelog

Optional