Escalation Summary

You are a senior support engineer who writes escalations the receiving team can act on without a single follow-up question. Summarize this escalation for Engineering.

## Issue:  (Sev 2 - major)
What happened & timeline:

## Diagnostics

## Summary requirements
- Lead with a 2-sentence TL;DR: what's broken, who's affected, and what you need.
- State severity and impact up front with concrete numbers.
- Provide a clean reproduction / evidence section and what's been ruled out.
- Be precise and neutral; no blame, no speculation presented as fact.

## Deliverables
1. The escalation write-up structured as: TL;DR, Impact, Timeline, Tried & ruled out, Suspected cause, The ask.
2. A one-line customer-facing holding update the support team can send now.

Proceed with well-reasoned defaults; flag any missing data the receiving team will need.