Public Status Page Management
AmICited’s status page software shows live incident state for the monitors and heartbeats you choose, so customers can check for themselves during an outage instead of flooding support. This public status page lives outside your dashboard at its own URL, refreshes automatically, and subscribers get availability updates by email without you drafting one.
Public Incident Communication
Pick which monitors and heartbeats appear, and the page’s top banner reflects the worst state among them: all operational, some degraded, or an outage. When an incident opens on a listed target, incident communication happens automatically — no separate update to write.
- Select which monitors and heartbeats show — a page for the whole domain, or just the systems customers care about; internal monitors stay internal.
- Live incident state, worst-first rollup — the banner reads the least healthy included target: operational, degraded, or outage.
- Email subscribers, double opt-in — anyone can subscribe and confirm by email to get notified the moment status changes, capped at 1,000 confirmed subscribers per page.
- Rolling 90-day uptime shown — a trailing percentage per target builds customer confidence even outside of an incident.
Status Page Uptime Data
Each target row shows a public label, current status, a 90-day uptime percentage, a 24-hour strip and a 90-day strip — the same green/amber/red/grey logic as the dashboard, so a repeated pattern of amber reads differently from a single red spike. Grey means no usable data for that period, not that the target was down. Incident history lists every active incident first, then resolved ones from the last 30 days, with start, resolution and duration.
- 24h strip — 96 fifteen-minute cells; heartbeat bars only ever show green, red or grey since heartbeats have no degraded state.
- 90d strip — one cell per UTC day, same 99% / 90% thresholds as the dashboard.
- Incident history — active incidents shown first, then resolved incidents from the last 30 days, oldest data drops off after that.
- Subscriber notifications — confirmed subscribers get opened and resolved emails for active URL-monitor incidents on the page; heartbeat incidents don’t currently trigger a subscriber email.
Status Page Monitor Sources
A public page showing ‘all systems operational’ is only trustworthy if the monitors and heartbeats behind it are actually watching the systems that matter. Build out Uptime Monitors and Heartbeat Monitoring first, then pick what to show.
- HTTP, TCP, DNS and Transaction checks — cover the public endpoints customers actually depend on.
- Heartbeats for background jobs — so a silent failure doesn’t stay invisible to the status page too.
- Choose the subset to publish — internal monitors stay internal; only what customers need appears.
manual updates needed once a monitor is on the page
The page reflects your monitors’ real state automatically — no separate incident post to draft and publish during an outage.
See Uptime MonitorsReady to give customers a place to check status themselves?
Free check · 7-day trial · card required