Skip to content

Outage tracker / Steam

Is Steam down?

I'm having a problem

Checks passingchecked moments ago

Our checks of Steam pass from all 10 regions we check.

As of Oct 14, 2026, 4:53 AM UTC, RealUptime's checks of Steam passed in all 10 regions that returned a reading.

Front-door and live API checks

Last time our checks failed from two or more distant regions: 4 min on Oct 13, 2026 (API, from Europe, Asia-Pacific and Australia).

Email me when our checks of Steam fail from two or more distant regions

One email when our checks of Steam fail from two or more distant regions, and one when they pass, after you confirm the address. No account, no card.

This is our own reading from outside. It is not Steam's official status.

our check readinglive · checked Oct 14, 2026, 4:53 AM UTC
US-East279 msChecks passing
US-West572 msChecks passing
Europe552 msChecks passing
Asia-Pacific345 msChecks passing
US-Central295 msChecks passing
Canada172 msChecks passing
UK343 msChecks passing
Southeast Asia618 msChecks passing
Australia424 msChecks passing
South America874 msChecks passing
their status pagetheir claim, not our reading

Steam publishes no status feed we can read, so the only reading here is our check reading on the left.

Steam response time, by region

US-East
452msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 425ms2026-09-16 UTC: p95 473ms2026-09-17 UTC: p95 496ms2026-09-18 UTC: p95 465ms2026-09-19 UTC: p95 442ms2026-09-20 UTC: p95 430ms2026-09-21 UTC: p95 459ms2026-09-22 UTC: p95 470ms2026-09-23 UTC: p95 501ms2026-09-24 UTC: p95 557ms2026-09-25 UTC: p95 472ms2026-09-26 UTC: p95 446ms2026-09-27 UTC: p95 434ms2026-09-28 UTC: p95 492ms2026-09-29 UTC: p95 495ms2026-09-30 UTC: p95 462ms2026-10-01 UTC: p95 463ms2026-10-02 UTC: p95 601ms2026-10-03 UTC: p95 456ms2026-10-04 UTC: p95 405ms2026-10-05 UTC: p95 393ms2026-10-06 UTC: p95 934ms2026-10-07 UTC: p95 424ms2026-10-08 UTC: p95 424ms2026-10-09 UTC: p95 435ms2026-10-10 UTC: p95 434ms2026-10-11 UTC: p95 448ms2026-10-12 UTC: p95 428ms2026-10-13 UTC: p95 378ms2026-10-14 UTC: p95 452ms
Sep 15Sep 29Oct 14
US-West
859msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 673ms2026-09-16 UTC: p95 567ms2026-09-17 UTC: p95 498ms2026-09-18 UTC: p95 527ms2026-09-19 UTC: p95 796ms2026-09-20 UTC: p95 726ms2026-09-21 UTC: p95 767ms2026-09-22 UTC: p95 962ms2026-09-23 UTC: p95 604ms2026-09-24 UTC: p95 897ms2026-09-25 UTC: p95 728ms2026-09-26 UTC: p95 815ms2026-09-27 UTC: p95 813ms2026-09-28 UTC: p95 790ms2026-09-29 UTC: p95 778ms2026-09-30 UTC: p95 804ms2026-10-01 UTC: p95 930ms2026-10-02 UTC: p95 961ms2026-10-03 UTC: p95 887ms2026-10-04 UTC: p95 820ms2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 939ms2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 982ms2026-10-10 UTC: p95 842ms2026-10-11 UTC: p95 662ms2026-10-12 UTC: p95 901ms2026-10-13 UTC: p95 990ms2026-10-14 UTC: p95 859ms
Sep 15Sep 29Oct 14
Europe
689msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 661ms2026-09-16 UTC: p95 640ms2026-09-17 UTC: p95 653ms2026-09-18 UTC: p95 641ms2026-09-19 UTC: p95 607ms2026-09-20 UTC: p95 610ms2026-09-21 UTC: p95 630ms2026-09-22 UTC: p95 608ms2026-09-23 UTC: p95 690ms2026-09-24 UTC: p95 703ms2026-09-25 UTC: p95 685ms2026-09-26 UTC: p95 673ms2026-09-27 UTC: p95 671ms2026-09-28 UTC: p95 700ms2026-09-29 UTC: p95 645ms2026-09-30 UTC: p95 641ms2026-10-01 UTC: p95 673ms2026-10-02 UTC: p95 740ms2026-10-03 UTC: p95 690ms2026-10-04 UTC: p95 617ms2026-10-05 UTC: p95 613ms2026-10-06 UTC: p95 636ms2026-10-07 UTC: p95 697ms2026-10-08 UTC: p95 649ms2026-10-09 UTC: p95 645ms2026-10-10 UTC: p95 623ms2026-10-11 UTC: p95 585ms2026-10-12 UTC: p95 620ms2026-10-13 UTC: p95 575ms2026-10-14 UTC: p95 689ms
Sep 15Sep 29Oct 14
Asia-Pacific
1.6sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 1.8s2026-09-16 UTC: p95 1.7s2026-09-17 UTC: p95 1.6s2026-09-18 UTC: p95 1.6s2026-09-19 UTC: p95 1.8s2026-09-20 UTC: p95 1.7s2026-09-21 UTC: p95 1.6s2026-09-22 UTC: p95 2.0s2026-09-23 UTC: p95 2.0s2026-09-24 UTC: p95 810ms2026-09-25 UTC: p95 1.9s2026-09-26 UTC: p95 1.9s2026-09-27 UTC: p95 1.9s2026-09-28 UTC: p95 1.7s2026-09-29 UTC: p95 1.7s2026-09-30 UTC: p95 1.9s2026-10-01 UTC: p95 1.8s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.7s2026-10-04 UTC: p95 1.7s2026-10-05 UTC: p95 1.9s2026-10-06 UTC: p95 2.2s2026-10-07 UTC: p95 1.8s2026-10-08 UTC: p95 1.8s2026-10-09 UTC: p95 1.7s2026-10-10 UTC: p95 1.8s2026-10-11 UTC: p95 1.7s2026-10-12 UTC: p95 1.6s2026-10-13 UTC: p95 1.7s2026-10-14 UTC: p95 1.6s
Sep 15Sep 29Oct 14
US-Central
841msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 752ms2026-09-16 UTC: p95 706ms2026-09-17 UTC: p95 768ms2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.3s2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 800ms2026-09-23 UTC: p95 776ms2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 823ms2026-09-26 UTC: p95 846ms2026-09-27 UTC: p95 747ms2026-09-28 UTC: p95 556ms2026-09-29 UTC: p95 643ms2026-09-30 UTC: p95 997ms2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 538ms2026-10-03 UTC: p95 719ms2026-10-04 UTC: p95 595ms2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 620ms2026-10-08 UTC: p95 732ms2026-10-09 UTC: p95 673ms2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 823ms2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 670ms2026-10-14 UTC: p95 841ms
Sep 15Sep 29Oct 14
Canada
824msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 641ms2026-09-16 UTC: p95 630ms2026-09-17 UTC: p95 678ms2026-09-18 UTC: p95 950ms2026-09-19 UTC: p95 552ms2026-09-20 UTC: p95 604ms2026-09-21 UTC: p95 617ms2026-09-22 UTC: p95 613ms2026-09-23 UTC: p95 541ms2026-09-24 UTC: p95 805ms2026-09-25 UTC: p95 760ms2026-09-26 UTC: p95 747ms2026-09-27 UTC: p95 917ms2026-09-28 UTC: p95 684ms2026-09-29 UTC: p95 702ms2026-09-30 UTC: p95 690ms2026-10-01 UTC: p95 664ms2026-10-02 UTC: p95 1.0s2026-10-03 UTC: p95 788ms2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 881ms2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 828ms2026-10-09 UTC: p95 817ms2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 898ms2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 799ms2026-10-14 UTC: p95 824ms
Sep 15Sep 29Oct 14
UK
457msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 438ms2026-09-16 UTC: p95 463ms2026-09-17 UTC: p95 574ms2026-09-18 UTC: p95 556ms2026-09-19 UTC: p95 552ms2026-09-20 UTC: p95 546ms2026-09-21 UTC: p95 498ms2026-09-22 UTC: p95 547ms2026-09-23 UTC: p95 556ms2026-09-24 UTC: p95 534ms2026-09-25 UTC: p95 535ms2026-09-26 UTC: p95 545ms2026-09-27 UTC: p95 500ms2026-09-28 UTC: p95 505ms2026-09-29 UTC: p95 526ms2026-09-30 UTC: p95 564ms2026-10-01 UTC: p95 580ms2026-10-02 UTC: p95 493ms2026-10-03 UTC: p95 483ms2026-10-04 UTC: p95 503ms2026-10-05 UTC: p95 500ms2026-10-06 UTC: p95 492ms2026-10-07 UTC: p95 478ms2026-10-08 UTC: p95 513ms2026-10-09 UTC: p95 543ms2026-10-10 UTC: p95 490ms2026-10-11 UTC: p95 546ms2026-10-12 UTC: p95 530ms2026-10-13 UTC: p95 557ms2026-10-14 UTC: p95 457ms
Sep 15Sep 29Oct 14
Southeast Asia
1.5sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 876ms2026-09-17 UTC: p95 867ms2026-09-18 UTC: p95 971ms2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.7s2026-09-22 UTC: p95 1.9s2026-09-23 UTC: p95 2.2s2026-09-24 UTC: p95 1.9s2026-09-25 UTC: p95 2.2s2026-09-26 UTC: p95 1.9s2026-09-27 UTC: p95 2.1s2026-09-28 UTC: p95 1.9s2026-09-29 UTC: p95 1.6s2026-09-30 UTC: p95 1.8s2026-10-01 UTC: p95 1.7s2026-10-02 UTC: p95 1.6s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.6s2026-10-06 UTC: p95 1.4s2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.5s
Sep 15Sep 29Oct 14
Australia
1.3sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 973ms2026-09-17 UTC: p95 962ms2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 927ms2026-09-23 UTC: p95 911ms2026-09-24 UTC: p95 935ms2026-09-25 UTC: p95 998ms2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 966ms2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.5s2026-10-06 UTC: p95 1.4s2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 957ms2026-10-14 UTC: p95 1.3s
Sep 15Sep 29Oct 14
South America
1.2sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.6s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.7s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.0s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.2s
Sep 15Sep 29Oct 14

