Content Snare
Day 0 after signup
3 minute outage on 27 October
Our redundancy kicked in and systems failed over automatically.
Why it works
- Lead with a concise summary so readers understand the incident and its impact before getting technical details.
- Explain the timeline and data impact plainly, then clearly state whether the reader needs to take action.
- Close with a direct support option and a personal sign-off to make follow-up feel approachable.
How it is built
- Personal greeting
- Incident summary
- Outage timeline
- Data impact details
Email copy
Hey [First name] Summary: Our redundant systems worked as expected during a short outage on 27 October. The main database failed over to a hot standby automatically, and it appears that only one answer was lost across almost 2,000 companies. Detail: Content Snare was down for about three and a half minutes, from 21:08 to 21:12 UTC. That was 5:08pm US Eastern, or 7:08am on the 28th in Brisbane. If you were using it then, a page may have hung or asked you to sign in again. A disk failed under our main database at Amazon Web Services (AWS), where Content Snare is hosted. AWS detected the failure about 90 seconds in, the switch to the standby took 55 seconds, and the app was fully back about a minute after that. Nothing you had already saved was lost. Every other change that failed during the outage went through when retried, and we’re contacting the customer whose answer didn’t save. You don’t need to do anything. If something from around that time looks off, reply to this email and we’ll look into it. Cheers, James Co-Founder - Content Snare Content Snare, 84 Brunswick Street, Fortitude Valley QLD 4006, Australia You received this because you signed up to receive product updates. To cancel product updates, click here. To manage what emails you receive or temporarily pause emails click here . Or to cancel ALL email from me, including Content Snare updates, click here.