Tickstem
The status page that updates itself
Most status pages lie. Not intentionally — they just require a human to update them, and humans are busy, stressed, and dealing with the incident when the incident happens. So the status page says "All systems operational" while users are hitting errors, and the truth comes out twenty minutes later when someone finally gets around to posting "We are investigating reports of..."
The problem isn't laziness. It's that updating a status page is a manual step in the middle of an already chaotic situation. The two systems — your monitoring and your status page — are disconnected.
The obvious fix
Connect them. If your status page is generated directly from your monitoring data, it updates the moment something goes wrong — no human required, no lag, no "we are investigating" posts that trail the actual problem by 15 minutes.
Tickstem now ships status pages that do exactly this. Enable one in the dashboard,
pick a slug, and your status page is live at
tickstem.dev/status/your-app. It reflects the current state of your
uptime monitors and heartbeat monitors automatically.
No code required. No webhooks to wire up. No separate service to configure. If you already have monitors running, your status page is one toggle away.
What it shows
The page has two sections. The first shows your HTTP endpoints — pulled from your uptime monitors — with their current status and 30-day uptime percentage. The second shows your scheduled jobs — pulled from your heartbeat monitors — with whether they're currently running and when they last pinged in.
That second section is where it gets interesting.
The gap other status pages miss
A status page that only shows HTTP endpoints can tell you your server is responding. It can't tell you whether your nightly data sync ran, whether the daily report job completed, or whether the backup that was supposed to finish at 3am actually finished.
Those are background jobs, and they fail silently. The server is healthy, the endpoint returns 200, but nothing useful is happening behind it. A user asks why their weekly digest didn't arrive and you have no idea — because your monitoring was watching the server, not the work.
Tickstem heartbeat monitors solve this by inverting the check: your job pings a URL after every successful run, and if the pings stop arriving, you get alerted. The status page surfaces this same signal publicly — so your users can see not just "API: Operational" but "Weekly digest: Running" or "Nightly sync: Missing".
Three steps to a live status page
- Go to Dashboard → Status Page
- Choose a slug and set your page title
- Toggle visibility to Public
Your monitors and heartbeats populate it automatically. Set it to Private first if you want to preview it before sharing — the URL works for you while logged in, invisible to everyone else.
Free tier accounts get a status page. No upgrade required.