Incident Communication Template Generator
Generate professional status page updates for every phase of an incident. Select your incident type, severity, and affected services - then copy and paste.
Separate multiple services with commas
Service Disruption - API and Web App
We are investigating reports that API and Web App are currently unreachable. This is being treated as a critical priority incident. Our engineering team is actively looking into the root cause. We will provide an update within 30 minutes.
Root Cause Identified - API and Web App
We have identified the root cause of the outage affecting API and Web App. [DESCRIBE ROOT CAUSE - e.g., "A configuration change caused elevated error rates on the primary database cluster."] A fix has been implemented and is being rolled out. We expect service to be restored within [ESTIMATED TIME]. We will continue to monitor and provide updates.
Fix Deployed, Monitoring - API and Web App
A fix has been deployed for the issue affecting API and Web App. Service has been restored and we are actively monitoring to confirm stability. Some users may need to refresh their browser or retry their last request. If you continue to experience issues, please contact our support team. We will post a final update once we are confident the issue is fully resolved.
Resolved - API and Web App
The outage affecting API and Web App has been fully resolved. All systems are operating normally. Total impact duration: [DURATION] Root cause: [BRIEF SUMMARY] We apologize for the disruption. A detailed postmortem will be published within 48 hours. Thank you for your patience.
Why incident communication matters
When your service goes down, your customers need to know three things: that you are aware of the problem, what you are doing about it, and when they can expect it to be fixed. A status page update that communicates this clearly reduces support ticket volume by 30-60% during incidents.
The four-phase update model (Investigating → Identified → Monitoring → Resolved) is the industry standard used by companies like GitHub, Atlassian, and Cloudflare. Each phase serves a specific communication purpose and sets appropriate expectations.
This generator creates templates for each phase based on your incident type and severity. Customize the bracketed placeholders with your specific details, then post to your status page.
Best practices for incident updates
- Post within 5 minutes of detecting an issue. Even "we are investigating" is better than silence.
- Update every 30 minutes during active incidents, even if there is no new information. "Still investigating" reassures users you have not forgotten.
- Be specific about impact - "API returning 503 errors for 15% of requests" is more useful than "experiencing issues."
- Use plain language. Your status page audience is customers, not engineers. Avoid internal jargon.
- Include a time estimate when possible. "We expect resolution within 1 hour" manages expectations better than open-ended updates.
- Always post a resolution update with the root cause and duration. This closes the loop for customers following along.
Automate your status page updates
Vantaj status pages update automatically from your monitors. When an outage is detected, the page reflects it in real time - no manual posting required.
Try Vantaj free