Why it matters
Degraded performance matters because teams need a precise shared meaning for a state where a service works partially or slowly but is not fully down. 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 state where a service works partially or slowly but is not fully down 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 degraded performance 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 search API responding in 4s instead of 200ms. When observed behavior stops matching the definition of degraded performance, the team treats that change as a reliability event with a clear owner and next step.
Common misconception
Degraded always means completely offline
That reading usually collapses distinct ideas into one slogan. Keep degraded performance tied to observable behavior so the definition stays useful under pressure.
How Fajita handles this
Fajita distinguishes degraded from down. See degraded vs down.