Investigate Website Health

Start in the product area that reported the symptom, then narrow the boundary before changing anything.

1. Confirm the Website and Website Environment.
2. Set the time range around the first observed failure.
3. Check Uptime for availability and response history.
4. Check Performance for loading and runtime regressions.
5. Run Site Audit for DNS, TLS, security-header, crawling, and Lighthouse evidence.
6. Check Issues for durable findings and prior work.
7. Use Operator when it is available to gather or execute supported operational work.
8. Compare the signal with Platform → Logs.

An external outage can produce performance failures, repeated alerts, and application errors at the same time. Treat the earliest independent evidence as the likely boundary; later symptoms may be consequences.

After correction, re-run the relevant check and confirm the public behavior. Silence alone is not verification.

If customer impact remains active and the boundary is unclear, open a support request.