OpenUptime as a Pingdom alternative
Pingdom is an established hosted service for website monitoring, with transaction checks and real user monitoring. OpenUptime covers uptime, incidents and status pages, with the source open and a self-hosted option.
Pingdom is a closed-source, hosted product from SolarWinds. Besides uptime checks it offers synthetic transaction monitoring, real user monitoring and page speed measurements. Information about other products is general and may be out of date. Check their own sites for current features and pricing.
At a glance
| Topic | OpenUptime | Pingdom |
|---|---|---|
| License | MIT license, source on GitHub | Closed source |
| Where it runs | Hosted service, or self-host with Docker and Postgres, or on Cloudflare Workers with Postgres | Hosted by the vendor only |
| Uptime checks | HTTP and HTTPS (expected status, keyword must or must not appear, custom headers), TCP, DNS, heartbeat, PostgreSQL, MySQL / MariaDB and Redis reachability | Website and server uptime checks from the vendor's locations |
| Transaction checks and real user monitoring | Not available | Offered as separate products |
| Status pages | Public status pages with grouped components, incident history, email subscriptions, an RSS feed and an embeddable badge | Offered; check their docs for details |
| Pricing | Free to self-host. The hosted service has plans; check the current ones | Check their current pricing |
What OpenUptime does not do
Check this list before you switch. It is short, and it is complete as of this page.
- No TLS certificate expiry monitoring.
- No ICMP ping monitor; use a TCP or HTTP check instead.
- No browser-based or multi-step transaction checks, and no real user monitoring.
- No SMS or phone-call alerts and no on-call rotation schedules. Escalation works by channel and by minutes unacknowledged.
- Database monitors check that the server answers; they send no credentials and run no queries.
What Pingdom is known for that OpenUptime does not do
- Scripted, multi-step transaction checks and real user monitoring. OpenUptime checks one request at a time.
- Page speed measurement. OpenUptime records response time of each check but does not analyse page loads.
Who each is best for
Pick Pingdom if
- You need to test a sign-in or checkout flow step by step, or measure what real visitors experience.
- You already run other SolarWinds tools and want one vendor.
Pick OpenUptime if
- A request that returns the right status and the right keyword is all you need to know about.
- You want an open-source tool, a self-hosted copy, or monitors managed by API or MCP.
- You also want to watch TCP ports, DNS, cron heartbeats and database reachability in the same place.
Moving from Pingdom
- Write your uptime checks as a JSON list with a name, a url or hostname, the interval in seconds and the type. Transaction checks have no equivalent and are not part of the list.
- The importer reads name (or friendly_name), target (or url, hostname, host), interval in seconds, and type (http, https, keyword, tcp, port, dns, heartbeat, postgres, mysql, redis). Intervals below 60 seconds are raised to 60.
- Open Monitors in OpenUptime and upload the JSON file with the import button, or send it to POST /api/monitors/import. Up to 500 monitors per file. Entries that cannot be imported are listed with the reason and the rest are created.
- Alert channels, status pages and incident history are not imported. Add your channels under Alerting, then create a status page and pick the monitors for it.
- Run both tools side by side for a few days before you switch alerts off in the old one, and compare the incidents each one opens.
Questions
How do I move my Pingdom monitors to OpenUptime?
Put your monitors in a JSON list and import it on the Monitors page or through the API. The importer accepts common field names used by other tools, skips entries it cannot read and reports why. Channels and status pages are set up again by hand.
What does Pingdom do that OpenUptime does not?
OpenUptime has no TLS certificate expiry monitoring, no ICMP ping monitor, no browser or multi-step checks, and no SMS, phone-call or on-call schedule features. If you rely on one of those, check whether the other tool covers it before you switch.
Can OpenUptime replace Pingdom transaction checks?
Not directly. OpenUptime checks single requests: status code, a keyword that must or must not appear, and custom headers. You can point separate monitors at the key steps of a flow, but it cannot click through a page.
Is OpenUptime cheaper than Pingdom?
Self-hosting costs only the infrastructure you run it on. The hosted service has plans, and Pingdom changes its own pricing from time to time, so compare the current pricing pages of both for the number of monitors and check interval you need.
Try OpenUptime
Start on the hosted service, or run it yourself. The source is on GitHub under the MIT license.
Pingdom 的替代方案：OpenUptime
Pingdom 是老牌托管的网站监控服务，提供事务检测和真实用户监控。OpenUptime 覆盖可用性、事件和状态页，源码公开，并可自托管。
Pingdom 是 SolarWinds 旗下的闭源托管产品。除可用性检测外，还提供合成事务监控、真实用户监控和页面速度测量。 关于其他产品的信息只是概括，可能已经过时。当前功能和价格请以其官网为准。
对比一览
| 项目 | OpenUptime | Pingdom |
|---|---|---|
| 许可证 | MIT 许可证，源码在 GitHub | 闭源 |
| 运行方式 | 托管服务；也可用 Docker 加 Postgres 自托管，或部署到 Cloudflare Workers 加 Postgres | 仅由厂商托管 |
| 可用性检测 | HTTP / HTTPS（预期状态码、关键字必须出现或不得出现、自定义请求头）、TCP、DNS、心跳、PostgreSQL、MySQL / MariaDB 与 Redis 连通性 | 从厂商的检测节点对网站和服务器做可用性检测 |
| 事务检测与真实用户监控 | 不提供 | 作为独立产品提供 |
| 状态页 | 公开状态页，支持分组、事件历史、邮件订阅、RSS 与可嵌入的状态徽章 | 提供；详情请查看其文档 |
| 价格 | 自托管免费。托管服务有各档套餐，请查看最新方案 | 请查看其最新价格 |
OpenUptime 没有的功能
切换之前请先看这份清单。它不长，截至本页是完整的。
- 不监控 TLS 证书到期。
- 没有 ICMP ping 监控；可改用 TCP 或 HTTP 检测。
- 没有基于浏览器或多步骤的事务检测，也没有真实用户监控。
- 没有短信或电话告警，也没有值班排班表。升级按告警渠道和未确认的分钟数进行。
- 数据库监控只检查服务端是否应答，不发送凭据，也不执行查询。
Pingdom 擅长而 OpenUptime 没有的功能
- 脚本化的多步骤事务检测和真实用户监控。OpenUptime 每次只检测一个请求。
- 页面速度测量。OpenUptime 会记录每次检测的响应时间，但不分析页面加载过程。
各自适合谁
适合选择 Pingdom 的情况
- 你需要逐步测试登录或结账流程，或衡量真实访客的体验。
- 你已经在用 SolarWinds 的其他工具，希望统一厂商。
适合选择 OpenUptime 的情况
- 你只需要知道请求是否返回了正确的状态码和关键字。
- 你想要开源工具、自托管的副本，或通过 API 或 MCP 管理监控项。
- 你还想在同一处监控 TCP 端口、DNS、定时任务心跳和数据库连通性。
从 Pingdom 迁移
- 把可用性检测整理成 JSON 列表，每项包含名称、url 或 hostname、以秒为单位的间隔和类型。事务检测没有对应功能，不在列表范围内。
- 导入时会识别 name（或 friendly_name）、target（或 url、hostname、host）、以秒为单位的 interval，以及 type（http、https、keyword、tcp、port、dns、heartbeat、postgres、mysql、redis）。小于 60 秒的间隔会提升到 60 秒。
- 在 OpenUptime 的监控页用导入按钮上传 JSON 文件，或发送到 POST /api/monitors/import。每个文件最多 500 个监控项。无法导入的条目会连同原因一并列出，其余照常创建。
- 告警渠道、状态页和事件历史不会被导入。请在告警页添加渠道，再创建状态页并选择要展示的监控项。
- 先让两个工具并行运行几天，再关闭旧工具的告警，并对比两边各自创建的事件。
常见问题
如何把 Pingdom 的监控项迁移到 OpenUptime？
把监控项整理成 JSON 列表，在监控页或通过 API 导入。导入器接受其他工具常见的字段名，读不懂的条目会被跳过并说明原因。告警渠道和状态页需要手动重新设置。
Pingdom 有哪些 OpenUptime 没有的功能？
OpenUptime 没有 TLS 证书到期监控、ICMP ping 监控、浏览器或多步骤检测，也没有短信、电话告警或值班排班功能。如果你依赖其中之一，切换前请先确认。
OpenUptime 能替代 Pingdom 的事务检测吗？
不能直接替代。OpenUptime 检测的是单个请求：状态码、必须或不得出现的关键字，以及自定义请求头。你可以为流程中的关键步骤分别建立监控项，但它无法模拟页面点击。
OpenUptime 比 Pingdom 便宜吗？
自托管只需承担运行它的基础设施成本。托管服务有各档套餐，Pingdom 的价格也会不时调整，请对照两边当前的价格页，按你需要的监控数量和检测间隔来比较。