
See every monitor live
One screen. Probe regions, AI-diagnosed incidents, latency charts, and a timeline your agent can read.
Probe sites. Dispatch incidents. Orchestrate AI agents that close the loop — before a human is paged.
Instant audit. No account required.
Three primitives, one loop. Every monitored site flows through them every minute.
16 sensors, every minute, from 8 regions. SSL, DNS, DNSSEC, CSP, HTTP, page weight, Core Web Vitals, and 9 more.
Vertex AI reads the payload, identifies the root cause, drafts a remediation prompt and exposes it via the upmonitor:// protocol.
MCP server hands the incident to Claude Code, Cursor, Continue, or Cline. The agent fixes it. You wake up to a closed ticket.
Every monitor, every check, every incident. Status pills update live. The dashboard mirrors what your AI agent reads through MCP.

One screen. Probe regions, AI-diagnosed incidents, latency charts, and a timeline your agent can read.
90 / 60 / 30 / 14-day expiry alerts. Chain-of-trust validation per region.
Full DS / DNSKEY / RRSIG validation. Catches drift before the .io zone breaks resolution.
Built-in. Your agent reads incidents directly — no glue code, no scraping dashboards.
Core Web Vitals enriched with font self-hosting, TTFB DNA, and AI-readable JSON output.
$ upmonitor monitor add upmonitor.io → reading config from .upmonitor.yml ✓ probe deployed to us-central1 ✓ probe deployed to europe-west1 ✓ probe deployed to asia-northeast1 ⚡ dispatched to MCP server
The Diagnostic Inbox is your single triage surface. Filter by sensor or by probe. Acknowledge what's owned. Resolve what's fixed. Hand the AI a pre-built prompt for what's still smoking.
Open the Inbox →

The UpMonitor CLI ships on npm. The Model Context Protocol server runs locally. Same probes, same payload — from your CI, your IDE, or your agent.
When SSL fails or DNS drifts, UpMonitor dispatches the full diagnostic payload to your agent. Your AI reads, decides, fixes.

Start free with one monitor. Move to Pro when you need AI Diagnosis and MCP. Agency unlocks unlimited monitors and team seats.
$0 / month
$9 / month
$18 / month
Run any diagnostic without an account — SSL, DNS, HTTP, security headers, Lighthouse+, and more. Each tool is scriptable from CI and returns JSON your AI agent can parse.
MCP is an open standard that lets AI agents like Claude and Gemini securely access data and tools. UpMonitor ships an MCP server so your agents pull full diagnostic context directly during an incident - no manual copy-paste from dashboards.
An Agentic Webhook delivers a secure Model Context Protocol (MCP) URI to your AI agent, pointing it at the exact logs, configs, and history needed to fix the incident. Standard webhooks only say "System Down"; UpMonitor hands the agent everything required to remediate.
Yes. UpMonitor is free forever for 1 monitor at 5-minute intervals - ideal for personal sites, portfolios, and indie projects.
Yes. The UpMonitor Shadow Monitor API is stateless and built for pre-deploy audits. Run a full SSL, DNS, and security headers check on every commit - one curl command, zero setup - and fail the build before bad config hits production.
Every UpMonitor alert includes a `upmonitor://monitor/<id>` link. Run `upmonitor register` once on your machine, then any click on that link from Slack, email, or an agent UI opens your local terminal loaded with the full diagnostic context - no copy-pasting IDs, no hunting for logs. Automated playbook execution is on the roadmap.
Free accounts run 5-minute checks. PRO and Agency both run 1-minute checks. PRO covers 6 global regions; Agency covers 12+ regions and adds Agentic Webhooks plus public status pages.
UpMonitor sends an instant email alert. PRO adds push notifications (PWA), Slack, and custom webhooks. With the MCP server enabled, your AI agent also receives a structured Agentic Webhook with full diagnostic context - and can start the repair autonomously.
Lighthouse+ is an enriched performance engine that adds proprietary audits - font self-hosting, TTFB DNA, and more - on top of standard Lighthouse data. The output is formatted for AI agents: they identify, apply, and verify performance fixes automatically via the CLI and Shadow API.
Every degraded monitor surfaces an Active Incident panel at the top of its details page - showing the root cause, three remediation steps, and a copy-pasteable prompt that hands the entire incident off to your AI agent (Claude Code, Cursor, Claude Desktop, or any MCP-compatible client). Two clicks from "site down" to "agent has the fix." Read the full lifecycle in the <a href="/docs/active-incident">Active Incident docs</a>.