Skip to main content

​
What a status page includes

Squasher status pages give you a customer-facing surface for service health. Each page can include:
  • Public components such as API, Checkout, or Background Jobs
  • Current component health
  • Active incidents
  • Recent incident history
  • Optional headline and support link

​
Build component health from monitors

Status pages are powered by your monitor configuration. When a monitor links to the same component name used on a status page, Squasher rolls monitor state into that public component automatically. This means the same monitor that alerts your team can also update your customer-facing health surface.

​
Keep customer updates aligned with incident response

When monitor thresholds are breached, Squasher can open incidents automatically. Those incidents then appear alongside the affected components on the public page, so internal response and external communication stay aligned.

​
Typical setup

  1. Create a status page.
  2. Add the customer-facing components you want to publish.
  3. Create monitors and link them to matching component names.
  4. Use Run now to validate behavior.
  5. Share the public page URL with customers.