Skip to content

Outage tracker / Slack

Is Slack down?

I'm having a problem

Vendor reports no incidentWhat Slack reports

Slack reports no incident on its status page.

As of the last successful poll, 2026-11-05 15:38 UTC.

Slack's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked moments ago

Our checks of Slack pass from all 10 regions we check.

As of Nov 5, 2026, 3:43 PM UTC, RealUptime's checks of Slack passed in all 10 regions that returned a reading.

Front-door and live API checks

Email me when Slack reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Slack's own statement from its status page, with our regional reading beside it.

our check readinglive · checked Nov 5, 2026, 3:43 PM UTC
US-East152 msChecks passing
US-West2557 msChecks passing
Europe252 msChecks passing
Asia-Pacific781 msChecks passing
US-Central3095 msChecks passing
Canada1824 msChecks passing
UK183 msChecks passing
Southeast Asia308 msChecks passing
Australia679 msChecks passing
South America467 msChecks passing
their status pagetheir claim, not our reading

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

from Slack's own status page, checked Nov 5, 2026, 3:32 PM UTC
Slack's own status page shows no incident, and our checks of Slack pass 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
557msp95 · 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-07 UTC: p95 190ms2026-10-08 UTC: p95 229ms2026-10-09 UTC: p95 234ms2026-10-10 UTC: p95 258ms2026-10-11 UTC: p95 224ms2026-10-12 UTC: p95 262ms2026-10-13 UTC: p95 263ms2026-10-14 UTC: p95 324ms2026-10-15 UTC: p95 300ms2026-10-16 UTC: p95 240ms2026-10-17 UTC: p95 989ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 749ms2026-10-20 UTC: p95 657ms2026-10-21 UTC: p95 640ms2026-10-22 UTC: p95 603ms2026-10-23 UTC: p95 602ms2026-10-24 UTC: p95 583ms2026-10-25 UTC: p95 563ms2026-10-26 UTC: p95 972ms2026-10-27 UTC: p95 612ms2026-10-28 UTC: p95 697ms2026-10-29 UTC: p95 632ms2026-10-30 UTC: p95 686ms2026-10-31 UTC: p95 693ms2026-11-01 UTC: p95 698ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 594ms2026-11-04 UTC: p95 570ms2026-11-05 UTC: p95 557ms
Oct 7Oct 21Nov 5
US-West
2.8sp95 · 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-07 UTC: p95 1.8s2026-10-08 UTC: p95 1.7s2026-10-09 UTC: p95 1.6s2026-10-10 UTC: p95 1.6s2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 1.7s2026-10-13 UTC: p95 1.7s2026-10-14 UTC: p95 1.6s2026-10-15 UTC: p95 1.7s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 2.4s2026-10-19 UTC: p95 2.5s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 2.2s2026-10-22 UTC: p95 2.4s2026-10-23 UTC: p95 2.3s2026-10-24 UTC: p95 2.3s2026-10-25 UTC: p95 2.4s2026-10-26 UTC: p95 2.4s2026-10-27 UTC: p95 2.4s2026-10-28 UTC: p95 2.3s2026-10-29 UTC: p95 2.2s2026-10-30 UTC: p95 2.3s2026-10-31 UTC: p95 2.3s2026-11-01 UTC: p95 2.3s2026-11-02 UTC: p95 2.5s2026-11-03 UTC: p95 3.3s2026-11-04 UTC: p95 3.1s2026-11-05 UTC: p95 2.8s
Oct 7Oct 21Nov 5
Europe
591msp95 · 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-07 UTC: p95 406ms2026-10-08 UTC: p95 353ms2026-10-09 UTC: p95 313ms2026-10-10 UTC: p95 402ms2026-10-11 UTC: p95 324ms2026-10-12 UTC: p95 283ms2026-10-13 UTC: p95 269ms2026-10-14 UTC: p95 256ms2026-10-15 UTC: p95 309ms2026-10-16 UTC: p95 269ms2026-10-17 UTC: p95 433ms2026-10-18 UTC: p95 547ms2026-10-19 UTC: p95 711ms2026-10-20 UTC: p95 558ms2026-10-21 UTC: p95 491ms2026-10-22 UTC: p95 537ms2026-10-23 UTC: p95 437ms2026-10-24 UTC: p95 411ms2026-10-25 UTC: p95 446ms2026-10-26 UTC: p95 484ms2026-10-27 UTC: p95 461ms2026-10-28 UTC: p95 460ms2026-10-29 UTC: p95 491ms2026-10-30 UTC: p95 531ms2026-10-31 UTC: p95 452ms2026-11-01 UTC: p95 487ms2026-11-02 UTC: p95 502ms2026-11-03 UTC: p95 458ms2026-11-04 UTC: p95 497ms2026-11-05 UTC: p95 591ms
Oct 7Oct 21Nov 5
Asia-Pacific
1.3sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 688ms2026-10-08 UTC: p95 769ms2026-10-09 UTC: p95 877ms2026-10-10 UTC: p95 784ms2026-10-11 UTC: p95 811ms2026-10-12 UTC: p95 771ms2026-10-13 UTC: p95 712ms2026-10-14 UTC: p95 693ms2026-10-15 UTC: p95 786ms2026-10-16 UTC: p95 822ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 1.6s2026-10-23 UTC: p95 1.7s2026-10-24 UTC: p95 1.8s2026-10-25 UTC: p95 1.7s2026-10-26 UTC: p95 1.7s2026-10-27 UTC: p95 1.7s2026-10-28 UTC: p95 1.6s2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
US-Central
3.5sp95 · 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-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.6s2026-10-15 UTC: p95 1.7s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 2.2s2026-10-19 UTC: p95 2.3s2026-10-20 UTC: p95 2.2s2026-10-21 UTC: p95 2.3s2026-10-22 UTC: p95 2.1s2026-10-23 UTC: p95 2.2s2026-10-24 UTC: p95 2.1s2026-10-25 UTC: p95 2.1s2026-10-26 UTC: p95 2.1s2026-10-27 UTC: p95 2.0s2026-10-28 UTC: p95 2.2s2026-10-29 UTC: p95 2.1s2026-10-30 UTC: p95 2.2s2026-10-31 UTC: p95 1.9s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 2.7s2026-11-03 UTC: p95 3.6s2026-11-04 UTC: p95 3.5s2026-11-05 UTC: p95 3.5s
Oct 7Oct 21Nov 5
Canada
2.7sp95 · 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-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.9s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 1.8s2026-10-24 UTC: p95 1.8s2026-10-25 UTC: p95 1.9s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 1.7s2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 1.7s2026-10-30 UTC: p95 1.7s2026-10-31 UTC: p95 1.7s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 2.2s2026-11-03 UTC: p95 2.7s2026-11-04 UTC: p95 2.8s2026-11-05 UTC: p95 2.7s
Oct 7Oct 21Nov 5
UK
558msp95 · 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-07 UTC: p95 361ms2026-10-08 UTC: p95 417ms2026-10-09 UTC: p95 404ms2026-10-10 UTC: p95 392ms2026-10-11 UTC: p95 429ms2026-10-12 UTC: p95 500ms2026-10-13 UTC: p95 512ms2026-10-14 UTC: p95 450ms2026-10-15 UTC: p95 368ms2026-10-16 UTC: p95 424ms2026-10-17 UTC: p95 354ms2026-10-18 UTC: p95 754ms2026-10-19 UTC: p95 776ms2026-10-20 UTC: p95 747ms2026-10-21 UTC: p95 751ms2026-10-22 UTC: p95 818ms2026-10-23 UTC: p95 785ms2026-10-24 UTC: p95 816ms2026-10-25 UTC: p95 762ms2026-10-26 UTC: p95 739ms2026-10-27 UTC: p95 751ms2026-10-28 UTC: p95 806ms2026-10-29 UTC: p95 658ms2026-10-30 UTC: p95 737ms2026-10-31 UTC: p95 637ms2026-11-01 UTC: p95 695ms2026-11-02 UTC: p95 631ms2026-11-03 UTC: p95 520ms2026-11-04 UTC: p95 457ms2026-11-05 UTC: p95 558ms
Oct 7Oct 21Nov 5
Southeast Asia
1.3sp95 · 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-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 793ms2026-10-10 UTC: p95 982ms2026-10-11 UTC: p95 740ms2026-10-12 UTC: p95 985ms2026-10-13 UTC: p95 752ms2026-10-14 UTC: p95 698ms2026-10-15 UTC: p95 924ms2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.6s2026-10-24 UTC: p95 1.4s2026-10-25 UTC: p95 1.5s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 1.7s2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
Australia
1.9sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 836ms2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 942ms2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 964ms2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.3s2026-10-20 UTC: p95 2.2s2026-10-21 UTC: p95 2.2s2026-10-22 UTC: p95 2.4s2026-10-23 UTC: p95 2.3s2026-10-24 UTC: p95 2.3s2026-10-25 UTC: p95 2.0s2026-10-26 UTC: p95 2.1s2026-10-27 UTC: p95 2.2s2026-10-28 UTC: p95 2.3s2026-10-29 UTC: p95 2.1s2026-10-30 UTC: p95 2.1s2026-10-31 UTC: p95 2.1s2026-11-01 UTC: p95 2.1s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 1.9s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
South America
1.9sp95 · 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-07 UTC: p95 597ms2026-10-08 UTC: p95 662ms2026-10-09 UTC: p95 787ms2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 714ms2026-10-15 UTC: p95 885ms2026-10-16 UTC: p95 869ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 1.9s2026-10-23 UTC: p95 8.9s2026-10-24 UTC: p95 1.8s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 1.7s2026-10-28 UTC: p95 1.9s2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 1.7s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5

