Steam store search not working: what is actually down

Type anything into the Steam store's search box this evening and you may get a page headed "Oops, sorry!" with one line underneath: there was a problem communicating with the Steam servers. Then you check whether Steam is down, every tracker tells you it is fine, and you start wondering what is wrong with your connection.

Nothing was wrong with your connection. Steam store search not working was real, it ran for about an hour and a half, and the reason the trackers disagreed is more interesting than the outage itself.

These are our own measurements, taken from outside any Steam account, on the evening of 15 September 2026.

Update, 22:25 UTC: Steam has recovered. Store search is returning results again, the community is answering normally, and specials and charts are back — every surface we had measured as broken is now healthy. The outage ran roughly from 20:50 to 22:25 UTC. What follows is what we recorded while it was happening, kept as written; the diagnosis of why the trackers missed it is the part that outlives the incident.

Valve's own titles sit behind the same client and Web API services SteamDB has flagged. (Official Steam screenshot)

Why Steam store search not working does not register as an outage

An uptime monitor asks a URL for its status code. Anything in the 200s means healthy, and it moves on. That is a perfectly sensible design until a service starts answering with an error page wrapped in a success code.

Which is exactly what the store search is doing. Requesting the search endpoint returns HTTP 200. The body of that 200 is the "Oops, sorry" screen. To a monitor the request succeeded; to a human the site is broken. So the dashboards report Steam at a hundred percent while thousands of people cannot find a game.

The store's front page has the same status code and is genuinely fine, which is what most trackers are actually sampling. Search is a different backend, and it is the one that is failing.

What is down and what is not

We checked each surface individually rather than trusting a single green light. As of this evening:

• Store search — returns 200, serves the error page. Broken.
• Steam Community — every path returns 503 Service Unavailable, consistently, on repeated attempts. Down.
• Store specials and charts — HTTP 500. Down.
• Store front page — 200 and fully rendered. Up.
• Individual game pages — 200. Up.
• The store's public price API — 200. Up.
• The Steam Web API — responds, though SteamDB has it flagged.

That is an unusual shape. It is not a platform falling over; it is a set of specific services failing while the ones next to them carry on. If you can open a game's store page from a link but cannot search your way to it, this is why.

Store pages open normally from a direct link even while search refuses to work. (Official Steam screenshot)

SteamDB has it; the generic trackers do not

SteamDB's status tool lists an active incident opened at 22:02 UTC on 15 September, covering the client, the community and the Web API. Its page refreshes every sixty seconds and it is the only monitor we found that had caught this, because it probes individual Steam services rather than pinging one address.

For context, the same tool puts the Steam Store at 99.973% uptime across 2026 — about forty-six minutes of downtime all year — and the Community at 99.944%, roughly ninety-four minutes. Steam is genuinely very reliable. That is precisely why an evening like this catches people out: the assumption that it is your end is usually correct.

Valve does not run a public status page and historically does not comment on these. During a much larger outage on Christmas Eve last year, when the store, community and Web APIs all went dark together and one tracker logged more than six thousand reports inside fifteen minutes, there was no official statement either — the service simply came back over the following hours.

What you can and cannot do right now

Before you reinstall anything or start editing DNS settings, here is what actually still works:

• You can open any store page you have a direct link to, read its description, and see its price.
• You can launch and play single-player games you already own. The client may complain at startup; offline mode exists for this.
• You cannot reliably search the store, browse specials, or open charts.
• You cannot use the community: profiles, forums, guides, workshop and the market are all returning 503.
• You may not be able to complete a purchase cleanly, which matters more than it sounds.

Counter-Strike 2's launch trailer, mirrored by GameSpot.

Owned games still launch; it is the store and community layers that are failing. (Official Steam screenshot)

Do not panic-buy during an outage

This is the one piece of advice worth taking away. When payment and entitlement services are unsteady, a purchase can charge your card and take longer than usual to appear in your library, or fail after the money has moved. Both resolve on their own, but "resolve on their own" can mean a day of not knowing.

If a sale is genuinely ending tonight, it is still better to wait an hour than to submit the same order three times because the confirmation never arrived — every attempt is a real transaction. And if something does go wrong, Steam's refund rules are clear enough and are unaffected by any of this; we have written up what qualifies for a refund separately.

The broader point: a discount you find during an outage is almost never worth rushing. Steam's discount cycle is predictable, and our sales calendar shows when the next real window opens. Very little that is on offer tonight will be gone forever tomorrow.

Where to look in the meantime

If you only wanted to check what something costs, you do not need Steam's search to be working. Price comparison sites keep their own catalogues, so ours is unaffected — you can browse the full catalogue, check today's deals or see what has just dropped, and each game page carries its price across every store we track, not just Steam.

Worth saying plainly: our price data comes from Steam's public API, which is one of the services still responding. If that goes too, our Steam prices will go stale like everyone else's. It has not, and they have not.

Games you already own launch fine; it is discovery and community that are broken. (Official Steam screenshot)

If you were hoping to try something new tonight and the store will not cooperate, the free-to-play route needs no shopping at all — Counter-Strike 2 and Dota 2 are free and already on the platform, and the wider free-games guide covers the giveaways running elsewhere this week.

The bottom line

On the evening of 15 September 2026, Steam store search, the community and the store's specials and charts pages failed for roughly ninety minutes, while the front page, individual game pages and the public price API kept working throughout. SteamDB opened an incident at 22:02 UTC covering the client, community and Web API. Valve said nothing, which is normal for Valve.

It is not your router, your region or your account. There was nothing to fix at your end and nothing useful to reinstall. It resolved in about an hour and a half, which is how these usually go — and the rule that matters next time is the same one: do not put an order through three times because the confirmation page never loaded.

The lasting point is the measurement problem. A service that answers with an error page inside an HTTP 200 is invisible to every monitor that only reads status codes, which is most of them. When a site is plainly broken in front of you and every tracker says it is fine, that mismatch is itself the evidence — not a reason to doubt yourself.