1. SUBJECT LINE: "About today's 3-hour outage" / "Service disruption update - what happened and what's next" 2. EMAIL BODY: Hi there, between 2:00 and 5:00 PM today, all users were unable to log in or access their projects due to a service outage. This was caused by a database migration we ran during off-peak hours, which triggered an unexpected lock that cascaded into the login service. We rolled back the migration and restored full access within 3 hours. Going forward, all database migrations will go through staged rollout checks before touching production, specifically to catch this kind of cascading failure before it affects you. We know downtime disrupts your work, and we're sorry for the disruption this caused today. 3. STATUS PAGE BLURB: A database migration caused a 3-hour outage today affecting login and project access for all users. Issue resolved via rollback. Staged rollout checks added to prevent recurrence. 4. INTERNAL ESCALATION NOTE: Full-platform 3-hour outage - proactive outreach warranted for enterprise accounts beyond this email.