Skip to content

Open-source status page, incident response and uptime monitoring

seo: consolidate competitor pages and repoint three guides (#2609)

Thibault Le Ouay7aeea0cecddc
diff --git a/apps/web/next.config.ts b/apps/web/next.config.ts
index cfe7daf92..f3911b2a1 100644
--- a/apps/web/next.config.ts
+++ b/apps/web/next.config.ts
@@ -205,6 +205,26 @@ const nextConfig: NextConfig = {
destination: "/docs/guides/how-to-connect-openstatus-to-claude-code",
permanent: true,
},
+ {
+ source: "/compare/atlassian-statuspage",
+ destination: "/guides/top-five-atlassian-statuspage-alternatives",
+ permanent: true,
+ },
+ {
+ source: "/compare/instatus",
+ destination: "/guides/top-five-instatus-alternatives",
+ permanent: true,
+ },
+ {
+ source: "/compare/pingdom",
+ destination: "/guides/top-five-pingdom-alternatives",
+ permanent: true,
+ },
+ {
+ source: "/compare/uptime-kuma",
+ destination: "/guides/hosted-uptime-kuma-alternative",
+ permanent: true,
+ },
];
},
async rewrites() {
diff --git a/apps/web/src/content/pages/compare/atlassian-statuspage.mdx b/apps/web/src/content/pages/compare/atlassian-statuspage.mdx
deleted file mode 100644
index b6e7c0441..000000000
--- a/apps/web/src/content/pages/compare/atlassian-statuspage.mdx
+++ /dev/null
@@ -1,140 +0,0 @@
----
-title: "Atlassian Statuspage vs openstatus"
-publishedAt: "2026-02-21"
-author: "openstatus"
-description: "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."
-category: "company"
-faq:
- - question: "Is openstatus a good Atlassian Statuspage alternative?"
- answer: "Yes. Openstatus includes built-in uptime monitoring from 28 global regions — something Atlassian Statuspage does not offer at all. Openstatus pricing is flat ($30/mo) and does not scale with subscriber count. Atlassian Statuspage charges per subscriber tier, meaning your bill grows as your audience does. Openstatus is also open-source and self-hostable."
- - question: "Does openstatus include uptime monitoring unlike Atlassian Statuspage?"
- answer: "Yes. Atlassian Statuspage has no built-in monitoring. You must connect a separate tool (Datadog, Pingdom, etc.) to detect incidents. Openstatus monitors your endpoints from 28 regions simultaneously and can update your status page automatically based on check results."
- - question: "How does openstatus pricing compare to Atlassian Statuspage?"
- answer: "Atlassian Statuspage starts at $29/month for one page and 100 subscribers, jumping to $99/month for three pages and $399/month for custom HTML/CSS. Subscriber-count tiers add cost as your audience grows. Openstatus starts at $30/month with flat pricing, unlimited subscribers, and monitoring included."
- - question: "What does the OpsGenie shutdown mean for Statuspage users?"
- answer: "OpsGenie, Atlassian's incident management tool often used alongside Statuspage, is shutting down in April 2027. Teams using the Statuspage + OpsGenie combination will need to find replacements for both. Openstatus covers the monitoring and status page layer in one product."
- - question: "Can I self-host openstatus?"
- answer: "Yes. Openstatus is open-source (AGPL-3.0) and fully self-hostable. Atlassian Statuspage is a closed-source SaaS with no self-hosting option."
----
-
-## Looking for an Atlassian Statuspage alternative?
-
-**TL;DR:** Atlassian Statuspage has no built-in monitoring, charges per subscriber tier, and gates custom styling behind a $399/month plan. Openstatus includes monitoring from 28 regions, flat pricing with unlimited subscribers, and is fully open-source. With OpsGenie shutting down in 2027, now is a good time to simplify your stack.
-
-If you're paying for Statuspage and a separate monitoring tool on top of it, openstatus replaces both. It includes uptime monitoring from 28 global regions and a native status page in one product — with flat pricing that doesn't scale with your subscriber count. Plus, with OpsGenie shutting down in 2027, now is a good time to simplify your stack.
-
-Atlassian Statuspage is the longest-established name in status pages, but it comes with significant trade-offs: **no built-in monitoring**, pricing that scales with your subscriber count, and customization gated behind its most expensive tier. Openstatus covers monitoring and status pages in one product at a fraction of the cost, with flat pricing and an open-source codebase.
-
-The most important structural difference: Atlassian Statuspage requires you to connect a separate monitoring tool (Datadog, Pingdom, New Relic) to detect incidents. Openstatus monitors your endpoints directly from 28 regions and updates your status page automatically — no second tool, no manual webhook wiring.
-
-Additionally, OpsGenie — Atlassian's incident management product often used alongside Statuspage — is shutting down in April 2027.
-
-## Feature Comparison
-
-| Feature | openstatus | Atlassian Statuspage |
-| -------------------------- | ---------------- | ----------------------- |
-| Open-source | Yes | No |
-| Self-hosted | Yes | No |
-| Built-in uptime monitoring | Yes | No |
-| Multi-region | 28 regions | Not applicable |
-| Monitoring as code | Yes | No |
-| OpenTelemetry export | Yes | No |
-| Subscriber-count billing | Flat (unlimited) | Scales with subscribers |
-| Custom HTML/CSS | Themes included | $399/mo plan only |
-| Team members | Unlimited | Restricted by plan |
-| Developer tooling | CLI, Terraform, GitHub Actions | No official |
-
-## Pricing Comparison
-
-| | openstatus | Atlassian Statuspage |
-| ------------------- | ---------------- | --------------------------- |
-| Starting price | $30/mo | $29/mo |
-| Monitoring included | Yes (28 regions) | No (requires separate tool) |
-| Status pages | 1 (+$20/mo each) | 1 |
-| Subscribers | Unlimited | 100 (scales with cost) |
-| Custom Themes | Included | $399/mo plan |
-| Team members | Unlimited | Restricted |
-| 3 status pages | $70/mo | $99/mo |
-
-The starting prices look similar, but Atlassian Statuspage's $29/month plan only includes 100 subscribers and no monitoring. To get custom styling, you need the $399/month plan. And you still need to pay for a separate monitoring tool on top of that. Openstatus includes monitoring, unlimited subscribers, and theming from $30/month.
-
-## Built for AI and Agentic Workflows
-
-Openstatus ships a CLI that integrates natively into AI-driven workflows. Whether you're using an AI agent or building your own agentic automation, the openstatus CLI lets you create monitors, trigger checks, and manage incidents programmatically, no browser required. Atlassian Statuspage has no CLI and no tooling designed for machine-to-machine interaction.
-
-## When to Choose openstatus
-
-- You want **monitoring + status page** in a single product without wiring up a second tool
-- You need **flat, predictable pricing** that does not scale with subscriber count
-- You want **open-source** software or need to self-host
-- You are not locked into the Atlassian ecosystem (Jira, Confluence)
-- You need **monitoring-as-code**, OpenTelemetry export, or CI/CD integration
-
-## When to Choose Atlassian Statuspage
-
-- Your organization is deeply embedded in the **Atlassian ecosystem** and requires native Jira integration
-- You need enterprise **subscriber management at very large scale** with Atlassian's compliance certifications
-- Your contracts or procurement processes are already tied to **Atlassian Enterprise agreements**
-
-## Switching from Atlassian Statuspage to openstatus
-
-Atlassian Statuspage is one of the most common platforms teams switch from. Use our **[Statuspage import tool](/guides/migrate-from-atlassian-statuspage)** to automatically migrate your components, incidents, and maintenance history in minutes.
-
-1. **Sign up** for a free openstatus account — no credit card required
-2. **Import your setup** — use the [step-by-step import guide](/guides/migrate-from-atlassian-statuspage) to bring over your components, incidents, and scheduled maintenance automatically
-3. **Create monitors** — add HTTP, TCP, or DNS monitors for each component. Unlike Statuspage, openstatus detects incidents automatically from 28 regions — no need for a separate Datadog or Pingdom integration
-4. **Configure alerts** — openstatus supports Slack, Discord, Email, PagerDuty, OpsGenie, Grafana OnCall, and more
-5. **Update your DNS** — point your custom status page domain to openstatus
-6. **Cancel Statuspage + monitoring tool** — since openstatus includes monitoring, you can cancel both your Statuspage subscription and the separate monitoring service
-
-With OpsGenie shutting down in April 2027, this is also a good time to consolidate your incident detection and communication into a single tool.
-
-## Related Resources
-
-- [Top 5 Atlassian Statuspage Alternatives](/guides/top-five-atlassian-statuspage-alternatives)
-- [Migrate from Atlassian Statuspage](/guides/migrate-from-atlassian-statuspage)
-- [Why Every SaaS Needs a Status Page](/guides/why-every-saas-needs-a-status-page)
-- [Status Pages for Compliance](/use-case/compliance)
-- [Pricing](/pricing)
-
-## Frequently asked questions
-
-<Details summary="Is openstatus a good Atlassian Statuspage alternative?">
-
-Yes. Openstatus includes built-in uptime monitoring from 28 global regions — something Atlassian Statuspage does not offer at all. Openstatus pricing is flat ($30/mo) and does not scale with subscriber count. Atlassian Statuspage charges per subscriber tier, meaning your bill grows as your audience does. Openstatus is also open-source and self-hostable.
-
-</Details>
-
-<Details summary="Does openstatus include uptime monitoring unlike Atlassian Statuspage?">
-
-Yes. Atlassian Statuspage has no built-in monitoring. You must connect a separate tool (Datadog, Pingdom, etc.) to detect incidents. Openstatus monitors your endpoints from 28 regions simultaneously and can update your status page automatically based on check results.
-
-</Details>
-
-<Details summary="How does openstatus pricing compare to Atlassian Statuspage?">
-
-Atlassian Statuspage starts at $29/month for one page and 100 subscribers, jumping to $99/month for three pages and $399/month for custom HTML/CSS. Subscriber-count tiers add cost as your audience grows. Openstatus starts at $30/month with flat pricing, unlimited subscribers, and monitoring included.
-
-</Details>
-
-<Details summary="What does the OpsGenie shutdown mean for Statuspage users?">
-
-OpsGenie, Atlassian's incident management tool often used alongside Statuspage, is shutting down in April 2027. Teams using the Statuspage + OpsGenie combination will need to find replacements for both. Openstatus covers the monitoring and status page layer in one product.
-
-</Details>
-
-<Details summary="Can I self-host openstatus?">
-
-Yes. Openstatus is open-source (AGPL-3.0) and fully self-hostable. Atlassian Statuspage is a closed-source SaaS with no self-hosting option.
-
-</Details>
-
----
-
-Start monitoring from 28 regions today
-
-<ButtonLink href="https://app.openstatus.dev?ref=compare-atlassianstatuspage">
- Get Started Free
-</ButtonLink>
-
----
diff --git a/apps/web/src/content/pages/compare/checkly.mdx b/apps/web/src/content/pages/compare/checkly.mdx
index 66c2db8ae..1e648c504 100644
--- a/apps/web/src/content/pages/compare/checkly.mdx
+++ b/apps/web/src/content/pages/compare/checkly.mdx
@@ -80,6 +80,7 @@ If you rely heavily on Playwright browser checks, openstatus is not a direct rep
- [Status page](/status-page)
- [Uptime monitoring](/uptime-monitoring)
+- [How to migrate from Checkly to openstatus](/guides/migrate-from-checkly)
- [Why Every SaaS Needs a Status Page](/guides/why-every-saas-needs-a-status-page)
- [SLA vs SLO vs SLI](/guides/sla-vs-slo-vs-sli)
- [Status Pages for API Providers](/use-case/api-providers)
diff --git a/apps/web/src/content/pages/compare/instatus.mdx b/apps/web/src/content/pages/compare/instatus.mdx
deleted file mode 100644
index d1a688729..000000000
--- a/apps/web/src/content/pages/compare/instatus.mdx
+++ /dev/null
@@ -1,119 +0,0 @@
----
-title: "Instatus vs openstatus"
-publishedAt: "2026-02-21"
-author: "openstatus"
-description: "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."
-category: "company"
-faq:
- - question: "Is openstatus a good Instatus alternative?"
- answer: "Yes, especially if you need real uptime monitoring alongside your status page. Instatus is a status-page-first product with basic HTTP monitoring added later. Openstatus was built around monitoring first — checking from 28 global regions simultaneously — with status pages as a native part of the product, not a bolt-on."
- - question: "Does openstatus include a status page like Instatus?"
- answer: "Yes. Openstatus includes branded status pages with custom domains, maintenance windows, and subscriber notifications on all paid plans. The status page is tightly coupled to your monitors, so incidents and response times reflect real check results."
- - question: "How does openstatus pricing compare to Instatus?"
- answer: "Instatus starts at $20/month for one custom-domain status page. Openstatus starts at $30/month and includes uptime monitoring from 28 regions, unlimited team members, and monitoring-as-code tooling. If you need both monitoring and a status page, openstatus covers both in one plan."
- - question: "Can I self-host openstatus?"
- answer: "Yes. Openstatus is open-source (AGPL-3.0) and fully self-hostable. Instatus is a closed-source SaaS with no self-hosting option."
----
-
-## Looking for an Instatus alternative?
-
-**TL;DR:** Instatus is a status-page-first product with basic monitoring bolted on. Openstatus was built around monitoring — 28 regions, parallel checks — with status pages as a native part of the product. If you want your status page backed by real monitoring data, choose openstatus.
-
-If you want your status page backed by real monitoring — not just a pretty page with bolted-on HTTP pings — openstatus is the stronger choice. It monitors from 28 regions simultaneously and surfaces results directly on your status page, so incidents are detected and communicated automatically.
-
-Openstatus and Instatus are both alternatives to Atlassian Statuspage, but they cover different ground. Instatus is focused purely on status pages — fast, CDN-delivered, with basic monitoring bolted on as a secondary feature. Openstatus treats **monitoring and status pages as equal parts of the same product**: checks run from 28 regions simultaneously, and your status page reflects those results in real time.
-
-The practical difference: with Instatus, your status page and your monitoring live in separate worlds. With openstatus, an incident detected by a monitor can surface directly on your status page — no manual update, no webhook wiring between tools.
-
-## Feature Comparison
-
-| Feature | openstatus | Instatus |
-| --------------------- | ------------------------------ | ---------- |
-| Open-source | Yes | No |
-| Self-hosted | Yes | No |
-| Scheduling strategy | Parallel (all regions at once) | Sequential |
-| Multi-region | 28 regions | ~4 regions |
-| Monitoring as code | Yes | No |
-| OpenTelemetry export | Yes | No |
-| Developer tooling | CLI, Terraform, GitHub Actions | No |
-| Status page | Yes | Yes |
-| Unlimited subscribers | Yes | Yes |
-| Team members | Unlimited | Unlimited |
-
-## Pricing Comparison
-
-| | openstatus | Instatus |
-| ----------------------- | --------------------------------------------------------------- | ---------------------------------------------- |
-| Free plan | 1 monitor, 1 status page | 1 status page (no custom domain) |
-| Starter/paid | $30/mo | $20/mo |
-| What's included | 20 monitors + 28 regions + status page + unlimited team members | 1 custom-domain status page + basic monitoring |
-| Additional status pages | $20/mo each | Included in higher plans |
-
-Instatus is $10/month cheaper on the base plan, but it does not include the depth of monitoring openstatus offers. If you're already paying for a separate monitoring tool alongside Instatus, openstatus replaces both at a lower combined cost.
-
-## When to Choose openstatus
-
-- You need **uptime monitoring** tightly integrated with your status page
-- You want **28-region parallel checks** rather than basic single-location HTTP pings
-- You need **monitoring-as-code** via YAML, CLI, Terraform, or GitHub Actions
-- You prefer **open-source** software or need to self-host
-- You want **OpenTelemetry export** to push check results into your existing observability stack
-
-## When to Choose Instatus
-
-- You want a **pure status page** with no monitoring requirements
-- You need a **static, CDN-delivered** status page with fast global load times
-- You are migrating from Atlassian Statuspage and monitoring is handled by a separate tool
-- You want the **lowest possible price** for a standalone status page
-
-## Switching from Instatus to openstatus
-
-Use our **[Instatus import tool](/guides/migrate-from-instatus)** to automatically migrate your status pages, components, and subscribers in minutes — no manual recreation needed.
-
-1. **Sign up** for a free openstatus account — no credit card required
-2. **Import your setup** — use the [step-by-step import guide](/guides/migrate-from-instatus) to bring over your status pages, components, and subscribers automatically
-3. **Create monitors** — add HTTP, TCP, or DNS monitors for each component on your status page, with 28-region coverage
-4. **Configure alerts** — openstatus supports Slack, Discord, Email, PagerDuty, OpsGenie, and more
-5. **Update your DNS** — point your custom status page domain to openstatus
-
-## Related Resources
-
-- [Migrate from Instatus](/guides/migrate-from-instatus)
-- [Top 5 Atlassian Statuspage Alternatives](/guides/top-five-atlassian-statuspage-alternatives)
-- [Why Every SaaS Needs a Status Page](/guides/why-every-saas-needs-a-status-page)
-- [Status Pages for Compliance](/use-case/compliance)
-- [Pricing](/pricing)
-
-## Frequently asked questions
-
-<Details summary="Is openstatus a good Instatus alternative?">
-
-Yes, especially if you need real uptime monitoring alongside your status page. Instatus is a status-page-first product with basic HTTP monitoring added later. Openstatus was built around monitoring first — checking from 28 global regions simultaneously — with status pages as a native part of the product, not a bolt-on.
-
-</Details>
-
-<Details summary="Does openstatus include a status page like Instatus?">
-
-Yes. Openstatus includes branded status pages with custom domains, maintenance windows, and subscriber notifications on all paid plans. The status page is tightly coupled to your monitors, so incidents and response times reflect real check results.
-
-</Details>
-
-<Details summary="How does openstatus pricing compare to Instatus?">
-
-Instatus starts at $20/month for one custom-domain status page. Openstatus starts at $30/month and includes uptime monitoring from 28 regions, unlimited team members, and monitoring-as-code tooling. If you need both monitoring and a status page, openstatus covers both in one plan.
-
-</Details>
-
-<Details summary="Can I self-host openstatus?">
-
-Yes. Openstatus is open-source (AGPL-3.0) and fully self-hostable. Instatus is a closed-source SaaS with no self-hosting option.
-
-</Details>
-
----
-
-Start monitoring from 28 regions today
-
-<ButtonLink href="https://app.openstatus.dev?ref=compare-instatus">Get Started Free</ButtonLink>
-
----
diff --git a/apps/web/src/content/pages/compare/pingdom.mdx b/apps/web/src/content/pages/compare/pingdom.mdx
deleted file mode 100644
index 2cdf45ad7..000000000
--- a/apps/web/src/content/pages/compare/pingdom.mdx
+++ /dev/null
@@ -1,124 +0,0 @@
----
-title: "Pingdom vs openstatus"
-publishedAt: "2026-06-19"
-author: "openstatus"
-description: "Looking for a Pingdom alternative? openstatus checks from 28 regions at once, includes a built-in status page, is open source, and starts free — while Pingdom has no free tier and starts at $15/month."
-category: "company"
-faq:
- - question: "Is openstatus a good Pingdom alternative?"
- answer: "Yes, for uptime monitoring and status pages. Openstatus monitors from 28 global regions simultaneously, is open-source and self-hostable, includes a built-in public status page, and starts free. Pingdom is a closed-source SolarWinds product with no free tier and no public status page, though it offers real user monitoring (RUM) and transaction checks that openstatus does not."
- - question: "Does Pingdom still have a free plan?"
- answer: "No. Pingdom discontinued its free tier after the SolarWinds acquisition. The cheapest paid plan starts at around $15/month (billed annually) for 10 uptime checks, with a 14-day trial. Openstatus has a permanent free plan with 1 monitor across 6 regions."
- - question: "Does openstatus include a status page like Pingdom?"
- answer: "Openstatus includes a built-in branded public status page with custom domains, maintenance windows, and subscriber notifications on every plan. Pingdom does not offer a public status page product — you would need a separate tool for incident communication."
- - question: "Is openstatus open-source?"
- answer: "Yes. Openstatus is AGPL-3.0-licensed and fully self-hostable. Pingdom is a closed-source SaaS owned by SolarWinds with no self-hosting option."
----
-
-## Looking for a Pingdom alternative?
-
-**TL;DR:** Openstatus monitors from 28 regions simultaneously, includes a built-in status page, is open-source, and starts free. Pingdom is a mature closed-source SolarWinds product with real user monitoring and transaction checks — but no free tier and no public status page.
-
-If you're evaluating Pingdom and the lack of a free tier, the closed-source model, or the missing status page gives you pause, openstatus is the alternative worth a look. It's open-source, checks from 28 regions in parallel, bundles a public status page with every plan, and you can start for free.
-
-Openstatus and Pingdom overlap on uptime monitoring but diverge from there. Openstatus focuses on **uptime monitoring plus status pages** — HTTP, TCP, and DNS checks from 28 global regions, paired with a public page for incident communication. Pingdom is a broader, older **website-performance** suite that adds real user monitoring (RUM), transaction monitoring, and page-speed analysis on top of uptime checks.
-
-For teams that want global uptime checks, a status page, and developer tooling without a per-feature bill, openstatus is the more direct fit. For teams that specifically need real user monitoring or recorded transaction checks, Pingdom covers ground openstatus doesn't.
-
-## Feature Comparison
-
-| Feature | openstatus | Pingdom |
-| ------------------------ | ---------------- | -------------------- |
-| Free plan | Yes | No (14-day trial) |
-| Multi-region | 28 regions | ~100 locations |
-| Parallel scheduling | Yes | No (round-robin) |
-| Status Page | Yes (built-in) | No |
-| Open-source | Yes (AGPL-3.0) | No |
-| Self-hostable | Yes | No |
-| Monitoring as code | Yes (Terraform) | No |
-| CLI | Yes | No |
-| MCP server | Yes | No |
-| OpenTelemetry exporter | Yes | No |
-| Real user monitoring | No | Yes |
-| Transaction monitoring | No | Yes |
-
-Pingdom checks from many locations but cycles through them one at a time. Openstatus checks all selected regions **simultaneously**, so a regional outage is caught on the same run rather than whenever the rotation comes back around.
-
-## Pricing Comparison
-
-| | openstatus | Pingdom |
-| -------------- | ----------------------- | ----------------------------- |
-| Free plan | 1 monitor, 6 regions | None |
-| Entry paid | $30/mo (20 monitors) | ~$15/mo (10 uptime checks) |
-| Status page | Included | Not available |
-| Team members | Unlimited on paid plans | Per-plan limits |
-| Open-source | Self-host for $0 | Not available |
-
-Pingdom's entry price looks low, but RUM and advanced features sit on separate add-ons, and there's no free tier to start on. Openstatus offers flat pricing with a status page and unlimited team members included.
-
-## When to Choose openstatus
-
-- You want uptime monitoring **with a built-in status page**
-- You want **28 regions** checked in parallel, not in rotation
-- You prefer **open-source** software or need to self-host
-- You want **monitoring as code** (Terraform), a CLI, and an MCP server
-- You want a **free tier** and predictable, low-cost pricing
-
-## When to Choose Pingdom
-
-- You need **real user monitoring (RUM)** to measure actual visitor experience
-- You need **recorded transaction checks** for multi-step browser flows
-- You want a **long-established** brand and don't need a public status page
-
-## Switching from Pingdom to openstatus
-
-If your Pingdom usage is primarily uptime and page checks, the move is straightforward:
-
-1. **Sign up** for a free openstatus account — no credit card required
-2. **Recreate your checks** in the dashboard, or define them as code with the [Terraform provider](/docs/reference/terraform) and the openstatus CLI
-3. **Set up your status page** — something Pingdom doesn't offer natively
-4. **Configure alerts** — openstatus supports Slack, Discord, Email, PagerDuty, OpsGenie, and more
-
-If you rely on Pingdom's RUM or transaction monitoring, openstatus is not a drop-in replacement for those — pair openstatus for uptime and status pages alongside a RUM tool.
-
-## Related Resources
-
-- [What Is Uptime Monitoring?](/guides/what-is-uptime-monitoring)
-- [Why Uptime Percentage Is Misleading](/guides/why-uptime-percentage-is-misleading)
-- [Why Every SaaS Needs a Status Page](/guides/why-every-saas-needs-a-status-page)
-- [Reduce Support Tickets with a Status Page](/use-case/reduce-support-tickets)
-- [Pricing](/pricing)
-
-## Frequently asked questions
-
-<Details summary="Is openstatus a good Pingdom alternative?">
-
-Yes, for uptime monitoring and status pages. Openstatus monitors from 28 global regions simultaneously, is open-source and self-hostable, includes a built-in public status page, and starts free. Pingdom is a closed-source SolarWinds product with no free tier and no public status page, though it offers real user monitoring (RUM) and transaction checks that openstatus does not.
-
-</Details>
-
-<Details summary="Does Pingdom still have a free plan?">
-
-No. Pingdom discontinued its free tier after the SolarWinds acquisition. The cheapest paid plan starts at around $15/month (billed annually) for 10 uptime checks, with a 14-day trial. Openstatus has a permanent free plan with 1 monitor across 6 regions.
-
-</Details>
-
-<Details summary="Does openstatus include a status page like Pingdom?">
-
-Openstatus includes a built-in branded public status page with custom domains, maintenance windows, and subscriber notifications on every plan. Pingdom does not offer a public status page product — you would need a separate tool for incident communication.
-
-</Details>
-
-<Details summary="Is openstatus open-source?">
-
-Yes. Openstatus is AGPL-3.0-licensed and fully self-hostable. Pingdom is a closed-source SaaS owned by SolarWinds with no self-hosting option.
-
-</Details>
-
----
-
-Start monitoring from 28 regions today
-
-<ButtonLink href="https://app.openstatus.dev?ref=compare-pingdom">Get Started Free</ButtonLink>
-
----
diff --git a/apps/web/src/content/pages/compare/uptime-kuma.mdx b/apps/web/src/content/pages/compare/uptime-kuma.mdx
deleted file mode 100644
index edcb604c8..000000000
--- a/apps/web/src/content/pages/compare/uptime-kuma.mdx
+++ /dev/null
@@ -1,130 +0,0 @@
----
-title: "Uptime Kuma vs openstatus"
-publishedAt: "2025-11-10"
-author: "openstatus"
-description: "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."
-category: "company"
-faq:
- - question: "Is openstatus a good Uptime Kuma alternative?"
- answer: "Yes, especially if you want managed cloud hosting or global multi-region monitoring. Both are open-source, but openstatus is available as a SaaS (no server to maintain) and monitors from 28 regions worldwide. Uptime Kuma is self-hosted only and checks from a single server location."
- - question: "What is the main difference between openstatus and Uptime Kuma?"
- answer: "The main difference is hosting model and monitoring coverage. Uptime Kuma is self-hosted only — you run it on your own server and it monitors from that single location. openstatus is available as a managed SaaS or self-hosted, and checks from 28 regions across multiple cloud providers simultaneously."
- - question: "Is openstatus free like Uptime Kuma?"
- answer: "openstatus has a free Hobby plan (1 monitor, 6 regions, 1 status page) with no credit card required. Uptime Kuma is fully free and open-source but requires you to provision, host, and maintain your own server."
- - question: "Does openstatus support self-hosting like Uptime Kuma?"
- answer: "Yes. openstatus is AGPL-3.0 licensed and can be self-hosted with Docker. You also get the option to use the managed cloud service without managing any infrastructure."
- - question: "Can openstatus monitor from multiple regions unlike Uptime Kuma?"
- answer: "Yes. openstatus monitors from 28 regions across 3 cloud providers (Fly.io, Koyeb, and Railway) simultaneously. Uptime Kuma only checks from the single server where it is installed, which means it cannot detect regional outages."
----
-
-## Looking for an Uptime Kuma alternative?
-
-**TL;DR:** Both are open-source. Openstatus offers managed SaaS hosting and monitors from 28 global regions simultaneously. Uptime Kuma is self-hosted only and checks from one server location. Choose openstatus for global coverage without infrastructure, Uptime Kuma for fully free self-managed monitoring.
-
-If you love the open-source ethos of Uptime Kuma but want managed hosting and global coverage, openstatus gives you both. Monitor from 28 regions across 3 cloud providers without maintaining your own server — or self-host it if you prefer. Either way, you get multi-region checks that Uptime Kuma's single-server architecture can't provide.
-
-Openstatus and Uptime Kuma are both open-source uptime monitoring tools, making this a comparison between two projects with shared values but different architectures. The fundamental difference is the **hosting model**: Uptime Kuma is self-hosted only — you run it on your own server and it monitors from that single location. Openstatus is available both as a **managed SaaS** and for self-hosting, and checks from **28 regions worldwide**.
-
-If you want zero infrastructure responsibility and global multi-region checks, openstatus is the natural choice. If you want a completely free, self-managed tool with full control and no external dependencies, Uptime Kuma is a solid option.
-
-## Feature Comparison
-
-| Feature | openstatus | Uptime Kuma |
-| ------------------- | ------------------- | ------------------------ |
-| Open-source | Yes | Yes |
-| Hosting model | SaaS or self-hosted | Self-hosted only |
-| Multi-cloud | 3 cloud providers | Single server |
-| Multi-region | 28 regions | 1 (your server location) |
-| OTel Export | Yes | No |
-| GitHub Action | Yes | No |
-| Team members | Unlimited | Unlimited |
-| Managed SaaS option | Yes | No |
-| Monitoring as code | Yes | No |
-
-## Pricing Comparison
-
-| | openstatus | Uptime Kuma |
-| ------------------- | --------------------------------------------- | ------------------------------------- |
-| Software cost | Free (Hobby), $30/mo (Starter), $100/mo (Pro) | Free |
-| Infrastructure cost | $0 (managed SaaS) | Your server cost ($5-20+/mo VPS) |
-| Maintenance | None (managed) | You manage updates, backups, uptime |
-| Multi-region | Included (28 regions) | Requires additional server per region |
-| Status page | Included | Included |
-
-Uptime Kuma is free software, but running it requires a server. A basic VPS costs $5-20/month, and you're responsible for updates, backups, and keeping the monitoring server itself online. Openstatus's managed SaaS eliminates that overhead. To get multi-region monitoring with Uptime Kuma, you'd need to run separate instances in each region.
-
-## When to Choose openstatus
-
-- You want **managed SaaS** with no infrastructure to maintain
-- You need **28-region global monitoring** from multiple cloud providers
-- You want **monitoring as code** via YAML and GitHub Actions
-- You need **OpenTelemetry export** or a tightly integrated status page
-- You want to **talk to the founders** directly (bootstrapped, small team)
-
-## When to Choose Uptime Kuma
-
-- You want **completely free** monitoring with no usage limits
-- You are comfortable **running your own server**
-- You need monitoring **behind a firewall** with no external SaaS dependency
-- You prefer a **single-location** check from your own infrastructure
-
-## Switching from Uptime Kuma to openstatus
-
-1. **Sign up** for a free openstatus account — no credit card required
-2. **Recreate your monitors** — use the dashboard or monitoring-as-code (YAML + CLI) to define your HTTP, TCP, and DNS checks
-3. **Set up your status page** — openstatus includes a branded status page with custom domain support
-4. **Configure alerts** — openstatus supports Slack, Discord, Email, PagerDuty, OpsGenie, and more
-5. **Decommission your server** — once your monitors are running on openstatus, you can shut down your Uptime Kuma instance and stop paying for the VPS
-
-openstatus ships automated importers for Statuspage, Better Stack, Instatus, and Checkly, but not for Uptime Kuma — so monitors are recreated rather than imported. [Monitoring as code](/docs/concept/uptime-monitoring-as-code) turns that into a one-time YAML file rather than an afternoon of dashboard clicking, and the same file stays version-controlled afterwards.
-
-If you prefer to self-host openstatus instead, check the [GitHub repository](https://github.com/openstatusHQ/openstatus) for Docker setup instructions.
-
-## Related Resources
-
-- [A hosted Uptime Kuma alternative](/guides/hosted-uptime-kuma-alternative) — the case for managed hosting in more depth
-- [Best Open Source Status Pages in 2026](/guides/best-opensource-status-page-2026)
-- [Why Every SaaS Needs a Status Page](/guides/why-every-saas-needs-a-status-page)
-- [Status Pages for Open Source Projects](/use-case/open-source)
-- [Uptime monitoring](/uptime-monitoring)
-- [Pricing](/pricing)
-
-## Frequently asked questions
-
-<Details summary="Is openstatus a good Uptime Kuma alternative?">
-
-Yes, especially if you want managed cloud hosting or global multi-region monitoring. Both are open-source, but openstatus is available as a SaaS (no server to maintain) and monitors from 28 regions worldwide. Uptime Kuma is self-hosted only and checks from a single server location.
-
-</Details>
-
-<Details summary="What is the main difference between openstatus and Uptime Kuma?">
-
-The main difference is hosting model and monitoring coverage. Uptime Kuma is self-hosted only — you run it on your own server and it monitors from that single location. openstatus is available as a managed SaaS or self-hosted, and checks from 28 regions across multiple cloud providers simultaneously.
-
-</Details>
-
-<Details summary="Is openstatus free like Uptime Kuma?">
-
-openstatus has a free Hobby plan (1 monitor, 6 regions, 1 status page) with no credit card required. Uptime Kuma is fully free and open-source but requires you to provision, host, and maintain your own server.
-
-</Details>
-
-<Details summary="Does openstatus support self-hosting like Uptime Kuma?">
-
-Yes. openstatus is AGPL-3.0 licensed and can be self-hosted with Docker. You also get the option to use the managed cloud service without managing any infrastructure.
-
-</Details>
-
-<Details summary="Can openstatus monitor from multiple regions unlike Uptime Kuma?">
-
-Yes. openstatus monitors from 28 regions across 3 cloud providers (Fly.io, Koyeb, and Railway) simultaneously. Uptime Kuma only checks from the single server where it is installed, which means it cannot detect regional outages.
-
-</Details>
-
----
-
-Start monitoring from 28 regions today
-
-<ButtonLink href="https://app.openstatus.dev?ref=compare-uptimekuma">Get Started Free</ButtonLink>
-
----
diff --git a/apps/web/src/content/pages/compare/uptime-robot.mdx b/apps/web/src/content/pages/compare/uptime-robot.mdx
index 9355e2ed8..734df904e 100644
--- a/apps/web/src/content/pages/compare/uptime-robot.mdx
+++ b/apps/web/src/content/pages/compare/uptime-robot.mdx
@@ -88,6 +88,7 @@ Most teams complete the switch in under an hour. If you need help, reach out at
- [Status page](/status-page)
- [Uptime monitoring](/uptime-monitoring)
+- [How to migrate from UptimeRobot to openstatus](/guides/migrate-from-uptime-robot) — the step-by-step move, once you have decided
- [Why Uptime Percentage Is Misleading](/guides/why-uptime-percentage-is-misleading)
- [SLA vs SLO vs SLI](/guides/sla-vs-slo-vs-sli)
- [Why Every SaaS Needs a Status Page](/guides/why-every-saas-needs-a-status-page)
diff --git a/apps/web/src/content/pages/guides/best-opensource-status-page-2026.mdx b/apps/web/src/content/pages/guides/best-opensource-status-page-2026.mdx
index 716c4c1a9..a6f5110c4 100644
--- a/apps/web/src/content/pages/guides/best-opensource-status-page-2026.mdx
+++ b/apps/web/src/content/pages/guides/best-opensource-status-page-2026.mdx
@@ -1,27 +1,32 @@
---
-title: "Best Open Source Status Page Tools in 2026"
-description: "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."
+title: "Best Self-Hosted Status Page Tools 2026"
+seo:
+ title: "Best Self-Hosted Status Page Tools in 2026"
+ description: "The self-hosted status page tools worth running in 2026 — openstatus, Cachet, Vigil, Statping-ng and Upptime — compared on maintenance, monitoring, and what each one costs you to operate."
+description: "The self-hosted status page tools worth running on your own infrastructure in 2026 — compared on maintenance, built-in monitoring, and the real operational cost of hosting them yourself."
author: "openstatus"
publishedAt: "2026-01-19"
category: "alternative"
faq:
- - question: "What is the best open-source status page tool in 2026?"
- answer: "openstatus is the top pick for 2026. It is actively maintained, offers both cloud-hosted and self-hosted deployments, includes built-in uptime monitoring, and integrates with Slack out of the box."
- - question: "What should I look for when choosing an open-source status page?"
- answer: "Focus on active maintenance, deployment flexibility (hosted vs. self-hosted), built-in monitoring, notification integrations (Slack, email, webhooks), and how easy it is for your end users to understand the current status at a glance."
- - question: "Can I self-host an open-source status page for free?"
- answer: "Yes. Tools like openstatus, Vigil, Cachet, and Statping-ng can all be self-hosted at no licensing cost. Keep in mind you will still need to provision and maintain your own infrastructure, so factor in server and operational costs."
+ - question: "What is the best self-hosted status page tool in 2026?"
+ answer: "openstatus is the strongest self-hosted option. It is actively maintained, ships as a Docker image you can run on your own infrastructure under AGPL-3.0, and unlike most self-hosted status pages it includes uptime monitoring rather than expecting you to wire in a separate tool. Cachet is the main alternative if you want something narrower and purely status-page focused."
+ - question: "What does self-hosting a status page actually cost?"
+ answer: "The software is free; the operation is not. Budget a VPS at $5-20/month, plus your time for upgrades, backups, TLS renewal, and keeping the box online. The subtler cost is architectural: a status page hosted on your own infrastructure can go down in the same incident it is supposed to report, which is the single strongest argument for hosting it somewhere else."
+ - question: "Should I self-host my status page or use a hosted one?"
+ answer: "Self-host when data residency, air-gapped networks, or full control of the stack are hard requirements, or when you genuinely enjoy running the infrastructure. Use a hosted page when you want it to stay up during your own outages and would rather not maintain another service. openstatus supports both from the same codebase, so the decision is not permanent."
+ - question: "Which self-hosted status pages include uptime monitoring?"
+ answer: "openstatus and Statping-ng monitor endpoints themselves. Cachet and Vigil are primarily status-page and reporting layers that expect check results from elsewhere, and Upptime uses GitHub Actions as its check runner. If you do not already have a monitoring stack, choosing a tool that includes checks saves you from running two services instead of one."
- question: "Is Upptime still a good choice in 2026?"
- answer: "Upptime pioneered a clever GitOps approach using GitHub Actions and Pages, but its last major release was in 2020. Because it is no longer actively maintained, we recommend choosing an actively developed alternative like OpenStatus for production use."
+ answer: "Upptime pioneered a clever GitOps approach using GitHub Actions and GitHub Pages, and it remains appealing if you want zero servers. But its last major release was in 2020, so for anything production-facing an actively maintained project is the safer choice."
---
-# The State of Open-Source Status Pages in 2026: What Are Your Best Options?
+# Best Self-Hosted Status Page Tools in 2026
-If there’s one thing we’ve learned in DevRel and platform engineering, it’s that **downtime is inevitable, but poor communication is a choice.** When your API goes down or latency spikes, your users shouldn't have to guess what's happening. A reliable, transparent status page is your frontline for maintaining developer trust.
+Running your own status page is a deliberate trade. You get full control of the data, no vendor bill, and a page that lives on infrastructure you own. In exchange you take on the server, the upgrades, the backups — and the awkward problem that your status page depends on infrastructure that may go down at the same time as everything else.
-But building a status page from scratch in 2026 is usually a waste of valuable engineering cycles. Instead, the open-source community has provided several excellent tools to do the heavy lifting for us.
+If that trade is one you want to make, these are the tools worth running in 2026. Each is compared on how actively it is maintained, whether it monitors anything itself, and what it genuinely costs to operate once you include the server and your own time.
-we’ve reviewed the current landscape of open-source status pages. Here is a breakdown of the top contenders this year, where they shine, and where they fall short.
+If you would rather not run it at all, a [hosted status page](/status-page) removes the operational half of the trade while keeping the open-source codebase.
---
@@ -82,7 +87,7 @@ Unfortunately, as of 2026, the project seems to have stalled. With its last majo
---
-### Summary Comparison
+### Self-hosting cost, side by side
| Tool | Active in 2026? | Deployment | Built-in Monitoring | Standout Feature |
| :-------------- | :-------------- | :------------------- | :------------------ | :-------------------------------- |
@@ -92,32 +97,38 @@ Unfortunately, as of 2026, the project seems to have stalled. With its last majo
| **Statping.ng** | ✅ Yes | Self-Hosted | ✅ Yes | All-in-one, but outdated UI |
| **Upptime** | ❌ No | GitHub Actions | ✅ Yes | Zero-server GitOps |
-### The Verdict
+### Which one to self-host
If you are starting a new project or migrating an old status page today, **openstatus** is the clear winner. Its modern architecture, active maintenance, and built-in integrations make it the easiest way to keep your users informed while your engineering team focuses on fixing the actual outages.
## Frequently asked questions
-<Details summary="What is the best open-source status page tool in 2026?">
+<Details summary="What is the best self-hosted status page tool in 2026?">
-openstatus is the top pick for 2026. It is actively maintained, offers both cloud-hosted and self-hosted deployments, includes built-in uptime monitoring, and integrates with Slack out of the box.
+openstatus is the strongest self-hosted option. It is actively maintained, ships as a Docker image you can run on your own infrastructure under AGPL-3.0, and unlike most self-hosted status pages it includes uptime monitoring rather than expecting you to wire in a separate tool. Cachet is the main alternative if you want something narrower and purely status-page focused.
</Details>
-<Details summary="What should I look for when choosing an open-source status page?">
+<Details summary="What does self-hosting a status page actually cost?">
-Focus on active maintenance, deployment flexibility (hosted vs. self-hosted), built-in monitoring, notification integrations (Slack, email, webhooks), and how easy it is for your end users to understand the current status at a glance.
+The software is free; the operation is not. Budget a VPS at $5-20/month, plus your time for upgrades, backups, TLS renewal, and keeping the box online. The subtler cost is architectural: a status page hosted on your own infrastructure can go down in the same incident it is supposed to report, which is the single strongest argument for hosting it somewhere else.
</Details>
-<Details summary="Can I self-host an open-source status page for free?">
+<Details summary="Should I self-host my status page or use a hosted one?">
-Yes. Tools like openstatus, Vigil, Cachet, and Statping-ng can all be self-hosted at no licensing cost. Keep in mind you will still need to provision and maintain your own infrastructure, so factor in server and operational costs.
+Self-host when data residency, air-gapped networks, or full control of the stack are hard requirements, or when you genuinely enjoy running the infrastructure. Use a hosted page when you want it to stay up during your own outages and would rather not maintain another service. openstatus supports both from the same codebase, so the decision is not permanent.
+
+</Details>
+
+<Details summary="Which self-hosted status pages include uptime monitoring?">
+
+openstatus and Statping-ng monitor endpoints themselves. Cachet and Vigil are primarily status-page and reporting layers that expect check results from elsewhere, and Upptime uses GitHub Actions as its check runner. If you do not already have a monitoring stack, choosing a tool that includes checks saves you from running two services instead of one.
</Details>
<Details summary="Is Upptime still a good choice in 2026?">
-Upptime pioneered a clever GitOps approach using GitHub Actions and Pages, but its last major release was in 2020. Because it is no longer actively maintained, we recommend choosing an actively developed alternative like OpenStatus for production use.
+Upptime pioneered a clever GitOps approach using GitHub Actions and GitHub Pages, and it remains appealing if you want zero servers. But its last major release was in 2020, so for anything production-facing an actively maintained project is the safer choice.
</Details>
diff --git a/apps/web/src/content/pages/guides/hosted-uptime-kuma-alternative.mdx b/apps/web/src/content/pages/guides/hosted-uptime-kuma-alternative.mdx
index 987fae496..640c85c8f 100644
--- a/apps/web/src/content/pages/guides/hosted-uptime-kuma-alternative.mdx
+++ b/apps/web/src/content/pages/guides/hosted-uptime-kuma-alternative.mdx
@@ -11,6 +11,10 @@ faq:
answer: "Uptime Kuma checks from a single location — the server you run it on. If that server has a network blip, you get false alerts; if it goes down, your monitoring goes down with it. It also can't tell you whether an outage is regional, because there's only one vantage point. A managed, multi-region tool solves both."
- question: "Can I keep Uptime Kuma and use openstatus too?"
answer: "Yes. Some teams run Uptime Kuma internally for homelab or internal services and use openstatus for external, multi-region checks and a public status page. They complement each other."
+ - question: "Does openstatus support self-hosting like Uptime Kuma?"
+ answer: "Yes. openstatus is AGPL-3.0 licensed and fully self-hostable with Docker, so you can run it on your own infrastructure the same way you run Uptime Kuma. The difference is that you also have the option of the managed service — with Uptime Kuma, self-hosting is the only option."
+ - question: "Can openstatus monitor from multiple regions unlike Uptime Kuma?"
+ answer: "Yes. openstatus checks from 28 regions across 3 cloud providers, and all selected regions fire simultaneously rather than in rotation. Uptime Kuma checks from the single server you run it on, so it cannot distinguish a regional outage from a global one. Matching that with Uptime Kuma means running a separate instance per region."
- question: "Is openstatus free like Uptime Kuma?"
answer: "Uptime Kuma is free to run if you cover your own hosting. openstatus has a permanent free plan for the managed service (1 monitor, 6 regions), paid plans from $30/month, and is also free to self-host under AGPL-3.0."
---
@@ -45,6 +49,32 @@ The point that matters most: openstatus checks from **28 regions at once**. A fa
And if your reason for choosing Uptime Kuma was *"I want to own it"*, you don't have to give that up. openstatus is open-source and self-hostable too — the checker runs as a small Docker image. You can start on the managed cloud and move to self-hosted later, or run both.
+## Feature Comparison
+
+| Feature | openstatus | Uptime Kuma |
+| ------------------- | ------------------- | ------------------------ |
+| Open-source | Yes | Yes |
+| Hosting model | SaaS or self-hosted | Self-hosted only |
+| Multi-cloud | 3 cloud providers | Single server |
+| Multi-region | 28 regions | 1 (your server location) |
+| OTel Export | Yes | No |
+| GitHub Action | Yes | No |
+| Team members | Unlimited | Unlimited |
+| Managed SaaS option | Yes | No |
+| Monitoring as code | Yes | No |
+
+## Pricing Comparison
+
+| | openstatus | Uptime Kuma |
+| ------------------- | --------------------------------------------- | ------------------------------------- |
+| Software cost | Free (Hobby), $30/mo (Starter), $100/mo (Pro) | Free |
+| Infrastructure cost | $0 (managed SaaS) | Your server cost ($5-20+/mo VPS) |
+| Maintenance | None (managed) | You manage updates, backups, uptime |
+| Multi-region | Included (28 regions) | Requires additional server per region |
+| Status page | Included | Included |
+
+Uptime Kuma is free software, but running it requires a server. A basic VPS costs $5-20/month, and you're responsible for updates, backups, and keeping the monitoring server itself online. Openstatus's managed SaaS eliminates that overhead. To get multi-region monitoring with Uptime Kuma, you'd need to run separate instances in each region.
+
## When to stay on Uptime Kuma
Be honest with yourself here — Kuma is the right call when:
@@ -72,9 +102,9 @@ Most Kuma setups are small enough to move in well under an hour.
## Related Resources
-- [Uptime Kuma vs openstatus](/compare/uptime-kuma) — full head-to-head
- [Best Open-Source Status Page Tools in 2026](/guides/best-opensource-status-page-2026)
- [What Is Uptime Monitoring?](/guides/what-is-uptime-monitoring)
+- [Uptime monitoring](/uptime-monitoring)
- [Status Pages for Open-Source Projects](/use-case/open-source)
## Frequently asked questions
@@ -97,6 +127,18 @@ Yes. Some teams run Uptime Kuma internally for homelab or internal services and
</Details>
+<Details summary="Does openstatus support self-hosting like Uptime Kuma?">
+
+Yes. openstatus is AGPL-3.0 licensed and fully self-hostable with Docker, so you can run it on your own infrastructure the same way you run Uptime Kuma. The difference is that you also have the option of the managed service — with Uptime Kuma, self-hosting is the only option.
+
+</Details>
+
+<Details summary="Can openstatus monitor from multiple regions unlike Uptime Kuma?">
+
+Yes. openstatus checks from 28 regions across 3 cloud providers, and all selected regions fire simultaneously rather than in rotation. Uptime Kuma checks from the single server you run it on, so it cannot distinguish a regional outage from a global one. Matching that with Uptime Kuma means running a separate instance per region.
+
+</Details>
+
<Details summary="Is openstatus free like Uptime Kuma?">
Uptime Kuma is free to run if you cover your own hosting. openstatus has a permanent free plan for the managed service (1 monitor, 6 regions), paid plans from $30/month, and is also free to self-host under AGPL-3.0.
diff --git a/apps/web/src/content/pages/guides/how-openstatus-compares-to-other-status-page-tools.mdx b/apps/web/src/content/pages/guides/how-openstatus-compares-to-other-status-page-tools.mdx
index a27171add..cfc57b924 100644
--- a/apps/web/src/content/pages/guides/how-openstatus-compares-to-other-status-page-tools.mdx
+++ b/apps/web/src/content/pages/guides/how-openstatus-compares-to-other-status-page-tools.mdx
@@ -1,27 +1,30 @@
---
-title: "How openstatus Compares to Other Status Page Tools"
-description: "A head-to-head comparison of openstatus vs. Atlassian Statuspage, Instatus, Betterstack, Datadog Status Page, and Status.io — features, pricing, monitoring, and developer experience."
+title: "Status Page Pricing Compared: Atlassian, Instatus, Better Stack, Datadog & openstatus"
+seo:
+ title: "Status Page Pricing Compared — Atlassian, Instatus, Better Stack & More"
+ description: "What a status page actually costs across Atlassian Statuspage, Instatus, Better Stack, Datadog and Status.io — list prices, per-seat charges, private-page add-ons and the cost of adding monitoring."
+description: "What a status page actually costs across the major providers — list prices, per-seat charges, private-page add-ons, and what you pay separately for monitoring."
author: "openstatus"
publishedAt: "2026-06-09"
-category: "alternative"
+category: "pricing"
faq:
- - question: "What makes openstatus different from other status page tools?"
- answer: "openstatus is the only tool that combines built-in synthetic monitoring, monitoring-as-code via Terraform, native OpenTelemetry export, private locations, an MCP server for AI coding agents, unlimited team members, and the option to self-host as open-source. Most competitors cover one or two of these — none cover all of them."
- - question: "Is openstatus a replacement for Atlassian Statuspage?"
- answer: "Yes, for most use cases. openstatus covers the core incident communication workflows (components, incidents, maintenances, subscribers) and adds built-in monitoring, monitoring-as-code, and an MCP server that Atlassian Statuspage doesn't ship. The one area where Atlassian still leads is deep Jira/Opsgenie integration for teams already standardized on Atlassian tooling."
- - question: "How does openstatus pricing compare?"
- answer: "openstatus starts at $30/month with unlimited team members and monitoring included. That's typically cheaper than Atlassian Statuspage ($99/month for private pages), Status.io ($349/month for advanced features), or Betterstack once you add private-page and styling add-ons. Instatus has a comparable free tier but no monitoring."
- - question: "Can I migrate my existing status page to openstatus?"
- answer: "Yes. openstatus ships a one-click importer for Atlassian Statuspage and Instatus that moves components, component groups, incidents with full update history, maintenances, and email subscribers. For other tools, components and subscribers can be imported via CSV."
- - question: "Is openstatus production-ready?"
- answer: "Yes. openstatus powers status pages for teams across SaaS, fintech, and infrastructure companies, and runs synthetic checks from multiple regions globally. The hosted platform is fully managed, and the same codebase backs the self-hosted distribution."
+ - question: "How much does a status page cost?"
+ answer: "It ranges from free to $349/month depending on what you need. Free tiers exist at openstatus, Instatus and Better Stack but are limited to a public page and a handful of components. A private, branded page on a custom domain starts at $30/month with openstatus, $50/month with Instatus, $99/month with Atlassian Statuspage, and $349/month with Status.io. Per-seat charges and monitoring are extra almost everywhere except openstatus."
+ - question: "Why is Atlassian Statuspage so expensive?"
+ answer: "Three multipliers stack. The $29/month entry plan caps you at 100 subscribers and the price climbs as that audience grows. A private page needs the $99/month tier. Custom HTML and CSS only appear on the $399/month plan. Seats are billed on top at roughly $20 each, and because Statuspage ships no monitoring, you also pay a separate monitoring vendor to feed it."
+ - question: "Which status page provider is cheapest?"
+ answer: "For a public page with no private access and a small component count, the free tiers at openstatus, Instatus and Better Stack all cost nothing. Once you need a private page, a custom domain, more than a couple of seats, and monitoring behind it, openstatus at $30/month is usually the lowest total because seats are unlimited and monitoring is included rather than billed separately."
+ - question: "Does the price include uptime monitoring?"
+ answer: "Usually not. Atlassian Statuspage, Instatus and Status.io ship no monitoring at all, so the checks that drive your components come from a separate tool you pay for on top. Better Stack and Datadog include monitoring but bill it per seat or per run. openstatus includes monitoring from 28 regions in the base price."
+ - question: "What hidden costs should I watch for?"
+ answer: "Subscriber-count billing, which grows with your audience rather than your usage. Per-seat pricing, which punishes you for adding engineers to an incident workflow. Private-page and custom-styling add-ons billed per page per month. And the separate monitoring bill, which is the largest hidden cost on any status-page-only product."
---
-# How openstatus Compares to Other Status Page Tools
+# Status Page Pricing Compared
-If you're evaluating status page tools in 2026, the market is crowded: Atlassian Statuspage is the incumbent, Instatus is the design-forward newcomer, Betterstack is the all-in-one bundle, Datadog is the observability extension, and Status.io is the long-standing pure-play.
+Status page pricing is hard to compare because almost nobody charges for one thing. The headline number buys a public page; private pages, extra seats, custom styling and the monitoring that feeds the page are billed separately, and the mix differs at every vendor.
-This guide is the head-to-head: how **openstatus** stacks up against each of them on the dimensions that actually matter — monitoring, developer experience, pricing, and incident workflows.
+This guide puts the actual cost side by side across **Atlassian Statuspage, Instatus, Better Stack, Datadog Status Page, Status.io and openstatus** — list price, what each charges per seat, what a private page costs, and what you still have to buy elsewhere.
## TL;DR
@@ -36,7 +39,7 @@ openstatus is the only tool in this comparison that combines **all** of the foll
Every other tool on this list is missing at least two of these. If those bullets describe what your team needs, the comparison is short. If you only need a small subset (e.g. just incident comms, or just a pretty page), some of the competitors are still credible — and we'll be honest about when.
-## At a Glance
+## What each provider costs
| Feature | openstatus | Atlassian Statuspage | Instatus | Betterstack | Datadog | Status.io |
| --- | --- | --- | --- | --- | --- | --- |
@@ -52,7 +55,7 @@ Every other tool on this list is missing at least two of these. If those bullets
Prices reflect publicly listed plans at time of writing and change frequently — always confirm with the vendor.
-## How openstatus Compares on Each Dimension
+## Where the cost actually comes from
### Monitoring depth
@@ -92,7 +95,7 @@ Datadog also ships MCP. None of the others do.
**openstatus wins on**: developer workflows, version-controlled config, and AI agent integration.
-### Pricing at scale
+### The bill at scale
openstatus is **$30/month with unlimited team members** and includes monitoring. Compare that to:
@@ -120,7 +123,7 @@ openstatus is the only tool here with an open-source codebase you can read, fork
**openstatus wins on**: ownership and optionality.
-## openstatus vs. Each Competitor
+## Cost by provider
### openstatus vs. Atlassian Statuspage
@@ -156,7 +159,7 @@ Status.io is the long-standing pure-play: status communication and nothing else,
**Pick openstatus if**: you want monitoring included, modern dev tooling, or aren't willing to jump to a $349/month tier for private pages. **Pick Status.io if**: you specifically want a tool that does one thing and is decoupled from the rest of your stack.
-## Where openstatus Isn't the Right Fit
+## When paying more is the right call
Being honest: openstatus is not for every team.
@@ -193,32 +196,32 @@ If you need help along the way, feel free to join our [Discord community](https:
## Frequently asked questions
-<Details summary="What makes openstatus different from other status page tools?">
+<Details summary="How much does a status page cost?">
-openstatus is the only tool that combines built-in synthetic monitoring, monitoring-as-code via Terraform, native OpenTelemetry export, private locations, an MCP server for AI coding agents, unlimited team members, and the option to self-host as open-source. Most competitors cover one or two of these — none cover all of them.
+It ranges from free to $349/month depending on what you need. Free tiers exist at openstatus, Instatus and Better Stack but are limited to a public page and a handful of components. A private, branded page on a custom domain starts at $30/month with openstatus, $50/month with Instatus, $99/month with Atlassian Statuspage, and $349/month with Status.io. Per-seat charges and monitoring are extra almost everywhere except openstatus.
</Details>
-<Details summary="Is openstatus a replacement for Atlassian Statuspage?">
+<Details summary="Why is Atlassian Statuspage so expensive?">
-Yes, for most use cases. openstatus covers the core incident communication workflows (components, incidents, maintenances, subscribers) and adds built-in monitoring, monitoring-as-code, and an MCP server that Atlassian Statuspage doesn't ship. The one area where Atlassian still leads is deep Jira/Opsgenie integration for teams already standardized on Atlassian tooling.
+Three multipliers stack. The $29/month entry plan caps you at 100 subscribers and the price climbs as that audience grows. A private page needs the $99/month tier. Custom HTML and CSS only appear on the $399/month plan. Seats are billed on top at roughly $20 each, and because Statuspage ships no monitoring, you also pay a separate monitoring vendor to feed it.
</Details>
-<Details summary="How does openstatus pricing compare?">
+<Details summary="Which status page provider is cheapest?">
-openstatus starts at $30/month with unlimited team members and monitoring included. That's typically cheaper than Atlassian Statuspage ($99/month for private pages), Status.io ($349/month for advanced features), or Betterstack once you add private-page and styling add-ons. Instatus has a comparable free tier but no monitoring.
+For a public page with no private access and a small component count, the free tiers at openstatus, Instatus and Better Stack all cost nothing. Once you need a private page, a custom domain, more than a couple of seats, and monitoring behind it, openstatus at $30/month is usually the lowest total because seats are unlimited and monitoring is included rather than billed separately.
</Details>
-<Details summary="Can I migrate my existing status page to openstatus?">
+<Details summary="Does the price include uptime monitoring?">
-Yes. openstatus ships a one-click importer for Atlassian Statuspage and Instatus that moves components, component groups, incidents with full update history, maintenances, and email subscribers. For other tools, components and subscribers can be imported via CSV.
+Usually not. Atlassian Statuspage, Instatus and Status.io ship no monitoring at all, so the checks that drive your components come from a separate tool you pay for on top. Better Stack and Datadog include monitoring but bill it per seat or per run. openstatus includes monitoring from 28 regions in the base price.
</Details>
-<Details summary="Is openstatus production-ready?">
+<Details summary="What hidden costs should I watch for?">
-Yes. openstatus powers status pages for teams across SaaS, fintech, and infrastructure companies, and runs synthetic checks from multiple regions globally. The hosted platform is fully managed, and the same codebase backs the self-hosted distribution.
+Subscriber-count billing, which grows with your audience rather than your usage. Per-seat pricing, which punishes you for adding engineers to an incident workflow. Private-page and custom-styling add-ons billed per page per month. And the separate monitoring bill, which is the largest hidden cost on any status-page-only product.
</Details>
diff --git a/apps/web/src/content/pages/guides/migrate-from-uptime-robot.mdx b/apps/web/src/content/pages/guides/migrate-from-uptime-robot.mdx
index 411aad3b9..3cd3f4163 100644
--- a/apps/web/src/content/pages/guides/migrate-from-uptime-robot.mdx
+++ b/apps/web/src/content/pages/guides/migrate-from-uptime-robot.mdx
@@ -141,6 +141,10 @@ Common reasons: UptimeRobot checks from a single location while openstatus check
---
+Still deciding rather than migrating? [UptimeRobot vs openstatus](/compare/uptime-robot) is the feature-by-feature comparison.
+
+---
+
Start monitoring from 28 regions today
<ButtonLink href="https://app.openstatus.dev?ref=migrate-uptimerobot">Get Started Free</ButtonLink>
diff --git a/apps/web/src/content/pages/guides/top-five-atlassian-statuspage-alternatives.mdx b/apps/web/src/content/pages/guides/top-five-atlassian-statuspage-alternatives.mdx
index 1d7ef84b0..31ac109d8 100644
--- a/apps/web/src/content/pages/guides/top-five-atlassian-statuspage-alternatives.mdx
+++ b/apps/web/src/content/pages/guides/top-five-atlassian-statuspage-alternatives.mdx
@@ -6,6 +6,12 @@ author: "openstatus"
publishedAt: "2026-06-09"
category: "alternative"
faq:
+ - question: "Is openstatus a good Atlassian Statuspage alternative?"
+ answer: "Yes. Openstatus includes built-in uptime monitoring from 28 global regions — something Atlassian Statuspage does not offer at all. Openstatus pricing is flat ($30/mo) and does not scale with subscriber count. Atlassian Statuspage charges per subscriber tier, meaning your bill grows as your audience does. Openstatus is also open-source and self-hostable."
+ - question: "How does openstatus pricing compare to Atlassian Statuspage?"
+ answer: "Atlassian Statuspage starts at $29/month for one page and 100 subscribers, jumping to $99/month for three pages and $399/month for custom HTML/CSS. Subscriber-count tiers add cost as your audience grows. Openstatus starts at $30/month with flat pricing, unlimited subscribers, and monitoring included."
+ - question: "What does the OpsGenie shutdown mean for Statuspage users?"
+ answer: "OpsGenie, Atlassian's incident management tool often used alongside Statuspage, is shutting down in April 2027. Teams using the Statuspage + OpsGenie combination will need to find replacements for both. Openstatus covers the monitoring and status page layer in one product."
- question: "How do I migrate from Atlassian Statuspage to an alternative?"
answer: "openstatus offers a one-click importer that automatically transfers your components, component groups, incidents (with all updates), maintenances, and email subscribers from Atlassian Statuspage. Just paste your API key, preview what will be imported, and confirm. See our step-by-step migration guide for details."
- question: "Which alternative is most cost-effective for small teams?"
@@ -58,6 +64,39 @@ Here's a high-level look at how these five alternatives stack up on key features
+## openstatus vs Atlassian Statuspage, feature by feature
+
+| Feature | openstatus | Atlassian Statuspage |
+| -------------------------- | ---------------- | ----------------------- |
+| Open-source | Yes | No |
+| Self-hosted | Yes | No |
+| Built-in uptime monitoring | Yes | No |
+| Multi-region | 28 regions | Not applicable |
+| Monitoring as code | Yes | No |
+| OpenTelemetry export | Yes | No |
+| Subscriber-count billing | Flat (unlimited) | Scales with subscribers |
+| Custom HTML/CSS | Themes included | $399/mo plan only |
+| Team members | Unlimited | Restricted by plan |
+| Developer tooling | CLI, Terraform, GitHub Actions | No official |
+
+## openstatus vs Atlassian Statuspage pricing
+
+| | openstatus | Atlassian Statuspage |
+| ------------------- | ---------------- | --------------------------- |
+| Starting price | $30/mo | $29/mo |
+| Monitoring included | Yes (28 regions) | No (requires separate tool) |
+| Status pages | 1 (+$20/mo each) | 1 |
+| Subscribers | Unlimited | 100 (scales with cost) |
+| Custom Themes | Included | $399/mo plan |
+| Team members | Unlimited | Restricted |
+| 3 status pages | $70/mo | $99/mo |
+
+The starting prices look similar, but Atlassian Statuspage's $29/month plan only includes 100 subscribers and no monitoring. To get custom styling, you need the $399/month plan. And you still need to pay for a separate monitoring tool on top of that. Openstatus includes monitoring, unlimited subscribers, and theming from $30/month.
+
+## Built for AI and Agentic Workflows
+
+Openstatus ships a CLI that integrates natively into AI-driven workflows. Whether you're using an AI agent or building your own agentic automation, the openstatus CLI lets you create monitors, trigger checks, and manage incidents programmatically, no browser required. Atlassian Statuspage has no CLI and no tooling designed for machine-to-machine interaction.
+
## Top Five Alternatives to Atlassian Statuspage
### 1. OpenStatus
@@ -164,12 +203,36 @@ While Atlassian Statuspage pioneered the status page market, several alternative
- **Betterstack** is a great option for those looking for an all-in-one monitoring and status page solution.
+## Related Guides
+
+- [How to migrate from Atlassian Statuspage to openstatus](/guides/migrate-from-atlassian-statuspage) — the step-by-step move, once you have picked
+- [Status page](/status-page) — what openstatus ships
+- [Status Page Pricing Compared](/guides/how-openstatus-compares-to-other-status-page-tools) — what each option actually costs
+
## Need Help or Have Questions?
If you need help along the way, feel free to join our [Discord community](https://www.openstatus.dev/discord), check our [documentation](https://www.openstatus.dev/docs) for more information or reach out to us via [email](mailto:[email protected])
## Frequently asked questions
+<Details summary="Is openstatus a good Atlassian Statuspage alternative?">
+
+Yes. Openstatus includes built-in uptime monitoring from 28 global regions — something Atlassian Statuspage does not offer at all. Openstatus pricing is flat ($30/mo) and does not scale with subscriber count. Atlassian Statuspage charges per subscriber tier, meaning your bill grows as your audience does. Openstatus is also open-source and self-hostable.
+
+</Details>
+
+<Details summary="How does openstatus pricing compare to Atlassian Statuspage?">
+
+Atlassian Statuspage starts at $29/month for one page and 100 subscribers, jumping to $99/month for three pages and $399/month for custom HTML/CSS. Subscriber-count tiers add cost as your audience grows. Openstatus starts at $30/month with flat pricing, unlimited subscribers, and monitoring included.
+
+</Details>
+
+<Details summary="What does the OpsGenie shutdown mean for Statuspage users?">
+
+OpsGenie, Atlassian's incident management tool often used alongside Statuspage, is shutting down in April 2027. Teams using the Statuspage + OpsGenie combination will need to find replacements for both. Openstatus covers the monitoring and status page layer in one product.
+
+</Details>
+
<Details summary="How do I migrate from Atlassian Statuspage to an alternative?">
openstatus offers a one-click importer that automatically transfers your components, component groups, incidents (with all updates), maintenances, and email subscribers from Atlassian Statuspage. Just paste your API key, preview what will be imported, and confirm. See our step-by-step migration guide for details.
diff --git a/apps/web/src/content/pages/guides/top-five-instatus-alternatives.mdx b/apps/web/src/content/pages/guides/top-five-instatus-alternatives.mdx
index 23249db72..d9d4d173a 100644
--- a/apps/web/src/content/pages/guides/top-five-instatus-alternatives.mdx
+++ b/apps/web/src/content/pages/guides/top-five-instatus-alternatives.mdx
@@ -6,6 +6,10 @@ author: "openstatus"
publishedAt: "2026-06-09"
category: "alternative"
faq:
+ - question: "Is openstatus a good Instatus alternative?"
+ answer: "Yes, especially if you need real uptime monitoring alongside your status page. Instatus is a status-page-first product with basic HTTP monitoring added later. Openstatus was built around monitoring first — checking from 28 global regions simultaneously — with status pages as a native part of the product, not a bolt-on."
+ - question: "How does openstatus pricing compare to Instatus?"
+ answer: "Instatus starts at $20/month for one custom-domain status page. Openstatus starts at $30/month and includes uptime monitoring from 28 regions, unlimited team members, and monitoring-as-code tooling. If you need both monitoring and a status page, openstatus covers both in one plan."
- question: "How do I migrate from Instatus to an alternative?"
answer: "openstatus offers a one-click importer that automatically transfers your components, component groups, incidents (with all updates), maintenances, and email subscribers. Paste your Instatus API key, preview what will be imported, and confirm. See our step-by-step migration guide for details."
- question: "Which Instatus alternative is most cost-effective for small teams?"
@@ -70,6 +74,32 @@ The comparison below is structured around these.
Prices reflect publicly listed plans at time of writing and change frequently — always confirm with the vendor before deciding.
+## openstatus vs Instatus, feature by feature
+
+| Feature | openstatus | Instatus |
+| --------------------- | ------------------------------ | ---------- |
+| Open-source | Yes | No |
+| Self-hosted | Yes | No |
+| Scheduling strategy | Parallel (all regions at once) | Sequential |
+| Multi-region | 28 regions | ~4 regions |
+| Monitoring as code | Yes | No |
+| OpenTelemetry export | Yes | No |
+| Developer tooling | CLI, Terraform, GitHub Actions | No |
+| Status page | Yes | Yes |
+| Unlimited subscribers | Yes | Yes |
+| Team members | Unlimited | Unlimited |
+
+## openstatus vs Instatus pricing
+
+| | openstatus | Instatus |
+| ----------------------- | --------------------------------------------------------------- | ---------------------------------------------- |
+| Free plan | 1 monitor, 1 status page | 1 status page (no custom domain) |
+| Starter/paid | $30/mo | $20/mo |
+| What's included | 20 monitors + 28 regions + status page + unlimited team members | 1 custom-domain status page + basic monitoring |
+| Additional status pages | $20/mo each | Included in higher plans |
+
+Instatus is $10/month cheaper on the base plan, but it does not include the depth of monitoring openstatus offers. If you're already paying for a separate monitoring tool alongside Instatus, openstatus replaces both at a lower combined cost.
+
## The Five Alternatives
### 1. openstatus — best for developer teams that want one tool
@@ -211,6 +241,7 @@ For the other alternatives, migration is typically a manual rebuild of component
- [Best Hosted Status Page Tools in 2026](/guides/best-hosted-status-page-2026) — the wider SaaS landscape ranked
- [Best Incident Communication Tools in 2026](/guides/best-incident-communication-tools-2026) — when you also need internal coordination
- [Top Five Atlassian Statuspage Alternatives in 2026](/guides/top-five-atlassian-statuspage-alternatives) — switching from Atlassian instead
+- [How to migrate from Instatus to openstatus](/guides/migrate-from-instatus) — the step-by-step move
## Need Help or Have Questions?
@@ -218,6 +249,18 @@ If you need help along the way, feel free to join our [Discord community](https:
## Frequently asked questions
+<Details summary="Is openstatus a good Instatus alternative?">
+
+Yes, especially if you need real uptime monitoring alongside your status page. Instatus is a status-page-first product with basic HTTP monitoring added later. Openstatus was built around monitoring first — checking from 28 global regions simultaneously — with status pages as a native part of the product, not a bolt-on.
+
+</Details>
+
+<Details summary="How does openstatus pricing compare to Instatus?">
+
+Instatus starts at $20/month for one custom-domain status page. Openstatus starts at $30/month and includes uptime monitoring from 28 regions, unlimited team members, and monitoring-as-code tooling. If you need both monitoring and a status page, openstatus covers both in one plan.
+
+</Details>
+
<Details summary="How do I migrate from Instatus to an alternative?">
openstatus offers a one-click importer that automatically transfers your components, component groups, incidents (with all updates), maintenances, and email subscribers. Paste your Instatus API key, preview what will be imported, and confirm. See our step-by-step migration guide for details.
diff --git a/apps/web/src/content/pages/guides/top-five-pingdom-alternatives.mdx b/apps/web/src/content/pages/guides/top-five-pingdom-alternatives.mdx
index 0b2d7a9fb..54a618bca 100644
--- a/apps/web/src/content/pages/guides/top-five-pingdom-alternatives.mdx
+++ b/apps/web/src/content/pages/guides/top-five-pingdom-alternatives.mdx
@@ -5,6 +5,10 @@ author: "openstatus"
publishedAt: "2026-06-19"
category: "alternative"
faq:
+ - question: "Is openstatus a good Pingdom alternative?"
+ answer: "Yes, for uptime monitoring and status pages. Openstatus monitors from 28 global regions simultaneously, is open-source and self-hostable, includes a built-in public status page, and starts free. Pingdom is a closed-source SolarWinds product with no free tier and no public status page, though it offers real user monitoring (RUM) and transaction checks that openstatus does not."
+ - question: "Does Pingdom still have a free plan?"
+ answer: "No. Pingdom discontinued its free tier after the SolarWinds acquisition. The cheapest paid plan starts at around $15/month (billed annually) for 10 uptime checks, with a 14-day trial. Openstatus has a permanent free plan with 1 monitor across 6 regions."
- question: "Why do teams look for a Pingdom alternative?"
answer: "The most common reasons are: Pingdom discontinued its free tier after the SolarWinds acquisition, so there's no way to start for free; pricing climbs once you add real user monitoring or transaction checks; it's closed-source with no self-hosting; and it has no built-in public status page, so you need a second tool for incident communication."
- question: "Which Pingdom alternative has the best free tier?"
@@ -55,6 +59,37 @@ If none of these apply, Pingdom is fine. If two or more do, the alternatives bel
Prices and limits change frequently — confirm with each vendor before deciding.
+## openstatus vs Pingdom, feature by feature
+
+| Feature | openstatus | Pingdom |
+| ------------------------ | ---------------- | -------------------- |
+| Free plan | Yes | No (14-day trial) |
+| Multi-region | 28 regions | ~100 locations |
+| Parallel scheduling | Yes | No (round-robin) |
+| Status Page | Yes (built-in) | No |
+| Open-source | Yes (AGPL-3.0) | No |
+| Self-hostable | Yes | No |
+| Monitoring as code | Yes (Terraform) | No |
+| CLI | Yes | No |
+| MCP server | Yes | No |
+| OpenTelemetry exporter | Yes | No |
+| Real user monitoring | No | Yes |
+| Transaction monitoring | No | Yes |
+
+Pingdom checks from many locations but cycles through them one at a time. Openstatus checks all selected regions **simultaneously**, so a regional outage is caught on the same run rather than whenever the rotation comes back around.
+
+## openstatus vs Pingdom pricing
+
+| | openstatus | Pingdom |
+| -------------- | ----------------------- | ----------------------------- |
+| Free plan | 1 monitor, 6 regions | None |
+| Entry paid | $30/mo (20 monitors) | ~$15/mo (10 uptime checks) |
+| Status page | Included | Not available |
+| Team members | Unlimited on paid plans | Per-plan limits |
+| Open-source | Self-host for $0 | Not available |
+
+Pingdom's entry price looks low, but RUM and advanced features sit on separate add-ons, and there's no free tier to start on. Openstatus offers flat pricing with a status page and unlimited team members included.
+
## The Five Alternatives
### 1. openstatus — best for teams that want monitoring and a status page in one open-source tool
@@ -124,7 +159,6 @@ The trade-off is that you're now operating the monitor: it runs from a single lo
## Related Guides
-- [Pingdom vs openstatus](/compare/pingdom) — full head-to-head
- [What Is Uptime Monitoring?](/guides/what-is-uptime-monitoring)
- [Best Hosted Status Page Tools in 2026](/guides/best-hosted-status-page-2026)
- [Why Every SaaS Needs a Status Page](/guides/why-every-saas-needs-a-status-page)
@@ -135,6 +169,18 @@ Join our [Discord community](https://www.openstatus.dev/discord), check the [doc
## Frequently asked questions
+<Details summary="Is openstatus a good Pingdom alternative?">
+
+Yes, for uptime monitoring and status pages. Openstatus monitors from 28 global regions simultaneously, is open-source and self-hostable, includes a built-in public status page, and starts free. Pingdom is a closed-source SolarWinds product with no free tier and no public status page, though it offers real user monitoring (RUM) and transaction checks that openstatus does not.
+
+</Details>
+
+<Details summary="Does Pingdom still have a free plan?">
+
+No. Pingdom discontinued its free tier after the SolarWinds acquisition. The cheapest paid plan starts at around $15/month (billed annually) for 10 uptime checks, with a 14-day trial. Openstatus has a permanent free plan with 1 monitor across 6 regions.
+
+</Details>
+
<Details summary="Why do teams look for a Pingdom alternative?">
The most common reasons are: Pingdom discontinued its free tier after the SolarWinds acquisition, so there's no way to start for free; pricing climbs once you add real user monitoring or transaction checks; it's closed-source with no self-hosting; and it has no built-in public status page, so you need a second tool for incident communication.
diff --git a/apps/web/src/content/pages/guides/what-is-a-status-page.mdx b/apps/web/src/content/pages/guides/what-is-a-status-page.mdx
index 38d37c424..879089270 100644
--- a/apps/web/src/content/pages/guides/what-is-a-status-page.mdx
+++ b/apps/web/src/content/pages/guides/what-is-a-status-page.mdx
@@ -1,31 +1,64 @@
---
-title: "What Is a Status Page?"
-description: "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."
+title: "Status Page Terminology: Partial Outage, Degraded and Major Outage Explained"
+seo:
+ title: "Status Page Terminology — Partial Outage, Degraded & Major Outage"
+ description: "What each status on a status page actually means: operational, degraded performance, partial outage, major outage, and under maintenance — with guidance on which to pick during an incident."
+description: "What each status on a status page actually means — operational, degraded performance, partial outage, major outage and under maintenance — and how to choose the right one while an incident is running."
author: "openstatus"
publishedAt: "2026-05-05"
-category: "fundamentals"
+category: "reference"
faq:
- - question: "What is a status page?"
- answer: "A status page is a public-facing web page that displays the real-time operational health of a service. It shows current uptime, active incidents, scheduled maintenance, and historical reliability metrics. The point is to give users a single, trustworthy place to check whether a problem is on your end or theirs."
- - question: "Why do companies need a status page?"
- answer: "Without a status page, every outage floods your support inbox with the same question: 'is it down?' A status page deflects that load, builds trust by being transparent during incidents, and signals operational maturity to enterprise buyers who often require one before signing a contract."
- - question: "What's the difference between a public and private status page?"
- answer: "A public status page is visible to anyone and shows curated, user-facing reliability data. A private status page is gated behind authentication and shows real-time operational metrics to internal teams or specific customers - typically more granular and used for SLO tracking, not customer communication."
- - question: "What should a status page include?"
- answer: "At minimum: current component statuses (API, dashboard, auth, etc.), active incidents with timestamps and updates, scheduled maintenance windows, and historical uptime for the last 30-90 days. Optional but valuable: subscription options (email, SMS, Slack, RSS), incident postmortems, and per-region status."
- - question: "Should my status page be on a separate domain?"
- answer: "Yes. Host it on a separate domain or subdomain (e.g., status.yourcompany.com) on independent infrastructure. If your main service is down and your status page is on the same servers, users see nothing - exactly when they need information most."
- - question: "How often should I update a status page during an incident?"
- answer: "Every 15-30 minutes during an active incident, even if there's nothing new to report. 'Still investigating, next update at 14:30' is more useful than silence. Silence makes users assume you've abandoned them."
- - question: "Do small companies need a status page?"
- answer: "If you have paying customers, yes. It's not about scale - it's about trust. A simple status page with uptime history and an incident feed signals you take reliability seriously. It takes less than an hour to set up and pays for itself the first time something breaks."
- - question: "What's the difference between a status page and a monitoring tool?"
- answer: "A monitoring tool checks whether your service is up and alerts your team. A status page communicates that information to users. They're connected - monitoring data often drives status page updates - but they serve different audiences. Monitoring is for engineers; status pages are for customers."
+ - question: "What does partial outage mean on a status page?"
+ answer: "A partial outage means part of a component is fully unavailable, or the component is unavailable for a subset of users — one region, one plan tier, or one integration. Requests to the affected part fail outright rather than merely running slowly. It sits between degraded performance, where things still work but badly, and a major outage, where nothing works for anyone."
+ - question: "What is the difference between degraded performance and a partial outage?"
+ answer: "Degraded performance means the component still works but not properly — slow responses, intermittent failures that succeed on retry, or one feature unavailable while the rest functions. A partial outage means something is failing outright, just not for everyone or not across the whole component. The test is failure versus slowness."
+ - question: "What does major outage mean?"
+ answer: "A major outage means the component is fully unavailable to essentially all users and nothing useful is being served. It is scoped to the component, not the whole service — a major outage on billing does not imply a major outage on your API, which is the reason to break a status page into components in the first place."
+ - question: "What does operational mean on a status page?"
+ answer: "Operational means the component is responding correctly and within its normal latency range, with no known issues. It is the default state. Leaving something marked operational while you actively investigate user reports is the fastest way to make a status page untrustworthy — move it to degraded performance while you look."
+ - question: "Which status should I use during an incident?"
+ answer: "Work through it in order. Is anything failing outright? If not, and it is only slow or flaky, use degraded performance. If something is failing, does it affect every user and all functionality in that component? If not, use partial outage. If so, use major outage. When two statuses both fit, choose the more severe — under-reporting costs more trust than over-reporting."
---
-When something breaks in production, users need to know if the problem is on your end or theirs. Without a single source of truth, they find out by filing duplicate support tickets, posting on social media, or assuming your whole company is down.
+Status pages use a small, shared vocabulary — operational, degraded performance, partial outage, major outage, under maintenance — and almost none of it is defined on the page itself. The result is that the same words mean different things at different companies, and readers guess.
-That single source of truth is the status page. It exists to deflect support load during outages, build trust through honest communication, and signal to enterprise buyers that you take reliability seriously.
+This is the reference for what each status means, and for how to pick the right one while an incident is still running. If you are looking for the broader introduction instead, [what a status page is and why you need one](/status-page) covers that.
+
+## Status page terminology
+
+### Operational
+
+Everything works. The component is responding correctly and within its normal latency range. This is the default state, and it should genuinely mean "no known issues" — marking something operational while you investigate reports is how status pages lose credibility.
+
+### Degraded performance
+
+The component works, but not properly. Responses are slow, a subset of requests fail and succeed on retry, or a feature is unavailable while the rest of the component functions.
+
+This is the most under-used status and the most useful one. Most real incidents are degradations, not outages, and reaching for "operational" or "major outage" because degraded feels ambiguous is what makes a status page feel dishonest.
+
+### Partial outage
+
+Part of the component is fully unavailable, or the component is unavailable for a subset of users — one region, one plan tier, one integration. Requests to the affected part fail rather than merely slow down.
+
+The distinction from degraded is failure, not slowness. The distinction from a major outage is scope: some users or some functionality still work completely.
+
+### Major outage
+
+The component is fully unavailable to essentially all users. Nothing useful is being served.
+
+Use it sparingly and honestly. A major outage on one component does not mean a major outage everywhere — component-level accuracy is the point of having components at all.
+
+### Under maintenance
+
+Planned, announced downtime inside a stated window. It reads differently from an outage to anyone looking, which is precisely why scheduled work belongs here rather than showing as an unexplained outage.
+
+### Choosing between them during an incident
+
+The practical test, in order: is anything failing outright? If no, and it is merely slow or flaky, that is degraded. If yes, does it affect everyone and everything in that component? If no, that is a partial outage. If yes, that is a major outage. When two statuses both fit, pick the more severe one — under-reporting costs you more trust than over-reporting.
+
+## Where these statuses appear
+
+A status page exists to deflect support load during outages, build trust through honest communication, and signal to enterprise buyers that you take reliability seriously. The vocabulary above is how it does that.
## What a Status Page Actually Shows
@@ -127,51 +160,33 @@ If you are ready to run one, a [hosted status page](/status-page) gives you comp
## Frequently asked questions
-<Details summary="What is a status page?">
-
-A status page is a public-facing web page that displays the real-time operational health of a service. It shows current uptime, active incidents, scheduled maintenance, and historical reliability metrics. The point is to give users a single, trustworthy place to check whether a problem is on your end or theirs.
-
-</Details>
-
-<Details summary="Why do companies need a status page?">
-
-Without a status page, every outage floods your support inbox with the same question: 'is it down?' A status page deflects that load, builds trust by being transparent during incidents, and signals operational maturity to enterprise buyers who often require one before signing a contract.
-
-</Details>
-
-<Details summary="What's the difference between a public and private status page?">
-
-A public status page is visible to anyone and shows curated, user-facing reliability data. A private status page is gated behind authentication and shows real-time operational metrics to internal teams or specific customers - typically more granular and used for SLO tracking, not customer communication.
-
-</Details>
-
-<Details summary="What should a status page include?">
+<Details summary="What does partial outage mean on a status page?">
-At minimum: current component statuses (API, dashboard, auth, etc.), active incidents with timestamps and updates, scheduled maintenance windows, and historical uptime for the last 30-90 days. Optional but valuable: subscription options (email, SMS, Slack, RSS), incident postmortems, and per-region status.
+A partial outage means part of a component is fully unavailable, or the component is unavailable for a subset of users — one region, one plan tier, or one integration. Requests to the affected part fail outright rather than merely running slowly. It sits between degraded performance, where things still work but badly, and a major outage, where nothing works for anyone.
</Details>
-<Details summary="Should my status page be on a separate domain?">
+<Details summary="What is the difference between degraded performance and a partial outage?">
-Yes. Host it on a separate domain or subdomain (e.g., status.yourcompany.com) on independent infrastructure. If your main service is down and your status page is on the same servers, users see nothing - exactly when they need information most.
+Degraded performance means the component still works but not properly — slow responses, intermittent failures that succeed on retry, or one feature unavailable while the rest functions. A partial outage means something is failing outright, just not for everyone or not across the whole component. The test is failure versus slowness.
</Details>
-<Details summary="How often should I update a status page during an incident?">
+<Details summary="What does major outage mean?">
-Every 15-30 minutes during an active incident, even if there's nothing new to report. 'Still investigating, next update at 14:30' is more useful than silence. Silence makes users assume you've abandoned them.
+A major outage means the component is fully unavailable to essentially all users and nothing useful is being served. It is scoped to the component, not the whole service — a major outage on billing does not imply a major outage on your API, which is the reason to break a status page into components in the first place.
</Details>
-<Details summary="Do small companies need a status page?">
+<Details summary="What does operational mean on a status page?">
-If you have paying customers, yes. It's not about scale - it's about trust. A simple status page with uptime history and an incident feed signals you take reliability seriously. It takes less than an hour to set up and pays for itself the first time something breaks.
+Operational means the component is responding correctly and within its normal latency range, with no known issues. It is the default state. Leaving something marked operational while you actively investigate user reports is the fastest way to make a status page untrustworthy — move it to degraded performance while you look.
</Details>
-<Details summary="What's the difference between a status page and a monitoring tool?">
+<Details summary="Which status should I use during an incident?">
-A monitoring tool checks whether your service is up and alerts your team. A status page communicates that information to users. They're connected - monitoring data often drives status page updates - but they serve different audiences. Monitoring is for engineers; status pages are for customers.
+Work through it in order. Is anything failing outright? If not, and it is only slow or flaky, use degraded performance. If something is failing, does it affect every user and all functionality in that component? If not, use partial outage. If so, use major outage. When two statuses both fit, choose the more severe — under-reporting costs more trust than over-reporting.
</Details>