Why it matters
Status-page subscriber matters because teams need a precise shared meaning for a person who opts in to receive status updates by email. Vague language turns incidents into arguments about words instead of fixes.
When everyone uses the same definition, alerts, status updates, and post-incident reviews stay aligned.
How it works
In practice, a person who opts in to receive status updates by email shows up as a concrete signal you can measure or communicate. Operators define what good looks like, watch for deviations, and record what happened when expectations break.
The useful version of status-page subscriber is operational: it changes who gets notified, what customers see, or which metric a team reviews after an incident.
Practical example
Imagine a team operating around subscriber confirms via double opt-in. When observed behavior stops matching the definition of status-page subscriber, the team treats that change as a reliability event with a clear owner and next step.
Common misconception
Subscribers are the same as alert channels for engineers
That reading usually collapses distinct ideas into one slogan. Keep status-page subscriber tied to observable behavior so the definition stays useful under pressure.
How Fajita handles this
Fajita uses verified double opt-in for subscribers. See double opt-in.