Status Page Templates: What to Write During an Incident

Templates reduce pressure

Status page updates are harder to write during an incident. Templates help teams communicate quickly without inventing wording while production is degraded.

The best templates are short, factual, and easy to adapt.

Useful incident states

For investigation: "We are investigating reports of degraded access to [service]. We will share another update by [time]."

For identified: "We have identified an issue affecting [service]. The team is working on mitigation."

For monitoring: "A fix has been applied and we are monitoring recovery."

For resolved: "The incident affecting [service] has been resolved. We are reviewing the cause and will follow up as needed."

Keep the wording customer-centered

Avoid internal system names unless customers recognize them. Say what users experience: login delays, API errors, failed checkout, delayed notifications, or degraded dashboard access.

Templates work best when connected to real monitoring and incident ownership. They should help the team communicate faster, not replace thoughtful updates.