---
title: "Uptime monitoring guides and how-tos · Fettle"
description: "Uptime monitoring how-tos: AI agents over MCP, multi-region consensus, API health checks, alerts, maintenance windows, TCP and DNS, uptime math."
url: "https://fettle.sh/guides"
---

/ guides

# Uptime monitoring guides and how-tos.

How checks, regions, alerts and maintenance work, and how to set each one up.

Each guide takes one technique and explains it down to the settings: what the check proves, where it misleads, and which Fettle options change the outcome. For a single platform or kind of job, the [use cases](https://fettle.sh/use-cases) go straight to the setup.

[Start here](https://fettle.sh/uptime-monitoring)

## [What is uptime monitoring? A developer's guide](https://fettle.sh/uptime-monitoring)

[Uptime monitoring checks your sites, APIs and jobs from outside on a schedule and alerts you when they stop answering. How checks, regions and alerts work.](https://fettle.sh/uptime-monitoring)

## [Set up uptime monitoring from Claude Code or Codex](https://fettle.sh/guides/uptime-monitoring-with-ai-agents)

[Connect Claude Code or Codex to Fettle over MCP, then let the agent create monitors and heartbeats, silence a deploy and triage an outage in the terminal.](https://fettle.sh/guides/uptime-monitoring-with-ai-agents)

## [Multi-region uptime checks: how regional consensus stops false alerts](https://fettle.sh/guides/multi-region-monitoring)

[How multi-region uptime monitoring decides a site is down: why Fettle needs every fresh region to agree, what a partial failure shows, and the trade-off.](https://fettle.sh/guides/multi-region-monitoring)

## [API health check monitoring: design a /health endpoint worth watching](https://fettle.sh/guides/api-health-check-monitoring)

[How to design an API health check endpoint worth monitoring, from shallow vs deep checks to status codes, then watch it with status and keyword checks.](https://fettle.sh/guides/api-health-check-monitoring)

## [Uptime alerts in Slack, Discord or a webhook](https://fettle.sh/guides/uptime-alerts-slack-discord-webhook)

[Send downtime alerts to Slack, Discord, Telegram or your own signed webhook: what triggers an alert, what stays quiet, and how repeats and recovery work.](https://fettle.sh/guides/uptime-alerts-slack-discord-webhook)

## [Maintenance windows: silence alerts, keep checking](https://fettle.sh/guides/maintenance-windows)

[How maintenance windows stop deploy alerts while checks keep running: one-off or recurring, timezones, uptime, and opening one from CI or an agent.](https://fettle.sh/guides/maintenance-windows)

## [TCP port and DNS monitoring: checks below HTTP](https://fettle.sh/guides/tcp-port-and-dns-monitoring)

[Watch databases, mail servers and SSH with TCP port checks, catch a database port left open to the internet, and alert when a DNS record changes.](https://fettle.sh/guides/tcp-port-and-dns-monitoring)

## [How to monitor an MCP server](https://fettle.sh/guides/monitor-mcp-server)

[Check a remote MCP server with an HTTP POST that sends a real JSON-RPC request, and a local stdio server with a heartbeat behind a scheduled smoke test.](https://fettle.sh/guides/monitor-mcp-server)

## [What 99.9% uptime actually allows](https://fettle.sh/guides/what-does-99-9-uptime-mean)

[99.9% uptime allows 43m 12s of downtime in a 30-day month. Budgets for every common target, and why your check interval limits what you can measure.](https://fettle.sh/guides/what-does-99-9-uptime-mean)