Vercel 504: cause and troubleshooting
A Vercel function or upstream request exceeded its execution time limit before producing a response.
What to check next
Inspect function logs and traces, reduce synchronous work, optimize external calls, and move durable long-running work into a background processing system.
Use the diagnostic code and provider headers as clues, then confirm the request against origin logs and deployment telemetry. A status code can be generated by a proxy, load balancer, function platform, or origin application; the same number does not always have the same cause across providers.
Keep a CDN error from becoming a long outage
Record the request identifier, timestamp, affected hostname, and deployment when investigating an intermittent failure. SteadyNode checks public endpoints on a schedule and translates recognized upstream errors into concise diagnostic context, helping teams identify whether a failure is at the edge or origin.

