CheckHTTP requests your site every minute from runners on AWS, Google Cloud and Azure.
Each check records the HTTP status, DNS, connect, TLS and time-to-first-byte, which runner made it and a HAR file you can open in your browser's dev tools. You see why it failed, not just that it did.
See all check types →
Choose how many runners must fail, for how many checks in a row, before anyone is woken up. One flaky network path won't page you; a real outage will, by email or webhook.
Set up alerts →
Add a small script and CheckHTTP collects Core Web Vitals (LCP, INP, CLS), slow pages and JavaScript errors from real browsers, next to your uptime checks.
How real-user monitoring works →
Runners on AWS, Google Cloud and Azure check your site independently, so a single provider's bad day doesn't look like your outage. This map shows the runners online right now.
Cloud status directory →CheckHTTP has an MCP server. Add it to Claude, Cursor or any MCP client and your agent can create monitors, read check results and investigate failures for you.
MCP setup guide →{
"mcpServers": {
"checkhttp": {
"url": "https://checkhttp.com/mcp/sse",
"type": "sse",
"headers": { "Authorization": "Bearer YOUR_API_KEY" }
}
}
}
$15/mo
Paste a URL. Your first checks run immediately.
Illustrations by Streamline (CC BY 4.0)