Skip to content

Outage tracker

Steam: probe event history

The last 24 hours in detail, 90 days of check results, a 12-month summary, our own probe event log, Steam's declared record, and how the two compare.

← Back to Steam's check readings

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.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Steam's own status page declared. Below it, any public chatter we saw about Steam and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Steam's own status page declared. Three records side by side; none of them changes another.

Our probes, api (primary)
Our probes, community
Our probes, connection servers
Our probes, images
Our probes, news
Our probes, player stats
Unverified user reportsNo reports about Steam in the last 24 hours, which is not evidence that nothing is wrong.
Steam's status pageSteam publishes no status feed we can read, so there is nothing to show here.

Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Steam's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Steam next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

  • Bluesky posts1 in the last hour (prior day averaged 1.4/hour)

Checks passing by region

Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionChecks passingProbes recorded
US-East99.94%52700
US-West99.93%51939
Europe99.92%49654
Asia-Pacific99.89%44633
US-Central99.91%23156
Canada99.93%23191
UK99.90%22926
Southeast Asia99.92%22390
Australia99.87%22447
South America99.50%22948

Monthly summary

Tracking Steam since Aug 8, 2026. In that time our checks failed from two or more distant regions in 8 probe events, 55 min in total. Months before that date are not tracked and carry no figure.

MonthUptime by our checksProbe eventsTime failing
Dec 2025not tracked
Jan 2026not tracked
Feb 2026not tracked
Mar 2026not tracked
Apr 2026not tracked
May 2026not tracked
Jun 2026not tracked
Jul 2026not tracked
Aug 2026 from Aug 8, 2026100%00 min
Sep 202699.92%433 min
Oct 202699.96%317 min
Nov 202699.94%15 min

Uptime by our checks is the share of each month in which no probe event was open for Steam. An event opens only when our checks fail from two or more distant regions, meaning regions on different continents. One that nothing else backs stops counting as an outage after 6 hours, and after 48 hours we treat our check as broken. An event that fails these rules is retracted, kept, and listed on the corrections page. An event that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and Steam's own status page contribute nothing to these figures.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime.

Our probe event log

Every probe event for Steam in the last 90 days, or since we started checking it if that is more recent. This list is probe-only: Steam's own declared incidents appear further down this page in their own attributed section, never merged with what our checks show here. User reports live on the live page, in their own labeled block.

