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 | 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
- Go to Settings → Notifications in your dashboard.
- Click Add channel.
- Choose Email or Webhook.
- For webhooks, enter the destination URL and an optional signing secret. See Webhooks for payload details and signing.
- 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.
Per-monitor notification routing Business
By default, every incident fires all notification channels configured for your org. On the Business plan, you can route each monitor's incidents to a specific subset of channels — for example, send production monitor alerts to your on-call webhook while staging monitors only notify an ops email.
Configuring routing
- Open the monitor you want to configure and click Edit.
- Scroll to the Notification Routing section.
- Check the channels that should receive alerts for this monitor. Leave all unchecked to use the org-wide default (all channels).
- Save the monitor.
Fallback behavior
If no channels are selected for a monitor, Nines falls back to firing all org channels. An empty selection means "use defaults", not "send to no one".
Plan changes
If your plan downgrades below Business, Nines ignores per-monitor mappings and reverts to firing all org channels. Your routing configuration is preserved — if you upgrade again, it resumes automatically.