E502 L2 — Steam Store Error
"We were unable to service your request. Please try again later. E502 L2" appears when buying a game, opening the cart, or loading store pages. It means Steam's storefront servers are overloaded — it's a Valve-side problem, not your account and not your PC.
Instant answer: check steamstat.us first. If the store graph is red, E502 L2 is a live Steam outage and the only real fix is waiting — typically under 30 minutes for routine hiccups, a few hours on major launch days.
What the code means
| Part | Meaning |
|---|---|
| E502 | HTTP 502 Bad Gateway — a Steam edge server couldn't get a response from the store backend. Sibling code E502 L3 is the same failure on a different internal hop; the fixes are identical. |
| L2 / L3 | Internal location tags for which storefront layer failed. Not an error on your machine, not a ban, not a regional block. |
| When it spikes | Big game launches, seasonal sale openings, major free weekends and the weekly Tuesday maintenance window. |
Fix checklist
Run these in order. Most E502 L2 errors clear at step 1.
- 1Confirm it's a Steam-side outage
Open
steamstat.usor Downdetector's Steam page. Red graphs on Store or Community = wait it out. Nothing local will help. - 2Fully exit and relaunch Steam
System tray → right-click Steam icon → Exit. Closing the window alone leaves the client running.
- 3Clear a stuck purchase
If E502 L2 hit mid-checkout, the order may sit as pending. Account details → cancel the pending purchase → place it again.
- 4Clear the download cache
Steam → Settings → Downloads → Clear Download Cache, then sign back in and retry the store.
- 5Try the browser store
When the client errors,
store.steampowered.comin a browser often still loads — purchases made there land in the same library. - 6Only if trackers show Steam is fine
Restart your router, disable VPN/proxy, or test another network. A VPN exit node hammered by other users can trigger 502s of its own.
What NOT to do
Related Steam errors
| Code / message | What it is |
|---|---|
| E502 L3 | Same storefront overload as E502 L2 — identical cause, identical fixes. |
| "Requires some maintenance" | Different problem: sign-in/service error, not the store. See the Steam service error guide. |
| Error 118 / 105 | Connection-level failures reaching Steam at all — usually local network, ISP or firewall, unlike E502 which starts on Valve's side. |