Is Slack down?
Is Slack not loading, repeatedly reconnecting, or failing to send messages? Check Slack Status first, then use targeted tests to distinguish a Slack-wide incident from a problem with your workspace, account, app, browser, or network.
Site Administrator
Last reviewed: September 25, 2026
LATEST RECORDED STATUS
Up Slack’s website appeared to be up and responding normally at the last check.
| Endpoint | Status | Observed |
|---|---|---|
| slack.com | Operational | 2026-11-09 12:34 UTC |
Is it working for you?
0 recent reports — more reports are needed for a useful trend.
For the full picture, including partial or regional outages a single external check may miss, see Slack’s official status page. official status page.
What this check can tell you
- Check Slack Status before making repeated local changes.
- If Slack works on another device or network, the problem is more likely related to your browser, app, VPN, proxy, security software, or connection.
- If several coworkers are affected across different networks, a broader Slack or workspace incident is more plausible.
- Failed sign-in, an unavailable workspace, unsent messages, and repeated reconnects can have different causes. Identify the failing action first.
- Record the exact symptom, approximate start time, affected workspace, device, browser, and network before contacting an administrator or support contact.
About Slack reliability
Understanding Slack availability
Slack may be partly available while a specific function is failing. An incident can affect sign-in, workspace loading, message delivery, file activity, notifications, or connection stability without making every Slack feature unavailable.
The official place to check reported Slack incidents is Slack Status. Compare its updates with what you observe: whether coworkers are affected, whether the same problem appears on another device or network, and whether the failure is limited to one workspace or action.
A clear status page does not rule out an account, workspace, browser, app, or network problem. If no Slack incident is listed, continue with targeted checks instead of repeatedly refreshing or reinstalling Slack.
How to troubleshoot Slack
Troubleshooting Slack problems
Check for a wider Slack incident
Open Slack Status and look for an active incident or degraded component. Ask a coworker to test the same workspace. If multiple people are affected at the same time, especially across different networks, avoid repeated reinstalls or configuration changes and follow the official incident updates.
Test whether the problem is local
- Try Slack on another device or a different network, such as a mobile connection.
- If Slack works elsewhere, restart the browser or Slack app and, where your organization permits it, temporarily test without a VPN, proxy, firewall rule, or security filter.
- If only one browser fails, try a private window or another browser. Extensions, blocked site data, an expired session, or a damaged local cache can affect Slack Web.
- If the desktop app fails while the browser works, the issue is more likely limited to the app installation or its local session.
Separate sign-in, account, and workspace issues
If Slack opens but sign-in fails, confirm that you are using the intended account and workspace sign-in flow. If you can sign in but only one workspace fails to load, compare it with another workspace or ask a coworker to test. Workspace membership, permissions, and organization access may require an administrator.
Identify the failing Slack function
A loaded Slack interface does not prove that every function is working. Note whether the problem affects loading, authentication, one workspace, message delivery, file activity, notifications, or connection stability. A narrow failure is more consistent with a particular feature, workspace, account, or network path than with a complete Slack outage.
Investigate browser and network errors
If the browser shows a timeout, refused connection, DNS failure, or gateway error, test another network and check whether unrelated websites load normally. These symptoms can occur between your device and Slack rather than at Slack itself. Use the matching guide when a specific error appears:
- [ERR_CONNECTION_TIMED_OUT](/guides/err-connection-timed-out)
- [ERR_CONNECTION_REFUSED](/guides/err-connection-refused)
- [DNS_PROBE_FINISHED_NXDOMAIN](/guides/dns-probe-finished-nxdomain)
- [HTTP 502 Bad Gateway](/guides/http-502-bad-gateway)
- [HTTP 503 Service Unavailable](/guides/http-503-service-unavailable)
If Slack Status is clear but the problem continues on only your account, workspace, device, or network, give your administrator or support contact the exact symptom, error text, approximate start time, affected workspace, and tests you completed.
Related troubleshooting guides
TROUBLESHOOTING GUIDE
ERR_CONNECTION_TIMED_OUT
`ERR_CONNECTION_TIMED_OUT` means the browser waited for the destination server or an intermediary to respond, but no usable response arrived before the connection timeout. Common causes include an unreachable or overloaded server, a firewall silently dropping traffic, incorrect DNS, a broken network route, or a CDN or proxy that cannot reach the origin. Test from another network first, then check DNS, infrastructure health, firewall rules, and resource usage.
TROUBLESHOOTING GUIDE
ERR_CONNECTION_REFUSED
ERR_CONNECTION_REFUSED means the browser reached a destination address, but the connection was rejected before the website returned a response. Common causes include a stopped web server, no process listening on port 80 or 443, a service bound only to localhost, an incorrect DNS destination, or a firewall rule blocking access. Check the destination and listener first, then test from an external network.
TROUBLESHOOTING GUIDE
DNS_PROBE_FINISHED_NXDOMAIN
DNS_PROBE_FINISHED_NXDOMAIN means DNS could not find the exact hostname requested. Check the spelling, subdomain, authoritative nameservers, required A, AAAA, or CNAME record, and domain registration status. If the DNS change was recent, cached negative responses may persist; it is usually a DNS or domain configuration issue rather than a web-server outage.
TROUBLESHOOTING GUIDE
502 Bad Gateway
A 502 Bad Gateway means a reverse proxy, load balancer, or CDN could not obtain a valid response from the backend server. Check the backend process, proxy error log, upstream host or port, socket permissions, resource limits, and CDN-to-origin access. The fault is usually between servers rather than in the browser.
TROUBLESHOOTING GUIDE
503 Service Unavailable
A 503 Service Unavailable response means the service cannot handle the request at that time. Common causes include exhausted CPU, memory, worker, or connection capacity; incomplete maintenance mode; an unavailable database or other dependency; or a proxy, WAF, rate limiter, or load balancer returning 503. Identify which layer generated the response, then review logs and resource usage before changing settings.
Sources & references
Official source
- Slack Status — check Slack’s reported service availability, affected components, and incident updates.
For account, workspace, browser, and app-specific issues, consult the relevant Slack support or administrator documentation for your organization’s sign-in and access process.
How this check works
Every time this page loads, our server makes its own request to slack.com (and its API domain, when applicable) and reports what it got back — a real HTTP response, a timeout, or a connection failure. That result is cached for up to 2 minutes.
This confirms external reachability; it does not test every feature, region, account, or network path. Cross-check the official status page when one is available.
Embed this live status badge
Add this badge to a dashboard, documentation page, or blog. The badge reads the cached Erriscope observation and links back to this status page.
<a href="https://erriscope.com/status/slack/"><img src="https://erriscope.com/status/badge/slack.svg" alt="Slack status on Erriscope" width="210" height="34"></a>Frequently asked questions
Is this the same as Slack's official status page?
No. This is a live, one-off connectivity check run from our own server, not Slack's own incident reporting. Their official status page can show partial, regional, or component-level issues our single external check cannot detect.
Why does this show "Up" when Slack feels slow or broken for me?
A basic reachability check confirms that the server responded to our request. It does not test every feature, region, ISP, browser, or account-specific issue.
How often is this checked?
A check is refreshed after the two-minute cache expires. The displayed check time shows when the observation was made.
Does an API outage mean the whole product is down?
Not necessarily. Many services split their website and API onto separate infrastructure, so one can fail while the other keeps working.
How do I check whether Slack is down?
Check the official Slack Status page and compare its updates with reports from coworkers. A failure affecting several users across different networks is stronger evidence of a broader incident than a problem limited to one device or connection.
Why does Slack work for other people but not for me?
The cause may be your browser, desktop app, network, VPN, proxy, security software, account, or workspace access. Test another network or device, then try another browser or Slack Web to narrow down the affected layer.
Why can I open Slack but not send messages?
Loading Slack and delivering a message are separate tests. Check whether messages fail in one conversation, one workspace, or everywhere, and ask another member to test. If the failure is widespread, check Slack Status; if it affects only your account or workspace, contact an administrator or support contact.
What should I do if Slack keeps reconnecting?
Check Slack Status, then test another network and device. If the connection is stable elsewhere, investigate the original network, VPN, proxy, firewall, browser, or app session instead of assuming Slack is unavailable for everyone.
Does a clear Slack Status page prove Slack has no problem?
No. The status page reports known service events, while an issue may still be limited to a workspace, account, device, browser, or network. Cross-device and cross-network tests help distinguish those cases.
What information should I collect before reporting a Slack problem?
Record the failing action, exact error text, approximate start time, affected workspace, device or browser, network used, and whether another device or coworker can reproduce the issue. This information helps separate a service incident from a local or access-related problem.
This is a live connectivity check from our server, not an official statement from Slack. A down result may also reflect a regional or partial outage.
LIVE CHECKS
