In this guide: Crisis communication when your website goes down: why communication matters, first message templates, updating customers, post-incident reports, and…
Every website goes down at some point — hosting outages, failed updates, DDoS attacks, expired domains, or hacks. Customers usually forgive downtime. What they don’t forgive is silence and confusion.
How you communicate during an outage can actually strengthen trust.
When your site is down, customers:
Clear communication:
Your first message should go out quickly — ideally within 15–30 minutes of confirming the issue. It doesn’t need all the answers.
Template 1 — Initial acknowledgment (social media or status page)
⚠️ We’re aware that [website/service] is currently unavailable for some users. Our team is investigating and working on a fix. We’ll share an update within [30 minutes/1 hour]. Thank you for your patience.
Template 2 — Online store
Our online store is temporarily unavailable. Your existing orders and payment information are safe. We’re working to restore access and will update you by [time]. For urgent requests, contact us at [email/WhatsApp/phone].
Template 3 — Possible security incident (be careful and factual)
We’ve detected an issue affecting our website and have taken it offline as a precaution while we investigate. We’ll share more information as soon as we can. If you have questions, contact [email].
Rules for first messages:
Where to communicate:
Update template:
Update [time]: We’ve identified the cause of the outage ([brief, non-technical explanation, e.g., “a server issue at our hosting provider”]) and are working on a fix. Some pages may load slowly as service is restored. Next update by [time].
Resolution template:
✅ Resolved: [Website] is back online and working normally. The issue was caused by [brief cause]. We’re sorry for the disruption and are taking steps to prevent it from happening again. If you notice any problems, please contact [email].
Stick to your update schedule — even if the update is “still working on it.”
For significant outages, publish or send a short post-incident summary within a few days:
Internally, run a blameless review: focus on process improvements, not individual blame.
If personal data was involved, follow applicable legal notification requirements and get professional advice.
Prevention helps too: monitoring, backups, staging, and security reduce how often you’ll need these templates. See What Is Uptime? and Online Reputation Management.
Further reading: Google Search Central SEO Starter Guide
We may earn a commission on purchases made through these links, at no extra cost to you.
Don’t miss the chance to participate in the biggest giveaway of this year.