Skip to content

Outage tracker / Slack

Is Slack down?

I'm having a problem

Operationalchecked moments ago

We reached Slack from all 10 regions we check.

As of Oct 5, 2026, 8:16 PM UTC, Slack answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 58 days we have measured Slack (since Aug 8, 2026).

Email me the next time we see Slack go down

Measured by our own probes from ten regions, not Slack's status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

our independent probeslive · checked Oct 5, 2026, 8:16 PM UTC
US-East64 msOperational
US-West1030 msOperational
Europe141 msOperational
Asia-Pacific571 msOperational
US-Central72 msOperational
Canada78 msOperational
UK183 msOperational
Southeast Asia913 msOperational
Australia643 msOperational
South America310 msOperational
their status pagetheir claim, not our reading

Slack reports: All systems operational (“No active incidents reported”)

from Slack's own status page, checked Oct 5, 2026, 8:13 PM UTC
Our probes and Slack's own status page agree: both show Slack as reachable right now.

This is Slack's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Slack response time, by region

US-East
168msp95 · latest
500ms250ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 197ms2026-09-07 UTC: p95 172ms2026-09-08 UTC: p95 180ms2026-09-09 UTC: p95 199ms2026-09-10 UTC: p95 246ms2026-09-11 UTC: p95 251ms2026-09-12 UTC: p95 200ms2026-09-13 UTC: p95 190ms2026-09-14 UTC: p95 278ms2026-09-15 UTC: p95 307ms2026-09-16 UTC: p95 328ms2026-09-17 UTC: p95 356ms2026-09-18 UTC: p95 381ms2026-09-19 UTC: p95 378ms2026-09-20 UTC: p95 290ms2026-09-21 UTC: p95 323ms2026-09-22 UTC: p95 343ms2026-09-23 UTC: p95 339ms2026-09-24 UTC: p95 404ms2026-09-25 UTC: p95 406ms2026-09-26 UTC: p95 283ms2026-09-27 UTC: p95 239ms2026-09-28 UTC: p95 292ms2026-09-29 UTC: p95 271ms2026-09-30 UTC: p95 313ms2026-10-01 UTC: p95 295ms2026-10-02 UTC: p95 309ms2026-10-03 UTC: p95 211ms2026-10-04 UTC: p95 167ms2026-10-05 UTC: p95 168ms
Sep 6Sep 20Oct 5
US-West
1.8sp95 · 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-06 UTC: p95 856ms2026-09-07 UTC: p95 676ms2026-09-08 UTC: p95 596ms2026-09-09 UTC: p95 460ms2026-09-10 UTC: p95 732ms2026-09-11 UTC: p95 625ms2026-09-12 UTC: p95 684ms2026-09-13 UTC: p95 830ms2026-09-14 UTC: p95 979ms2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 354ms2026-09-18 UTC: p95 484ms2026-09-19 UTC: p95 820ms2026-09-20 UTC: p95 838ms2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 751ms2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 837ms2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.7s2026-10-02 UTC: p95 1.8s2026-10-03 UTC: p95 1.9s2026-10-04 UTC: p95 1.8s2026-10-05 UTC: p95 1.8s
Sep 6Sep 20Oct 5
Europe
330msp95 · latest
500ms250ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 350ms2026-09-07 UTC: p95 326ms2026-09-08 UTC: p95 309ms2026-09-09 UTC: p95 307ms2026-09-10 UTC: p95 364ms2026-09-11 UTC: p95 353ms2026-09-12 UTC: p95 386ms2026-09-13 UTC: p95 398ms2026-09-14 UTC: p95 376ms2026-09-15 UTC: p95 387ms2026-09-16 UTC: p95 416ms2026-09-17 UTC: p95 433ms2026-09-18 UTC: p95 431ms2026-09-19 UTC: p95 426ms2026-09-20 UTC: p95 433ms2026-09-21 UTC: p95 426ms2026-09-22 UTC: p95 411ms2026-09-23 UTC: p95 442ms2026-09-24 UTC: p95 485ms2026-09-25 UTC: p95 418ms2026-09-26 UTC: p95 460ms2026-09-27 UTC: p95 477ms2026-09-28 UTC: p95 439ms2026-09-29 UTC: p95 394ms2026-09-30 UTC: p95 444ms2026-10-01 UTC: p95 339ms2026-10-02 UTC: p95 318ms2026-10-03 UTC: p95 388ms2026-10-04 UTC: p95 396ms2026-10-05 UTC: p95 330ms
Sep 6Sep 20Oct 5
Asia-Pacific
685msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 792ms2026-09-07 UTC: p95 599ms2026-09-08 UTC: p95 533ms2026-09-09 UTC: p95 560ms2026-09-10 UTC: p95 570ms2026-09-11 UTC: p95 739ms2026-09-12 UTC: p95 645ms2026-09-13 UTC: p95 602ms2026-09-14 UTC: p95 522ms2026-09-15 UTC: p95 504ms2026-09-16 UTC: p95 620ms2026-09-17 UTC: p95 602ms2026-09-18 UTC: p95 694ms2026-09-19 UTC: p95 760ms2026-09-20 UTC: p95 822ms2026-09-21 UTC: p95 958ms2026-09-22 UTC: p95 986ms2026-09-23 UTC: p95 994ms2026-09-24 UTC: p95 897ms2026-09-25 UTC: p95 911ms2026-09-26 UTC: p95 996ms2026-09-27 UTC: p95 952ms2026-09-28 UTC: p95 844ms2026-09-29 UTC: p95 859ms2026-09-30 UTC: p95 823ms2026-10-01 UTC: p95 627ms2026-10-02 UTC: p95 771ms2026-10-03 UTC: p95 758ms2026-10-04 UTC: p95 810ms2026-10-05 UTC: p95 685ms
Sep 6Sep 20Oct 5
US-Central
1.2sp95 · 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-06 UTC: p95 916ms2026-09-07 UTC: p95 912ms2026-09-08 UTC: p95 966ms2026-09-09 UTC: p95 979ms2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 1.0s2026-09-12 UTC: p95 888ms2026-09-13 UTC: p95 947ms2026-09-14 UTC: p95 968ms2026-09-15 UTC: p95 497ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 857ms2026-09-23 UTC: p95 829ms2026-09-24 UTC: p95 845ms2026-09-25 UTC: p95 901ms2026-09-26 UTC: p95 969ms2026-09-27 UTC: p95 878ms2026-09-28 UTC: p95 688ms2026-09-29 UTC: p95 782ms2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.2s
Sep 6Sep 20Oct 5
Canada
1.2sp95 · 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-06 UTC: p95 734ms2026-09-07 UTC: p95 627ms2026-09-08 UTC: p95 508ms2026-09-09 UTC: p95 532ms2026-09-10 UTC: p95 494ms2026-09-11 UTC: p95 642ms2026-09-12 UTC: p95 805ms2026-09-13 UTC: p95 747ms2026-09-14 UTC: p95 728ms2026-09-15 UTC: p95 615ms2026-09-16 UTC: p95 618ms2026-09-17 UTC: p95 453ms2026-09-18 UTC: p95 819ms2026-09-19 UTC: p95 836ms2026-09-20 UTC: p95 797ms2026-09-21 UTC: p95 827ms2026-09-22 UTC: p95 842ms2026-09-23 UTC: p95 508ms2026-09-24 UTC: p95 814ms2026-09-25 UTC: p95 899ms2026-09-26 UTC: p95 796ms2026-09-27 UTC: p95 868ms2026-09-28 UTC: p95 720ms2026-09-29 UTC: p95 865ms2026-09-30 UTC: p95 941ms2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.2s
Sep 6Sep 20Oct 5
UK
331msp95 · 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-06 UTC: p95 461ms2026-09-07 UTC: p95 533ms2026-09-08 UTC: p95 522ms2026-09-09 UTC: p95 322ms2026-09-10 UTC: p95 428ms2026-09-11 UTC: p95 350ms2026-09-12 UTC: p95 409ms2026-09-13 UTC: p95 347ms2026-09-14 UTC: p95 313ms2026-09-15 UTC: p95 311ms2026-09-16 UTC: p95 313ms2026-09-17 UTC: p95 292ms2026-09-18 UTC: p95 270ms2026-09-19 UTC: p95 322ms2026-09-20 UTC: p95 392ms2026-09-21 UTC: p95 473ms2026-09-22 UTC: p95 478ms2026-09-23 UTC: p95 481ms2026-09-24 UTC: p95 446ms2026-09-25 UTC: p95 518ms2026-09-26 UTC: p95 592ms2026-09-27 UTC: p95 503ms2026-09-28 UTC: p95 482ms2026-09-29 UTC: p95 430ms2026-09-30 UTC: p95 416ms2026-10-01 UTC: p95 400ms2026-10-02 UTC: p95 365ms2026-10-03 UTC: p95 371ms2026-10-04 UTC: p95 389ms2026-10-05 UTC: p95 331ms
Sep 6Sep 20Oct 5
Southeast Asia
1.2sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.0s2026-09-07 UTC: p95 889ms2026-09-08 UTC: p95 846ms2026-09-09 UTC: p95 940ms2026-09-10 UTC: p95 921ms2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 812ms2026-09-13 UTC: p95 889ms2026-09-14 UTC: p95 817ms2026-09-15 UTC: p95 859ms2026-09-16 UTC: p95 758ms2026-09-17 UTC: p95 845ms2026-09-18 UTC: p95 979ms2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 936ms2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.5s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.2s
Sep 6Sep 20Oct 5
Australia
1.1sp95 · 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-06 UTC: p95 1.0s2026-09-07 UTC: p95 964ms2026-09-08 UTC: p95 885ms2026-09-09 UTC: p95 932ms2026-09-10 UTC: p95 888ms2026-09-11 UTC: p95 880ms2026-09-12 UTC: p95 946ms2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 979ms2026-09-15 UTC: p95 872ms2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 862ms2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 918ms2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 974ms2026-09-23 UTC: p95 854ms2026-09-24 UTC: p95 935ms2026-09-25 UTC: p95 901ms2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 1s2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 866ms2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
South America
912msp95 · 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-06 UTC: p95 900ms2026-09-07 UTC: p95 1.0s2026-09-08 UTC: p95 945ms2026-09-09 UTC: p95 790ms2026-09-10 UTC: p95 794ms2026-09-11 UTC: p95 683ms2026-09-12 UTC: p95 823ms2026-09-13 UTC: p95 835ms2026-09-14 UTC: p95 794ms2026-09-15 UTC: p95 709ms2026-09-16 UTC: p95 833ms2026-09-17 UTC: p95 879ms2026-09-18 UTC: p95 876ms2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 930ms2026-09-21 UTC: p95 982ms2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 864ms2026-09-24 UTC: p95 759ms2026-09-25 UTC: p95 846ms2026-09-26 UTC: p95 846ms2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 917ms2026-09-29 UTC: p95 888ms2026-09-30 UTC: p95 802ms2026-10-01 UTC: p95 913ms2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 912ms
Sep 6Sep 20Oct 5

