Pingdom (by SolarWinds) is a widely used enterprise uptime monitoring service. Its HTTP check type evaluates status codes and response times. Alert24 healthcheck endpoints work with Pingdom's standard HTTP check — no keyword matching or custom configuration required.
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 an uptime check
- In Pingdom, navigate to Monitoring → Uptime
- Click + Add uptime check
- Enter a descriptive Name (e.g. "Production API — Alert24")
- Set Check interval (1 minute gives the most granular data)
- Under Connect to, select HTTP or HTTPS
- Set the Host to
app.alert24.net - Set the URL to
/api/healthcheck/ak_live_YOUR_KEY/YOUR_CHECK_ID - Leave Port at 443 (HTTPS default)
- Under Who to alert, select your notification contacts
- Click Create check
Pingdom will mark the check as down when it receives a 503 and alert your configured contacts.
Org-wide check
To monitor all your active Alert24 checks with a single Pingdom test:
- Host:
app.alert24.net - URL:
/api/healthcheck/ak_live_YOUR_KEY
Tips
- String matching: Not needed. Pingdom's default behavior (2xx = up) is correct. Adding string matching would require Pingdom to parse the JSON body, which adds unnecessary complexity.
- Response time alerts: Pingdom can alert on slow responses in addition to downtime. Alert24 healthcheck endpoints are served from Cloudflare's edge and are typically fast (< 100ms), so response time alerts won't interfere.
- Probe location: Pingdom checks from multiple global locations. Pick a region close to your users for the most representative latency data.
- SSL monitoring: Pingdom can separately monitor certificate expiration. If you use Alert24's SSL check type for a domain, you can let Alert24 handle the SSL alerting and use Pingdom just for uptime.