In short
- Steam down? Valve’s downtime FAQ names no weekly day; Team17 and a status tracker report Tuesday afternoon to evening US time (about 30 minutes per Team17, 15 to 30 per the tracker).
- If the trackers are green and Steam still fails, the fault is most likely between you and Steam, or in one game’s own servers.
- The error number says where it broke: -105 is DNS, -118 is a timeout, E502 L3 usually means store overload.
Checked against: Valve’s Steam Support downtime FAQ and Steam Dashboard’s status page.
The idea that Steam goes down every Tuesday is half true, and the missing half is the part that matters. A status tracker and at least one publisher’s support page report a weekly maintenance slot, but Valve’s own downtime FAQ never mentions Tuesdays. It says planned work happens during business hours at Valve’s Pacific-time office, is staggered across different times of day, and usually lasts less than an hour. So “it’s Tuesday” is a hunch about Steam downtime, not a diagnosis.
This guide gives you the hunch’s real numbers (the window in Pacific and Eastern time, and what three sources say about it), then a four-check routine that separates a Steam outage from a fault on your own PC, router or line. It works whether you typed “down steam” or “steampowered down”: steampowered.com is the store’s domain, and the store is only one part of Steam that can fail alone. I could not stage an outage, so nothing below is a test result. Every rule comes from Valve’s support pages, the trackers’ own documentation and the sources listed at the end, all read on 16 November 2026.
Quick start: Steam won’t connect, so run four checks in order
- Check Steam’s side. Open two status trackers on your phone’s mobile data. A red Store, Community or Client row means the fault is Valve’s: wait.
- Check your side of the line. Load an ordinary website, then the Steam store site on a second device on the same Wi-Fi.
- Reset the client. Quit Steam completely, reopen it, and restart the PC if it still hangs.
- Check the path between you and Steam. Router, firewall, ports, DNS, then any VPN or proxy.
If a tracker is red at check 1, stop there; nothing on your PC can fix Valve’s servers. The diagram folds the same logic into three questions.

