Impact first
Say what customers experience before describing internal systems.
FREE · PRIVATE · NO SIGN-UP
Incident update message generator
Turn the facts you have into a calm, useful status page update. Generate messages for every incident phase and planned maintenance.
What should customers know?
Ready to publish
Message quality
3/4- Customer impact is clear
- Response action is explained
- Next update is promised
- Add customer instructions when useful
A good incident update reduces uncertainty
An incident update is a short, timestamped message that explains the customer impact, what is known, what the response team is doing, and when customers will hear more. It should report confirmed facts without hiding uncertainty or inventing a resolution estimate. For the full method, read the guide on how to write incident status updates.
Facts, not guesses
Separate what you have confirmed from what is still being investigated.
Promise the next update
Give a specific update time and post again even if the situation has not changed.
Incident status message examples
Investigating
Investigating API errors
Some API requests are returning errors. Our engineers are investigating the cause. We will share another update within 30 minutes.
Identified
Database latency identified
Elevated database latency is delaying dashboard requests. We have identified the cause and are applying a mitigation. We will update you again by 15:00 UTC.
Monitoring
Service recovering
The mitigation is in place and request success rates have recovered. We are monitoring the service before marking this incident resolved.
Resolved
API errors resolved
API request success rates have returned to normal. This incident is resolved. We are reviewing the event and will share follow-up information if appropriate.
Incident communication FAQ
What should an incident update include?
Lead with the customer impact, say what the team is doing, and give a specific time for the next update. Share confirmed facts and label anything still under investigation.
How often should a status page be updated?
Set the next update time in the first message and keep that promise, even when there is no major change. During a serious outage, updates every 30 to 60 minutes are a useful starting point.
What is the difference between investigating and identified?
Investigating means the cause is not confirmed. Identified means the team has confirmed the cause and is working on a fix or mitigation. Do not move to identified based only on a suspicion.
Should an incident update include an estimated resolution time?
Only include an estimate when the team has enough evidence to trust it. An accurate next-update time is more useful than a speculative resolution time that may slip.
Does this generator send or store incident details?
No. The messages are generated locally in your browser. Uptimepage does not receive or store anything you type into this tool.
Your message is ready. Give it a status page.
Publish incident updates, show live component health, and notify subscribers from one public Uptimepage status page. Start free, no card.
more free tools · uptime SLA calculator · error budget calculator · cron expression generator