Nov 3, 2026, 10:58 PM UTC to Nov 3, 2026, 11:03 PM UTC5 min
multiple regions
US-East: failing from Nov 3, 2026, 10:58 PM UTC, recovered Nov 3, 2026, 11:01 PM UTCUS-Central: failing from Nov 3, 2026, 10:58 PM UTC, recovered Nov 3, 2026, 11:02 PM UTCSoutheast Asia: failing from Nov 3, 2026, 10:58 PM UTC, recovered Nov 3, 2026, 11:03 PM UTCSouth America: failing from Nov 3, 2026, 10:59 PM UTC, recovered Nov 3, 2026, 11:03 PM UTC
Oct 20, 2026, 10:02 PM UTC to Oct 20, 2026, 10:09 PM UTC7 min
multiple regions
US-East: failing from Oct 20, 2026, 10:04 PM UTC, recovered Oct 20, 2026, 10:05 PM UTCUS-West: failing from Oct 20, 2026, 10:03 PM UTC, recovered Oct 20, 2026, 10:05 PM UTCEurope: failing from Oct 20, 2026, 10:03 PM UTC, recovered Oct 20, 2026, 10:05 PM UTCAsia-Pacific: failing from Oct 20, 2026, 10:04 PM UTC, recovered Oct 20, 2026, 10:07 PM UTCUS-Central: failing from Oct 20, 2026, 10:02 PM UTC, recovered Oct 20, 2026, 10:06 PM UTCCanada: failing from Oct 20, 2026, 10:04 PM UTC, recovered Oct 20, 2026, 10:08 PM UTCUK: failing from Oct 20, 2026, 10:03 PM UTC, recovered Oct 20, 2026, 10:07 PM UTCSoutheast Asia: failing from Oct 20, 2026, 10:02 PM UTC, recovered Oct 20, 2026, 10:07 PM UTCAustralia: failing from Oct 20, 2026, 10:05 PM UTC, recovered Oct 20, 2026, 10:09 PM UTCSouth America: failing from Oct 20, 2026, 10:02 PM UTC, recovered Oct 20, 2026, 10:06 PM UTC
Oct 13, 2026, 10:01 PM UTC to Oct 13, 2026, 10:06 PM UTC4 min
multiple regions
Europe: failing from Oct 13, 2026, 10:01 PM UTC, recovered Oct 13, 2026, 10:05 PM UTCAsia-Pacific: failing from Oct 13, 2026, 10:02 PM UTC, recovered Oct 13, 2026, 10:04 PM UTCAustralia: failing from Oct 13, 2026, 10:02 PM UTC, recovered Oct 13, 2026, 10:06 PM UTC
Oct 6, 2026, 10:09 PM UTC to Oct 6, 2026, 10:15 PM UTC6 min
multiple regions
US-East: failing from Oct 6, 2026, 10:11 PM UTC, recovered Oct 6, 2026, 10:12 PM UTCUS-West: failing from Oct 6, 2026, 10:11 PM UTC, recovered Oct 6, 2026, 10:14 PM UTCUS-Central: failing from Oct 6, 2026, 10:10 PM UTC, recovered Oct 6, 2026, 10:14 PM UTCCanada: failing from Oct 6, 2026, 10:11 PM UTC, recovered Oct 6, 2026, 10:15 PM UTCUK: failing from Oct 6, 2026, 10:11 PM UTC, recovered Oct 6, 2026, 10:15 PM UTCAustralia: failing from Oct 6, 2026, 10:09 PM UTC, recovered Oct 6, 2026, 10:14 PM UTCSouth America: failing from Oct 6, 2026, 10:11 PM UTC, recovered Oct 6, 2026, 10:15 PM UTC
Sep 29, 2026, 10:06 PM UTC to Sep 29, 2026, 10:12 PM UTC6 min
multiple regions
Europe: failing from Sep 29, 2026, 10:07 PM UTC, recovered Sep 29, 2026, 10:09 PM UTCCanada: failing from Sep 29, 2026, 10:06 PM UTC, recovered Sep 29, 2026, 10:11 PM UTCAustralia: failing from Sep 29, 2026, 10:06 PM UTC, recovered Sep 29, 2026, 10:12 PM UTC
Sep 22, 2026, 10:28 PM UTC to Sep 22, 2026, 10:44 PM UTC15 min
multiple regions
US-East: failing from Sep 22, 2026, 10:30 PM UTC, recovered Sep 22, 2026, 10:40 PM UTCUS-West: failing from Sep 22, 2026, 10:28 PM UTC, recovered Sep 22, 2026, 10:40 PM UTCEurope: failing from Sep 22, 2026, 10:28 PM UTC, recovered Sep 22, 2026, 10:41 PM UTCAsia-Pacific: failing from Sep 22, 2026, 10:31 PM UTC, recovered Sep 22, 2026, 10:41 PM UTCUS-Central: failing from Sep 22, 2026, 10:29 PM UTC, recovered Sep 22, 2026, 10:41 PM UTCCanada: failing from Sep 22, 2026, 10:31 PM UTC, recovered Sep 22, 2026, 10:43 PM UTCUK: failing from Sep 22, 2026, 10:29 PM UTC, recovered Sep 22, 2026, 10:41 PM UTCSoutheast Asia: failing from Sep 22, 2026, 10:32 PM UTC, recovered Sep 22, 2026, 10:40 PM UTCAustralia: failing from Sep 22, 2026, 10:30 PM UTC, recovered Sep 22, 2026, 10:44 PM UTCSouth America: failing from Sep 22, 2026, 10:29 PM UTC, recovered Sep 22, 2026, 10:41 PM UTC
Sep 15, 2026, 10:01 PM UTC to Sep 15, 2026, 10:06 PM UTC5 min
multiple regions
US-East: failing from Sep 15, 2026, 10:01 PM UTC, recovered Sep 15, 2026, 10:02 PM UTCUS-West: failing from Sep 15, 2026, 10:02 PM UTC, recovered Sep 15, 2026, 10:04 PM UTCAsia-Pacific: failing from Sep 15, 2026, 10:01 PM UTC, recovered Sep 15, 2026, 10:04 PM UTCAustralia: failing from Sep 15, 2026, 10:01 PM UTC, recovered Sep 15, 2026, 10:06 PM UTC
Sep 8, 2026, 10:06 PM UTC to Sep 8, 2026, 10:13 PM UTC6 min
multiple regions
US-East: failing from Sep 8, 2026, 10:06 PM UTC, recovered Sep 8, 2026, 10:11 PM UTCUS-West: failing from Sep 8, 2026, 10:08 PM UTC, recovered Sep 8, 2026, 10:10 PM UTCEurope: failing from Sep 8, 2026, 10:07 PM UTC, recovered Sep 8, 2026, 10:09 PM UTCAsia-Pacific: failing from Sep 8, 2026, 10:08 PM UTC, recovered Sep 8, 2026, 10:10 PM UTCUK: failing from Sep 8, 2026, 10:09 PM UTC, recovered Sep 8, 2026, 10:13 PM UTC

Permanent probe event records

Every closed Steam probe event gets its own permanent, citable page: the region-by-region timeline of our check results, which stays up even after the event log above ages out of this 90-day window.

Full detail on what a probe does and does not prove is in the methodology page.