UptimeRobot is one of the most widely used uptime monitoring services. Its free plan checks every 5 minutes; paid plans check every minute. Because it evaluates HTTP status codes automatically, it works with Alert24 healthcheck endpoints out of the box — no JSON parsing needed.
Before you start
You'll need:
- An Alert24 API key (Settings → API Keys → Create API Key)
- The ID of the check you want to monitor, found in Monitoring → [check name] or via the API
Add a monitor
- Log in to UptimeRobot and click + Add New Monitor
- Set Monitor Type to HTTP(s)
- Enter a Friendly Name (e.g. "Production API via Alert24")
- Paste your healthcheck URL into the URL field:
https://app.alert24.net/api/healthcheck/ak_live_YOUR_KEY/YOUR_CHECK_ID - Set your preferred Monitoring Interval (5 min on free, 1 min on Pro)
- Under Alert Contacts, select who gets notified on downtime
- Click Create Monitor
UptimeRobot will now poll Alert24 on your chosen interval. When Alert24 reports the check as down or degraded, it returns 503, and UptimeRobot marks the monitor as DOWN and fires your alerts.
Org-wide monitor
To get a single monitor that alerts if any of your services are down, use the org-wide endpoint instead:
https://app.alert24.net/api/healthcheck/ak_live_YOUR_KEY
Tips
- Custom status codes (Pro): UptimeRobot Pro lets you define which HTTP codes count as success. The default (2xx = up, anything else = down) works correctly with Alert24's 200/503 responses — no changes needed.
- Keyword monitoring: Not required. Alert24's status code response is sufficient; adding keyword checks just creates unnecessary load.
- Check freshness: Alert24 serves cached status. The
X-Alert24-Checked-Atresponse header tells you when the last real check ran. UptimeRobot doesn't surface this, but it's visible viacurl -i.
Alert24 rate limits
Alert24 allows 60 healthcheck requests per minute per API key. UptimeRobot's fastest polling interval (1 minute) stays well within this limit even if you're running several monitors against the same key.