Try to load Steampowered.com yesterday and you'd have been greeted with this message: "You've made too many requests recently. Please wait and try your request again later." No, you weren't being throttled for refreshing too aggressively. The Steam store was genuinely down, and the timing was hard to ignore: the outage hit on July 9, the same day the Steam Summer Sale ended.
The error wasn't isolated to one region or one part of the platform. SteamStat.us confirmed that both the Steam store and Steam community pages were returning "too many requests" errors simultaneously. That kind of widespread failure across two separate services points to something at the infrastructure level, not a user-side problem.
What actually went down, and what kept working
Here's the thing: not everything broke. Steam's matchmaking services stayed operational throughout the outage, meaning players already in games could keep playing without interruption. Friends lists remained visible, and the Steam client itself continued functioning for people who were already logged in.
The damage was contained to the web-facing side of Steam. Anyone trying to browse the store, check their community profile, or access Steampowered.com directly hit the wall. For players mid-session or already in the client, it was business as usual.
Dubai was the exception. Even after the broader outage cleared, SteamStat.us showed that Steam's website servers in Dubai remained down. Everyone outside that region should have been able to load the site normally once the fix rolled out.
The Summer Sale timing is hard to ignore
Valve hasn't confirmed a cause, but the circumstantial evidence is pretty compelling. The Steam Summer Sale is one of the highest-traffic events on the platform each year. On the final day of a major sale, millions of players are simultaneously browsing deals, checking wishlists, and making last-minute purchases before discounts expire.
That kind of concentrated traffic spike is exactly the sort of thing that can overwhelm rate-limiting systems and produce exactly the error players saw. Whether it was a traffic surge, a backend configuration issue, or something else entirely, Valve has not issued a public statement explaining what caused the outage.
Back online, mostly
The fix came through at around 4:33 PM PT on July 9. The "too many requests" error cleared for the vast majority of users, and the Steam store returned to normal operation. The Dubai server issue was the only lingering problem confirmed after recovery.
For players who ran into technical problems during the chaos, it's worth knowing these kinds of platform-side errors are completely separate from client-level issues. If you've been dealing with game-specific crashes or errors unrelated to this outage, our Everwind crash fix guide covers startup errors and black screens that are worth checking out. For general troubleshooting across other titles, the gaming guides hub has you covered.
Steam outages are rare enough that this one caught a lot of players off guard. The platform's reliability is generally taken for granted, which makes any downtime feel more disruptive than it might otherwise be. Keep an eye on SteamStat.us for real-time status updates if you hit issues the next time something feels off with the store.
If you're spending your post-sale downtime in other games, our Retro Rewind broken tapes guide is a solid read while you wait for your new library additions to download.
