The server, while acting as a gateway, received an invalid response from the upstream server.
A proxy or load balancer tried to forward your request to another server, but that server gave a bad response.
Backend server crashed
Backend server overloaded
Network issues between servers
Deployment in progress
DNS resolution failure
Wait and retry (often transient)
Check if backend services are running
Verify network connectivity
Check deployment status
DevConsole shows request timing to identify where delays occur. Useful for debugging gateway issues.
Debug it with DevConsole — $29A proxy or load balancer tried to forward your request to another server, but that server gave a bad response.
Wait and retry (often transient) Check if backend services are running Verify network connectivity Check deployment status
No, 502 is a server error. This means the issue is on the server side, not with your request.