Skip to main content
Ionhour
Status pages

What to put on a public status page during an incident

Customers do not need every detail. They need to know you have noticed, what is affected, and when they will hear from you next.

I

Ionhour team

September 8, 2026 · 1 min read

A status page earns trust in the first ten minutes of an incident, long before the root cause is known. The goal is not to explain everything; it is to stop customers wondering whether anyone is looking.

The first update

Post early, even if you know very little. A good first update says:

  • What customers might notice, in their words, not yours.
  • Which parts of the product are affected and which are fine.
  • When the next update will be posted.

Keep the cadence you promised

If you said thirty minutes, post in thirty minutes, even when the update is “still investigating.” Silence reads as chaos. When the incident is resolved, say so plainly and link to a short write-up once it is ready.

ShareXLinkedIn

Ionhour team

Product & engineering

The people who design, build and run Ionhour, sharing what we learn from monitoring production systems every day.

Know the moment a job doesn’t run.

Cron jobs, websites, and APIs — watched 24/7, with alerts in Slack, SMS, or email.