Slack uptime
Slack, checked by StatOSS every 5 minutes from Aarhus and Copenhagen in Denmark, Falkenstein in Germany, Ashburn in the USA, Singapore, and Sydney in Australia. Measured from outside, with every outage dated in UTC.
Slack is up.
Up for 6 d 3 h. Last checked 2026-10-06 11:38 UTC from Singapore: 200 in 468 ms.
Last 24 hours
Up for 6 d 3 h100% passed
288 checks, median 135 ms from Falkenstein, all passed
95% under 240 ms
Response time by region
Medians over this range, on one scale up to 800 ms. Europe's places are scaled to Falkenstein, its fastest shared place.
Last 90 days
Up for 6 d 3 h100% passed
1,764 checks, median 137 ms from Falkenstein, all passed
95% under 229 ms
Response time by region
Medians over this range, on one scale up to 800 ms. Europe's places are scaled to Falkenstein, its fastest shared place.
In the last 24 hours Slack passed 288 of 288 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.
| Last | Passed | Checks | Outages |
|---|---|---|---|
| 24 hours | 100% | 288 of 288 | 0 |
| 7 days | Not enough history yet: checks began on 30 Sep 2026 | ||
| 30 days | Not enough history yet: checks began on 30 Sep 2026 | ||
| 90 days | Not 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.
| From | Median | 95th percentile | Mean | Checks |
|---|---|---|---|---|
| Falkenstein, Germany | 135 ms | 230 ms | 164 ms | 201 |
| Ashburn, USA | 37 ms | 57 ms | 47 ms | 561 |
| Copenhagen, Denmark | 209 ms | 303 ms | 230 ms | 170 |
| Singapore | 457 ms | 734 ms | 492 ms | 555 |
| Sydney, Australia | 267 ms | 377 ms | 293 ms | 84 |
| Aarhus, Denmark | 174 ms | 386 ms | 215 ms | 193 |
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: Aarhus and Copenhagen in Denmark, Falkenstein in Germany, 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.