Skip to main content
Health checks monitor your websites and APIs, alerting you when they go down.

​
Creating a Health Check

  1. Go to Health Checks in the dashboard
  2. Click Add Health Check
  3. Fill in the details:
  1. Click Create

​
How It Works

Every interval, we:
  1. Send an HTTP request to your URL
  2. Record response time and status code
  3. Mark as UP if status is 2xx, DOWN otherwise
  4. Send alert if status changes

​
Alert Behavior

  • First failure: Wait and retry
  • Confirmed down: Send alert after multiple failures
  • Recovery: Send “back up” notification
We use confirmation checks to avoid false alerts from temporary network issues.

​
Expected Status Codes

By default, 2xx responses are considered healthy. You can customize:

​
Keyword Matching

Optionally check that the response contains specific text: Example: Check that your API returns "status":"ok".

​
Retry Settings

​
Uptime Statistics

For each health check, you’ll see:
  • 24h Uptime: Last 24 hours
  • 7d Uptime: Last 7 days
  • 30d Uptime: Last 30 days
  • Response Time: Average, min, max

​
Public Status Pages

Requires PRO plan
Share a public status page with your users:
  1. Go to the health check settings
  2. Enable “Public Status Page”
  3. Copy the public URL
Your users can see uptime status without logging in.

​
Incidents

When a health check fails, an incident is created:
  • Start time
  • Error message or status code
  • Duration (when recovered)
View incident history in the Health Check details.

​
Best Practices

Create a /health endpoint that checks critical dependencies:
  • Critical services: Every 30 seconds
  • Regular websites: Every 60 seconds
  • Non-critical: Every 5 minutes
Set timeout higher than your typical response time. If your API responds in 500ms, use 5-10s timeout.

​
Limits