StatOSS

Slack uptime

Slack, checked by StatOSS every 5 minutes from Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia. Measured from outside, with every outage dated in UTC.

slack.com/api/api.testEvery 5 minutes

Slack is up.

Up for 51 d 10 h. Last checked 2026-11-20 18:55 UTC from Ashburn, USA: 200 in 82 ms.

Last 24 hours

Up for 51 d 10 h100% passed

288 checks, median 132 ms from Falkenstein, all passed

95% under 137 ms

Response time by region
EuropeEurope132 ms
N. AmericaNorth America80 ms
AsiaAsia309 ms
OceaniaOceania220 ms

Medians over this range, on one scale up to 500 ms.

Last 90 days

Up for 51 d 10 h100% passed

14,804 checks, median 134 ms from Falkenstein, all passed

95% under 244 ms

Response time by region
EuropeEurope134 ms
N. AmericaNorth America48 ms
AsiaAsia320 ms
OceaniaOceania259 ms

Medians over this range, on one scale up to 500 ms. Europe's places are scaled to Falkenstein, its fastest shared place.

Each bar of the first strip is one check, five minutes apart; each bar of the second is a day. Height is response time, red is a failed check, amber a timeout. Times are UTC, as of 2026-11-20 18:56 UTC.

In the last 30 days Slack passed 8,863 of 8,863 checks, 100%.

No outage since checks began on 30 Sep 2026.

Availability

The share of checks that passed, and the outages that began, in each window up to now.

LastPassedChecksOutages
24 hours100%288 of 2880
7 days100%2,015 of 2,0150
30 days100%8,863 of 8,8630
90 daysNot enough history yet: checks began on 30 Sep 2026

A year of checks is kept; the year's figure appears here once there is a year of them.

Response time by location

Over the last 7 days, from the checks that passed: the time from the start of the request to the answer's headers, with the DNS lookup, the connection and TLS included.

FromMedian95th percentileMeanChecks
Falkenstein, Germany132 ms140 ms141 ms420
Helsinki, Finland189 ms194 ms190 ms42
Ashburn, USA71 ms125 ms69 ms503
Copenhagen, Denmark162 ms181 ms180 ms42
Singapore311 ms455 ms333 ms505
Sydney, Australia231 ms434 ms282 ms504

Outages

None detected since checks began on 30 Sep 2026.

What is checked

Team chat, and the place many teams send their alerts, deploy notices and bot messages.

StatOSS sends GET https://slack.com/api/api.test and counts the check as passed on status 200 with the text "ok":true in the body within 10 seconds. The Web API's test method, which needs no token and answers `{"ok":true}`. Slack answers errors with 200 as well, so the check looks for that text.

Messages in real time go over a separate WebSocket service, and incoming webhooks to a separate address; neither is checked.

Slack reports its own incidents at slack-status.com. The figures here are measured from outside and can differ from it in both directions.

How it is measured

  • One check every 5 minutes, from one location at a time in turn: Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia.
  • A check fails when no answer comes within 10 seconds, when the connection or TLS fails, or when the answer is not status 200 with the text "ok":true in the body.
  • A failed check is repeated at once from a second location, and counts only when that location fails too, or cannot answer within 20 seconds.
  • Two failed checks in a row make an outage, dated from the second, and the first check that passes ends it. A failure shorter than 10 minutes may not make one, and times are good to about 5 minutes.
  • Availability is the share of checks that passed. There are no maintenance windows: every check counts.

It is the same check a StatOSS status page runs for its owner, with the same rules; the docs on checks have the details.