Open-source status page, incident response and uptime monitoring
TypeScript alertingincident-managementmcpmcp-servermonitoringmonitoring-as-codeobservabilityon-callopen-sourcesrestatus-pagestatuspagesynthetic-monitoringterraformtinybirdtursouptimeuptime-checkeruptime-monitor
chore: more content (#2293)
Maximilian Kaske9edb5871161a
diff --git a/apps/web/src/content/pages/blog/reflecting-1-year-building-openstatus.mdx b/apps/web/src/content/pages/blog/reflecting-1-year-building-openstatus.mdxindex 49c7f70fc..e2c640de6 100644--- a/apps/web/src/content/pages/blog/reflecting-1-year-building-openstatus.mdx+++ b/apps/web/src/content/pages/blog/reflecting-1-year-building-openstatus.mdx@@ -44,7 +44,7 @@ This initial idea served as the seed from which our entire project would grow.As we progressed, we talked to a lot of users, VC. We explored various directions, sometimes feeling a bit lost in the sea of possibilities:1. **Serverless monitoring**: Given that most of our users were Vercel customers, we considered specializing in this area.-2. **Incident management**: Inspired by products like [incident.io](https://incident.io/), we contemplated starting with status pages and expanding into incident management. However, we realized this would target larger, Series B+ startups, involving longer sales processes and diverging from our core audience of small teams from bootstrapped businesses or Series A startups.+2. **Incident management**: Inspired by products like incident.io, we contemplated starting with status pages and expanding into incident management. However, we realized this would target larger, Series B+ startups, involving longer sales processes and diverging from our core audience of small teams from bootstrapped businesses or Series A startups.3. **AI-enhanced alerting systems**: We briefly considered focusing on our product's alerting capabilities and incorporating AI for smart alerts. In retrospect, this seemed more like an attempt to capitalize on the AI trend rather than a strategic decision.4. **Real User Monitoring (RUM)**: We implemented this feature, but after discussions, we recognized the need to focus on our core strength: synthetic monitoring.diff --git a/apps/web/src/content/pages/compare/datadog.mdx b/apps/web/src/content/pages/compare/datadog.mdxnew file mode 100644index 000000000..cf60443f3--- /dev/null+++ b/apps/web/src/content/pages/compare/datadog.mdx@@ -0,0 +1,95 @@+---+title: "Datadog Synthetics vs openstatus"+publishedAt: "2026-06-19"+author: "openstatus"+description: "Looking for a Datadog Synthetics alternative without the enterprise bill? openstatus does uptime and API monitoring from 28 regions with a built-in status page, open source, from $30/month — flat, no per-run fees."+category: "company"+faq:+ - question: "Is openstatus a good Datadog Synthetics alternative?"+ answer: "Yes, for uptime and API monitoring with a status page. Openstatus runs HTTP, TCP, and DNS checks from 28 regions with flat pricing and a built-in status page, and it's open-source. Datadog Synthetics is far more powerful for browser-based, multi-step synthetic tests inside a full observability platform — but its per-run, per-seat pricing climbs steeply, and it has no standalone free tier for synthetics."+ - question: "Why is openstatus cheaper than Datadog Synthetics?"+ answer: "Datadog prices synthetic tests per run and per location, so frequent checks across multiple regions add up fast — published comparisons cite thousands of dollars a month for high-frequency uptime checks. Openstatus uses flat pricing: paid plans start at $30/month for 20 monitors across 28 regions with no per-run fees and unlimited team members."+ - question: "Does openstatus include a status page?"+ answer: "Yes. Openstatus includes a branded public status page with custom domains, maintenance windows, and subscriber notifications on every plan. Datadog offers a status page product, but it's a separate part of the platform and assumes you're already a Datadog customer."+ - question: "When should I stay on Datadog Synthetics?"+ answer: "If you need browser-based, scripted multi-step synthetic tests tightly correlated with APM traces, logs, and metrics in one platform, Datadog is the stronger choice. Openstatus is the better fit when you mainly need uptime and API checks plus a status page without the platform cost."+---++## Looking for a Datadog Synthetics alternative?++**TL;DR:** Openstatus does uptime and API monitoring from 28 regions with a built-in status page, open-source code, and flat $30/month pricing. Datadog Synthetics is more powerful for scripted browser tests inside a full observability platform — but you pay per run, per seat, and per location.++If your Datadog Synthetics bill is climbing because uptime checks are priced per run, openstatus is the alternative to weigh. It covers HTTP, TCP, and DNS monitoring from 28 global regions, bundles a status page, and charges a flat rate with no per-check metering.++Openstatus and Datadog solve different scopes of the same problem. Openstatus is a focused **uptime monitoring and status page** tool — it tells you when your endpoints are down or slow and lets you communicate that to users. Datadog Synthetics is one module of a sprawling **observability platform** that correlates synthetic tests with APM, logs, RUM, and infrastructure metrics.++For teams that want straightforward uptime and API monitoring with predictable pricing and a public status page, openstatus is the leaner fit. For teams already standardized on Datadog who need scripted browser journeys tied into traces and logs, Datadog's depth is hard to match — at a price.++## Feature Comparison++| Feature | openstatus | Datadog Synthetics |+| ----------------------------- | ---------------- | --------------------- |+| Pricing model | Flat | Per run / per seat |+| Standalone free tier | Yes | No |+| Multi-region | 28 regions | Many (managed + private) |+| Status Page | Yes (built-in) | Separate product |+| Open-source | Yes (AGPL-3.0) | No |+| Self-hostable | Yes | No |+| Monitoring as code | Yes (Terraform) | Yes (Terraform) |+| CLI | Yes | Yes |+| OpenTelemetry exporter | Yes | Native (Datadog) |+| Browser / multi-step synthetics | No | Yes |+| APM / logs / RUM correlation | No | Yes |++## Pricing Comparison++| | openstatus | Datadog Synthetics |+| -------------- | ----------------------- | ----------------------------- |+| Free plan | 1 monitor, 6 regions | None (platform trial only) |+| Model | Flat per plan | Per API/browser test run |+| Entry paid | $30/mo (20 monitors) | Usage-based, scales with runs |+| Status page | Included | Separate product |+| Team members | Unlimited on paid plans | Per-seat |++Datadog's per-run pricing is efficient for occasional, scripted checks but expensive for the high-frequency, multi-region uptime monitoring most teams actually want. Published comparisons put monitoring 50 endpoints every minute from three locations in the thousands of dollars per month on Datadog. Openstatus runs that workload on flat pricing.++## When to Choose openstatus++- You mainly need **uptime and API monitoring**, not scripted browser flows+- You want a **built-in status page** for incident communication+- You want **flat, predictable pricing** without per-run metering+- You prefer **open-source** software or need to self-host+- You want **monitoring as code**, a CLI, and OpenTelemetry export++## When to Choose Datadog Synthetics++- You need **browser-based, multi-step synthetic tests** (login, checkout, search)+- You want synthetics **correlated with APM traces, logs, and RUM** in one place+- You're **already standardized on Datadog** and budget isn't the constraint++## Switching from Datadog Synthetics to openstatus++If your Datadog Synthetics usage is mostly HTTP/API uptime checks rather than scripted browser tests, migrating is simple:++1. **Sign up** for a free openstatus account+2. **Recreate your API checks** in the dashboard or as code via the [Terraform provider](/docs/reference/terraform) and CLI+3. **Move alerting** to openstatus channels — Slack, Discord, PagerDuty, OpsGenie, and more+4. **Publish a status page** — included with every openstatus plan++If you depend on Datadog's browser synthetics and trace correlation, keep those in Datadog and use openstatus for cost-efficient uptime monitoring and your public status page.++## Related Resources++- [Checkly vs openstatus](/compare/checkly) — another synthetic-monitoring comparison+- [What Is Synthetic Monitoring?](/guides/what-is-synthetic-monitoring)+- [What Is Uptime Monitoring?](/guides/what-is-uptime-monitoring)+- [Status Pages for API Providers](/use-case/api-providers)+- [Pricing](/pricing)++---++Start monitoring from 28 regions today++<ButtonLink href="https://app.openstatus.dev?ref=compare-datadog">Get Started Free</ButtonLink>++---diff --git a/apps/web/src/content/pages/compare/pingdom.mdx b/apps/web/src/content/pages/compare/pingdom.mdxnew file mode 100644index 000000000..07e0ec11a--- /dev/null+++ b/apps/web/src/content/pages/compare/pingdom.mdx@@ -0,0 +1,98 @@+---+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)++---++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/guides/hosted-uptime-kuma-alternative.mdx b/apps/web/src/content/pages/guides/hosted-uptime-kuma-alternative.mdxnew file mode 100644index 000000000..edbf290a3--- /dev/null+++ b/apps/web/src/content/pages/guides/hosted-uptime-kuma-alternative.mdx@@ -0,0 +1,86 @@+---+title: "A Hosted Uptime Kuma Alternative"+description: "Love Uptime Kuma but tired of running it yourself? openstatus is the open-source, managed, multi-region alternative — unlimited monitors, a status page, and no VPS to babysit. Self-host it too, if you want."+author: "openstatus"+publishedAt: "2026-06-19"+category: "alternative"+faq:+ - question: "Is openstatus a hosted version of Uptime Kuma?"+ answer: "Not literally — they're separate projects — but openstatus fills the same need without the self-hosting. Both are open-source uptime monitors with status pages. The key difference: Uptime Kuma runs on a single server you maintain, while openstatus is a managed, multi-region service. You can still self-host openstatus if you want full control."+ - question: "What's the main limitation of Uptime Kuma?"+ 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: "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."+---++## You like Uptime Kuma. You're just tired of running it.++Uptime Kuma is a great piece of software. It's open-source, the UI is clean, it does HTTP, TCP, DNS, and more, and it gives you a status page — all for the cost of a VPS. For a homelab or a side project, it's hard to beat.++The friction shows up when the thing you use to know your service is down is itself something you have to keep up:++- **It runs from one location.** Your Kuma instance has a single network vantage point. A blip on its host looks identical to a real outage, so you get false alerts — and a genuinely regional outage is invisible, because there's nothing to compare against.+- **It's a single point of failure.** If the box running Uptime Kuma goes down, your monitoring goes down with it. The monitor that's supposed to wake you up is asleep.+- **You're on the hook for upkeep.** Patches, database growth, backups, the occasional migration. It's not much, until it's the week everything else is on fire too.++None of this means Kuma is wrong. It means at a certain point you want the same idea — open-source, monitors plus a status page — without operating it yourself.++## openstatus: the managed, multi-region take on the same idea++[openstatus](https://openstatus.dev) is an open-source synthetic monitoring and status page platform. The overlap with Uptime Kuma is deliberate: open-source, uptime checks, a built-in status page. The difference is operational.++| | Uptime Kuma | openstatus |+| --- | --- | --- |+| Hosting | Self-hosted only | Managed cloud **or** self-host |+| Check locations | Single (your server) | 28 regions, checked in parallel |+| Resilience | Single point of failure | Distributed, managed infrastructure |+| Status page | Yes | Yes (custom domains, subscribers) |+| Monitoring as code | No | Terraform, CLI, MCP server |+| Open-source | Yes (MIT) | Yes (AGPL-3.0) |+| Upkeep | You | Us (or you, if self-hosting) |++The point that matters most: openstatus checks from **28 regions at once**. A failure has to show up across multiple continents before it alerts, which kills the single-location false positives Kuma can't avoid — and tells you immediately whether an outage is global or just one region.++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.++## When to stay on Uptime Kuma++Be honest with yourself here — Kuma is the right call when:++- You're monitoring **internal or homelab** services and a single location is fine+- You want **zero recurring cost** and already have a server to run it on+- You enjoy running your own infrastructure and want **total control**++## When to switch to openstatus++- You need **multi-region** checks to trust your alerts and catch regional outages+- You don't want your monitor to be a **single point of failure**+- You'd rather **not maintain** the monitoring infrastructure yourself+- You want **monitoring as code** (Terraform), a CLI, or an MCP server for AI agents+- You still want **open-source** — just managed++## Moving from Uptime Kuma to openstatus++1. **Sign up** for a free openstatus account — no credit card required+2. **Recreate your monitors** in the dashboard, or define them as code with the [Terraform provider](/docs/reference/terraform) and CLI+3. **Rebuild your status page** — add components, custom domain, and let users subscribe+4. **Point your alerts** at Slack, Discord, Email, PagerDuty, OpsGenie, and more++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)+- [Status Pages for Open-Source Projects](/use-case/open-source)++---++Open-source monitoring, without the VPS to babysit++<ButtonLink href="https://app.openstatus.dev?ref=guide-hosted-uptime-kuma">Try openstatus free</ButtonLink>++---diff --git a/apps/web/src/content/pages/guides/migrate-from-atlassian-statuspage.mdx b/apps/web/src/content/pages/guides/migrate-from-atlassian-statuspage.mdxindex dfba5dfe7..88df33b6d 100644--- a/apps/web/src/content/pages/guides/migrate-from-atlassian-statuspage.mdx+++ b/apps/web/src/content/pages/guides/migrate-from-atlassian-statuspage.mdx@@ -34,7 +34,7 @@ For background on why we built the importer, see the [announcement blog post](/b## What Gets Imported-Openstatus reads from the [Statuspage REST API](https://developer.statuspage.io/) and maps your data as follows.+Openstatus reads from the Statuspage REST API and maps your data as follows.### Field Mappingdiff --git a/apps/web/src/content/pages/guides/migrate-from-uptime-robot.mdx b/apps/web/src/content/pages/guides/migrate-from-uptime-robot.mdxnew file mode 100644index 000000000..10099703f--- /dev/null+++ b/apps/web/src/content/pages/guides/migrate-from-uptime-robot.mdx@@ -0,0 +1,122 @@+---+title: "How to Migrate from UptimeRobot to openstatus"+description: "A step-by-step guide to moving from UptimeRobot to openstatus — exporting your monitors, recreating them in the UI or as code, wiring up alerts, and publishing a status page. Most teams finish in under an hour."+author: "openstatus"+publishedAt: "2026-06-19"+category: "alternative"+howto:+ totalTime: "PT1H"+ steps:+ - name: "Create a free openstatus account"+ text: "Sign up at app.openstatus.dev. No credit card is required, and the free plan is enough to recreate your first monitors and a status page."+ - name: "List your UptimeRobot monitors"+ text: "Open your UptimeRobot dashboard and note each monitor's type (HTTP, keyword, ping, port), URL, check interval, and alert contacts. The UptimeRobot API can export this list if you have many monitors."+ - name: "Recreate monitors in openstatus"+ text: "Add each monitor in the openstatus dashboard, or define them as code with the Terraform provider or CLI. Choose the regions to check from and set assertions on status code, latency, or body."+ - name: "Wire up notifications"+ text: "Connect your alert channels — Slack, Discord, Email, PagerDuty, OpsGenie, and more — and attach them to your monitors."+ - name: "Publish your status page"+ text: "Create a status page, add components backed by your monitors, set a custom domain, and let users subscribe by email, RSS, or JSON."+ - name: "Run in parallel, then switch off"+ text: "Leave both tools running for a week or two. Once you trust the openstatus alerts and your status page is live, disable the UptimeRobot monitors and cancel the plan."+faq:+ - question: "Does openstatus automatically import my UptimeRobot monitors?"+ answer: "openstatus's one-click importer covers status-page tools (Instatus, Atlassian Statuspage, Better Stack) — it imports components, incidents, maintenances, and subscribers. UptimeRobot is a monitoring tool, so its monitors are recreated rather than imported: rebuild them in the dashboard, or define them as code with the Terraform provider or CLI. Most setups take under an hour."+ - question: "How long does migrating from UptimeRobot take?"+ answer: "For a typical setup of a few dozen monitors, under an hour. If you define monitors as code with Terraform or the CLI, you can script the whole thing and apply it in one go."+ - question: "Will my uptime history transfer from UptimeRobot?"+ answer: "Historical uptime data stays in UptimeRobot — it isn't transferred. openstatus starts collecting data the moment your monitors go live. Many teams run both in parallel for a short period before switching off UptimeRobot."+ - question: "Why migrate from UptimeRobot in the first place?"+ answer: "Common reasons: UptimeRobot checks from a single location while openstatus checks from 28 regions in parallel; UptimeRobot restricted its free tier to non-commercial use in October 2024; openstatus is open-source and self-hostable; and openstatus includes monitoring as code, a CLI, and an MCP server for AI agents."+---++## Why teams move from UptimeRobot to openstatus++UptimeRobot is a familiar, low-cost monitor, and for basic single-location checks it does the job. Teams usually switch when they outgrow that:++- **Single-location checks** mean false positives from probe-side blips and no way to tell a regional outage apart from a global one. openstatus checks from **28 regions in parallel**.+- **The free tier is now non-commercial only** (since October 2024), so production use needs a paid plan anyway.+- **No monitoring as code** — no Terraform provider, no CLI. openstatus ships both, plus an MCP server for AI agents.+- **Open-source and self-hostable** — openstatus is AGPL-3.0; UptimeRobot is closed-source SaaS.++See the full [UptimeRobot vs openstatus comparison](/compare/uptime-robot) for the side-by-side.++## What transfers, and what doesn't++Set expectations before you start:++- **Monitors** — recreated, not imported. openstatus's importer is built for status-page tools (Instatus, Atlassian Statuspage, Better Stack), not monitoring tools. Rebuilding monitors is quick, and defining them as code makes it quicker.+- **Uptime history** — stays in UptimeRobot. openstatus starts fresh from the moment monitors go live. Run both in parallel for a week or two if you want overlap.+- **Alert contacts** — reconfigured in openstatus, which supports more channels (Slack, Discord, PagerDuty, OpsGenie, and more).++## Step 1 — Create a free openstatus account++Sign up at [app.openstatus.dev](https://app.openstatus.dev?ref=migrate-uptimerobot). No credit card required. The free plan is enough to recreate your first monitors and a status page; upgrade when you need more monitors or a custom domain.++## Step 2 — List your UptimeRobot monitors++In UptimeRobot, note each monitor's:++- **Type** — HTTP(s), keyword, ping, or port+- **URL or host**+- **Check interval**+- **Alert contacts**++If you have many monitors, the UptimeRobot API can dump the full list as JSON so you don't have to copy them by hand.++## Step 3 — Recreate your monitors in openstatus++Two ways, depending on how you like to work.++**In the dashboard** — add each monitor, pick the regions to check from, and set assertions on status code, latency, headers, or body.++**As code** — define monitors with the [Terraform provider](/docs/reference/terraform) so they live in version control and apply in one command:++```terraform+resource "openstatus_http_monitor" "api" {+ name = "API Health Check"+ url = "https://api.example.com/health"+ periodicity = "1m"+ regions = ["iad", "ams", "syd"]++ status_code_assertions {+ target = 200+ comparator = "eq"+ }+}+```++The same is available through the openstatus CLI if you'd rather script it than write HCL.++## Step 4 — Wire up notifications++Connect your alert channels and attach them to your monitors. openstatus supports Slack, Discord, Email, PagerDuty, OpsGenie, Telegram, and more — so you can usually consolidate channels you had scattered across UptimeRobot.++Because checks run from multiple regions, openstatus only alerts once several regions agree a check has failed, which cuts the false positives that single-location monitoring produces.++## Step 5 — Publish your status page++UptimeRobot's status page is basic; this is where openstatus pulls ahead. Create a status page, add components backed by your monitors, set a custom domain, and let users subscribe by email, RSS/Atom, or JSON. Publish status reports and schedule maintenance windows from the same workspace.++## Step 6 — Run in parallel, then switch off++Leave both tools running for a week or two. Once you trust the openstatus alerts and your status page is live, disable the UptimeRobot monitors and cancel the plan.++## Related Resources++- [UptimeRobot vs openstatus](/compare/uptime-robot) — full head-to-head+- [Top Five Pingdom Alternatives in 2026](/guides/top-five-pingdom-alternatives)+- [What Is Uptime Monitoring?](/guides/what-is-uptime-monitoring)+- [Why Every SaaS Needs a Status Page](/guides/why-every-saas-needs-a-status-page)++## Need Help?++Join our [Discord community](https://www.openstatus.dev/discord), check the [documentation](https://www.openstatus.dev/docs), or reach out via [email](mailto:[email protected]).++---++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.mdxindex 0abfd87d3..6c33715bc 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@@ -24,10 +24,10 @@ If you're evaluating your options, you're in the right place. In this article, wThe alternatives we'll cover:- [OpenStatus](https://openstatus.dev)-- [Status.io](https://status.io)-- [Datadog Status Page](https://www.datadoghq.com/product/status-page/)-- [Instatus](https://instatus.com)-- [Betterstack](https://betterstack.com/status-pages/)+- Status.io+- Datadog Status Page+- Instatus+- Betterstack## Why Look for an Atlassian Statuspage Alternative?@@ -90,7 +90,7 @@ Here's a high-level look at how these five alternatives stack up on key featuresheight={575}/>-[Status.io](https://status.io) s a long-standing, cloud-based status page provider used by major companies like Docker. It focuses purely on status communication and incident management, positioning itself as a dedicated communication hub rather than a monitoring tool.+Status.io is a long-standing, cloud-based status page provider used by major companies like Docker. It focuses purely on status communication and incident management, positioning itself as a dedicated communication hub rather than a monitoring tool.- **Key Features**:- **Incident Management**: Robust tools for managing and communicating incidents to subscribers.@@ -107,7 +107,7 @@ Here's a high-level look at how these five alternatives stack up on key featuresheight={575}/>-For teams already embedded in the Datadog ecosystem, their [Status Page](https://www.datadoghq.com/blog/status-pages/) product is a natural extension. It leverages your existing monitoring data, dashboards, and incident management workflows.+For teams already embedded in the Datadog ecosystem, their Status Page product is a natural extension. It leverages your existing monitoring data, dashboards, and incident management workflows.- **Key Features**:- **Deep Ecosystem Integration**: Automatically link status page incidents to Datadog monitors, logs, and traces.@@ -125,7 +125,7 @@ For teams already embedded in the Datadog ecosystem, their [Status Page](https:/height={575}/>-[Instatus](https://instatus.com) has strong focus on integrating with your existing tools. It's a popular choice for modern tech companies that want an automated status page.+Instatus has strong focus on integrating with your existing tools. It's a popular choice for modern tech companies that want an automated status page.- **Key Features**:- **Third-Party Integrations**: Its primary strength is connecting to external monitoring tools (like UptimeRobot, Pingdom, DataDog) to automate status updates.@@ -145,7 +145,7 @@ For teams already embedded in the Datadog ecosystem, their [Status Page](https:/height={575}/>-[Betterstack](https://betterstack.com/status-page/) bundles uptime monitoring, incident management, and status pages into a single, cohesive platform. It's well-regarded for its generous free tier and all-in-one approach.+Betterstack bundles uptime monitoring, incident management, and status pages into a single, cohesive platform. It's well-regarded for its generous free tier and all-in-one approach.- **Key Features**:- **All-in-One Solution**:A single platform for monitoring, on-call scheduling, incident management, and status pages.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.mdxindex 73880a889..6d31008ca 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@@ -22,7 +22,7 @@ faq:Instatus is a nice status page tool — and a great fit if you already have monitoring solved and just want a branded page on top. The moment you also need monitoring, monitoring-as-code, OpenTelemetry, or private probes, you start stretching it beyond what it was designed for.-If you're switching for the **monitoring + status page** bundle, look at [openstatus](https://openstatus.dev), [Datadog](https://www.datadoghq.com/product/status-page/), or [Betterstack](https://betterstack.com/status-pages/). If you want a **pure status page** for serious incident comms, look at [Atlassian Statuspage](https://www.atlassian.com/software/statuspage) or [Status.io](https://status.io). If you want **open-source and self-hostable**, openstatus is currently the only option on this list.+If you're switching for the **monitoring + status page** bundle, look at [openstatus](https://openstatus.dev), Datadog, or Betterstack. If you want a **pure status page** for serious incident comms, look at Atlassian Statuspage or Status.io. If you want **open-source and self-hostable**, openstatus is currently the only option on this list.## Why Teams Leave Instatus@@ -119,7 +119,7 @@ When a check fails, the status page can update automatically or wait for a humanheight={575}/>-[Atlassian Statuspage](https://www.atlassian.com/software/statuspage) is the original and most mature status page product. It's deeply focused on incident communication — subscriber management, templates, audit trails, and integrations with Jira and Opsgenie are all first-class.+Atlassian Statuspage is the original and most mature status page product. It's deeply focused on incident communication — subscriber management, templates, audit trails, and integrations with Jira and Opsgenie are all first-class.It does not include monitoring. You bring your own (Datadog, New Relic, Atlassian's own monitoring, etc.) and pipe events in. If incident comms is the hard problem and monitoring is already solved elsewhere, Statuspage's depth here is hard to match.@@ -137,7 +137,7 @@ It does not include monitoring. You bring your own (Datadog, New Relic, Atlassiaheight={575}/>-[Status.io](https://status.io) is a long-standing, cloud-based status page provider. It's intentionally narrow: status communication and incident management, no monitoring. Customers like Docker have used it for years.+Status.io is a long-standing, cloud-based status page provider. It's intentionally narrow: status communication and incident management, no monitoring. Customers like Docker have used it for years.If you specifically want a tool that does one thing and stays out of your monitoring stack, Status.io is a sensible choice. The flip side is that the headline pricing for advanced features (private pages, full customization) starts at $349/month, which is a steep jump from Instatus.@@ -155,7 +155,7 @@ If you specifically want a tool that does one thing and stays out of your monitoheight={575}/>-[Datadog Status Page](https://www.datadoghq.com/blog/status-pages/) is the natural extension if Datadog is already your observability backbone. It links incidents directly to monitors, logs, and traces — meaning the page reflects the same source of truth your on-call team is already looking at.+Datadog Status Page is the natural extension if Datadog is already your observability backbone. It links incidents directly to monitors, logs, and traces — meaning the page reflects the same source of truth your on-call team is already looking at.You're paying Datadog prices and committing further to the ecosystem, so this only makes sense if you're already in. As a standalone Instatus replacement for a small team it's almost always overkill.@@ -173,7 +173,7 @@ You're paying Datadog prices and committing further to the ecosystem, so this onheight={575}/>-[Betterstack](https://betterstack.com/status-page/) bundles uptime monitoring, on-call scheduling, incident management, and status pages into one product. The free tier is genuinely usable for personal projects and small side businesses, and Terraform support makes it a credible option for infrastructure teams.+Betterstack bundles uptime monitoring, on-call scheduling, incident management, and status pages into one product. The free tier is genuinely usable for personal projects and small side businesses, and Terraform support makes it a credible option for infrastructure teams.The catch is per-page and per-seat add-ons: custom styling is a $12-per-page-per-month upcharge, the private status page lives behind a $42 add-on, and seats scale at $29 each. The bundle gets pricier than it looks once you're past the free tier.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.mdxnew file mode 100644index 000000000..9e7ef5e58--- /dev/null+++ b/apps/web/src/content/pages/guides/top-five-pingdom-alternatives.mdx@@ -0,0 +1,142 @@+---+title: "Top Five Pingdom Alternatives in 2026"+description: "The honest guide to Pingdom alternatives in 2026 — including openstatus, UptimeRobot, Better Stack, Checkly, and Uptime Kuma — with pricing, monitoring depth, free tiers, and who each is actually for."+author: "openstatus"+publishedAt: "2026-06-19"+category: "alternative"+faq:+ - 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?"+ answer: "UptimeRobot has the most generous free tier (50 monitors), but it's limited to non-commercial use since October 2024. openstatus offers a permanent free plan with multi-region monitoring and a status page, and Better Stack has a usable free tier for solo developers. For unlimited free monitors, the self-hosted Uptime Kuma is the cheapest option if you're willing to run it."+ - question: "Which Pingdom alternative includes a status page?"+ answer: "openstatus, Better Stack, and Uptime Kuma include a status page. Pingdom itself does not offer a public status page, which is one of the more common reasons teams switch. UptimeRobot and Checkly are primarily monitoring tools."+ - question: "Is there an open-source Pingdom alternative?"+ answer: "Yes. openstatus (AGPL-3.0) and Uptime Kuma (MIT) are both open-source. openstatus is open-source but also offers a managed, multi-region cloud, while Uptime Kuma is self-hosted only and runs from a single location."+---++## TL;DR++Pingdom is a mature website-performance suite, but it has no free tier, is closed-source, and doesn't include a public status page. The alternatives below cover the gaps people most often switch for.++If you want **uptime monitoring plus a status page in one open-source tool**, look at [openstatus](https://openstatus.dev). If you want a **generous free tier for personal projects**, UptimeRobot or Better Stack. If you need **scripted browser checks**, Checkly. If you want **unlimited free monitors and are happy to self-host**, Uptime Kuma.++## Why Teams Leave Pingdom++Pingdom is a capable product — real user monitoring and transaction checks are genuinely useful. But there are recurring reasons teams move on:++- **No free tier.** Pingdom retired its free plan after SolarWinds acquired it. The cheapest paid plan starts around $15/month, and there's only a 14-day trial to evaluate.+- **No public status page.** Pingdom monitors, but it doesn't give you a branded page to communicate incidents to users — so you end up paying for a second tool.+- **Closed-source, no self-hosting.** Teams with data-residency, audit, or compliance requirements increasingly want an open-source, self-hostable option.+- **Price climbs with features.** Real user monitoring and transaction monitoring sit on higher tiers and add-ons; the entry price isn't the real price.+- **Round-robin locations.** Pingdom cycles through its check locations rather than testing them all at once, so a regional outage can take a full rotation to surface.++If none of these apply, Pingdom is fine. If two or more do, the alternatives below are worth a look.++## What to Look For in a Pingdom Alternative++1. **Free tier or trial** — can you evaluate it (and stay) without a contract?+2. **Status page** — is incident communication built in, or another bill?+3. **Monitoring depth** — HTTP, TCP, DNS, multi-region, and how locations are scheduled.+4. **Configuration model** — UI-only, API, CLI, or a real Terraform provider.+5. **Hosting model** — cloud-only or self-hostable, and where your data lives.++## Pingdom Alternatives at a Glance++| Feature | openstatus | UptimeRobot | Better Stack | Checkly | Uptime Kuma |+| -------------------- | ---------------- | --------------- | ------------ | ------------- | ------------- |+| Free tier | Yes | Yes (non-commercial) | Yes | Yes (limited) | Yes (self-host) |+| Built-in status page | Yes | Basic | Yes | No | Yes |+| Multi-region | 28 (parallel) | Single location | Yes | ~19 regions | Single |+| Browser checks | No | No | No | Yes | No |+| Monitoring as code | Yes (Terraform) | No | Yes | Yes (JS) | No |+| Open-source | Yes (AGPL-3.0) | No | No | No | Yes (MIT) |+| Self-hostable | Yes | No | No | No | Yes |++Prices and limits change frequently — confirm with each vendor before deciding.++## The Five Alternatives++### 1. openstatus — best for teams that want monitoring and a status page in one open-source tool++[openstatus](https://openstatus.dev) is an open-source synthetic monitoring and status page platform. It runs HTTP, TCP, and DNS checks from 28 regions **simultaneously** and powers a public or private status page from the same workspace.++The differentiator versus Pingdom is that monitoring and incident communication live in one tool — you don't pay for a status page separately — and the whole thing is open-source. Define monitors in the dashboard, or as code via the Terraform provider so they live in version control.++- **Monitoring**: HTTP, TCP, DNS from 28 regions checked in parallel, with assertions and thresholds.+- **Config**: Terraform provider, a CLI, and an MCP server for AI agents.+- **Pricing**: Permanent free tier; paid plans from $30/month with unlimited team members; self-host for $0.+- **Trade-offs**: No real user monitoring or scripted browser checks — it's focused on uptime and status, not full RUM.++**Best for**: Developer teams that want uptime monitoring, a status page, and developer tooling in one open-source product.++### 2. UptimeRobot — best for a generous free tier on personal projects++UptimeRobot is the well-known budget option, with a free plan that covers up to 50 monitors. It's simple, familiar, and fast to set up.++The catches: as of October 2024 the free tier is restricted to **non-commercial use**, checks run from a single location at a time, and team access carries a per-seat add-on.++- **Strengths**: Large free tier, simple UI, long track record.+- **Trade-offs**: Single-location checks, per-seat team pricing, closed-source.++**Best for**: Personal projects and side businesses that fit inside the non-commercial free tier.++### 3. Better Stack — best all-in-one bundle with on-call++Better Stack bundles uptime monitoring, on-call scheduling, incident management, and status pages. The free tier is usable for small teams, and it ships a Terraform provider.++The trade-off is add-on pricing — custom styling, private status pages, and extra seats stack up once you're past the free tier.++- **Strengths**: Monitoring + on-call + status in one product, generous free tier, Terraform support.+- **Trade-offs**: Per-page and per-seat add-ons; no OpenTelemetry; closed-source.++**Best for**: Small teams that want the on-call + status-page bundle and fit the free tier.++### 4. Checkly — best for scripted browser and API monitoring++Checkly is a code-first synthetic monitoring tool built around Playwright. If the reason you used Pingdom was transaction monitoring, Checkly is the more modern take on that.++It's developer-focused (monitoring as code in JavaScript) but doesn't include a public status page, and pricing is usage-based.++- **Strengths**: Powerful browser-based checks, code-first workflow, multi-region.+- **Trade-offs**: No built-in status page; usage-based pricing; closed-source.++**Best for**: Teams that need end-to-end browser flows as monitoring. See our [Checkly comparison](/compare/checkly) for detail.++### 5. Uptime Kuma — best for unlimited free monitors if you self-host++Uptime Kuma is the most popular open-source self-hosted monitor. Run it on a VPS or homelab and you get unlimited monitors and a status page for the cost of hosting.++The trade-off is that you're now operating the monitor: it runs from a single location, and if its host goes down, so does your monitoring.++- **Strengths**: Open-source (MIT), unlimited monitors, clean UI, large community.+- **Trade-offs**: Single-location, self-managed, no managed multi-region.++**Best for**: Homelabs and teams that want full control and don't mind running the infrastructure. If you like Kuma but want a managed, multi-region option, see [hosted Uptime Kuma alternative](/guides/hosted-uptime-kuma-alternative).++## Pick the Right One++- **One open-source tool for monitoring + status page** → openstatus+- **Generous free tier, personal project** → UptimeRobot+- **All-in-one with on-call** → Better Stack+- **Scripted browser checks** → Checkly+- **Unlimited free monitors, self-hosted** → Uptime Kuma++## 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)++## Need Help or Have Questions?++Join our [Discord community](https://www.openstatus.dev/discord), check the [documentation](https://www.openstatus.dev/docs), or reach out via [email](mailto:[email protected]).++---++Start monitoring from 28 regions today++<ButtonLink href="https://app.openstatus.dev?ref=guide-pingdom-alternatives">Get Started Free</ButtonLink>++---diff --git a/apps/web/src/content/pages/guides/why-is-my-monitor-failing.mdx b/apps/web/src/content/pages/guides/why-is-my-monitor-failing.mdxnew file mode 100644index 000000000..f8881072d--- /dev/null+++ b/apps/web/src/content/pages/guides/why-is-my-monitor-failing.mdx@@ -0,0 +1,108 @@+---+title: "Why Is My Monitor Failing? A Troubleshooting Guide"+description: "Your monitor says your site is down, but it loads fine in your browser. Here's how to tell a real outage from a false positive, the common causes, and how to fix each one."+author: "openstatus"+publishedAt: "2026-06-19"+category: "fundamentals"+faq:+ - question: "Why does my monitor say my site is down when it loads fine for me?"+ answer: "Almost always one of three things: the check is failing from a region you can't see from your browser, your firewall or bot-protection is blocking the probe's IP, or a single probe location had a transient network blip. Load the site from a different network and region, then check whether the failure is reported from one region or several — a single-region failure is usually a false positive."+ - question: "What is a false positive in uptime monitoring?"+ answer: "A false positive is an alert that fires when nothing was actually wrong — typically because a single probe location hit a transient network issue, a rate limit, or a bot-detection rule. The fix is to require multiple regions to fail before alerting, so isolated probe-side problems are ignored."+ - question: "How do I stop getting false alerts?"+ answer: "Require multi-region confirmation before alerting, set a realistic timeout (network round-trips from distant regions take longer than local requests), allowlist your monitor's probe IPs in your WAF and rate limiter, and make sure your assertions aren't too strict. openstatus retries a failing check before counting it as down, and only alerts once more than 50% of a monitor's regions agree the check has failed."+ - question: "Why is my monitor failing intermittently?"+ answer: "Intermittent failures usually point to rate limiting, an overloaded origin under certain traffic, bot-protection challenges that fire occasionally, DNS issues, or a timeout set too aggressively. Look at which regions fail and whether failures cluster at specific times or request volumes."+ - question: "Could my monitor be failing because of SSL?"+ answer: "Yes. An expired, misconfigured, or incomplete certificate chain causes checks to fail even when the server responds — browsers and probes both reject invalid certificates. If the failure started abruptly on a specific date, an expired certificate is a prime suspect."+---++Your phone buzzes: a monitor is down. You open the site in your browser and it loads instantly. So which is lying — the monitor, or your browser?++Usually neither. The monitor is checking from a place, in a way, and with rules that differ from what your browser does. This guide walks through how to tell a real outage from a false positive, and the common causes for each.++## First: is it a real outage or a false positive?++Before debugging anything, answer one question — **how many regions are reporting the failure?**++- **One region fails, the rest pass** → almost always a false positive. A transient network issue on the probe side, not your service. This is exactly why monitoring from a single location is unreliable.+- **Multiple regions on different continents fail** → take it seriously. Something is genuinely wrong, even if it loads from your machine.++Your browser is a single vantage point on a good network — it tells you very little about what a user in another region experiences. Trust the cross-region signal, not your own refresh.++## Common causes of a failing monitor++### 1. Bot protection or WAF blocking the probe++Cloudflare, AWS WAF, and similar tools can challenge or block automated traffic — and monitoring requests look automated. The site loads for you and fails for the probe because the probe got a challenge page or a `403`.++**Fix:** Allowlist your monitor's probe IP ranges in your WAF and bot-protection rules. Confirm you're asserting on the response you actually expect (a challenge page often returns a `200` with the wrong body).++### 2. Rate limiting++Frequent checks, or checks from several regions at once, can trip a rate limiter — especially if the monitored endpoint is also taking real traffic. Failures that appear under load or at specific times point here.++**Fix:** Allowlist probe IPs, or monitor a dedicated health endpoint that isn't rate-limited.++### 3. Timeout set too low++A request from a region on the other side of the world takes longer than one from your laptop down the street. If your timeout is tuned to local latency, distant regions will "fail" on slow-but-working responses.++**Fix:** Set a timeout that accounts for real cross-region round-trip time. If only your most distant regions fail, the timeout is the likely culprit.++### 4. SSL/TLS certificate problems++An expired certificate, a misconfigured or incomplete chain, or a hostname mismatch causes checks to fail even though the server is up. If the failure started abruptly on a specific date, suspect an expired certificate first.++**Fix:** Check the certificate's expiry and chain. Monitor certificate expiry so you're warned before it bites.++### 5. DNS issues++If the monitor can't resolve your domain — or resolves it to the wrong place — every check fails before a single byte of HTTP is exchanged. DNS propagation, a lapsed record, or a registrar problem all show up this way.++**Fix:** Verify the domain resolves correctly from multiple resolvers. A dedicated DNS monitor catches resolution problems your HTTP monitor only reports as a generic failure.++### 6. Assertions that are too strict++If your monitor asserts on an exact response body or a specific header, a harmless change — a new whitespace, a reworded message, an added field — fails the check even though the endpoint is healthy.++**Fix:** Assert on what actually signals health: the status code, and a stable substring rather than the entire body.++### 7. Redirects not followed++If your endpoint now returns a `301`/`302` and the monitor isn't set to follow redirects, it records the redirect as a non-`200` failure.++**Fix:** Enable follow-redirects, or point the monitor at the final URL.++### 8. The IP allowlist you forgot about++Internal services, staging, and APIs behind an allowlist will reject the probe outright. The service is up; the probe just isn't on the guest list.++**Fix:** Allowlist probe IPs, or use a [private location](/docs/concepts/private-locations) so the check runs inside your network.++## How openstatus reduces false positives++The single biggest source of false alerts is the single-location check. openstatus addresses it by design:++- **Multi-region by default** — checks run from up to 28 regions, in parallel.+- **Retry before counting a failure** — a failing check is retried before it's recorded as down, so a one-off network hiccup never reaches the alerting stage.+- **Majority confirmation before alerting** — more than 50% of the regions running a monitor have to fail before it pages you. An isolated probe-side blip in one or two regions is ignored.+- **The right check type** — HTTP, TCP, and DNS monitors so resolution and connectivity problems are reported as what they are, not as a vague failure.+- **Assertions and thresholds** — assert on status, latency, headers, or body so "healthy" means what you decide it means.++A monitor that cries wolf gets muted, and a muted monitor is worse than no monitor. The goal isn't to alert on every blip — it's to alert when something is genuinely, reproducibly wrong.++## Related Resources++- [What Is Uptime Monitoring?](/guides/what-is-uptime-monitoring)+- [Why Uptime Percentage Is Misleading](/guides/why-uptime-percentage-is-misleading)+- [HTTP Headers for Monitoring](/guides/http-headers)+- [What Is Synthetic Monitoring?](/guides/what-is-synthetic-monitoring)++---++**openstatus checks from up to 28 regions and only alerts when they agree** — fewer false positives, real outages caught fast. Open-source, free to start.++<ButtonLink href="https://app.openstatus.dev?ref=guide-monitor-failing">Try openstatus free</ButtonLink>++---