Website down message to customers: templates
Copy-ready messages for when your website or app is down: a status page update, banner, email, social post, support auto-reply, maintenance page and the all-clear.
· 6 min read · By the Spot Downtime team
When your site goes down, customers notice within minutes. What they want to know is simple: is it you or me, are you on it, and when will it be back? A short message that answers those three questions stops the flood of support tickets and keeps people from assuming the worst.
Below are templates for each place you'll need one. Replace the parts in square brackets and post the first update fast.
What every outage message needs
- What's affected, in the customer's words: “checkout”, not “payments-api”.
- That you know and are working on it. The first update matters more than the perfect update.
- When you'll update next, not a guess at when it's fixed. “Next update in 30 minutes” is a promise you can keep.
- A workaround, if there is one.
- Where to follow along: one link, usually your status page.
1. Status page: the first update
Post this the moment you confirm a problem, even before you know the cause.
Investigating: [Login / Checkout / The website] is down for some customers
We're seeing [errors when signing in / pages not loading] and are looking into it now.
Your data is safe. Next update by [14:30 UTC].The updates that follow (identified, monitoring, resolved) and how to word them are in how to write incident updates customers trust.
2. Website or in-app banner
Keep it to one line, and link to the status page for details.
We're having trouble with [checkout] right now. We're on it. Updates: status.[yourdomain].com3. Email to customers
Send email only for a long or serious outage, or to the customers it actually hit. A ten-minute blip doesn't need an email.
Subject: [Product] is having problems right now
Hi [first name],
Since [13:10 UTC], [Product] has been [unavailable / failing to load dashboards] for some customers.
We know about it and our team is working on a fix.
[Your data is safe and nothing has been lost.]
[In the meantime, you can still ... ]
We'll post updates every [30 minutes] at status.[yourdomain].com,
and email you again when it's fixed.
Sorry for the disruption,
[Name], [Product] team4. Social media post
We're aware [Product] is down for some of you and we're working on it.
Follow along at status.[yourdomain].com. Sorry for the trouble.Reply to people who tag you with the same link. One copy-pasted, friendly reply beats silence.
5. Support auto-reply
Thanks for getting in touch. We're currently dealing with an outage affecting [checkout],
and your message may be about that. Live updates: status.[yourdomain].com.
If your question is about something else, we'll reply as soon as we can.6. Planned maintenance page
We'll be back soon
[Product] is down for scheduled maintenance until about [16:00 UTC].
We're [upgrading our database] to make things faster.
Updates: status.[yourdomain].comServe the maintenance page with HTTP 503 and a Retry-After header, so search engines come back later instead of indexing the maintenance page in place of your content.
7. It's fixed: the all-clear
Post it everywhere the outage message went: status page, banner (then remove it), email and social.
Resolved: [Checkout] has been working normally since [15:05 UTC].
Between [13:10 and 15:05 UTC], [some customers couldn't complete orders]
because [a database update failed]. We've [rolled it back and added a check
so it can't happen again]. [Orders placed during this time were not charged.]
We're sorry for the disruption.For anything bigger, follow up with a short write-up within a few days. Our post-incident review template has the structure.
Don't find out from customers
The worst way to learn your site is down is a customer email. Uptime monitoring tells you first, so your first update goes out before the tickets arrive.
Post updates from one place
Get new guides by email
Practical posts on monitoring, outages, error fixes and on-call, when they're published. No spam.
Keep reading
- Incidents · Status pagesHow to write incident updates customers trust (with templates)During an outage, what you say matters almost as much as how fast you fix it. A simple four-stage structure, ready-to-use templates, and the mistakes that make customers lose trust.October 2, 2026 · 4 min read
- Status pages · IncidentsStatus page best practices: what to show, what to write and what to avoidHow to decide which services a status page lists, how to word incidents and maintenance, where to host it, and the mistakes that make customers stop trusting it.November 6, 2026 · 6 min read