Back to tools

Steam API Status & Ping Checker

Check whether the Steam Web API, Steam Community, Steam Store, the game-server query protocol, and Steam's login/content servers are up — and how fast each is responding right now.

Demo mode — this tool's live backend is not connected yet. Results shown are illustrative.

Live monitor (mock)

Not checked yet

Steam Web API

api.steampowered.com

Checking…
Response time—
24h historynow →
What breaks for your server when this is downPlayer-stat lookups, inventory reads, and any plugin or website that authenticates players or pulls stats through the Web API stop working. Your server itself keeps running fine — this is an auth/data-layer outage, not a server outage.

Steam Community

steamcommunity.com

Checking…
Response time—
24h historynow →
What breaks for your server when this is downProfile pages, groups, and Steam OpenID logins used by web admin panels and community sites stop resolving. Players already connected in-game are unaffected.

Steam Store

store.steampowered.com

Checking…
Response time—
24h historynow →
What breaks for your server when this is downDLC and app-ownership checks slow down or start timing out. Rarely affects a running Rust server directly, unless plugins gate content behind a live store-ownership lookup.

Game Server Query (A2S)

UDP query protocol — used by the in-game server browser & BattleMetrics-style tools

Checking…
Response time—
24h historynow →
What breaks for your server when this is downThis is the one that actually hurts: A2S is what the in-game server browser (and third-party trackers) use to list your server. When it’s down, your server can be fully online with players connected, and still disappear from the browser — because queries time out, not because anything crashed. Don’t restart your server chasing this one; check A2S status first.

Steam CMS / Login

Steam content manifest & client login servers

Checking…
Response time—
24h historynow →
What breaks for your server when this is downNew connections fail outright: players can’t authenticate with Steam, so nobody can join ANY server, including yours, until this recovers. This is the one Steam-side outage that looks exactly like "my server is down" from a player’s point of view — but isn’t.

Reading the states

Up, degraded, down — and why the endpoint matters

Steam isn't one service. Each of these fails independently, and each failure looks different from inside your server.

UpResponding normally within expected latency.
DegradedResponding, but slow or intermittently failing.
DownNot responding, or failing consistently.

Before you blame Steam

Is it just me?

A quick self-check before assuming a Steam-wide outage — this list is not sent anywhere.

Recent incidents (demo)

Incident history

Canned example entries showing the shape of the real incident feed once the backend exists.

  • A2S query timeouts increased for roughly 40 minutes

    Game Server Query (A2S) · 6 h ago

  • Elevated Store latency during a sale event

    Steam Store · 18 h ago

  • <script>alert(1)</script> spike in login failures (demo)

    Steam CMS / Login · 30 h ago

Once you've ruled out Steam's own endpoints, the next question is whether your own box is actually reachable from the internet.

Check your server ports directly with the Open Port Checker.

Running your own game server?

Wespner game servers with DDoS protection, NVMe drives and activation within minutes.

Browse hosting