MonitorHound logo MonitorHound

HTTP Monitoring

Monitor any HTTP or HTTPS endpoint for availability, performance, and correctness. Detect outages, slowdowns, and unexpected responses before they affect your users.

The problem

Your website could go down at any time — a failed deployment, an overwhelmed database, an expired DNS record, or a cloud provider incident. Without active monitoring, you rely on your users to tell you something is broken. By then, the damage to trust and revenue is already done.

How MonitorHound helps

MonitorHound sends HTTP requests to your endpoints at regular intervals — as frequently as every minute, with custom intervals available for enterprise customers. Each check verifies the response status code, measures response time, and optionally validates the response body. When something goes wrong, you are alerted immediately.

What you can monitor

  • Website homepage and key pages
  • REST API endpoints
  • Health check routes
  • Webhook URLs
  • Login and authentication flows
  • Third-party service dependencies
  • Status code validation (2xx, 3xx, 4xx, 5xx)
  • Response body content matching

Example configuration

{
  "type": "http",
  "url": "https://api.example.com/health",
  "method": "GET",
  "interval_seconds": 60,
  "timeout_seconds": 30,
  "expected_status": 200,
  "headers": {
    "Authorization": "Bearer <token>"
  }
}

Frequently asked questions

What HTTP methods are supported?

MonitorHound supports GET, POST, PUT, PATCH, DELETE, and HEAD requests. You can configure custom headers, request bodies, and authentication for each monitor.

Can I monitor authenticated endpoints?

Yes. You can add custom headers including Authorization tokens, API keys, and cookies. Basic auth and bearer token authentication are both supported.

How does content matching work?

You can specify a string or pattern that must appear in the response body. If the expected content is missing — even when the status code is 200 — the check is marked as failed and an alert is triggered.

What happens during a timeout?

If the endpoint does not respond within the configured timeout period, the check is marked as failed. The default timeout is 30 seconds, configurable per monitor.

Start monitoring your endpoints

Set up HTTP monitoring in under a minute. Free plan includes 10 monitors.

Start Free Monitoring