Is Slack Down Right Now?

The instant check tool above tests slack.com live from HostTracker's network of 300+ worldwide locations at once, rather than from 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.