A status page tells customers what’s working before they have to ask. Pulseback pages follow your monitors on their own and take updates straight from incidents.
Create a page
In Status pages → New status page, set:
| Setting | Notes |
|---|---|
| Name | Shown at the top, e.g. “Acme”. |
| Slug | The page lives at https://status.pulseback.io/<slug>. Lowercase letters, numbers and dashes. |
| Brand colour | Any hex colour. |
| Logo and support link | Optional. |
| Show uptime | Show the 90-day bars and uptime percentages. |
| Hide branding | Removes “Powered by Pulseback”, on plans that include it. |
| Published | Unpublished pages aren’t public. |
Components
Components are what your customers recognise, like “Dashboard”, “Public API” or “Webhooks”. Link each to one or more monitors and its state follows them:
| Linked monitors | Component shows |
|---|---|
| All down | Major outage |
| Some down | Partial outage |
| Some degraded, none down | Degraded performance |
| Some in maintenance, none down or degraded | Under maintenance |
| Otherwise | Operational |
The page’s overall status is its worst component.
Set a component’s state by hand when you know more than the checks do, and clear it to go back to automatic.
Posting updates
Post from an incident with Post status update, or from the page itself. Each update has a status (Investigating, Identified, Monitoring or Resolved), a message, the affected components, and whether to email subscribers. One update can go to several pages.
Write for customers: what’s affected, what still works, and when the next update is due.
Scheduled maintenance
Add a maintenance window with a title, description, start and end, and the affected components. During the window those components show Under maintenance and alerts from their monitors are suppressed (unless you turn that off). Subscribers can be emailed when it’s scheduled.
Subscribers
Visitors subscribe by email from the page. They confirm with a link (double opt-in), and every message has a one-click unsubscribe link. You can see and remove subscribers in the page’s settings.
Custom domains
On plans with custom domains, serve your page from your own hostname, like status.acme.dev:
- In the page’s settings, enter the hostname.
- At your DNS provider, add a CNAME record:
| Type | Name | Target |
|---|---|---|
CNAME |
status (for status.acme.dev) |
status.pulseback.io |
- Back in Pulseback, click Verify. Once the record resolves, Pulseback issues the HTTPS certificate and the page is live on your domain. DNS changes can take a few minutes to propagate.
Use a subdomain: a CNAME can’t sit on your bare domain (acme.dev). If you use Cloudflare for the domain, set the record to DNS only while it verifies.
JSON
Every published page is also available as JSON, with CORS open to any origin, for an in-app banner or your own widget:
curl https://app.pulseback.io/api/public/status/<slug>It returns the page’s overall state, components with their states and 90-day uptime, active incidents with their updates, scheduled maintenance and the last 90 days of resolved incidents.