Why it matters
Major outage matters because teams need a precise shared meaning for a severe failure that blocks core customer journeys. 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 severe failure that blocks core customer journeys 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 major outage 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 login and checkout both unavailable. When observed behavior stops matching the definition of major outage, the team treats that change as a reliability event with a clear owner and next step.
Common misconception
Every failed check is a major outage
That reading usually collapses distinct ideas into one slogan. Keep major outage tied to observable behavior so the definition stays useful under pressure.
How Fajita handles this
Reserve major outage language for core path failures and keep status copy honest.