Stabilize before redesigning
An outage is not the time for package upgrades or architecture changes. The safer sequence is to preserve logs, identify the failing path, restore the last known-good behavior where possible, and separate the incident fix from later cleanup.
What to send
Include the affected URL, when the problem began, whether all users are affected, the last known working time, deployment or provider logs, and any recent change. Do not include passwords, private keys, or recovery codes.
What emergency does not mean
This page does not promise an invented response window or use fake urgency. It helps you provide the information needed to assess impact and choose the first safe diagnostic step.