Is Slack down right now?
HostTracker's monitoring network reached slack.com and completed a full check without errors. It has been up for 14d 10h.
Checking slack.com right now
A fresh check, started when you opened this page - each probe runs its own independent DNS, TCP, TLS and HTTP request. Anonymous runs sample the network; a signed-in account checks from more locations.
Incident history
LAST 90 DAYSNo incidents recorded in the last 90 days.
About Slack outages
Written by the HostTracker monitoring team · updated from live probe data.
Slack has become the default real-time communication layer for a large share of remote and hybrid teams, so an outage doesn't just interrupt casual chat - it can stall incident response, block approvals, and cut off the exact channel many teams would otherwise use to coordinate during a crisis (including, ironically, coordinating around a Slack outage itself). Slack outages often affect messaging, huddles/calls, and integrations (like bots and webhooks posting into channels) somewhat independently, so a team might find messages aren't sending while huddles still connect, or vice versa. A live check of slack.com's own reachability is a useful first signal before assuming the problem is your workspace's specific configuration.
Common causes of Slack downtime
Backend messaging infrastructure incidents that delay or fail to deliver messages while the app itself still loads
Realtime connection (WebSocket) issues that cause the app to appear "stuck" or show stale data until manually refreshed
Integration/API-layer incidents that break bots, webhooks, and third-party app connections without affecting core messaging
Regional network routing issues that make slack.com unreachable from specific corporate networks or countries
Not sure whether it's Slack or your own connection? Read the full breakdown in our website down checker guide for a general walkthrough of diagnosing any outage, from DNS failures to expired certificates.
Other services we track
HostTracker has monitored websites and online services since 2004 and is trusted by 500,000+ sites today, covering 13 check types from 300+ global locations. Want the same multi-location confirmation and instant alerts for your own site or any service you depend on? Getting started costs nothing - start a free monitor or compare plans and pricing.
Questions people ask during an outage
The live probe run on this page tests slack.com from a broad sample of HostTracker's 300+-location monitoring network - many independent networks at the same moment, rather than just your own connection. If every location fails to reach it, the outage is real and affects everyone; if only a few locations fail while most load normally, the problem is local to those regions or networks rather than Slack being fully down. A single refresh from your own browser can never make that distinction, because it only ever tests from one vantage point on one network.
Yes. HostTracker lets you add any URL - including third-party services you depend on, not just your own website - as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.
This pattern (messages appear to send on your end but don't arrive for others) typically points to a backend delivery incident rather than a full outage - the client-side app and your connection are working, but Slack's message-delivery infrastructure is degraded or delayed somewhere between sending and delivery. This is different from a connection failure, where the app itself would show an error or fail to load. If it's happening for your whole team, not just you, it's worth checking whether Slack has an acknowledged incident before assuming it's a workspace-specific setting.
It's uncommon but possible - most Slack incidents affect shared backend infrastructure broadly rather than being scoped to individual workspaces, so a genuine Slack-side outage usually affects many organizations simultaneously. If Slack looks fine everywhere else but consistently fails for your organization specifically, the more likely causes are a corporate network/firewall change, a DNS issue on your network, or a workspace-specific configuration problem rather than a Slack-side outage - worth ruling those out first before assuming a broad incident.
Monitor your website from 300+ locations
Start a free trial and get instant alerts when your site goes down - verified from multiple locations before you're notified.