Is it Slack, or is it you?

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 Slack -- it cannot diagnose Slack's own systems.

What we measured, function by function

Slack 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: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
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 we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 64msstatus code: 200checked: Oct 5, 2026, 8:16 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Slack normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 1030msstatus code: 200checked: Oct 5, 2026, 8:16 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Slack normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 72msstatus code: 200checked: Oct 5, 2026, 8:13 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Slack normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 78msstatus code: 200checked: Oct 5, 2026, 8:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Slack normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 310msstatus code: 200checked: Oct 5, 2026, 8:13 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Slack normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 141msstatus code: 200checked: Oct 5, 2026, 8:15 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Slack normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 183msstatus code: 200checked: Oct 5, 2026, 8:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Slack normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 571msstatus code: 200checked: Oct 5, 2026, 8:16 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Slack normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 913msstatus code: 200checked: Oct 5, 2026, 8:12 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Slack normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 643msstatus code: 200checked: Oct 5, 2026, 8:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Slack 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 Slack, 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 have not received any reports for Slack yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for Slack.

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

We have been measuring Slack 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 Slack covering any window you pick, with our measurements and Slack's own claim at the time, side by side.

Full availability history for Slack: 90-day availability by region, month-by-month uptime, and every incident on record.

Put this badge in your README

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

The badge shows the share of our probes that succeeded 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: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Slack's SLA implies, from our measurement

At or above your target

We measured none of downtime for Slack over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Slack'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://slack.com/api/api.test
secondary
https://status.slack.com/
secondaryfunctional: live API
https://slack.com/api/auth.test
RealUptime is not affiliated with Slack; the name identifies what we measured, and nothing here speaks for Slack's own team. We send a single web request to Slack from 10 regions on our own schedule and time the response. We do not see inside Slack's systems, do not use an account or real transaction, and are not the same signal Slack's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Slack is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.