Status Page

A status page is a customer-facing view of your services and incidents, hosted at status.blametrail.com/<your-slug>. Use it to keep customers informed about active incidents, share historical reliability, and reduce inbound support load during outages.

Plan availability

Each tenant can publish a single status page.

Creating your status page

1. Open Organization → Status Page.
2. Choose a slug — lowercase letters, numbers, and hyphens only (for example, acme). Your page will be reachable at status.blametrail.com/acme.
3. Set a display name that customers will see (typically your company or product name).
4. Optionally add a headline (a short sentence shown under the title) and a support URL (a link customers can use to contact you).
5. Save. The page is created in draft mode and is not yet visible to the public.

Adding services

Decide which services should appear on the public page:

1. From the Status Page editor, pick a service from the Add service dropdown.
2. Optionally override the display name — the public label can be friendlier than your internal service name.
3. Reorder services with the position field; lower numbers appear first.
4. Remove a service at any time; removing it does not delete the underlying service.

The status of each listed service is derived automatically from its current monitoring state — operational, degraded, down, or unknown.

Publishing

Toggle Published on to make the page reachable at status.blametrail.com/<slug>. Toggling off returns the page to draft mode immediately. The public URL responds with a 404 while the page is unpublished.

Visibility

Every published status page has a visibility setting that controls who can view it:

• Public (default) — Anyone with the link can view the page. This matches how Statuspage, BetterStack, and most incident-communication tools work, and is the right choice when the page is meant for your customers.
• Private (members only) — Visitors must be signed into BlameTrail and be a member of your organization. Anyone else sees a login prompt; signed-in users on other organizations see a generic "not found" page (the existence of the page is not revealed).

Change the setting under Organization → Status Page → Page settings → Who can view this page. Toggles take effect immediately — no cache wait.

If you've shared the public URL with external viewers before flipping to private, they'll see a login prompt on their next visit (and a "not found" page if they try to sign in with an account outside your organization). There's no broadcast; existing tabs continue to show whatever they last loaded until the viewer navigates.

Under the hood, private pages:

• Never hit a shared cache. The backend serves them with Cache-Control: private, no-store, and BlameTrail's own server-side rendering bypasses its normal data cache when fetching them.
• Are gated by session cookie. If the viewer has no session, they're redirected to blametrail.com/login?redirect=<status-url> and bounced back after a successful login.

Custom branding (Pro)

Pro tenants can set a brand color (any hex value) that is applied to the page header. Combined with the headline and support URL, this gives you a status page that matches your product without needing a separate hosting setup.

Publishing incident updates

Incidents are private by default. To surface an incident on your public page:

1. Open the incident in BlameTrail.
2. Click Publish to status page, optionally giving the incident a customer-facing public title (for example, hide an internal codename).
3. Post updates as the situation evolves. Each update has a status:
   • Investigating — you've acknowledged the issue and are looking into it.
   • Identified — root cause is known.
   • Monitoring — a fix is in place; you're watching for recovery.
   • Resolved — the incident is over.

Updates appear in chronological order under the incident on the public page. Resolving the incident in BlameTrail moves it from Active incidents to Incident history.

Incident history

The page shows the last 90 days of resolved public incidents.

Caching

Public status responses are served with Cache-Control: public, max-age=30, s-maxage=30 so any CDN or reverse proxy in front of BlameTrail can absorb traffic spikes during outages. Incident publishes and status flips appear within 30 seconds of being posted.

Private pages are never cached at a shared layer — each request is served fresh, scoped to the viewer's session.