Notifications

Nines sends alerts when incidents are created or resolved. Configure email and webhook channels under Settings → Notifications.

Notification channels

Two channel types are available:

  • Email — available on all plans. Nines sends an HTML email to the address on your account when an incident is created, updated, or resolved.
  • Webhook — available on Pro and Business plans. Nines sends a signed JSON POST to a URL you configure. Use this to forward alerts to Slack, PagerDuty, a custom on-call system, or any HTTP endpoint.

What triggers a notification

Notifications fire for the following events:

Event Email Webhook
Incident created (region failure) ✓ ✓
Incident created (availability burn-rate) Owner only Owner only
Incident created (latency burn-rate) Owner only Owner only
Incident updated ✓ ✓
Incident resolved ✓ ✓

Burn-rate notifications are owner-only

Burn-rate incidents reflect your internal SLO posture — how fast your error budget is depleting. This information is sensitive: a high burn multiplier reveals the degree of latency or availability degradation before you choose to communicate it publicly. For this reason, burn-rate incident notifications are sent only to the account owner and are never shown on the public status page.

Region-failure incidents, which reflect binary outages visible to end users, are shown on the public status page.

Adding a notification channel

  1. Go to Settings → Notifications in your dashboard.
  2. Click Add channel.
  3. Choose Email or Webhook.
  4. For webhooks, enter the destination URL and an optional signing secret. See Webhooks for payload details and signing.
  5. Save the channel. Nines will use it for all future incidents.

Testing your webhook

After saving a webhook channel, you can trigger a test by manually resolving and re-opening a monitor incident, or by using the Nines API. Check your webhook endpoint's logs to verify the signed payload arrives correctly.

See Webhooks for the full payload schema, signing details, and retry behavior.