Website uptime monitoring
Know when your site stops loading, starts returning errors or quietly serves the wrong page, before your visitors tell you.
What each check does
- Requests the URL, follows redirects and records the status code and the response time.
- Compares the status with the one you expect, 200 by default.
- Optionally looks for a keyword in the page, or makes sure an error message is absent.
When it alerts
- No answer within the timeout (10 seconds by default), a refused connection or a TLS error.
- A status other than the expected one, or a keyword check that does not pass.
- You choose how many failed checks in a row open an incident: 1, 2, 3, 5 or 10.
https://example.comGood to know
- Expect a redirect: set the status to 301 or 302 and the Location it should point to, and the redirect itself is checked.
- Check from several regions and count a failure only when most of them fail, so one bad route does not page you.
- Get a separate alert when the site is up but slower than a threshold you set, after 3, 5 or 10 slow checks.
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.
Try it on the Free plan
The Free plan includes 3 monitors checked every 5 minutes, with every alert channel. No card needed.
Questions
How often is my website checked?
Every 5 minutes on the Free plan, every minute from Lite and every 30 seconds on Team. Each check uses one credit of your monthly allowance.
Why use a keyword check?
A broken page often still returns 200: a blank template, a maintenance banner or an error rendered by the application. Looking for a word that only appears on a working page catches it.
Does it work behind Cloudflare or another CDN?
Yes. The check opens the public URL like a visitor would. If your CDN challenges automated requests, allow the OpenUptime user agent or add a header the CDN lets through.
网站可用性监控
在访客告诉你之前，先知道网站打不开、开始报错，或者悄悄返回了错误的页面。
每次检查做什么
- 请求这个 URL，跟随重定向，记录状态码和响应时间。
- 把状态码和你预期的值比较，默认是 200。
- 可以在页面中查找关键词，或确认某段错误信息没有出现。
什么时候告警
- 在超时时间内（默认 10 秒）没有响应、连接被拒绝或 TLS 出错。
- 状态码不是预期值，或关键词检查没有通过。
- 连续失败多少次才开启故障由你决定：1、2、3、5 或 10 次。
https://example.com使用说明
- 检查重定向：把预期状态码设为 301 或 302，并填写应跳转到的 Location，检查的就是重定向本身。
- 从多个区域检查，只有多数区域失败才算一次故障，一条线路出问题不会把你叫醒。
- 网站可以访问但比你设定的阈值慢时，在连续 3、5 或 10 次变慢后单独提醒你。
所有监控通用
- 通过邮件、Slack、Discord、Teams、Telegram、PagerDuty、Webhook、飞书、ntfy 和手机 App 告警。
- 可设置恢复阈值，服务连续多次正常后故障才结束。
- 依赖关系：依赖另一个监控的监控，在被依赖方宕机期间不会告警。
- 维护窗口、故障历史，以及由同一组监控生成的公开状态页。
常见问题
多久检查一次网站？
免费版每 5 分钟一次，Lite 起每分钟一次，Team 套餐每 30 秒一次。每次检查消耗每月额度中的 1 个。
为什么要用关键词检查？
坏掉的页面常常仍返回 200：空白模板、维护横幅，或应用自己渲染的错误页。查找一个只会出现在正常页面上的词，就能发现这些情况。
网站在 Cloudflare 或其他 CDN 后面能用吗？
可以。检查会像访客一样打开公网 URL。如果 CDN 会拦截自动化请求，请放行 OpenUptime 的 User-Agent，或添加一个 CDN 会放行的请求头。