Loading status…
Loading status…
Slack status · Communication · checked (4m ago)
No — Slack is not down. All Slack systems are reported operational.
According to Slack's official status page, Slack was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Slack's feed reported no outage in 100.00% of our checks.
Everything above is read from Slack's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Slack in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Slack is a workplace messaging platform: channels, direct messages, huddles, file sharing and a large app and integration ecosystem. Because so much is built on its APIs, a Slack incident frequently breaks other teams' internal tooling along with the chat itself.
Slack publishes its own status API rather than using Statuspage, returning an overall state plus a list of currently active incidents. isuptime reports degraded when any incident is active. Slack's own convention is worth knowing: it describes most problems as affecting a subset of teams, because its infrastructure is sharded — an incident that is total for your workspace can be invisible to another company on the same day.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Slack's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Slack was down.
9 other services isuptime tracks were also reporting a problem as of the same check, 4m ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Slack's status endpoint.
Every incident Slack has published in the last 12 months.
Slack has not published a single incident in the last 12 months. That is a statement about Slack's posting habits as much as its reliability — a status page only records what its owner decides to record.
Slack shards workspaces, so “not down for everyone” is a real possibility here in a way it is not for most services. If one workspace fails and another works in the same client, the problem is that workspace's shard or your membership in it. Connection failures behind a corporate proxy or VPN are common. If messages appear to send but never arrive, check whether you are offline in the client — Slack queues locally and looks like it is working.
Slack is reporting no problems right now. If it stops, these cover the same job — each shows its own live status.
Status shown for each is read from that provider's own feed, on the same schedule as this page.