Website Down & Maintenance Message Generator
Write an outage or maintenance notice in a minute and copy it
How to write a good outage notice
A good notice tells people what is broken, what they can do and when they will hear from you next. Speed matters more than polish.
- Post early. Publish the first notice within minutes, even if all you can say is that you are investigating. Silence makes customers assume the worst and fills your support inbox.
- Say what is affected. Name the service and, if you can, the part that is broken: logins, payments, the API. Readers want to know whether the problem is the one they are seeing.
- Do not guess the cause. While you are still investigating, say so. Name a cause only once you have confirmed it, and do not blame a supplier in public.
- Give a workaround. If there is another way to get the job done, such as a mobile app, a phone line or an older endpoint, put it near the top.
- Promise the next update, not the fix. A time for the next update is a promise you can keep. A time for the fix often is not. If you give an estimate, call it an estimate.
- Close the loop. When it is over, say so plainly, give the times and tell people where to go if something still looks wrong. Apologise once, without excuses.
- Use one place as the source. Keep the full timeline on your status page and link to it from emails and social posts, so every update lands in one place.
Frequently Asked Questions
Is what I type sent anywhere?
Which stage should I choose?
Can I change the text before I post it?
Want Automated Monitoring?
Get 24/7 monitoring with instant alerts when issues are detected.
Start your 14-day trial