Check your own site while you wait on Steam

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Steam. It cannot diagnose Steam's own systems.

What we measured, function by function

Steam answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 279msstatus code: 200checked: Oct 14, 2026, 4:52 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Steam normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 572msstatus code: 200checked: Oct 14, 2026, 4:53 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Steam normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 295msstatus code: 200checked: Oct 14, 2026, 4:50 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Steam normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 172msstatus code: 200checked: Oct 14, 2026, 4:49 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Steam normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 874msstatus code: 200checked: Oct 14, 2026, 4:50 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Steam normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 552msstatus code: 200checked: Oct 14, 2026, 4:53 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Steam normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 343msstatus code: 200checked: Oct 14, 2026, 4:53 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Steam normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 345msstatus code: 200checked: Oct 14, 2026, 4:53 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Steam normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 618msstatus code: 200checked: Oct 14, 2026, 4:52 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Steam normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 424msstatus code: 200checked: Oct 14, 2026, 4:52 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Steam normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Steam, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We started counting reports for Steam on September 23, 2026.

Recent probe events

Checks failing, 4mour checks · Europe and Asia-Pacific and Australia2026-10-13
Checks failing, 6mour checks · South America and US-East and UK and US-Central and US-West and Australia and Canada2026-10-06
Checks failing, 6mour checks · Europe and Australia and Canada2026-09-29
Checks failing, 15mour checks · Europe and South America and US-East and UK and Asia-Pacific and US-Central and Southeast Asia and US-West and Australia and Canada2026-09-22
Checks failing, 5mour checks · US-East and Asia-Pacific and US-West and Australia2026-09-15
Checks failing, 6mour checks · Europe and US-East and UK and Asia-Pacific and US-West2026-09-08

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Steam since August 8, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Steam covering any window you pick, with our check readings and Steam's own claim at the time, side by side.

Full check history for Steam: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

Steam uptime by RealUptime's checksLive, from this page's own readings.
[![Steam uptime by RealUptime's checks](https://realuptime.io/outages/steam/badge.svg?days=30)](https://realuptime.io/outages/steam)
<a href="https://realuptime.io/outages/steam"><img src="https://realuptime.io/outages/steam/badge.svg?days=30" alt="Steam uptime by RealUptime's checks"></a>

The badge shows the share of our checks that passed over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Steam down?", https://realuptime.io/outages/steam. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

How our checks compare with Steam's stated SLA

At or above your target

Our checks of Steam failed for 36 minutes over the last 30 days, which is 99.9154% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from Steam's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.steampowered.com/ISteamWebAPIUtil/GetServerInfo/v1/
secondaryfunctional: live API
https://store.steampowered.com/api/appdetails?appids=440

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: api.steampowered.com

RealUptime is not affiliated with Steam; the name identifies what we checked, and nothing here speaks for Steam's own team. We send a single web request to Steam from 10 regions on our own schedule and time the response. We do not see inside Steam's systems, do not use an account or real transaction, and are not the same signal Steam's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Steam is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.