We last checked Slack at 20:40 UTC and it responded normally in 262 ms. Nobody has reported a problem in the last 24 hours.
Slack problem reports, last 24 hours
Reports from visitors per hour, in your local time. When reports rise well above the usual level, Slack is probably having problems.
Having a problem with Slack?
Choose what isn't working. Reports are anonymous and help other people see if the problem is widespread.
Most reported problems
Recent reports
- No reports in the last 24 hours.
Our checks of slack.com
Over the last 7 days we checked slack.com 2,016 times: 100% of checks succeeded, with an average response time of 214 ms. None of our checks of slack.com has failed in that time.
Each bar is one hour. Green: every check reached slack.com. Amber: some failed. Red: all failed. Grey: not checked that hour.
Recent Slack outages
We haven't recorded any Slack outages since we started keeping this history on 24 October 2026. We record one when our checks of slack.com fail for 15 minutes in a row, when problem reports jump well above normal, or when Slack's official status page reports a major outage.
Times are in UTC. Each entry is a time when our checks failed for at least 15 minutes, problem reports jumped well above normal, or Slack's status page reported a major outage.
How Slack outages usually look
Slack breaks in pieces more often than it goes fully dark. Its status page tracks login and SSO, connectivity, messaging, files, notifications, huddles, search, apps and integrations, workflows and canvases separately, and incidents frequently affect just one of them. A typical partial outage looks like messages sending with a delay, files that will not upload, search returning nothing, or huddles that refuse to connect while chat works. Some incidents also hit only a share of workspaces, so a colleague at another company may be fine while your team is stuck.
Big Slack outages tend to land on busy Monday mornings. On 4 January 2021, the first working day of the year, Slack was down for hours: returning users with cold caches created a traffic surge that overloaded AWS network gateways Slack relies on. Problems on your side look different. Company firewalls, proxies and VPNs often block the WebSocket connections Slack needs, which gives you a grey 'Last updated' banner rather than an outright error. Because many workspaces sign in through a company identity provider such as Okta or Microsoft, a login failure can also be your employer's SSO, not Slack.
Common Slack errors and what they mean
Slack cannot connect.
The desktop app cannot reach Slack at all. It can be a Slack connectivity incident, but often a proxy, firewall, antivirus or VPN is blocking the app.
What to do: Click Restart Slack under the message. If it keeps happening and slack-status.com is clear, run the connection test at slack.com/help/test.
For some reason, Slack couldn't load.
Slack started but could not load your workspace. This is often a corrupted local cache or a browser extension rather than an outage.
What to do: In the desktop app use Help > Troubleshooting > Clear Cache and Restart. In a browser, try a private window to rule out extensions.
Sorry! Something went wrong, but we're looking into it
Slack's servers returned an error. This is a server-side problem, and if many people see it at once it is an outage.
What to do: Reload with Ctrl+R (Cmd+R on Mac) and check slack-status.com. If no incident is listed and it continues, contact Slack support.
Last updated less than a minute ago…
Shown in a grey banner when Slack's live WebSocket connection keeps dropping. It usually means a network device is interfering, not that Slack is down.
What to do: Ask your IT team to allow WebSocket connections to wss-primary.slack.com, wss-backup.slack.com and wss-mobile.slack.com.
What to do if Slack is not working
- On slack-status.com, look at the exact component that is failing (Messaging, Files, Huddles, Login/SSO) rather than the overall banner.
- In the desktop app, go to Help > Troubleshooting > Clear Cache and Restart. This fixes most 'couldn't load' problems caused by stale local data.
- Run Slack's connection test at slack.com/help/test. It shows whether your network can reach the Slack services the app needs.
- Open your workspace at app.slack.com in a private browser window. If it works there, the problem is your desktop app or a browser extension.
- If you cannot sign in, check whether other company tools that use the same single sign-on (Okta, Microsoft, Google) are working. If not, the fault is your SSO provider.
- On a work laptop, disconnect from the VPN briefly. Corporate proxies often block the WebSocket traffic Slack depends on.
- If support asks for detail, collect Net Logs from Help > Troubleshooting > Restart and Collect Net Logs while the problem is happening.
Official Slack status and help
- Slack System Status Where the company itself confirms outages and posts updates.
- Slack help centre Official help articles and contact options.
- @SlackHQ on X Official account, useful for updates during big outages.
Slack outage FAQ
Is Slack down for everyone, or just me?
Look at the status at the top of this page. We connect to slack.com directly from our servers, so if our check works but Slack doesn't work for you, the problem is more likely your device, network or account. If our check fails, or reports have jumped in the last hour, Slack is probably having a wider outage.
Why does this page say Slack is up when it isn't working for me?
Our check confirms that slack.com is reachable and responding. An outage can still affect only part of Slack, such as logging in, the mobile app or a single feature, or only some regions. That's why visitor reports matter: when many people report problems at once, we flag Slack as having problems even if the website loads.
How often do you check Slack?
We check Slack automatically every 5 minutes, and again whenever someone opens this page and our last check is more than a few minutes old. A failed check is retried once before it counts.
How do I report a problem with Slack?
Use "Report a problem" on this page to tell us what isn't working. Reports are anonymous: we don't store your IP address, only a one-way code that stops the same person reporting many times, plus your country.
Does Slack still post outages on X?
Not on a dedicated account. Slack retired its @SlackStatus account in October 2023 and now posts incident updates on slack-status.com, which also has RSS and Atom feeds you can subscribe to.
Why is Slack down for my team but not for someone at another company?
Some Slack incidents only hit a share of workspaces. Your company may also route Slack through its own VPN, proxy or single sign-on, any of which can fail independently. Check slack-status.com, then ask your IT team.
Why are Slack huddles not connecting when messages work?
Huddles use separate audio and video infrastructure, listed as its own component on Slack's status page. They also need extra network access that strict company firewalls sometimes block. If the status page shows Huddles as fine, try another network.
This page's guide was last reviewed on 24 October 2026. Spotted something wrong or out of date? Tell us.
