Checked — last confirmed 5 minutes ago
Their status source has not responded to us recently. It may well be fine; we will not tell you it is when we cannot see it.
8 separate problems in the last 48 hours, most recently 8 hours ago.
This longer record is here so the 48-hour picture above can mean something — without it we could tell you a problem happened, but not whether that is normal for Steam.
The longest outage we have on record ran 2h 45m. We have only been recording Steam for 3 days, so treat these figures as provisional.
| Started | Lasted | Severity | What happened |
|---|---|---|---|
| 2026-08-01 20:30 UTC | 1h 35m | having problems | We measured HTTP 200 in 3034 ms from the edge |
| 2026-08-01 17:40 UTC | 2h 45m | having problems | We measured HTTP 403 in 3109 ms from the edge |
| 2026-08-01 17:20 UTC | 15 min | having problems | We measured HTTP 200 in 3396 ms from the edge |
| 2026-08-01 16:40 UTC | 35 min | having problems | We measured HTTP 200 in 3143 ms from the edge |
| 2026-08-01 15:45 UTC | 25 min | having problems | We measured HTTP 403 in 914 ms from the edge |
| 2026-08-01 15:00 UTC | 5 min | having problems | We measured HTTP 403 in 43 ms from the edge |
| 2026-08-01 14:20 UTC | 5 min | having problems | We measured HTTP 403 in 208 ms from the edge |
| 2026-08-01 03:05 UTC | 10 min | having problems | We measured HTTP 403 in 33 ms from the edge |
Valve publishes no machine-readable status feed at all. Every site claiming to show "Steam status" is either running its own probes or scraping a community project. We probe Steam's public endpoints from Cloudflare's edge and report what we measured — not Valve's own view, because there isn't one.
This is the one entry on the board where a green light means "we could reach Steam", not "Valve says Steam is healthy". We label it as our own measurement everywhere it appears, because the distinction genuinely matters — reachable and working are not the same thing.
Status pages report the vendor's view of their own service, and they lag real
outages — often by many minutes, sometimes by hours, because a human usually has to
confirm before anything is posted. They also can't see the two things most likely to
be wrong at your end.
The first is your own connection under load. A line that idles at 20 ms can
jump to 300 ms the moment something starts uploading, which drops you from sessions
and looks exactly like a server fault. Your plan speed says nothing about this; it's
called bufferbloat and almost nobody measures it.
The second is where everyone else in your group is. A service can be healthy in your
region and unwell in theirs, and if one person is hosting, their problem is everyone's
problem.
Steam's own client has a downloads page showing your connection to their content servers, which tells you more about download problems than any external status site can.
Steam being fine where you are does not mean it is fine for everyone in your group. The live dashboard resolves status against each person's own region, and will tell you which of your friends is in an affected area — plus who has the connection to host, which is usually a different question from who has the fastest plan.