OpenUptime

What you can monitor

One place for your websites, APIs, certificates, domains, databases and scheduled jobs. Each page explains what a check does and when it alerts.

Website monitoringKnow when your site stops loading, starts returning errors or quietly serves the wrong page, before your visitors tell you.API monitoringAn API can answer quickly and still be broken. Send the request your clients send and check what comes back.SSL certificate monitoringAn expired certificate takes a site offline for every browser at once. Find out weeks ahead, not from your users.Domain expiry monitoringWhen a domain lapses, its website, email and APIs go with it. Get a reminder while you still have time to renew.DNS monitoringA wrong DNS record breaks a site or mail as surely as a crashed server, and cached answers hide it for hours. Check the record itself.TCP port monitoringNot every service speaks HTTP. A port check tells you whether the service is listening and how long the connection takes.Cron job monitoringA job that silently stops is worse than one that fails loudly. A heartbeat monitor waits for your job to check in, and tells you when it does not.WebSocket monitoringLive updates, chat and trading feeds run over WebSocket, where an HTTP check sees nothing. Check the connection the way your app uses it.MCP server monitoringAI agents fail quietly when an MCP server is down or a tool changes under them. Check the server the way an agent connects to it.Database monitoringWhen the database stops answering, every page that needs it fails. Check the server directly, without giving the monitor a login.Blockchain node monitoringAn RPC node that answers HTTP can still be behind the chain. Ask the node whether it is in sync.

On every monitor

  • Alerts by email, Slack, Discord, Teams, Telegram, PagerDuty, webhooks, Lark, ntfy and the mobile app.
  • Recovery thresholds, so an incident closes only after the service has answered several times in a row.
  • Dependencies: a monitor that depends on another stays quiet while that one is down.
  • Maintenance windows, incident history and public status pages built from the same monitors.
Start monitoringCompare plans

Questions

What can OpenUptime monitor?

Websites and APIs over HTTP, SSL certificates, domain expiry, DNS records, TCP ports, PostgreSQL, MySQL and Redis, WebSocket endpoints, MCP servers, EVM and Solana nodes, and cron jobs through heartbeats.

Do all monitor types cost the same?

A check uses one credit whatever its type, times the number of regions it runs from. Heartbeat pings use none. SSL certificate checks need Lite or above.

Which types can check from several regions?

Website and API (HTTP), TCP port, WebSocket and MCP monitors. The others run from the main location.

可以监控什么

网站、API、证书、域名、数据库和定时任务，都在一个地方监控。每一页都会说明检查做了什么，以及什么时候告警。

网站监控在访客告诉你之前，先知道网站打不开、开始报错，或者悄悄返回了错误的页面。API 监控API 可能响应很快，却已经坏了。发送和你的客户端相同的请求，检查返回的内容。SSL 证书监控证书一过期，所有浏览器都会同时打不开网站。提前几周知道，而不是等用户来告诉你。域名到期监控域名一过期，网站、邮件和 API 都会跟着失效。在还来得及续费的时候收到提醒。DNS 监控一条错误的 DNS 记录和服务器崩溃一样会让网站或邮件失效，而缓存会把问题掩盖好几个小时。直接检查记录本身。TCP 端口监控不是每个服务都用 HTTP。端口检查会告诉你服务是否在监听，以及建立连接需要多久。定时任务监控悄悄停掉的任务比大声报错的任务更糟糕。心跳监控等待你的任务按时报到，没报到就提醒你。WebSocket 监控实时更新、聊天和行情推送都跑在 WebSocket 上，HTTP 检查看不到它们。按照应用的实际用法检查连接。MCP 服务器监控MCP 服务器宕机或工具悄悄变化时，AI Agent 会无声地失败。按照 Agent 连接它的方式检查服务器。数据库监控数据库一旦不响应，所有依赖它的页面都会出错。直接检查服务器，而且不需要给监控任何登录凭据。区块链节点监控能响应 HTTP 的 RPC 节点，也可能已经落后于链上。直接问节点自己是否已同步。

所有监控通用

  • 通过邮件、Slack、Discord、Teams、Telegram、PagerDuty、Webhook、飞书、ntfy 和手机 App 告警。
  • 可设置恢复阈值，服务连续多次正常后故障才结束。
  • 依赖关系：依赖另一个监控的监控，在被依赖方宕机期间不会告警。
  • 维护窗口、故障历史，以及由同一组监控生成的公开状态页。
开始监控比较套餐

常见问题

OpenUptime 能监控什么？

通过 HTTP 监控网站和 API，以及 SSL 证书、域名到期、DNS 记录、TCP 端口、PostgreSQL、MySQL 和 Redis、WebSocket 端点、MCP 服务器、EVM 和 Solana 节点，还可以通过心跳监控定时任务。

所有监控类型的价格一样吗？

无论哪种类型，每次检查消耗 1 个额度，再乘以检查的区域数。心跳请求不消耗额度。SSL 证书检查需要 Lite 或以上套餐。

哪些类型支持多区域检查？

网站和 API（HTTP）、TCP 端口、WebSocket 和 MCP 监控。其他类型从主节点检查。