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 Nov 7, 2026, 5:37 PM 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: 5 min on Nov 3, 2026 (API, Community and News, from South America, US-East, US-Central and Southeast Asia).

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 Nov 7, 2026, 5:37 PM UTC
US-East515 msChecks passing
US-West1705 msChecks passing
Europe375 msChecks passing
Asia-Pacific1025 msChecks passing
US-Central2294 msChecks passing
Canada183 msChecks passing
UK520 msChecks passing
Southeast Asia1066 msChecks passing
Australia941 msChecks passing
South America729 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
844msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 460ms2026-10-15 UTC: p95 486ms2026-10-16 UTC: p95 483ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 864ms2026-10-20 UTC: p95 759ms2026-10-21 UTC: p95 801ms2026-10-22 UTC: p95 675ms2026-10-23 UTC: p95 631ms2026-10-24 UTC: p95 687ms2026-10-25 UTC: p95 634ms2026-10-26 UTC: p95 1.0s2026-10-27 UTC: p95 721ms2026-10-28 UTC: p95 812ms2026-10-29 UTC: p95 721ms2026-10-30 UTC: p95 781ms2026-10-31 UTC: p95 713ms2026-11-01 UTC: p95 750ms2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 783ms2026-11-04 UTC: p95 804ms2026-11-05 UTC: p95 837ms2026-11-06 UTC: p95 762ms2026-11-07 UTC: p95 844ms
Oct 9Oct 23Nov 7
US-West
2.5sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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 1.0s2026-10-15 UTC: p95 922ms2026-10-16 UTC: p95 973ms2026-10-17 UTC: p95 2.2s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.5s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 2.3s2026-10-22 UTC: p95 2.4s2026-10-23 UTC: p95 2.3s2026-10-24 UTC: p95 2.3s2026-10-25 UTC: p95 2.3s2026-10-26 UTC: p95 2.5s2026-10-27 UTC: p95 2.4s2026-10-28 UTC: p95 2.3s2026-10-29 UTC: p95 2.3s2026-10-30 UTC: p95 2.4s2026-10-31 UTC: p95 2.3s2026-11-01 UTC: p95 2.5s2026-11-02 UTC: p95 2.3s2026-11-03 UTC: p95 2.5s2026-11-04 UTC: p95 3.0s2026-11-05 UTC: p95 2.3s2026-11-06 UTC: p95 2.1s2026-11-07 UTC: p95 2.5s
Oct 9Oct 23Nov 7
Europe
803msp95 · 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-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 637ms2026-10-15 UTC: p95 630ms2026-10-16 UTC: p95 610ms2026-10-17 UTC: p95 621ms2026-10-18 UTC: p95 742ms2026-10-19 UTC: p95 851ms2026-10-20 UTC: p95 761ms2026-10-21 UTC: p95 741ms2026-10-22 UTC: p95 779ms2026-10-23 UTC: p95 696ms2026-10-24 UTC: p95 637ms2026-10-25 UTC: p95 678ms2026-10-26 UTC: p95 692ms2026-10-27 UTC: p95 727ms2026-10-28 UTC: p95 710ms2026-10-29 UTC: p95 717ms2026-10-30 UTC: p95 752ms2026-10-31 UTC: p95 704ms2026-11-01 UTC: p95 712ms2026-11-02 UTC: p95 728ms2026-11-03 UTC: p95 778ms2026-11-04 UTC: p95 817ms2026-11-05 UTC: p95 858ms2026-11-06 UTC: p95 803ms2026-11-07 UTC: p95 803ms
Oct 9Oct 23Nov 7
Asia-Pacific
2.2sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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.8s2026-10-15 UTC: p95 2.1s2026-10-16 UTC: p95 1.9s2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.5s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 2.7s2026-10-22 UTC: p95 2.3s2026-10-23 UTC: p95 2.6s2026-10-24 UTC: p95 3.6s2026-10-25 UTC: p95 1.7s2026-10-26 UTC: p95 3.1s2026-10-27 UTC: p95 3.4s2026-10-28 UTC: p95 2.5s2026-10-29 UTC: p95 2.3s2026-10-30 UTC: p95 2.4s2026-10-31 UTC: p95 2.2s2026-11-01 UTC: p95 1.8s2026-11-02 UTC: p95 2.5s2026-11-03 UTC: p95 2.7s2026-11-04 UTC: p95 2.4s2026-11-05 UTC: p95 1.6s2026-11-06 UTC: p95 2.0s2026-11-07 UTC: p95 2.2s
Oct 9Oct 23Nov 7
US-Central
3.0sp95 · latest
5s2.5s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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 1.3s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 934ms2026-10-17 UTC: p95 768ms2026-10-18 UTC: p95 854ms2026-10-19 UTC: p95 906ms2026-10-20 UTC: p95 962ms2026-10-21 UTC: p95 966ms2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 995ms2026-10-24 UTC: p95 1.3s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 2.2s2026-10-29 UTC: p95 2.0s2026-10-30 UTC: p95 2.2s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 1.9s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 3.4s2026-11-04 UTC: p95 3.2s2026-11-05 UTC: p95 3.5s2026-11-06 UTC: p95 2.6s2026-11-07 UTC: p95 3.0s
Oct 9Oct 23Nov 7
Canada
2.9sp95 · latest
5s2.5s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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 937ms2026-10-15 UTC: p95 894ms2026-10-16 UTC: p95 754ms2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 1.9s2026-10-19 UTC: p95 1.9s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 1.8s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 1.8s2026-10-24 UTC: p95 1.9s2026-10-25 UTC: p95 2.0s2026-10-26 UTC: p95 2.0s2026-10-27 UTC: p95 1.7s2026-10-28 UTC: p95 1.8s2026-10-29 UTC: p95 1.7s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 1.8s2026-11-06 UTC: p95 2.5s2026-11-07 UTC: p95 2.9s
Oct 9Oct 23Nov 7
UK
658msp95 · 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-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 467ms2026-10-15 UTC: p95 495ms2026-10-16 UTC: p95 535ms2026-10-17 UTC: p95 468ms2026-10-18 UTC: p95 734ms2026-10-19 UTC: p95 761ms2026-10-20 UTC: p95 737ms2026-10-21 UTC: p95 840ms2026-10-22 UTC: p95 969ms2026-10-23 UTC: p95 789ms2026-10-24 UTC: p95 934ms2026-10-25 UTC: p95 801ms2026-10-26 UTC: p95 752ms2026-10-27 UTC: p95 798ms2026-10-28 UTC: p95 929ms2026-10-29 UTC: p95 821ms2026-10-30 UTC: p95 899ms2026-10-31 UTC: p95 723ms2026-11-01 UTC: p95 749ms2026-11-02 UTC: p95 696ms2026-11-03 UTC: p95 769ms2026-11-04 UTC: p95 666ms2026-11-05 UTC: p95 854ms2026-11-06 UTC: p95 680ms2026-11-07 UTC: p95 658ms
Oct 9Oct 23Nov 7
Southeast Asia
1.3sp95 · 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-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.4s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.4s2026-10-20 UTC: p95 2.1s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.8s2026-10-24 UTC: p95 1.4s2026-10-25 UTC: p95 1.7s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 1.7s2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 1.5s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 2.1s2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.7s2026-11-06 UTC: p95 1.3s2026-11-07 UTC: p95 1.3s
Oct 9Oct 23Nov 7
Australia
2.3sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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.1s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 2.4s2026-10-19 UTC: p95 2.3s2026-10-20 UTC: p95 2.6s2026-10-21 UTC: p95 2.3s2026-10-22 UTC: p95 2.4s2026-10-23 UTC: p95 2.4s2026-10-24 UTC: p95 2.5s2026-10-25 UTC: p95 2.2s2026-10-26 UTC: p95 2.4s2026-10-27 UTC: p95 2.5s2026-10-28 UTC: p95 2.6s2026-10-29 UTC: p95 2.4s2026-10-30 UTC: p95 2.4s2026-10-31 UTC: p95 2.4s2026-11-01 UTC: p95 2.4s2026-11-02 UTC: p95 2.2s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 2.4s2026-11-05 UTC: p95 2.1s2026-11-06 UTC: p95 2.0s2026-11-07 UTC: p95 2.3s
Oct 9Oct 23Nov 7
South America
2.3sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-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.1s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 2.3s2026-10-22 UTC: p95 2.3s2026-10-23 UTC: p95 8.5s2026-10-24 UTC: p95 2.0s2026-10-25 UTC: p95 2.0s2026-10-26 UTC: p95 2.1s2026-10-27 UTC: p95 2.1s2026-10-28 UTC: p95 2.7s2026-10-29 UTC: p95 2.0s2026-10-30 UTC: p95 2.1s2026-10-31 UTC: p95 1.9s2026-11-01 UTC: p95 1.9s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 2.0s2026-11-06 UTC: p95 2.2s2026-11-07 UTC: p95 2.3s
Oct 9Oct 23Nov 7

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
  • CommunityUS-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
  • Connection serversUS-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
  • ImagesUS-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
  • NewsUS-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
  • Player statsUS-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: 515msstatus code: 200checked: Nov 7, 2026, 5:37 PM 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: 1705msstatus code: 200checked: Nov 7, 2026, 5:37 PM 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: 2294msstatus code: 200checked: Nov 7, 2026, 5:37 PM 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: 183msstatus code: 200checked: Nov 7, 2026, 5:36 PM 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: 729msstatus code: 200checked: Nov 7, 2026, 5:36 PM 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: 375msstatus code: 200checked: Nov 7, 2026, 5:35 PM 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: 520msstatus code: 200checked: Nov 7, 2026, 5:37 PM 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: 1025msstatus code: 200checked: Nov 7, 2026, 5:34 PM 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: 1066msstatus code: 200checked: Nov 7, 2026, 5:36 PM 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: 941msstatus code: 200checked: Nov 7, 2026, 5:35 PM 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, 5mour checks · South America and US-East and US-Central and Southeast Asia2026-11-03
Checks failing, 7mour 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-10-20
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" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

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.

How our checks compare with Steam's stated SLA

At or above your target

Our checks of Steam failed for 16 minutes over the last 30 days, which is 99.9624% 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
secondary
https://steamcommunity.com/
secondary
https://api.steampowered.com/ISteamDirectory/GetCMListForConnect/v1/?cellid=0
secondary
https://api.steampowered.com/ISteamUserStats/GetNumberOfCurrentPlayers/v1/?appid=440
secondary
https://shared.akamai.steamstatic.com/store_item_assets/steam/apps/440/header.jpg
secondary
https://api.steampowered.com/ISteamNews/GetNewsForApp/v2/?appid=440&count=1

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.