---
title: "Incident Update Generator: Free Status Page Message Templates"
description: "Generate clear status page incident updates in seconds: investigating, identified, monitoring, resolved and maintenance messages. Free, no sign-up."
url: https://statusentry.com/tools/incident-update-generator
updated: 2026-10-20
---

Free tool

# Incident update generator

Fill in a few details and get a clear, calm status page update for any stage of an incident. Free, no sign-up, nothing leaves your browser.

Tip: use our [incident communication templates](https://statusentry.com/blog/incident-communication-templates) for email and social, and the [maintenance announcement templates](https://statusentry.com/blog/how-to-announce-scheduled-maintenance) for planned work.

Examples

## Incident update examples for each stage

Investigating

**Login failures for some users**

We're investigating reports that some users can't log in. We'll post an update within 30 minutes.

Identified

**Login failures for some users**

We've identified the cause: a configuration change to our authentication service. We're rolling it back now. Next update within 30 minutes.

Monitoring

**Login failures for some users**

A fix has been applied and logins are succeeding again. We're monitoring to make sure the issue doesn't return.

Resolved

**Login failures for some users**

This incident has been resolved. Logins have been working normally since 14:20 UTC. Thanks for your patience.

Best practices

## How to write a good incident update

- **Lead with impact.** Say what users will notice before anything else.
- **Be specific.** Name the service, region or feature. “Some users can't log in” beats “issues”.
- **Promise the next update.** Give a time and keep it, even if there's no news.
- **Skip blame and guesses.** Share the cause only once you know it.
- **Close the loop.** Post a resolved update, and a postmortem for major incidents — see our [postmortem example](https://statusentry.com/blog/postmortems).

## Incident update FAQ

**What should an incident update include?**

What is affected, what users will notice, what you are doing about it, and when the next update will come. Skip internal jargon, blame and guesses about the cause.

**How often should I post incident updates?**

Post the first update within about 10 minutes of confirming an issue, then every 30–60 minutes until it is resolved, even if nothing has changed.

**What are the stages of an incident update?**

Most status pages use four: Investigating (you know something is wrong), Identified (you know the cause), Monitoring (a fix is in place) and Resolved (service is back to normal).

**Does this generator use AI?**

No. It fills proven templates with your details, entirely in your browser. Statusentry's AI writing assistant can then refine your own drafts inside the app.

## Post updates where customers look.

Publish incidents on a hosted status page and notify subscribers by email, Slack and webhook. Start free.

[Create your status page](https://app.statusentry.com/signup) [More free tools](https://statusentry.com/resources)