# Uptimepage

> Uptime monitoring and public status pages that just work.

Uptimepage is a hosted uptime-monitoring and public status-page service for teams. Checks run as often as every 60 seconds from five regions (San Jose, New York, Frankfurt, Helsinki and Singapore); a failing check opens an incident automatically and posts it to a branded status page on your own subdomain. Alerts carry dedupe and flap-suppression so brief blips never page on-call. Organizations have role-based members and an audit log, and monitors, status pages and incidents are managed by REST API, Terraform or MCP. The production source is published under AGPL, so a team can audit what it runs and self-host if its requirements change. Public data is available as JSON, an RSS feed and an embeddable SVG badge. Uptimepage operates the hosted service at uptimepage.dev: the Standard plan is free with no card, the first 1,000 accounts get a more generous founding plan kept for life, and Pro is paid for teams in production.

## Product
- [Homepage](https://uptimepage.dev): Product overview, features and pricing.
- [Architecture](https://uptimepage.dev/architecture): Interactive map of how a request and a check move through the system.
- [Start free](https://app.uptimepage.dev): Sign in and add your first monitor.

## Use cases
- [Status Page & Uptime Monitoring for SaaS](https://uptimepage.dev/status-page-for-saas): Public status pages and 60-second uptime monitoring for SaaS teams. 8 check types from HTTP to browser logins, Slack and email alerts, 90-day history.
- [Status Pages for Agencies & Client Sites](https://uptimepage.dev/status-page-for-agencies): Monitor every client site and give each a branded status page from one account. 60s checks, Slack, email and webhook alerts. Free to start.
- [Open-Source Status Page, Self-Hosted](https://uptimepage.dev/open-source-status-page): An open-source status page with uptime monitoring built in, self-hosted with docker compose or free on the hosted tier. Branded pages, subscribers, incidents.
- [Open-Source Uptime Monitoring, Self-Hosted](https://uptimepage.dev/open-source-uptime-monitoring): An open-source uptime monitor you can self-host: 8 check types from HTTP to cron heartbeats, many regions, automatic incidents and a status page. AGPL, free.
- [White-Label Uptime Monitoring & Status Pages](https://uptimepage.dev/white-label-uptime-monitoring): White-label uptime monitoring and branded status pages for resellers and MSPs. Your logo, colours and subdomain per client. Free to start, no card.
- [Uptime Monitoring for Developers, as Code](https://uptimepage.dev/uptime-monitoring-for-developers): Uptime monitoring for developers: define monitors as code with a Terraform provider, REST API and MCP. 8 check types, HTTP to browser flows. Free, no card.
- [Cron Job Monitoring and Heartbeat Checks](https://uptimepage.dev/cron-job-monitoring): Heartbeat monitoring for cron jobs, backups, queue workers and pipelines. Your job calls a ping URL, we alert when it goes quiet. Free to start, no card.
- [Browser Login Monitoring for Real Sign-Ins](https://uptimepage.dev/browser-login-monitoring): Synthetic login monitoring in a real browser: fill the form, submit, assert the page behind it. Import a Chrome recording. Free to start.
- [An UptimeRobot Alternative with Status Pages](https://uptimepage.dev/vs/uptimerobot): Comparing uptime monitors? Uptimepage pairs 8 check types at 60s with branded status pages and Slack, email and webhook alerts. Free to start.
- [Statuspage Alternative with Monitoring Built In](https://uptimepage.dev/vs/statuspage): Uptimepage pairs a branded public status page with uptime monitoring in one product: 60s checks, email and webhook subscribers, incidents. Free to start.
- [Better Uptime (Better Stack) Alternative](https://uptimepage.dev/vs/better-stack): Better Uptime is now Better Stack. Uptimepage is hosted monitoring and status pages for teams, driven as code, AGPL if you self-host.
- [A OneUptime Alternative That’s Quick to Run](https://uptimepage.dev/vs/oneuptime): An open-source monitor and status page that’s quick to run: one binary plus Postgres and ClickHouse, Terraform and MCP, AGPL. Free on the hosted tier.
- [An Uptime Kuma Alternative You Run as Code](https://uptimepage.dev/vs/uptime-kuma): Open-source uptime monitoring and branded status pages, managed as code with Terraform, a REST API and MCP. Team roles and subscribers. Free to start, no card.
- [Pingdom Alternative with Status Pages Built In](https://uptimepage.dev/vs/pingdom): A Pingdom alternative with 8 check types and branded status pages in one product, plus Slack, email and webhook alerts. Free to start, open source.
- [Uptimepage vs Upptime, Cachet & Statping](https://uptimepage.dev/vs/self-hosted-status-pages): How Uptimepage compares to Upptime, Cachet and Statping in 2026: built-in monitoring, 60-second checks, status pages, subscribers and config-as-code.
- [Uptimepage vs the Self-Hosted Monitoring Tools](https://uptimepage.dev/vs/self-hosted-monitoring): How Uptimepage compares to Uptime Kuma, OpenStatus, OneUptime, Gatus and Kener in 2026: checks, status pages, multi-region probes and config-as-code.
- [Terraform Status Page](https://uptimepage.dev/terraform-status-page): Create a status page, its components and its subscribers in Terraform, not by clicking. Official provider, monitors and page in one apply. Free to start.
- [Terraform Uptime Monitoring](https://uptimepage.dev/terraform-uptime-monitoring): Declare uptime monitors and alert channels in Terraform with the Uptimepage provider. Eight check types, HTTP to browser flows. Free to start, no card.
- [MCP Server for Uptime Monitoring](https://uptimepage.dev/mcp-server): Model Context Protocol server for uptime monitoring. 25 tools read monitors, incidents and status pages, and write only with your approval. Free, no card.
- [Why Uptimepage](https://uptimepage.dev/why-uptimepage): What you get with Uptimepage: failures confirmed across regions before anything wakes you, incidents and subscribers included, monitors an assistant sets up.
- [About Uptimepage](https://uptimepage.dev/about): Who builds and operates Uptimepage: a hosted uptime monitoring and status page service run from Nicosia, Cyprus, with production source public under AGPL.

## Comparisons
- [OpenStatus vs Uptime Kuma](https://uptimepage.dev/compare/openstatus-vs-uptime-kuma): OpenStatus and Uptime Kuma compared on facts: monitoring as code with hosted probes vs the click-driven self-hosted classic, and where each stops. July 2026.
- [Uptime Kuma vs Gatus](https://uptimepage.dev/compare/uptime-kuma-vs-gatus): Gatus vs Uptime Kuma: Kuma configures in a UI, Gatus lives in YAML. Check types, status pages, alerting and team features compared honestly. August 2026.
- [Pingdom vs StatusCake](https://uptimepage.dev/compare/pingdom-vs-statuscake): Pingdom and StatusCake compared on facts: pricing models, check types, intervals, probe locations and the status page catch. July 2026.
- [Uptime Kuma vs Healthchecks](https://uptimepage.dev/compare/uptime-kuma-vs-healthchecks): Uptime Kuma probes your service; Healthchecks waits for your job to ping it. Active checks against a dead-man's-switch, and which one you need. July 2026.
- [Uptime Kuma vs Cachet](https://uptimepage.dev/compare/uptime-kuma-vs-cachet): Uptime Kuma runs the checks, Cachet publishes the page. What Cachet v3 added, what it still will not do, and which one you actually need. July 2026.
- [OpenStatus vs Gatus](https://uptimepage.dev/compare/openstatus-vs-gatus): OpenStatus brings 28 hosted regions and a Terraform provider; Gatus brings one YAML file and a tiny binary. Where each one fits. July 2026.
- [Blackbox exporter vs Uptime Kuma](https://uptimepage.dev/compare/blackbox-exporter-vs-uptime-kuma): The Blackbox exporter is a probe with no scheduler, no alerts and no dashboard. Uptime Kuma is a finished product. What each really costs. July 2026.
- [Uptime Kuma vs Zabbix](https://uptimepage.dev/compare/uptime-kuma-vs-zabbix): Zabbix watches infrastructure from the inside with agents. Uptime Kuma asks services from the outside. What each takes to run, and where both go blind.
- [Uptime Kuma vs Upptime](https://uptimepage.dev/compare/uptime-kuma-vs-upptime): Uptime Kuma is a container you host. Upptime runs on GitHub Actions with nothing to host. Intervals, status pages, alerting and the limits of each. July 2026.
- [Uptime Kuma vs OneUptime](https://uptimepage.dev/compare/uptime-kuma-vs-oneuptime): Uptime Kuma watches uptime in one container. OneUptime bundles monitoring, status pages, on-call, logs and APM. Scope, weight and team features. July 2026.
- [Uptime Kuma vs Kener](https://uptimepage.dev/compare/uptime-kuma-vs-kener): Uptime Kuma is a monitoring dashboard that can publish a page. Kener is a status page with checks attached. Check types, branding, API, roles. July 2026.
- [Uptime Monitors With Terraform Providers (2026)](https://uptimepage.dev/compare/terraform-providers): Plenty of uptime vendors ship a Terraform provider; far fewer can manage the status page too. Who maintains theirs, and who's a dead fork. Verified July 2026.
- [Terraform Provider for Uptime Kuma](https://uptimepage.dev/compare/terraform-uptime-kuma): Uptime Kuma publishes none of its own. Seven community providers do, one of them is good, and all of them want your admin password. August 2026.
- [Terraform Provider for UptimeRobot](https://uptimepage.dev/compare/terraform-uptimerobot): UptimeRobot maintains its own provider, v1.10.0 in July 2026. Monitors, alert contacts and a public status page in code, and the gap. August 2026.
- [Terraform for Atlassian Statuspage](https://uptimepage.dev/compare/terraform-statuspage): Atlassian ships no Terraform provider for Statuspage. Two community ones exist, the popular one stopped in 2022, and neither creates the page. August 2026.
- [Which Monitors Ship an MCP Server](https://uptimepage.dev/compare/mcp-servers): Which uptime and status-page vendors ship an MCP server, whether it is hosted, whether it uses OAuth, and what it lets an assistant change. July 2026.

## Blog
- [How to debug a redirect loop, one hop at a time](https://uptimepage.dev/blog/how-to-debug-redirect-loops): Trace ERR_TOO_MANY_REDIRECTS with curl and response headers. Find conflicting HTTPS, hostname, and login rules, then monitor the path after fixing it.
- [How to monitor SSL certificate expiry when auto-renewal fails](https://uptimepage.dev/blog/how-to-monitor-ssl-certificate-expiry): Check the certificate your server serves, catch failed renewals before expiry, and set up TLS alerts alongside HTTPS monitoring. Includes OpenSSL checks.
- [Uptime Kuma API: what exists, and what to use instead](https://uptimepage.dev/blog/uptime-kuma-rest-api): Uptime Kuma ships no REST API for managing monitors. Here is every HTTP route it exposes, what the Socket.IO interface really is, and where the wrappers stop.
- [Why DNS returns different IP addresses on different resolvers](https://uptimepage.dev/blog/why-dns-returns-different-ip-addresses): Compare DNS answers from Cloudflare and Google, read TTLs, and query authoritative nameservers to separate normal CDN routing from a broken DNS change.
- [ICMP vs TCP vs UDP: the difference, explained for developers](https://uptimepage.dev/blog/icmp-vs-tcp-vs-udp): What ICMP, TCP and UDP each prove about a host, why a closed port answers differently on each, and where ping and port checks mislead. With RFC links.
- [Your cron job can fail for months and nothing will tell you](https://uptimepage.dev/blog/cron-jobs-fail-silently): A scheduled job that stops running produces no error and no alert. GitLab's nightly backup failed for months before anyone noticed. Why, with sources.
- [How to monitor an MCP server](https://uptimepage.dev/blog/monitor-an-mcp-server): An MCP server can return 200 on every request and still be useless to an agent. Probe the handshake instead, with one HTTP POST and one assertion.
- [8 best Statuspage alternatives in 2026, free and paid](https://uptimepage.dev/blog/statuspage-alternatives): Eight real Atlassian Statuspage alternatives compared honestly: which include the monitoring it leaves out, and which stop charging you per subscriber.
- [What is an uptime SLA? Percentages, credits and fine print](https://uptimepage.dev/blog/uptime-sla): An uptime SLA is a contract promise with a penalty, not a measurement. What each percentage allows, what a credit really pays, and the clauses that decide it.
- [Scheduling in Rust: one heap, not a timer per task](https://uptimepage.dev/blog/rust-scheduler-one-heap): Every check my uptime monitor runs is scheduled from one BinaryHeap on one task. No timers, no locks, no drift. Five things that fell out of building it.
- [How much downtime is 99.9% uptime? 43 minutes a month](https://uptimepage.dev/blog/how-much-downtime-is-99-9-uptime): 99.9% uptime allows 43 minutes of downtime a month and 8 hours 46 minutes a year. What uses that time, and why three nines is the normal SaaS promise.
- [How much downtime is 99.95% uptime? 21.6 minutes a month](https://uptimepage.dev/blog/how-much-downtime-is-99-95-uptime): 99.95% uptime allows 21 minutes 36 seconds of downtime a month and 4 hours 23 minutes a year. Why it is the target behind a 99.9% promise, not the promise.
- [How much downtime is 99.99% uptime? 4.3 minutes a month](https://uptimepage.dev/blog/how-much-downtime-is-99-99-uptime): 99.99% uptime allows 4 minutes 19 seconds of downtime a month and 52 minutes 34 seconds a year. Four nines is a design decision, not a question of effort.
- [Your login page returns 200. Nobody can sign in.](https://uptimepage.dev/blog/monitor-the-login-not-the-login-page): A 200 proves the page was sent. It proves nothing about the form. Four ways a login breaks while every check stays green, and how to tell them apart.
- [Your E2E login test never runs in production](https://uptimepage.dev/blog/your-login-test-never-runs-in-production): Your end to end login test runs in CI, against staging, at merge time. The faults that lock real customers out cannot happen there.
- [How I stop one bad probe from waking you at 3 a.m.](https://uptimepage.dev/blog/stop-false-uptime-alerts): One monitoring location with a bad network day is the classic false alert. Here is how repeat checks plus a region vote keep that alert away from your phone.
- [Your domain can expire while your uptime monitor stays green](https://uptimepage.dev/blog/domain-expired-but-site-still-up): An expired domain does not go dark. It serves a parking page that returns 200 OK, so uptime monitors report it healthy while the site is gone.
- [How I mapped my codebase for humans and AI agents](https://uptimepage.dev/blog/map-your-codebase-for-ai-agents): I turned 146,000 lines of Rust into three files: for me, for the next AI agent, and an interactive map. The method, the prompts, and the AI's wrong counts.
- [Do I need an uptime monitor? Count what downtime costs you](https://uptimepage.dev/blog/do-i-need-an-uptime-monitor): An uptime monitor is cheap. One outage you find out about from a customer is not. How to price your own downtime, and what to watch besides the homepage.
- [How to write incident status updates that build trust](https://uptimepage.dev/blog/how-to-write-incident-status-updates): A guide to writing status page updates during an outage: the four stages, how often to post, and what to say at each one so customers keep trusting you.
- [Why I chose Rust over Go for an uptime monitor](https://uptimepage.dev/blog/choosing-rust-for-an-uptime-monitor): Go is the usual pick for a service like this. I chose Rust for one reason: a monitor sells clean timing, and its own runtime must not add random delay.
- [Is 98% uptime good? It allows 7.3 days of downtime a year](https://uptimepage.dev/blog/is-98-uptime-good): 98% uptime sounds high, but it allows 7.3 days of downtime a year. When 98% is enough, what to aim for instead, and a downtime table for every target.
- [The status page you can't fake: measured uptime, not published](https://uptimepage.dev/blog/status-page-you-cant-fake): Why a status page's uptime bar must come from real checks, not the incidents you chose to publish, and a quick test for any page.
- [8 best Pingdom alternatives in 2026, free and paid](https://uptimepage.dev/blog/pingdom-alternatives): Eight real Pingdom alternatives compared honestly: which replaces uptime checks, which replaces synthetics and RUM, and which ends usage-based pricing.
- [Error budgets, explained: SLOs, burn rate, when to stop shipping](https://uptimepage.dev/blog/error-budgets-explained): What an error budget is, the simple formula, how burn rate becomes an alert, and the rule that makes it work. With a free calculator.
- [ClickHouse disk full: system tables ate 12 GB (the fix)](https://uptimepage.dev/blog/clickhouse-system-tables-filled-disk): Disk at 100%, Postgres down with 'no space left on device'. Real data: 20 MB; ClickHouse had logged 12 GB about itself. The config that fixes it, for good.
- [Postgres vs ClickHouse is the wrong question. I use both.](https://uptimepage.dev/blog/postgres-vs-clickhouse-uptime-monitor): My uptime monitor runs Postgres and ClickHouse side by side. Which data goes where comes down to one question, and four database tricks fall out of it.
- [Why I dropped reqwest for hyper in my Rust uptime prober](https://uptimepage.dev/blog/http-prober-in-rust-no-reqwest): I swapped reqwest for raw hyper to probe uptime in Rust. Four things it taught me, each one a detail a normal HTTP client hides from you.
- [Email bombing through uptime monitoring pages](https://uptimepage.dev/blog/email-bombing-uptime-pages): Attackers flood an inbox to bury one real alert, like bank fraud. How subscription bombing works, and how to build a monitor that can't be abused.
- [Building an uptime monitor in Rust: one binary, two databases](https://uptimepage.dev/blog/building-an-uptime-monitor-in-rust): The Rust build behind Uptimepage: a custom hyper client doing ~130K checks a second on one core, a single-heap scheduler, and ClickHouse rollups.
- [Best open-source, self-hosted uptime monitors (2026)](https://uptimepage.dev/blog/best-self-hosted-uptime-monitoring-tools): A fair look at the open-source, self-hostable tools for watching sites and APIs in 2026: what each is good at, where it stops, and how to pick one.
- [The night Emma stopped opening dashboards](https://uptimepage.dev/blog/ask-dont-click): A 2 a.m. alert, and an on-call engineer who never opened a tab. A short story about asking your monitoring questions instead of clicking through it.
- [The mystery of the "down" website](https://uptimepage.dev/blog/osi-layers): "The site is down!" But what does "down" really mean? A detective story through the seven network layers, and the one quiet failure no alarm caught.
- [Monitoring as code: put your uptime checks in a pull request](https://uptimepage.dev/blog/monitoring-as-code): Click-created monitors rot: nobody recalls why a threshold is set, and the reasoning leaves with its author. Terraform fixes that, and bites back in places.
- [Your monitors can talk to an AI, with your permission](https://uptimepage.dev/blog/mcp-server): Uptimepage now speaks MCP, so an LLM can answer "what's broken and since when?" in plain language, plus what we did to stop it from wrecking things.
- [Why your uptime monitor should be boring](https://uptimepage.dev/blog/boring-uptime): A monitor that surprises you is doing the wrong job. What changes when you treat the watchdog like a smoke detector: cheap, dumb, unmissable when it matters.

## Documentation
Index: https://uptimepage.dev/docs
- [Getting started](https://uptimepage.dev/docs/getting-started): Sign in with GitHub or Google, add your first monitor, pick an interval and regions, route an alert to Slack or email, and publish a status page in ten minutes.
- [Overview](https://uptimepage.dev/docs/overview): What uptimepage is: one Rust binary that runs uptime checks, keeps config in Postgres and results in ClickHouse, and serves the app, the API and status pages.
- [Architecture](https://uptimepage.dev/docs/architecture): How a check and a request move through uptimepage: scheduler, executor, ingest, the Postgres and ClickHouse stores, probe agents, and the invariants each keeps.
- [Web UI](https://uptimepage.dev/docs/ui): A tour of the app: the dashboard cards and monitor table, the monitor detail view with its charts and timeline, incidents, settings, and sharing one monitor.
- [Incident management](https://uptimepage.dev/docs/incidents): How a run of failing checks becomes a tracked incident: acknowledgement, ownership, on-call, escalation, public updates, and the retrospective that closes it.
- [Monitor types](https://uptimepage.dev/docs/monitor-types): The eight check kinds, HTTP, TCP, ping, heartbeat, DNS, TLS certificate, domain expiry and browser flow, what each one really proves, and which to reach for.
- [Notifications](https://uptimepage.dev/docs/notifications): Alert channels for Slack, email, webhooks, PagerDuty, Telegram and more, how a monitor binds the ones that should hear about it, and what decides when it fires.
- [Public status page](https://uptimepage.dev/docs/public-status): The customer-facing surface: components and their uptime, incident updates, scheduled maintenance, subscribers, badges, and the public JSON and RSS endpoints.
- [Per-org status pages](https://uptimepage.dev/docs/per-org-status): Running one or more branded status pages per organization, each on its own subdomain, showing only the monitors, incidents and maintenance you curate onto it.
- [Share links](https://uptimepage.dev/docs/share-links): Read-only capability URLs that open one monitor's full dashboard, with status, uptime, latency charts and incident history, for anyone you send the link to.
- [Team](https://uptimepage.dev/docs/team): Organizations, the member and owner roles and what each can do, inviting people by email, seats, and what happens to their work when someone leaves the org.
- [Organizations](https://uptimepage.dev/docs/organizations): Running more than one organization: when a second is worth it, switching between them, what changing a slug breaks, and the 30-day window to undo a delete.
- [Variables and secrets](https://uptimepage.dev/docs/variables): Reusable org-scoped values and write-only secrets, referenced in a monitor's HTTP request fields, so a credential lives in one place instead of every monitor.
- [Authentication](https://uptimepage.dev/docs/authentication): OAuth sign-in, passkeys, magic links and the code beside them, managing the sign-in methods that open an account, and org-bound API tokens with scoped access.
- [REST API](https://uptimepage.dev/docs/api): The /api/v1 surface: monitors, incidents, notification channels, status pages and the public endpoints, with the OpenAPI document and token authentication.
- [Terraform](https://uptimepage.dev/docs/terraform): Managing monitors, notification channels and status pages as code with the uptimepage Terraform provider, from install and credentials to a first apply.
- [MCP server](https://uptimepage.dev/docs/mcp): Let an LLM client answer questions about one organization and take guarded actions over the Model Context Protocol, with scopes, confirmations and audit.
- [Quotas and rate limits](https://uptimepage.dev/docs/quotas): How a plan bounds resources and per-minute request budgets, where each limit is enforced, and what an API client sees when it reaches the ceiling on either one.
- [Multi-tenancy](https://uptimepage.dev/docs/multi-tenancy): The org model, how the active org is resolved from the authenticated session, and how tenant isolation is enforced in every query rather than by convention.
- [Plans and limits](https://uptimepage.dev/docs/hosted/plans-and-limits): The quotas and rate budgets each hosted plan carries, how the Standard and Founding tiers differ, and what happens when an organization reaches a ceiling.
- [Probe regions](https://uptimepage.dev/docs/hosted/regions): Where the hosted service checks from, how to pick regions for a monitor, how agreement between regions confirms an outage, and what our probes cannot reach.
- [Data retention](https://uptimepage.dev/docs/hosted/data-retention): How long raw check results, rollups, incidents and audit records are kept on the hosted service, and which layer a chart reads for the range you asked for.
- [Support](https://uptimepage.dev/docs/hosted/support): How to reach us about an account, a security report, a bug or a feature request, what to include so we can help, and where the hosted service stands on SLAs.
- [Configuration](https://uptimepage.dev/docs/configuration): Every configuration key, its default, and the environment variable that overrides it, across the server, storage, scheduler, alerting and status page sections.
- [Deployment](https://uptimepage.dev/docs/deployment): Running the production stack behind Caddy: automatic TLS, the auth boundary, the public status surface, outbound email, database backups, and the upgrade path.
- [Kubernetes](https://uptimepage.dev/docs/kubernetes): Installing the Helm charts for the control plane and for standalone probe agents: external databases, ingress timeouts, ICMP permissions and cluster versions.
- [Multi-region probes](https://uptimepage.dev/docs/multi-region): Running probe agents in more than one region, how an agent pulls its config and ships results back, and the operator surface that manages regions and keys.
- [Metrics and tracing](https://uptimepage.dev/docs/metrics): The Prometheus series the service exposes, what each one measures and the labels it carries, and how to ship traces off the box to an OpenTelemetry collector.
- [Troubleshooting](https://uptimepage.dev/docs/troubleshooting): Symptoms you are likely to hit while operating an instance, from a failing readiness probe to missing metrics and checks that never run, and what each means.
- [Development](https://uptimepage.dev/docs/development): Local setup for working on the service itself: the toolchain, Postgres and ClickHouse containers, everyday workflows, and the test gates a change has to pass.
- [Benchmarks](https://uptimepage.dev/docs/benchmarks): Criterion micro-benchmarks measuring the cost of a single check through the same production HTTP path, how to run them, and how to read the numbers they print.
- [Load test](https://uptimepage.dev/docs/loadtest): The end-to-end harness that drives the real check executor against in-process mock servers, how to run it, and what its throughput and latency output tells you.

## Tools
All free tools: https://uptimepage.dev/tools
- [Uptime SLA & Downtime Calculator](https://uptimepage.dev/tools/uptime-sla-calculator): Turn an uptime percentage into allowed downtime per day, week, month and year. A free SLA and SLO calculator with the full nines reference table.
- [Cron Expression Generator & Parser](https://uptimepage.dev/tools/cron-expression-generator): Build and read cron expressions in plain English, with the next run times and a reference table of the most common schedules. Free, no sign-up.
- [Error Budget & Burn Rate Calculator](https://uptimepage.dev/tools/error-budget-calculator): Turn an SLO target and your measured availability into error budget spent, budget left and burn rate, with a burn-rate reference table. Free, no sign-up.
- [Incident Update Message Generator](https://uptimepage.dev/tools/incident-update-generator): Write clear investigating, identified, monitoring, resolved and maintenance messages for your status page. Free, private and generated in your browser.
- [DNS Lookup: Compare Two Resolvers Side by Side](https://uptimepage.dev/tools/dns-lookup): Check A, MX, NS, TXT and CAA records against Cloudflare and Google at once and see where they disagree. Free, no sign-up, runs in your browser.
- [HTTP Header & Redirect Chain Checker](https://uptimepage.dev/tools/http-header-checker): See every redirect hop, the final status code and the response headers a URL returns, the way an uptime monitor sees them. Free, no sign-up.
- [SSL Certificate Checker: Expiry and Chain](https://uptimepage.dev/tools/ssl-certificate-checker): Read any public host's TLS certificate: days until expiry, who issued it, which names it covers and whether the chain is complete. Free, no sign-up.
- [Domain Expiry Checker: Date and Registrar](https://uptimepage.dev/tools/domain-expiry-checker): Check a domain's registration expiry date, days remaining and registrar using public RDAP data. Free, no sign-up. Set up monitoring before renewal is due.

## Developers & automation
- [MCP server](https://mcp.uptimepage.dev/mcp): Connect an LLM client (Claude, IDEs) to read monitors and incidents and take fenced actions. OAuth one-click.
- [Terraform provider](https://registry.terraform.io/providers/uptimepage/uptimepage): Manage monitors, status pages and notification channels as config-as-code.

## Optional
- [Full text](https://uptimepage.dev/llms-full.txt): Every marketing page and blog post inlined.
- [Terms of Service](https://uptimepage.dev/terms)
- [Privacy Policy](https://uptimepage.dev/privacy)
- [Cookie Policy](https://uptimepage.dev/cookies)
- [Impressum](https://uptimepage.dev/impressum)
- [Abuse Policy](https://uptimepage.dev/abuse-policy)
- [Security Policy](https://uptimepage.dev/security-policy)
- [Uptimepage Bot](https://uptimepage.dev/bot)