Status Pages

What are status pages?

Status pages give your users a public view of your service health. Link your monitors, heartbeats, and API tests as components, and ThunderHooks automatically shows their current status.

Creating a status page

Go to Status Pages in the sidebar and click New Status Page:

• Name — your service or company name
• Slug — the URL path (your page lives at /status/{slug})
• Brand color — customize the accent color
• Public — toggle whether the page is publicly accessible

Adding components

Components are the services shown on your status page. Each one is linked to a monitor, heartbeat, or API test:

1. Open your status page
2. Click Add Component
3. Select a monitor, heartbeat, or API test
4. Give it a display name

The component's status updates automatically based on the linked check.

Incidents

When something goes wrong, create an incident to keep your users informed:

1. Click New Incident on the status page admin
2. Set the title, status (investigating, identified, monitoring, resolved), and impact level
3. Add updates as you work through the issue

Incidents appear on the public status page with a timeline of updates.

Real-time updates

The public status page uses server-sent events (SSE) for live updates. When a component's status changes or a new incident update is posted, visitors see it immediately without refreshing.

Public URL

Your status page is available at:

https://thunderhooks.com/status/{slug}

Share this URL with your users, embed it in your docs, or link to it from your app's error pages.

API access

Each status page also has a JSON API at:

https://thunderhooks.com/status/{slug}/api

This returns the current status of all components and recent incidents in a machine-readable format.