HTTP 502 Bad Gateway — What It Means & How to Fix It

What Does This Error Mean?

A 502 Bad Gateway error means the website you are visiting uses multiple servers behind the scenes — and one of them sent back a bad or unreadable response to another. Think of it like a relay race where one runner passed a broken baton. The front-facing server got a garbage response from the back-end server, so it showed you an error instead. This is always the website's problem, not yours.

Affected Models

All web browsers
All websites using load balancers or reverse proxies
Mobile browsers
Large and high-traffic websites

Common Causes

The website's back-end server crashed or became unreachable
The server is overloaded from too much traffic
A recent update to the website broke communication between its servers
The website's content delivery network (CDN) has an outage
Network issues between the website's own servers are causing communication failures

How to Fix It

Wait 1–2 minutes and reload the page. Many 502 errors are caused by temporary traffic spikes that resolve quickly.

Major websites like YouTube, Gmail, and Amazon occasionally show 502 errors during high traffic periods — they usually recover within minutes.
Hard refresh the page with Ctrl+F5 (Windows) or Cmd+Shift+R (Mac).

This bypasses cached content and sends a fresh request.
Check a site like downdetector.com to see if other users are reporting the same issue.

If many people are affected, it confirms the problem is on the website's end.
Clear your browser cache and cookies, then try again.

Cached error responses can sometimes stick around even after the server recovers.
Try again in 30 minutes. If the error persists after several hours, check the website's social media or status page for updates.

Serious 502 outages are usually acknowledged publicly by the website's team.

When to Call a Professional

A 502 error cannot be fixed by a visitor — it is entirely a server infrastructure problem. If the site stays down for more than a few hours, report it to the support team. Website owners should check server logs, examine the back-end service health, and review any recent deployments that may have caused the issue.

Frequently Asked Questions

What is a 'gateway' in a 502 error?

Most big websites use multiple servers. One server handles your request up front (the gateway). It then forwards that request to another server to do the actual work. If that back-end server sends back something broken or nothing at all, you see a 502.

Is my data safe if I was in the middle of something?

If you submitted a payment or form right before the error, check your email for a confirmation. Be cautious about retrying a payment — the first attempt may have gone through even if you saw the error. Check your bank statement before retrying.

Is a 502 more serious than a 500 error?

They are both server-side errors, but a 502 suggests a more complex infrastructure problem — communication between multiple servers failed. A 500 can be caused by a single small bug. Both should resolve in time.