"Steam is down" almost never means the whole of Steam is down. Steam is a stack of loosely-coupled services — the store website, the connection managers your client logs into, the download CDN, per-game server backends, and the login/auth layer — and they fail independently. A stalled download and a "can't sign in" error are different outages with different fixes, so the first job is to figure out which piece broke.
The parts of Steam that fail separately ¶
- The store (store.steampowered.com) — the website. Can be down while the client works fine.
- The Steam network / connection managers (CMs) — what your desktop client connects to for friends, chat, and cloud. When these struggle, the client shows "Steam is having trouble connecting."
- The content / download CDN — game downloads and updates. Slow or stalled downloads while everything else works points here.
- Login / auth (Steam + Steam Guard) — sign-in and two-factor. An auth incident locks people out even though games and store are up.
- Per-game servers — CS2, Dota, TF2, etc. run on their own backends; one game's matchmaking can be down while Steam itself is perfectly healthy.
Steam also has a famously heavy weekly maintenance window (Tuesday afternoons, US Pacific), when the network briefly drops for many users by design — not an outage, just routine.
The check ¶
- Probe Steam from four regions. Check store.steampowered.com from US East, US West, Europe, and Asia. All four failing is a real store outage; a mixed result is regional. This isolates "Steam is down" from "my ISP can't reach Steam."
- Separate the client from the store. If the store website loads but your client won't connect, it's a Steam-network (CM) problem, not the website. If the client is fine but a specific game won't matchmake, it's that game's servers.
- Check the game hub + the game itself. For a specific title, the game-server status hub and a direct query beat guessing. For a server you can address directly, an A2S_INFO probe is the fastest smoke test of whether it's actually up.
The game vs. Steam vs. your ISP ¶
| What you see | Likely component | What to do |
|---|---|---|
| Store website won't load | Store front-end | Check regions; if global, wait it out. |
| Client "trouble connecting" | Steam network (CMs) | Check for the Tuesday maintenance window; otherwise wait. |
| Downloads stuck at 0 B/s | Content CDN | Change your download region in settings. |
| Can't sign in / Steam Guard | Auth | Wait; don't spam login attempts. |
| One game won't matchmake | That game's servers | Check the game hub, not Steam. |
| Only you affected | Local / ISP | Flush DNS, try another network. |
If it's your connection, not Steam ¶
When all four regions reach Steam but you can't, it's local. Steam's client uses specific ports and a persistent connection that firewalls, VPNs, and some ISPs interfere with. Quick tests: load the store in a browser (isolates the client), try a mobile hotspot (isolates your router/ISP), switch your download region in Steam settings if only downloads are broken, and flush DNS. If store pages load on cellular but not home Wi-Fi, the block is on your network.
FAQ ¶
Is Steam down for everyone or just me?
Probe store.steampowered.com from multiple regions. If every region fails, it's a real outage; if they all succeed but you can't connect, it's your network or ISP. Remember Steam's parts fail independently — the store can be down while the client works, and one game's servers can be down while Steam is fine.
Why do my Steam downloads stall when everything else works?
That's the content-delivery (CDN) layer, not Steam as a whole. The most common fix is changing your download region in Steam settings — a congested or degraded regional cache stalls downloads while the store, chat, and games keep working normally.
Steam drops every Tuesday — is that an outage?
No. Steam runs routine maintenance on Tuesday afternoons (US Pacific), and the network briefly becomes unavailable for many users by design. It's short and expected. If your problem lines up with that window, wait a few minutes rather than troubleshooting.