When is Steam’s Tuesday maintenance? The window in PT and ET
Reports put the weekly slot on Tuesday late afternoon to evening US time, starting somewhere between about 1 and 5 PM Pacific (4 and 8 PM Eastern) and lasting 15 to 30 minutes, but Valve does not publish it. That range is my reading of the three sources below, two of which disagree by a few hours.
| Source | What it says | Pacific / Eastern |
|---|---|---|
| Valve downtime FAQ | No weekly slot. Planned work in Pacific business hours, “early morning or in the late afternoon”, staggered across the day, usually under an hour. | No day or time given |
| Team17 support page (9 May 2025) | Tuesdays, starting sometime between 1 and 3 PM Pacific, about 30 minutes. | 1–3 PM PT / 4–6 PM ET |
| Steam Dashboard status page (read 16 Nov 2026) | “Tuesday evenings US time”, usually around 00:00 UTC on Wednesday, 15–30 minutes. | Now: 4 PM PT / 7 PM ET. In summer: 5 PM PT / 8 PM ET |
The biggest takeaway: no source gives a fixed minute, so treat Tuesday afternoon and evening in the US as the time to suspect maintenance, not a schedule to plan your evening around.
Valve’s FAQ explains why the slot sits in Pacific time. It schedules planned downtime during business hours at its Pacific-time office so as many team members as possible can help if something goes wrong. It puts peak user load at around 12:00 PT and the lowest count at around 23:00 PT, and says work expected to last under an hour goes in the early morning or the late afternoon, away from that peak. A late-afternoon Pacific slot fits that rule, which is why I would trust the Tuesday pattern as a pattern but not as a promise.
Daylight saving shifts the third row. US daylight saving time ends on the first Sunday of November, so on 16 November 2026 Pacific is UTC−8 and Eastern is UTC−5, and 00:00 UTC on Wednesday is 4 PM Tuesday Pacific and 7 PM Eastern. When clocks go forward in March the same UTC time becomes 5 PM Pacific and 8 PM Eastern. Whether Valve pins the slot to UTC or to Pacific time is not published. In Europe, 00:00 UTC is 01:00 in Berlin or Warsaw on Wednesday morning in winter.
Two limits. Valve’s FAQ carries a 2021 timestamp in its page data, so it may predate current practice. And it says unplanned downtime from a hardware failure, a network problem or a provider problem “happens when it happens”, so a stall on a Friday morning is not maintenance.
Store, community or game server: which part of Steam is down?
Steam is several systems, and one can fail while the others work. Steam Dashboard probes five of them separately (Store, Community, Web API, Client and Game Coordinator), and game servers are a further layer. Matching your symptom to a layer tells you which tracker row to read.
| What you see | Part of Steam to suspect | Tracker row |
|---|---|---|
| Store pages or checkout fail; library and friends work | The store (steampowered.com) | Store |
| Profiles, discussions, Workshop or Market fail | The community site (steamcommunity.com) | Community |
| Client stuck on login, or friends and chat offline | The login side: the connection managers, the servers the client logs in through for authentication, friends and chat | Client row on Steam Dashboard (the nearest match; the page does not define the row); login servers on steamstat.us |
| Steam is fine but one multiplayer game will not match | That game’s own servers | The game’s row, where a tracker lists one |
The biggest takeaway: a single red row points to one layer, while maintenance takes several down at once. Steam Dashboard says that during weekly maintenance “the store, community, and game servers may be temporarily unavailable”. My reading is that a lone red Store row outside Tuesday is more likely overload than maintenance, since sale and launch crowds are the usual cause of store errors (see E502 L3 below).
Game servers deserve their own look. Steam Dashboard shows Counter-Strike 2, Dota 2 and Team Fortress 2 servers separately and notes that “CS2 can have issues while Steam is fine, and vice versa”. If only one game fails, a tracker’s all-green Steam row will not help you.
Which unofficial status trackers can you trust?
Valve does not publish a per-service status board that I could find. Its support pages send you to store.steampowered.com/stats, which they call the Steam Server Status page, and say that if you hit timeouts on Steam sites it is “very likely that there is a system-wide issue” (Troubleshooting Network Connectivity). The page itself is titled Steam Charts and shows users online, so a page that loads does not prove login works. For per-service answers you need an independent tracker.
| Tracker | How it knows | Use it for, and its blind spot |
|---|---|---|
| Valve’s stats page | Valve’s own page; Valve treats timeouts as a sign of a system-wide issue | The fastest official signal. Shows users online, not per-service health. |
| Steam Dashboard (steamdb.com) | Its own probes every 2 minutes against Store, Community, Web API, Client and Game Coordinator; independent of Valve | Service-by-service answer plus an outage log kept since 2 July 2026. Probes run from its servers, so its response times “reflect server-to-Steam latency rather than your personal connection”. |
| steamstat.us | Run from the SteamDatabase project; SteamMonitor holds connections to Steam servers in each datacenter; Counter-Strike status comes from Valve’s own API | A regional view of the login servers. Its README says its data endpoint is not a public API. |
| Downdetector | Crowdsourced user reports, according to StatusGator, a competitor | Catches launch-day overload (it showed a surge when Hollow Knight: Silksong went on sale). Counts complaints, so it cannot tell Steam’s fault from yours. |
The biggest takeaway: use two probing trackers and treat Downdetector as a tiebreaker. Every probe tests from its own servers, so a green board means Steam is reachable from there, not from your living room. That is why check 2 exists.
One naming trap. I read the steamdb.com page, which calls itself Steam Dashboard and says it is independent of Valve. The classic steamdb.info blocked my automated fetch, so I did not read it and cannot vouch for it. steamstat.us blocked automated fetches too, so I confirmed what it monitors only from its GitHub README, not by loading the page.
The 4 checks, in order
Check 1: Is it Steam? (about 2 minutes)
Open Steam Dashboard’s Is Steam Down page and steamstat.us on your phone’s mobile data, so the trackers load even if your home line is the problem. A red Store, Community or Client row, or a Valve stats page that times out, means stop and wait. If it is Tuesday afternoon or evening in the US, maintenance is a reasonable first suspect, though Valve does not publish the slot. Valve says planned downtime usually lasts under an hour; the trackers’ figure for the weekly slot is 15 to 30 minutes.
While you wait, Offline Mode only helps if you prepared it. Valve’s conditions: start Steam online with “Remember me” ticked, update your games, launch each one once, leave “Don’t save account credentials on this computer” unticked in Settings > Security, then choose Go Offline. Valve adds that if Steam is demanding a login “there is no option to bypass that without going online”, and that games needing a connection or an external launcher will not run. So set it up now, while Steam works.
If the store throws E502 L3, do not keep pressing Purchase. GoSunoob describes it as store overload with no fix on your side. If a sale-day checkout ends with something you did not want, the Steam refund rules (14 days, under 2 hours played) decide what you can reverse.
Check 2: Is it your connection?
Load an ordinary website on the PC. Then load the Steam store site on a second device on the same Wi-Fi, and on a phone using mobile data. Steam Dashboard’s own advice is the same: if all its services are green but Steam fails for you, restart your router or try mobile data. The results sort themselves:
- No site loads: modem, router or ISP. Reboot both, then call your provider.
- Other sites load, the store fails on every device: the path to Steam is blocked or slow (check 4).
- The store loads on the phone but not the PC: your PC or its settings (checks 3 and 4).
A timing trap: Valve notes that if Steam only misbehaves at certain hours, for example in the evenings between 5 and 11 PM, your ISP may be blocking or “shaping” the connection, and suggests testing at other hours. The Tuesday window overlaps that evening range for Eastern readers, so a recurring evening failure can be misread as maintenance. If trackers are green at the moment Steam fails for you, suspect the line before Valve.
Check 3: Reset the client
Quit Steam completely, reopen it, and restart the PC if it still hangs. Steam Dashboard says to right-click the tray icon and choose Exit on Windows; one troubleshooting guide says to end the task in Task Manager, and also suggests running Steam as administrator.
Two resets are worth knowing, with limits. Opting out of the client beta puts you back on the stable client; in my view a reasonable step if the trouble began right after an update and you are on the beta. Guides disagree on where the setting sits (Windows Report puts it on the Account tab), so look for Client Beta Participation under Settings and choose the option that opts out of all beta programs. Changing the download region (Steam > Settings > Downloads, per Steam Dashboard) only affects downloads, so it should not fix a login or a store error.
Check 4: Is something between you and Steam blocking it?
Work down this list in this order; most of it comes from Valve’s own support pages.
- Router. Valve says to reboot the modem and router first, then plug the PC straight into the modem. If Steam works that way, the router is the cause: try switching off stateful inspection, dynamic packet filtering, QoS and UPnP.
- Firewall. Valve warns that after a recent Steam update a firewall may block Steam from connecting. Remove Steam’s entries, restart Steam and re-authorise it when prompted. Disabling the firewall briefly is a test only; Valve does not recommend leaving it off.
- Ports. Valve lists what logging in and downloading need: TCP 80 and 443, plus UDP and TCP 27015–27050. University and business networks often block them, and the ports cannot be remapped to HTTP or a custom range.
- DNS. If you see -105 or -137, flush the cache with
ipconfig /flushdns(Microsoft documents it) and try a different DNS server; Help Desk Geek suggests both for -105. - VPN or proxy. Switch both off and retry; a dead proxy produces its own error (-130, below).
- Last attempt before reinstalling. The Help Desk Geek guide to the Steam-network error (check 3) also suggests adding
-tcpto the Steam shortcut’s Target field, since Steam uses UDP by default. It comes from a single guide, so treat it as low confidence.
If you do reinstall, back up the steamapps folder first, as that guide advises, and copy your save data out too: where PC games keep their saves. And when Steam connects again but a game then crashes, read the error code first.
Steam connection errors decoded: what the number tells you
Steam shows the same sentence under different numbers, and the number says where the connection failed. The message “Unable to connect to server. Server may be offline or you may not be connected to the internet” appears with Error Code 102 and with Error Code 105. I found no Valve page that decodes these numbers. The meanings below come from Chromium’s network-error list, whose numbers and descriptions match for each numbered code in the table. I am inferring that the two lists line up rather than quoting Valve, so treat the table as a working guide.

