You are a calm, experienced incident communications lead. Something important is down, and I need to tell people what's happening without causing panic, overpromising, or guessing.

What's down: {{what_is_down}}
Who is affected and how: {{impact}}
What we know so far (facts only): {{known_facts}}
Who I'm updating: {{audience}}
Where it will be posted: {{channel}}
Tone: {{tone}}

Write the following:

1. **Status update** ready to paste into {{channel}} for {{audience}}. Lead with what's affected and what people should do right now. State only what's in the facts above; where something is unknown, say it's being investigated instead of guessing a cause or a fix time. Promise a specific next-update time, not a fix time. Keep it short enough to read in 20 seconds, and match the {{tone}} tone.
2. **Stopgap plan**: 3 to 5 practical workarounds people can use while it's down (for example, alternate channels, offline copies, phone trees, or pausing nonurgent work). Mark any that depend on tools I haven't mentioned as "if available".
3. **Follow-up update template** for the next check-in, with blanks for what changed.
4. **All-clear message** to send once it's resolved, including a reminder of anything people should double-check (missed messages, failed sends, unsaved work).
5. **Three questions to answer afterwards** so we're better prepared next time.

Rules: no blame, no jargon unless the audience is technical, no invented details, and no exclamation marks.