Incidents & alerting

A scheduled check can open an incident for a few different kinds of problem:

• Availability — the target failed a basic check: a DNS, TCP, or TLS error, or an HTTP error status. Available on every plan.
• Performance (slow response) — the target responded, but slower than the threshold you configured. Available on team and enterprise plans.
• API assertions— the response body didn't match a condition you defined. Available on enterprise plans only.
• SSL expiry— the target's certificate is approaching or past its expiration date. Available on starter, team, and enterprise plans.
• Email DNS— the target's email-related DNS records changed or a lookup failed. Available on team and enterprise plans.

When an incident fires, RegionCheck notifies whichever alert channels you've set up on that scheduled check. RegionCheck supports five channel types on every plan:

• Email — sends to a configured address.
• Slack — posts to a Slack incoming webhook URL. Only webhooks on webhook.slack.com are accepted.
• Teams — posts to a Microsoft Teams webhook URL. Only webhooks on *.webhook.office.com, *.logic.azure.com, or *.environment.api.powerplatform.com are accepted.
• PagerDuty — sends to a PagerDuty routing key.
• Webhook — sends to any HTTPS URL you control, with an optional signing secret and a custom header. The destination is IP-validated at send time.

How many alert channels you can configure depends on your plan: 1 on free, 25 on starter, 100 on team, and 1,000 on enterprise.

Create an alert channel with POST /api/alert-channels:

curl -s https://regioncheck.io/api/alert-channels \
  -H "Authorization: Bearer $REGIONCHECK_API_KEY" \
  -X POST -d '{"type": "slack", "config": {"webhook_url": "https://webhook.slack.com/..."}}'

The MCP server exposes the same capability through the create_alert_channel tool. Once a channel is created, you can send it a test notification with test_alert_channel before relying on it.