Skip to main content

Status Page Notifications

Pick how you want to hear about Cloudflare incidents - email, a webhook into your own systems, or a message in Slack, Discord, or Google Chat.

Overview

Sign up for notifications on every incident, scheduled maintenance, or a narrower filter. Alerts go to the destination of your choice. Notifications are served by the Status Page itself for quick, reliable delivery.

Notifications use a separate account from your Cloudflare dashboard. Sign in with an email magic link.

Getting started

  1. On the Status Page, click Subscribe to Updates, Quick Notifications and pick your notification method.
  2. Click the magic link in the confirmation email. That confirms your subscription and signs you in.
  3. Add more destinations (a webhook, a Slack channel, another email) and tune the rules in notification settings.

When notifications fire

Every notification names what happened and what kind of event it was. The combinations you'll see:

Eventnotification_typeincident_type
New incident openednewincident
Incident updatedupdatedincident
Incident resolvedclosedincident
Backfilled past incidentretroactiveincident
Scheduled maintenance announcednewmaintenance
Maintenance updateupdatedmaintenance
Maintenance completedclosedmaintenance

Rules and filters

A rule has four filters. Leave one untouched and it matches everything for that dimension; narrow it down to be more selective. A rule fires when an incident matches all of them at once.

FilterWhat it controlsValues
TypeIncidents, scheduled maintenance, or both.
IncidentMaintenance
ImpactHow severe an incident has to be before you hear about it.
NoneMinorMajorCritical
StatusWhich incident lifecycle states fire this rule.
InvestigatingIdentifiedMonitoringResolvedScheduledIn ProgressCompletedCanceled
ComponentsRestrict to specific servicesAPI, Dashboard, Workers KV, etc.

You can also subscribe to a single specific incident from its detail page. The rule cleans itself up the moment the incident is resolved.

Destinations

Email

All notification emails come from noreply@notify.cloudflarestatus.com. Add it to your safe-senders list so messages don't get filtered into spam.

Setup
  1. In Destinations click Create destination and pick Email.
  2. Enter the address you want to deliver to.
  3. Click the link in the verification email within an hour.
What you'll get

Subject lines look like Cloudflare Incident - {name} - {date} (or Cloudflare Maintenance for scheduled maintenance). The body has the incident name, current status, the latest update, affected components, and a button that opens the full incident page.

Webhook

JSON POSTed to a URL you control. Pipe it into your own alerting, paging, or whatever else you've already wired up.

Notifications will always fire, even if Cloudflare itself is down. Consider where you are hosting your endpoint if receiving these notifications during an outage is critical.

Setup
  1. Build an endpoint that accepts a POST with a JSON body and returns 2xx on success.
  2. In Destinations create a Webhook destination and paste the URL.
Requirements
  • HTTPS on port 443. Real domain - raw IPs are rejected.
  • Requests time out after 15 seconds. Redirects aren't followed.
Field reference
FieldMeaning
meta.rule_idPublic id of the rule that matched.
meta.destination_idPublic id of the webhook destination.
meta.unsubscribeOne-click link that disables this destination.
incident.notification_typeOne of new, updated, closed, retroactive.
incident.incident_typeincident or maintenance.
incident.statusCurrent lifecycle state - see the chips in the Filters section above for the full list.
incident.impactnone, minor, major, or critical.
incident.backfilledtrue when the incident was created retroactively for a past issue.
incident.shortlinkCanonical link to the incident page.
incident.components[]Components affected by this incident.
incident.latest_updateThe most recent update.
incident.scheduled_for
incident.scheduled_until		Start / end window for scheduled maintenance. Null for regular incidents.

Slack

We post a formatted message into whichever Slack channel you point us at.

Setup
  1. Open the Slack apps page and click Add to Slack and select your channel.
  2. Copy the generated https://hooks.slack.com/services/... URL.
  3. In Destinations create a Slack destination and paste the URL.

You can also use the newer Slack Apps feature, following their guide: Sending messages using Incoming Webhooks.

Discord

Drops a rich embed into a Discord channel.

Setup
  1. In your Discord server, open Server Settings → Integrations → Webhooks.
  2. Click New Webhook, pick the target channel, and optionally set a name and avatar.
  3. Click Copy Webhook URL.
  4. In Destinations create a Discord destination and paste the URL.

Discord's own docs: Intro to Webhooks.

Google Chat

Posts a card into a Google Chat space.

Setup
  1. Open the Google Chat space you want notifications in.
  2. Click the space name in the header and choose Apps & integrations.
  3. Click + Add webhooks, you can use https://www.cloudflare.com/favicon.ico for the avatar URL.
  4. Click Copy URL. It looks like https://chat.googleapis.com/v1/spaces/....
  5. In Destinations create a Google Chat destination and paste the URL.

Managing and unsubscribing

  • Pause or archive a rule any time from Rules. Useful while you're testing, or during a planned change.
  • Every email has a one-click unsubscribe link in the footer that disables that destination immediately.
  • Delete your account from Account. We'll email a confirmation link so it can't happen by accident.

RULE STATES YOU'LL SEE

ActivePausedArchived

Limits and quotas

  • An account is required. Even for webhook, Slack, Discord, or Google Chat destinations, you need an email-verified account. The email is how we manage your destinations and log you in.
  • Up to 15 destinations and 15 rules per account. A single rule can fan out to up to 15 destinations.
  • Webhooks do not use the Cloudflare ASN or Cloudflare IPs.