What it is
The project's API logs show a spike in 5xx responses over the last 24 hours.
Why it matters
These are requests that failed on the server, so users saw an error. A spike concentrated in time normally points at a deploy; one that is spread out points at a dependency or a resource limit.
How to fix it
Correlate the spike with your deploy timeline first — that answers it most of the time. Then group by endpoint and status: a single endpoint is a code path, a broad spread is usually the database or a connection ceiling.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.