/ status page
A status page that updates from your monitors
Every plan includes a hosted status page. Pick the monitors to show, and the page keeps their status, their daily uptime and any incident current on its own. When something goes down, your users see it on the page before they open a support ticket.
See it live on Fettle’s own status page.
What the page does on its own
- Components from your monitors
- Pick the monitors to show, give them public names, and group them. A component's status comes from its monitor, so nobody has to set it by hand.
- Incidents that open on their own
- When a monitor on the page goes down, the page opens a public incident named after the component, and resolves it when the monitor recovers. Internal error details stay internal.
- Updates you write
- Post investigating, identified, monitoring and resolved updates from the dashboard, the API or the MCP server, so Claude or Codex can draft the update while you fix the outage.
- Maintenance shown as maintenance
- A component under an active maintenance window shows as under maintenance, not as an outage.
- Daily uptime history
- Each component carries a strip of daily uptime, up to 90 days, as far back as your plan keeps history. Incidents from the last 14 days stay listed below.
- Email for subscribers
- Visitors subscribe with their email and confirm it, and hear about incidents and updates. From Plus. A blip that resolves within 3 minutes sends no email.
Where it lives
Each page has its own address on status.fettle.sh and its own share card, and it refreshes in the visitor’s browser while they watch. Custom domains are not available. The page carries a small Fettle link; from Max, you can remove it.
Plans
Status pages per organization: 1 on Free, 1 on Plus, 3 on Pro and 10 on Max. Confirmed subscribers per organization, across all its pages: 50 on Plus, 250 on Pro and 1000 on Max. Every plan and limit is on the pricing page.