Why it matters
Hosted status page matters because teams need a precise shared meaning for a status page served on infrastructure managed by the monitoring provider. 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 status page served on infrastructure managed by the monitoring provider 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 hosted status page 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 https://example.fajita status hostname. When observed behavior stops matching the definition of hosted status page, the team treats that change as a reliability event with a clear owner and next step.
Common misconception
Hosted pages cannot use custom domains
That reading usually collapses distinct ideas into one slogan. Keep hosted status page tied to observable behavior so the definition stays useful under pressure.
How Fajita handles this
Fajita provides hosted status pages and optional custom domains.