FaultPilot
FaultPilot home

FaultPilot documentation

Status Pages

Publish monitored service health, incidents, maintenance, branding, and custom-domain HTTPS.

Open in FaultPilot
1

Create and brand

  1. Create a page with a customer-facing name and description.
  2. Upload a compact logo and favicon; FaultPilot optimizes supported assets.
  3. Add only monitors and names customers should be able to see.
2

Custom domain

  1. Choose a hostname such as status.example.com.
  2. Create the CNAME record shown by FaultPilot and wait for public DNS propagation.
  3. Verify and save the hostname before visiting it over HTTPS.
  4. FaultPilot's controlled on-demand TLS issues a certificate only for an approved status-page hostname.
3

Health history

  1. Daily bars are derived from retained monitor results, not the current state alone.
  2. No-data days remain neutral rather than pretending the service was down.
  3. Maintenance and incidents provide context but are not the same operational object.
4

Publish updates

  1. Use incidents for unplanned customer impact.
  2. Use maintenance windows for planned work.
  3. Keep private diagnostics, credentials, and internal hostnames out of public descriptions.