Running a status page
When your service is down, the worst place for the page that says so is on the same infrastructure that just failed.
Host it somewhere else
A status page shares the fate of whatever it runs on, so it belongs off your main stack — a small separate machine, a different network, ideally a second provider. If both go down together it was never a status page, it was a second victim. See adding a second provider.
What to put on it
- Current state per service, in plain language.
- A short, honest note during an incident — what is affected, what you are doing, when you will update next.
- A history, so customers can see your track record rather than guess at it.
Keep it honest and automatic
Drive the top-line state from your own monitoring where you can, so it cannot quietly show green while things burn. But write incident updates by hand — a human sentence during an outage buys more goodwill than any dashboard. Pair it with clear incident updates to your customers.
Still stuck? Mail support@novogara.com — an engineer answers, at any hour. Back to the knowledge base