Is Slack down right now?

No. Our checks are finding no problems with Slack right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Slack continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.

The problems visitors report most often on this page are website / app down, can't log in, messages not sending, no notifications, calls dropping and upload failing. Those are the options the report button offers for Slack, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.

Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With Slack specifically, messaging, calls, uploads, search and sign-in are separate systems, and Slack incidents often reach a subset of workspaces. Yours can be broken while a colleague on another is fine, and calls use a live connection that corporate networks block on their own. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.

For Slack, open the same workspace in a browser rather than the app, and on mobile data if you can. Working in a browser but not the app points at the app or its cache. One workspace failing while another loads points at Slack. A problem that follows you across networks and devices is very unlikely to be yours.

If this page shows evidence of problems, the fault is most likely on Slack's side. Specifically: do not resend a message stuck on sending. Slack queues it and delivers it when the connection returns, so resending posts it twice. Anything you can already see has been delivered even if the app looks stalled. Reporting it here helps other people see they are not alone.

Continuously, around the clock. Slack publishes a machine-readable status feed, so our first check reads it directly and reports what Slack itself says. If that feed is unreachable we fall back to a direct HTTP probe, then an ICMP ping, then reports from visitors. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.

Yes, at slack-status.com, and it is linked further up this page. That is Slack's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.

No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to Slack or slack.com. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need Slack's own support, not us.