When an incident happens it's often necessary to share more information than just a simple red and green icon with an up/down status on your status page.
More insights generally help users to accommodate for the interruption and remove the need for any follow-up questions. But crafting a well-written incident update in the heat of a service outage is challenging. Incident communication templates save you stress and hassle.
📌 To learn about details of status updates on Palzin Monitor status pages.
Here are status page templates to consider for different use cases. Feel free to use them as they are or adjust them so they fit your specific use case.
Use this when you want to tell your users and customers to prepare for planned maintenance such as a database migration.
Note that the key to effective communication of maintenance is to let people know early. This can mean 3 days or several weeks depending on the scale of the maintenance and importance of your service.
Announcement message
[Your company name] will be performing routine maintenance on June 10 starting at 14:00 (UTC+1). You may not be able to access [company website] for a short period of time, but we’ll have things back up and running as soon as possible to minimize disruption to you.
In progress message
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Completed message
The scheduled maintenance has been completed. Thank you for your patience!
Use this in case of an incident, where a small feature is not working correctly or where a small amount of users is impacted.
Investigating message
We’re having some trouble with [service affected]. We’re working to fix the problem as quickly as we can. We’ll share another update shortly.
Alternatively, you can provide a specific timeframe like 10 or 30 minutes - but be cautious as users might take your word for it.
Resolved message
We’re back! [service affected] should be up and running. Thanks for bearing with us.
Use this in case of an incident, where a key feature is not working correctly or where a large amount of users is impacted.
Investigating message
We’re investigating an issue with [service affected] that is impacting some users. We’re working to fix the problem as quickly as we can. We’ll share another update shortly.
Resolved message
We’re back! [service affected] should be up and running. Thanks for bearing with us.
Use this in case of an incident, where the whole service is down or when all of your users are impacted.
Investigating message
[service] is down for most users. We’re working to fix the problem as quickly as we can. We’ll share another update shortly.
Resolved message
We’re back! [service affected] should be up and running. Thanks for bearing with us.
Want to know how the best companies communicate downtime? Check out some great examples of status pages and explore specific historical outages and how they were communicated.
We notify you when your website experiences downtime
Stay informed with a comprehensive infrastructure monitoring platform
Check Uptime, Ping, Ports, SSL, and more.
Receive incident alerts via Slack, SMS, and phone.
Easily schedule on-call duties.
Create a free status page on your own domain.
It takes less than a minutes to setup your first monitoring.
