# OpenUptime

> OpenUptime is an open source uptime monitor with status pages and an MCP server, so an AI agent can run your monitoring. It is MIT licensed, runs on Cloudflare Workers and Postgres or in Docker, and is also available as a hosted service.

The hosted service is operated by BECOOL INC. in Toronto, Canada. Contact: hi@openuptime.app.

## Key facts

- HTTP, HTTPS, TCP, DNS, PostgreSQL, MySQL and Redis checks, with keyword matching and slow-response alerts
- Heartbeat monitors for cron jobs and background workers
- SSL certificate expiry monitoring (hosted service, Lite and above)
- Checks every minute, every 30 seconds on the Team plan
- Multi-region checks from probes you can also run yourself
- Alerts to Slack, Lark / Feishu, Telegram, PagerDuty, email and webhooks
- Incidents that open and resolve automatically, with manual updates and maintenance windows
- Public status pages with 90-day history, email and RSS subscribers, and custom domains on paid plans
- A complete REST API and API keys
- An MCP server with OAuth, scoped to workspaces or projects
- Workspaces, projects and roles
- Self-hosting on Cloudflare Workers and Postgres or in Docker, MIT licensed

## Documentation

- [Self-host](https://openuptime.app/docs/self-host): Run your own copy on Cloudflare Workers or in Docker, with a Postgres database you control.
- [API reference](https://openuptime.app/docs/api): Manage monitors, incidents, alert channels and status pages with JSON over HTTPS.
- [MCP server](https://openuptime.app/docs/mcp): Let an AI agent such as Claude or Cursor manage monitors, incidents and status pages.
- [Multi-region checks](https://openuptime.app/docs/regions): Check one monitor from several regions and run your own probes.
- [Embed your status](https://openuptime.app/docs/embed): Show the live state of a status page on your site or in a README.

## Product

- [About](https://openuptime.app/about): what OpenUptime is, who operates it, and what it does not do
- [Pricing](https://openuptime.app/pricing): the Free, Lite, Starter and Team plans, and what the checks allowance means
- [Changelog](https://openuptime.app/changelog): what changed and when
- [Source code](https://github.com/becoolme/openuptime): MIT licensed

## Comparisons and articles

- [Your redirects are part of your product, so monitor them](https://openuptime.app/blog/redirect-monitoring): A normal uptime check follows redirects and reports 200, so a forgotten or broken redirect goes unnoticed. How redirects get lost in migrations and deploys, and how to check the redirect itself.
- [Setting up a status page: what to show and what to leave off](https://openuptime.app/blog/status-page-guide): A status page is only useful if people believe it. How to pick components, link them to real checks, write incident updates, and keep API status honest.
- [Node.js, PHP and eMudhra: what to patch (October 2026)](https://openuptime.app/blog/nodejs-php-emudhra-patch-week): Node.js security releases, two critical PHP remote-code-execution bugs and eight distrusted eMudhra intermediates: what changed, what to update, and what monitoring can and cannot tell you.
- [Why Postgres and not D1 (the short answer is Docker)](https://openuptime.app/blog/why-postgres-not-d1): OpenUptime runs on Cloudflare Workers but keeps its data in Postgres. Four reasons, an honest list of what it costs, and why D1 is not ruled out.
- [How to monitor SSL certificate expiry before visitors see a warning](https://openuptime.app/blog/ssl-certificate-expiry-monitoring): Get a notice 14, 7, 3 and 1 days before an HTTPS certificate expires, with two ways to set it up and what is checked.
- [How to monitor a cron job and get alerted when it stops running](https://openuptime.app/blog/cron-job-monitoring): Use a heartbeat monitor so a missed backup, report or sync raises an alert instead of going unnoticed: one curl at the end of the job, a grace period and a failure threshold.
- [Manage your uptime monitors from Claude with the OpenUptime MCP server](https://openuptime.app/blog/openuptime-mcp-claude): Connect Claude, Cursor or Codex to OpenUptime in one command, choose exactly what the agent may reach, and manage monitors, incidents and status pages in plain language.
- [Meet OpenUptime, an open source uptime monitor you can run yourself](https://openuptime.app/blog/introducing-openuptime): What an open source uptime monitor does when your site goes down at 3 a.m., what it keeps an eye on, and how to run it: hosted, in Docker, or on your own Cloudflare account.
- [Statuspage alternative: monitoring and a public page in OpenUptime](https://openuptime.app/blog/statuspage-alternative): Compare an integrated monitor and status page with Atlassian’s dedicated incident-communication product.
- [Uptime Kuma alternative: compare two open source monitors](https://openuptime.app/blog/uptime-kuma-alternative): Compare setup, monitoring scope, team workflows and the features that differ between OpenUptime hosted and MIT editions.
- [Better Stack alternative: when OpenUptime is enough](https://openuptime.app/blog/better-stack-alternative): A focused uptime monitor or a full incident-response platform? Compare responder pricing, checks and operational tradeoffs.
- [UptimeRobot alternative: OpenUptime vs UptimeRobot](https://openuptime.app/blog/uptimerobot-alternative): Compare free plans, real check capacity, team access and self-hosting before moving your monitors.

## Optional

- [Complete text of this site's key pages](https://openuptime.app/llms-full.txt)
- [Support](https://openuptime.app/support), [Imprint](https://openuptime.app/imprint), [Privacy Policy](https://openuptime.app/privacy), [Terms of Service](https://openuptime.app/terms)
- [简体中文首页](https://openuptime.app/zh-Hans)