Check your own site while you wait on Slack

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: 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
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: 152msstatus code: 200checked: Nov 5, 2026, 3:43 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
      Checks passinglatency: 2557msstatus code: 200checked: Nov 5, 2026, 3:41 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
      Checks passinglatency: 3095msstatus code: 200checked: Nov 5, 2026, 3:40 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
      Checks passinglatency: 1824msstatus code: 200checked: Nov 5, 2026, 3:40 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
    Checks passinglatency: 467msstatus code: 200checked: Nov 5, 2026, 3:42 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 252msstatus code: 200checked: Nov 5, 2026, 3:41 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
      Checks passinglatency: 183msstatus code: 200checked: Nov 5, 2026, 3:40 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 781msstatus code: 200checked: Nov 5, 2026, 3:40 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
      Checks passinglatency: 308msstatus code: 200checked: Nov 5, 2026, 3:43 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
      Checks passinglatency: 679msstatus code: 200checked: Nov 5, 2026, 3:43 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 probe events

Slack Real-Time Connection Disruption, 1mdeclared on their status page2026-10-22
Single Sign On errors, 1mdeclared on their status page2026-10-14
Slack for iOS closing unexpectedly when opening channels, 73h 28mdeclared on their status page2026-10-09
Free Plan Customers Are Experiencing Message Failures, 6h 20mdeclared on their status page2026-10-01
Some customers experiencing blurry image previews and download issues, 8h 56mdeclared on their status page2026-09-12
Trouble loading Workspace-level Apps & Workflows settings page is returning blank pages, 2h 40mdeclared on their status page2026-09-10
Trouble Accessing Historical Messages With Custom Data Retention Policies Enabled, 769h 9mdeclared on their status page2026-08-13
Trouble Using Search Bar For Some Admins, 2h 44mdeclared on their status page2026-08-06

check 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 check readings and Slack's own claim at the time, side by side.

Full check history for Slack: 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

Slack uptime by RealUptime's checksLive, from this page's own readings.
[![Slack uptime by RealUptime's checks](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 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 Slack down?", https://realuptime.io/outages/slack. The readings change with every check, so give the date you read them.

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

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: slack.com

RealUptime is not affiliated with Slack; the name identifies what we checked, 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 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.