Status Page Notifications
Pick how you want to hear about Utilbot incidents and maintenance — email, a webhook into your own systems, or a Discord channel.
Overview
Every subscriber gets notified about every incident and maintenance update — there’s no account to sign in to and no per-subscription filtering yet. Notifications are served by the Status Page itself, independently of Utilbot’s own infrastructure, for reliable delivery even during a wide outage.
Getting started
- On the Status Page, click Get Notifications and pick a destination.
- Email subscriptions need one extra step: click the confirmation link we send you. Webhook and Discord destinations are verified immediately with a test message.
- Every notification — email, webhook, and Discord — includes a one-click unsubscribe link specific to that destination.
Destinations
Subject lines look like Utilbot Incident – {name} – {date} (or Utilbot Maintenance for scheduled maintenance). The body has the current status, the latest update, a link to the full incident page, and an unsubscribe link.
Webhook
JSON POSTed to a URL you control. Notifications fire even if Utilbot itself is down, so host your endpoint somewhere that stays up during an outage.
- HTTPS on port 443, with a real domain — raw IPs are rejected.
- Requests time out after 15 seconds; redirects aren’t followed.
POST /your-endpoint HTTP/1.1
Content-Type: application/json
User-Agent: Utilbot-StatusPage-Notifications/1.0
{ "meta": {...}, "incident": {...} }Discord
Paste an incoming webhook URL from a Discord channel and updates post there as a formatted embed (title, status, and a link to the incident), subject to the same HTTPS/timeout rules as the generic webhook above.