# Upcertain

> Uptime monitoring for small teams and agencies: HTTP, keyword, ping, port, SSL certificate and heartbeat monitors as often as every 30 seconds, failures confirmed by re-checks before an incident opens, alerts to email, Slack, Discord, Microsoft Teams, Google Chat and signed webhooks, status pages on your own domain, a REST API and an MCP server for AI agents.

Upcertain is in early access: billing is not enabled, plans are assigned from the account settings, and prices are shown as "Early access". Checks run from one region (Seoul, AWS ap-northeast-2). It does not offer multi-region checks, browser or synthetic checks, DNS monitors, SMS or phone alerts, or on-call schedules.

Plans:
- Basic: 10 monitors, checks every 1 min at the fastest, 1 status page, owner only.
- Team: 100 monitors, checks every 30 s at the fastest, unlimited status pages, unlimited team members, custom domains, MCP access.
- Business: custom limits set per account.

## Product
- [Home](https://upcertain.com/): What Upcertain does: six monitor types, confirmed incidents, alert channels, status pages, REST API and MCP.
- [Pricing](https://upcertain.com/pricing): Plans and their limits (monitors, fastest interval, status pages, seats) and the plan FAQ.
- [Changelog](https://upcertain.com/changelog): Dated list of user-facing changes to Upcertain.
- [Upcertain status](https://upcertain.com/s/upcertain): Upcertain's own public status page, an example of the product's status pages.

## Developers
- [MCP server docs](https://upcertain.com/mcp): How to connect Claude, Cursor or another MCP client to https://upcertain.com/api/mcp, the tools it offers, example prompts and the REST API.
- [Upcertain for AI assistants](https://upcertain.com/ai-info): Factual summary for assistants: capabilities, plans, limits and when Upcertain is the wrong choice.
- MCP server endpoint: https://upcertain.com/api/mcp (streamable HTTP; OAuth 2.1 sign-in or an API key; read-only by default).
- REST API base: https://upcertain.com/api/v1 (account, monitors, incidents, maintenance, status pages; bearer API keys created by owners and admins).
- [Full text for assistants](https://upcertain.com/llms-full.txt): this summary, the answers to common questions and the full text of every guide and doc.

## Features
- [Features](https://upcertain.com/features): What Upcertain monitors and how: HTTP, keyword, ping, port, SSL and heartbeat checks, confirmed incidents, alerts and status pages on your domain.
- [Status pages on your own domain](https://upcertain.com/features/status-pages): Public, private or password-protected status pages that update from your monitors, show each service's downtime and run on your own domain.
- [Website and API uptime monitoring](https://upcertain.com/features/uptime-monitoring): Check websites and APIs as often as every 30 seconds with HTTP and keyword monitors, re-check before an incident opens, and alert the team that owns it.
- [Heartbeat monitoring for cron jobs and workers](https://upcertain.com/features/heartbeat-monitoring): Know when a cron job, queue worker or backup stops running. Your job calls a unique URL on schedule; Upcertain alerts when the calls stop arriving.
- [Incidents: one record from first failure to recovery](https://upcertain.com/features/incidents): Every confirmed outage becomes an incident with its cause, the failed request, a timeline, acknowledgement, team notes and status page updates.
- [Keyword monitoring for pages that fail quietly](https://upcertain.com/features/keyword-monitoring): Catch pages that return 200 but show an error, an empty list or a maintenance notice: keyword monitors check that a phrase is, or is not, on the page.
- [Ping and port monitoring for servers and services](https://upcertain.com/features/ping-and-port-monitoring): Watch servers, mail servers, databases and game servers with ping and TCP port monitors, with a TCP fallback when ICMP is blocked by a firewall.
- [SSL certificate monitoring and expiry alerts](https://upcertain.com/features/ssl-monitoring): Get warned before a TLS certificate expires and alerted when one is invalid: expiry, hostname and chain checks, with warnings on the days you choose.

## Alert channels
- [Alert channels](https://upcertain.com/channels): Send Upcertain downtime, recovery and SSL alerts to email, Slack, Discord, Microsoft Teams, Google Chat or your own signed webhooks.
- [Slack uptime alerts](https://upcertain.com/channels/slack): Post Upcertain down, recovery and SSL alerts to a Slack channel through an incoming webhook, with acknowledge and incident links in each message.
- [Discord downtime alerts](https://upcertain.com/channels/discord): Get Upcertain uptime, recovery and SSL expiry alerts in a Discord channel through a channel webhook. Useful for small teams and communities.
- [Email downtime alerts](https://upcertain.com/channels/email): Upcertain email alerts: one message per recipient with a personal stop link, acknowledge buttons for people who can act, and weekly or monthly reports.
- [Google Chat uptime alerts](https://upcertain.com/channels/google-chat): Send Upcertain down, recovery and SSL expiry alerts into a Google Chat space with an incoming webhook, set up in a couple of minutes.
- [Microsoft Teams uptime alerts](https://upcertain.com/channels/microsoft-teams): Post Upcertain downtime, recovery and SSL alerts to a Microsoft Teams channel through a Workflows webhook, with links to acknowledge each incident.
- [Signed webhooks for down, recovery and SSL events](https://upcertain.com/channels/webhooks): Receive Upcertain alerts as signed JSON in your own system: event types, the payload, the headers and how to verify the HMAC-SHA256 signature.

## Documentation
- [Documentation](https://upcertain.com/docs): How to set up Upcertain: heartbeat monitors, status pages on a custom domain, password protection, and connecting AI agents over MCP.
- [Put a status page on your own domain](https://upcertain.com/docs/status-pages/custom-domain): Serve an Upcertain status page at status.yourcompany.com: add the CNAME, verify it, and get an HTTPS certificate issued automatically.
- [Set up a heartbeat monitor for a cron job](https://upcertain.com/docs/monitors/heartbeat): Create a heartbeat monitor and call its URL from cron, Node.js, Python, PHP, Laravel or GitHub Actions, so you hear when a scheduled job stops.
- [Add a status badge to your README or website](https://upcertain.com/docs/status-pages/badge): Show a status page's live state as a small badge in a GitHub README, documentation or your website, with copy-ready Markdown, HTML and embed code.
- [Connect Upcertain to Claude](https://upcertain.com/docs/mcp/claude): Add Upcertain as a custom connector in Claude on the web or desktop, sign in, choose read-only or read-write, and ask Claude about monitors and incidents.
- [Email subscribers on a status page](https://upcertain.com/docs/status-pages/subscribers): Let visitors subscribe to a status page by email, confirm with one button, and receive every announcement you publish with a one-click unsubscribe.
- [HTTP monitors: options and status codes](https://upcertain.com/docs/monitors/http): Every option of an Upcertain HTTP monitor: method, headers, body, authentication, expected status codes, timeout, redirects and certificate checks.
- [Import monitors from a CSV file](https://upcertain.com/docs/monitors/import-csv): Create many monitors at once from a CSV file or a list of URLs: the columns Upcertain reads, the preview, plan limits and how groups are created.
- [Keyword monitors: check what a page says](https://upcertain.com/docs/monitors/keyword): Set up a keyword monitor that fails when a word is missing from a page, or when an error message appears, with case-sensitive matching if you need it.
- [Password-protected and private status pages](https://upcertain.com/docs/status-pages/password-protection): Share a status page with customers or staff only: protect it with a password, or make it private to signed-in members of your account.
- [Ping monitors: check that a host is reachable](https://upcertain.com/docs/monitors/ping): How Upcertain's ping monitor checks a server with ICMP, falls back to TCP on ports 443 and 80, and when to use a port or HTTP monitor instead.
- [Port monitors: check a TCP service](https://upcertain.com/docs/monitors/port): Monitor any TCP service, such as SMTP, PostgreSQL, Redis or SSH, by opening a connection to its port on a schedule and alerting when it stops answering.
- [REST API reference](https://upcertain.com/docs/api): Upcertain's REST API: authentication with API keys, endpoints for monitors, uptime, incidents, maintenance and status pages, errors and rate limits.
- [Schedule maintenance windows](https://upcertain.com/docs/status-pages/maintenance): Schedule one-off or recurring maintenance so planned work does not alert anyone or count against uptime, and show it on your status pages ahead of time.
- [SSL certificate monitors and expiry warnings](https://upcertain.com/docs/monitors/ssl): Set up an SSL certificate monitor, choose the days you are warned before expiry, and route the warnings to the person who renews certificates.
- [Team roles and the audit log](https://upcertain.com/docs/team-roles): What owners, admins, editors, viewers and notify-only contacts can do in Upcertain, how invitations work, and what the audit log records.
- [Use Upcertain from Claude Code](https://upcertain.com/docs/mcp/claude-code): Add Upcertain's MCP server to Claude Code with one command, sign in from the terminal, and check monitors and incidents while you work.
- [Use Upcertain in Cursor](https://upcertain.com/docs/mcp/cursor): Connect Cursor to Upcertain's MCP server through mcp.json, sign in or use an API key, and ask about monitors and incidents from the editor.
- [Working with incidents](https://upcertain.com/docs/incidents): How incidents open and resolve in Upcertain, how to acknowledge one, add notes, post a status update, read the failed request, and export history as CSV.

## Uptime monitoring guides
- [Uptime monitoring guides](https://upcertain.com/learn): Plain guides to uptime monitoring: confirmation checks, check intervals, false alarms during deploys, heartbeat monitoring and what 99.9% uptime allows.
- [Confirmation checks: how to stop false downtime alerts](https://upcertain.com/learn/confirmation-checks): Why one failed check should not wake anyone, how re-checks before an incident work, and how to choose the number of checks and the time between them.
- [Cron job monitoring: catching jobs that silently stop](https://upcertain.com/learn/cron-job-monitoring): Why cron jobs fail without anyone noticing, the ways to monitor them, and how heartbeat monitoring alerts you when a scheduled job does not run.
- [Dead man's switch monitoring for scheduled jobs](https://upcertain.com/learn/dead-mans-switch-monitoring): How dead man's switch (heartbeat) monitoring catches cron jobs, backups and workers that silently stop, and how to choose the period and grace time.
- [Downtime alerts during deploys: why they happen and how to stop them](https://upcertain.com/learn/deploy-false-alarms): Rolling restarts and deploys often return 502 or 503 for a minute. How to stop those responses from paging your team without missing real outages.
- [How often should you check uptime? 30 seconds, 1 minute or 5 minutes](https://upcertain.com/learn/check-interval): What a 30-second, 1-minute or 5-minute check interval means for how fast you hear about an outage and which short outages you miss entirely.
- [How to check if a website is down, for everyone or just you](https://upcertain.com/learn/how-to-check-if-a-website-is-down): Quick ways to tell whether a website is down for everyone or only for you, with the commands to run, and why a one-off check is not monitoring.
- [How to create a status page customers will trust](https://upcertain.com/learn/how-to-create-a-status-page): A practical guide to building a status page: what to show, how to name services, where to host it, how to write updates, and what to do during an outage.
- [How to monitor website uptime, step by step](https://upcertain.com/learn/how-to-monitor-website-uptime): A step-by-step setup for website uptime monitoring: what to check, how often, how to avoid false alarms, where alerts go, and how to tell customers.
- [How to monitor your MCP server's uptime](https://upcertain.com/learn/monitor-mcp-server-uptime): Your MCP server is now part of your product. How to monitor a remote MCP endpoint, why to expect a 401, and what to watch besides the endpoint itself.
- [Incident response for small teams](https://upcertain.com/learn/incident-response-small-teams): A lightweight incident process for teams without an on-call rotation: who responds, how to acknowledge, what to tell customers and how to learn from it.
- [Monitoring from one region: what checks from Seoul mean for you](https://upcertain.com/learn/monitoring-from-seoul): Upcertain checks from Seoul. What single-region monitoring catches, what it can miss, how distance affects response times, and when it suits Asia-Pacific teams.
- [SSL certificate expiry: why it still causes outages](https://upcertain.com/learn/ssl-expiry-monitoring): Automated renewal did not end expired-certificate outages. Why renewals fail, how far ahead to be warned, and what to check besides the expiry date.
- [Uptime monitoring pricing compared: what you pay for](https://upcertain.com/learn/uptime-monitoring-pricing-compared): How uptime monitoring tools price their plans: per monitor, per seat, per site or by tier, with entry plans and add-ons from their own pricing pages.
- [What 99.9% uptime means in minutes](https://upcertain.com/learn/what-does-99-9-uptime-mean): 99.9% uptime allows 43 minutes of downtime a month and about 8 hours 46 minutes a year. A table for 99% to 99.999%, and what the numbers leave out.
- [What is uptime monitoring?](https://upcertain.com/learn/what-is-uptime-monitoring): Uptime monitoring checks your websites, APIs and servers on a schedule and alerts you when they stop working. How it works, what it catches and what it misses.

## Upcertain compared
- [Upcertain compared](https://upcertain.com/compare): Factual comparisons of Upcertain with other uptime monitoring and status page tools, with the sources each fact was read from.
- [Upcertain and Better Stack compared](https://upcertain.com/compare/better-stack): How Upcertain compares with Better Stack for uptime monitoring and status pages: what each includes, where Better Stack does more, and who each suits.
- [Upcertain and UptimeRobot compared](https://upcertain.com/compare/uptimerobot): How Upcertain compares with UptimeRobot on check intervals, seats, status pages, alerts and AI access, with UptimeRobot's figures from its pricing page.
- [Freshping has shut down: moving your monitors](https://upcertain.com/compare/freshping): Freshworks retired Freshping in March 2026. How to rebuild your monitors, alerts and status page elsewhere, with a CSV import into Upcertain.
- [Upcertain and Atlassian Statuspage compared](https://upcertain.com/compare/statuspage): Atlassian Statuspage is a status communication tool priced by subscribers and team members. How it compares with Upcertain's monitoring-driven status pages.
- [Upcertain and Cronitor compared](https://upcertain.com/compare/cronitor): Cronitor prices per monitor and per user, with cron monitoring at its core. How it compares with Upcertain's heartbeat and uptime monitoring.
- [Upcertain and Dead Man's Snitch compared](https://upcertain.com/compare/dead-mans-snitch): Dead Man's Snitch watches cron jobs with "snitches" on simple plans. How it compares with Upcertain's heartbeats, uptime checks and status pages.
- [Upcertain and Healthchecks.io compared](https://upcertain.com/compare/healthchecks-io): Healthchecks.io is a focused cron job monitor with a generous free tier. How it compares with Upcertain, which pairs heartbeats with uptime checks.
- [Upcertain and HetrixTools compared](https://upcertain.com/compare/hetrixtools): HetrixTools offers uptime and blacklist monitoring with a free tier and checks from 12 locations. How it compares with Upcertain.
- [Upcertain and Hyperping compared](https://upcertain.com/compare/hyperping): Upcertain and Hyperping side by side: monitors, seats, status pages, on-call and browser checks, with Hyperping's figures from its pricing page.
- [Upcertain and Instatus compared](https://upcertain.com/compare/instatus): Instatus starts from the status page; Upcertain starts from monitoring. How they compare on monitors, checks, subscribers, domains and team members.
- [Upcertain and Oh Dear compared](https://upcertain.com/compare/oh-dear): Oh Dear prices by the number of sites with every feature on every plan. How it compares with Upcertain on checks, verification, status pages and pricing.
- [Upcertain and OpenStatus compared](https://upcertain.com/compare/openstatus): OpenStatus offers status pages and multi-region uptime monitoring with a free plan. How it compares with Upcertain on checks, regions, pages and plans.
- [Upcertain and Pingdom compared](https://upcertain.com/compare/pingdom): Pingdom, part of SolarWinds, offers uptime, transaction and real user monitoring for larger sites. How it compares with Upcertain for smaller teams.
- [Upcertain and Pulsetic compared](https://upcertain.com/compare/pulsetic): Pulsetic offers uptime, cron and status page monitoring with regional checks and a free plan. How its plans compare with Upcertain's.
- [Upcertain and Site24x7 compared](https://upcertain.com/compare/site24x7): Site24x7 is a full monitoring suite from Zoho with a free plan and trial. How its website monitoring compares with Upcertain's focused uptime service.
- [Upcertain and StatusCake compared](https://upcertain.com/compare/statuscake): Upcertain and StatusCake side by side: monitors and intervals per plan, team members, page speed and domain checks, alert channels and status pages.
- [Upcertain and Uptime.com compared](https://upcertain.com/compare/uptime-com): Uptime.com covers many check types from a global probe network. How it compares with Upcertain on checks, locations, alerts, users and status pages.
- [Upptime or a hosted monitor: how to choose](https://upcertain.com/compare/upptime): Upptime runs uptime checks and a status page on GitHub Actions, Issues and Pages. When that is enough, and when a hosted monitor fits better.
- [Uptime Kuma or a hosted monitor: how to choose](https://upcertain.com/compare/uptime-kuma): Uptime Kuma is a capable self-hosted monitor. What running it yourself involves, where it does more than Upcertain, and when hosted monitoring fits better.

## Upcertain for your kind of team
- [Upcertain for your kind of team](https://upcertain.com/for): How agencies, SaaS teams and makers of side projects use Upcertain: what to monitor, how to route alerts and how to run a status page.
- [Uptime monitoring for agencies](https://upcertain.com/for/agencies): Monitor every client's sites in one place, alert the right people per client, and give each client a status page of their own on their domain.
- [Uptime monitoring for SaaS teams](https://upcertain.com/for/saas): Monitor the app, API, sign-in and background jobs of a SaaS product, alert the team that owns each service, and keep customers informed on a status page.
- [Uptime monitoring for Shopify stores](https://upcertain.com/for/shopify): Shopify runs the platform, but your theme, apps and integrations can still break the store. What to monitor and how to hear about it first.
- [Uptime monitoring for side projects](https://upcertain.com/for/side-projects): Keep an eye on a side project without a pager: check the site and its jobs, get alerts where you already are, and show a status page to your users.
- [Uptime monitoring for WordPress sites, without a plugin](https://upcertain.com/for/wordpress): Monitor a WordPress site from outside: catch the critical error page, plugin breakage, an expired certificate and WP-Cron that stopped running.
- [Website monitoring for small businesses](https://upcertain.com/for/small-business): Know when your business website, booking form or online shop stops working, without being technical: what to monitor, who should hear, and what to do.

## Blog
- [Blog](https://upcertain.com/blog): Notes from the team that builds Upcertain: how we decide a site is down, what we show on status pages, and connecting AI agents to monitoring.
- [How Upcertain decides a site is down](https://upcertain.com/blog/how-we-decide-a-site-is-down): From a failed request to an alert in Slack: the checks, re-checks and rules Upcertain uses before it calls something an outage, and why.
- [Brief outages on status pages: why we fold them and show each service's downtime](https://upcertain.com/blog/brief-outages-on-status-pages): Why Upcertain status pages group simultaneous incidents, show each service's own downtime and fold short blips into one line a day without hiding them.
- [Ask Claude what's down: connecting your uptime monitors over MCP](https://upcertain.com/blog/ask-claude-whats-down): Connect Upcertain's MCP server to Claude and Claude Code, then ask about outages, uptime and incidents in plain language. Setup, prompts and safeguards.
- [Freshping shut down in 2026. What to look for in the next monitor](https://upcertain.com/blog/freshping-shutdown-what-next): Freshping's free monitoring ended in March 2026. A checklist for choosing what comes next, from check intervals to status pages, and how to move quickly.
- [Monitoring a Next.js app on Vercel: health route, keyword check and cron heartbeats](https://upcertain.com/blog/monitor-nextjs-on-vercel): A worked setup for a Next.js app on Vercel: a health route that checks the database, keyword and SSL monitoring, and heartbeats for Vercel cron jobs.
- [Monitoring a Supabase-backed app: what to check and how](https://upcertain.com/blog/monitor-supabase-app): How to monitor an app built on Supabase: a health check through your own API, a port check on the connection pooler and heartbeats sent from pg_cron.
- [Heartbeats for systemd timers, Kubernetes CronJobs and queue workers](https://upcertain.com/blog/heartbeats-for-systemd-kubernetes-and-workers): Patterns for adding heartbeat monitoring to systemd timers, Kubernetes CronJobs, Windows Task Scheduler and long-running queue workers.
- [Slack alert fatigue: how to keep an alert channel worth reading](https://upcertain.com/blog/slack-alert-fatigue): Why alert channels turn into noise and the settings that fix it: confirmation, one message per incident, recovery in place, routing by owner and grouping.
- [An error budget for small teams: spending your 43 minutes a month](https://upcertain.com/blog/error-budget-for-small-teams): Turn an uptime target into a monthly downtime budget, see what deploys, incidents and maintenance spend from it, and decide when to slow down.
- [Incident communication templates for small teams](https://upcertain.com/blog/incident-communication-templates): Copy-ready status page updates for investigating, identified, monitoring and resolved incidents, plus maintenance notices and a short post-incident note.
- [Status 200, still broken: catching silent failures with keyword checks](https://upcertain.com/blog/keyword-monitoring-silent-failures): Pages that return 200 while broken are the outages status-code checks miss. Common patterns, the keyword to use for each, and how to keep the checks honest.

## Tools
- [Uptime and downtime calculator](https://upcertain.com/tools/uptime-calculator): Calculator: uptime percentage to allowed downtime per period, and downtime back to uptime.

## Optional
- [Contact](https://upcertain.com/contact): Contact form for Business plans, onboarding and support.
- [Privacy policy](https://upcertain.com/privacy): What Upcertain collects, where it is stored (Seoul) and for how long.
- [Terms of service](https://upcertain.com/terms): Terms of service during early access.
- Support: upcertain-support@innovation-insight.com