Uptime.com is a dedicated uptime monitoring service that checks from over 30 global locations. Its HTTP check type evaluates status codes and marks anything outside the 2xx range as a failure, which works correctly with Alert24's 200/503 healthcheck endpoints.
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 check
- In Uptime.com, go to Checks → Add a Check
- Set Check Type to HTTP/S
- Enter a Name (e.g. "API Gateway — Alert24")
- Paste your healthcheck URL:
https://app.alert24.net/api/healthcheck/ak_live_YOUR_KEY/YOUR_CHECK_ID - Set Monitoring Interval (1 minute is available on most plans)
- Under Locations, choose the regions to monitor from
- Select Alert Contacts for notifications
- Under Success Criteria, confirm the expected response code is 200 (the default)
- Click Save
Org-wide check
To track all your active Alert24 checks with one Uptime.com monitor:
https://app.alert24.net/api/healthcheck/ak_live_YOUR_KEY
Tips
- Sensitivity: Uptime.com lets you configure how many consecutive failures trigger an alert (e.g. 2 of 2 locations). Keeping this at the default helps avoid alerts for transient network issues between Uptime.com probes and Cloudflare's edge.
- Status pages: Uptime.com has a built-in status page feature. You can attach an Alert24 healthcheck monitor to a status page component so your public status page reflects the same state as your Alert24 checks.
- SSL checks: Uptime.com can monitor certificate expiration separately from uptime. If Alert24 is already monitoring your SSL certificates, you can skip this to avoid duplicate alerting.
- Response time SLA: Uptime.com tracks response times per check. Since Alert24 healthchecks are served from Cloudflare's edge, response times are typically 20–80ms from any global location.