| What Steam shows | What it means | Try first |
|---|---|---|
| Error Code: -105 or -137 | -105: the host name could not be resolved. -137: a DNS error. Your lookup failed, not necessarily Steam. | Flush DNS, try another DNS server, restart the router. |
| Error Code: -102 | A connection attempt was refused. | Firewall, VPN or proxy, security software. |
| Error Code: -118 | A connection attempt timed out: nothing answered in time. | Check the trackers first (Valve treats timeouts as a system-wide signal), then router and firewall. |
| Error Code: -130 | No connection could be made to a proxy server. | Turn off the VPN or proxy. |
| E502 L3, “Something went wrong” | Overloaded or unstable store servers, usually from heavy traffic. Notebookcheck reported a Downdetector surge at the Silksong launch and quotes no Valve statement. | Nothing to fix. Wait and do not resubmit. |
| Could not connect to the Steam network | The client cannot reach Steam: your side or Valve’s. | Run checks 1 and 2, then the firewall. |
The biggest takeaway: -105 and -137 point at your DNS lookup, -118 means no answer arrived in time, and E502 L3 is the one code here that sources tie to store overload. Treat them as a working guide, and confirm with check 1 before changing settings. The Help Desk Geek guide puts the Steam-network message down to a failed connection, a glitch, Valve’s servers or a firewall.
What to do depending on how you play
| You are | Do this | Why |
|---|---|---|
| Single-player on PC | Set up Offline Mode now, while Steam works. | Valve: it needs an online first start and cannot bypass a login later. |
| Competitive multiplayer | Read your game’s own server row, not just the Steam row. | Steam Dashboard: a game can fail while Steam is fine. |
| Sale-day shopper | Wait out E502 L3 instead of resubmitting. | It is store overload; there is no fix on your side. |
| Steam Deck or other Valve hardware | Test on a wired connection, try another Wi-Fi band, and try a different authentication protocol if you use PEAP or WEP. | Valve’s own hardware network page recommends these tests. |
Valve’s hardware troubleshooting page covers the Steam Deck, Steam Machine and Steam Frame, and includes the same server-status check. On a Deck, the wired test needs a USB-C ethernet adapter. If you are new to the handheld, our Steam Deck beginner’s guide covers the basics.
FAQ
Is Steam down every Tuesday?
No promise exists. Valve’s FAQ names no weekday and says it staggers planned work, while Team17 and Steam Dashboard report a weekly Tuesday slot. A Tuesday afternoon or evening outage is a reasonable first suspect for maintenance; on another day planned work is still possible, since Valve staggers it, so check the trackers.
How long does Steam downtime last?
Valve says planned downtime usually lasts under an hour. Steam Dashboard puts the weekly slot at 15 to 30 minutes and says most outages last 5 to 30 minutes, with rare major ones running up to several hours. If your problem outlasts an hour with green trackers, it is probably not Valve.
Why does steampowered.com not load when other sites do?
Either the store is down, or something on your side is failing to reach it. A red Store row means wait; a green row plus a store that loads on your phone means check DNS, the firewall and the ports in check 4.
Can I play when Steam is down?
Only if Offline Mode was set up beforehand and the game does not need a connection or an external launcher. Otherwise a login screen cannot be skipped.
Should I reinstall Steam?
Treat it as the last resort. It does nothing for an outage, and it costs you time if the cause was DNS or a firewall rule. Back up steamapps and your saves first.
Your next step
Bookmark Steam Dashboard’s status page and steamstat.us today, and set up Offline Mode for the single-player games you care about while Steam works. Next time Steam will not connect, run the four checks in order and stop at the first red tracker. Everything here was checked on 16 November 2026; Valve’s downtime FAQ is older, so if a screen or a time does not match, trust the live tracker over this page.
Sources
- Valve. Steam Downtime and Server Maintenance. Steam Support
- Valve. Troubleshooting Network Connectivity. Steam Support
- Valve. Required Ports for Steam. Steam Support
- Valve. Using a Router with Steam. Steam Support
- Valve. Using a Firewall with Steam. Steam Support
- Valve. Offline Mode. Steam Support
- Valve. Steam Hardware – Network + Wi-Fi Troubleshooting. Steam Support
- Steam Dashboard (steamdb.com). Is Steam Down? Real-time Steam outage detector
- Steam Dashboard (steamdb.com). Steam Server Status: real-time server monitor
- SteamDatabase. steamstat.us (README). GitHub
- SteamDatabase. SteamMonitor (README). GitHub
- Team17 Support. Weekly Scheduled Steam Maintenance (9 May 2025)
- Chromium. net/base/net_error_list.h (network error codes). GitHub
- The Windows Club. Steam Error Code 102 or 137 on Windows PC
- The Windows Club. Steam Error Code 105, Unable to connect to server
- Help Desk Geek. How to Fix Steam Error Code -105
- Help Desk Geek. How to Fix a “Could not connect to the Steam network” Issue
- Notebookcheck. Steam down on Hollow Knight: Silksong release date as buyers struggle to purchase games (4 September 2025)
- GoSunoob. Something Went Wrong E502 L3, Steam Store Down Explained
- StatusGator. 5 Downdetector Alternatives: Is There a Better Way to Know if a Service Is Down?
- Microsoft. ipconfig. Microsoft Learn
- Windows Report. How to Opt in or Out of Steam Client Beta
- timeanddate.com. Daylight Saving Time 2026 in the United States
I've been playing video games for over 20 years, spanning everything from early PC titles to modern open-world games. I started Switchblade Gaming to publish the kind of accurate, well-researched guides I always wanted to find — built on primary sources, tested in-game, and kept up to date after patches. I currently focus on Minecraft and Pokémon GO.
