How to use it
- Read the live status above. It tests Slack from outside your network.
- Open the official Slack System Status page for confirmed incidents.
- If Slack is up, work through the fixes below, cheapest first.
- Press the report button if it still fails, so other visitors see it.
Is Slack down for everyone or only for you?
Slack has a web API that handles most actions and a separate real-time connection, a WebSocket, that pushes new messages to you as they arrive. If the API works but the WebSocket is blocked, Slack opens and loads old messages but new ones do not appear on their own. That is the usual pattern on strict office networks.
Our check calls Slack's public website and its API test endpoint from outside your network. If they answer, the service is reachable. Slack's own status site shows incidents and also lists which features are affected, such as messaging, calls or file uploads.
The live check on this page requests slack.com and slack.com from our servers every few minutes. A normal answer from those addresses means the service is reachable from outside your network. It does not prove that every feature inside Slack works, which is why the problem reports and the fixes below matter.
What usually breaks with Slack
Cannot connect or load
The app shows a connection error or a blank screen. Proxies, firewalls, antivirus and VPNs are the common blockers.
Messages arrive late or not at all
A grey banner appears and you must refresh to see new messages. This means the real-time WebSocket connection is failing.
Calls and huddles
Huddles will not start or audio drops. Calls use their own media connection, separate from message delivery.
Files, search and notifications
Uploads fail, search returns nothing or push alerts do not come. These are separate features and can degrade on their own.
Workflows and integrations
Apps and automations stop posting. The cause can be Slack's API or the third-party app itself.
How to fix Slack when it only fails for you
Start at the top. The first steps are the cheapest and fix most cases that are not a real outage.
- Reload the app. Press Ctrl+R on Windows and Linux or Cmd+R on Mac. This often clears a transient server error.
- Clear the cache and restart. In the desktop app open Help, then Troubleshooting, then Clear Cache and Restart. On Windows 10 the menu is behind the three-line icon at the top left.
- Run Slack's connection test. Open slack.com/help/test in the browser you use. If it reports errors, send the result to your network administrator.
- Try a private window. Open Slack in an Incognito or private window. If it works there, a browser extension is the cause, so disable extensions one by one.
- Ask your admin to allow WebSockets. Slack's help lists wss-primary.slack.com, wss-backup.slack.com and wss-mobile.slack.com. Blocking these causes the grey banner.
- Turn off VPN or proxy. Disconnect them briefly and see whether Slack reconnects. Some security tools inspect and break WebSocket traffic.
- Collect Net Logs. Under Help, Troubleshooting choose Restart and Collect Net Logs, reproduce the problem, then Stop Logging. Support can use the file.
- Update or reinstall the app. On mobile, update Slack from the App Store or Google Play. On desktop, reinstall from slack.com/downloads. Your messages stay in the workspace.
If none of this helps and the live check above shows the service as up, read our guide on why a website is not loading, or see how to flush DNS.
Common Slack error messages
| Message or code | What it means | What to do |
|---|---|---|
| Slack cannot connect | Network settings or security tools such as a proxy, firewall, antivirus or VPN may be interfering. | Use Restart Slack, then review proxy and firewall settings or collect Net Logs. |
| For some reason, Slack couldn't load | A browser extension, security software or an issue on Slack's end stopped the app from loading. | Clear the cache, test in a private window and run slack.com/help/test. |
| Sorry! Something went wrong, but we're looking into it | A server error on Slack's side. | Reload with Ctrl+R or Cmd+R and check status.slack.com for incidents. |
| Last updated less than a minute ago | A grey banner that means the WebSocket connection is failing, so new messages are not delivered automatically. | Ask your network administrator to allow the Slack WebSocket domains. |
Official Slack status and support
The company itself has the final word on outages. Check Slack System Status for confirmed incidents and use Slack Help Center if your account has a problem that is not an outage. We are not affiliated with Slack.
Facts and menu names on this page were checked against the official sources below on October 25, 2026. Apps change their menus, so a setting may sit in a slightly different place in your version.
Other services people check
Frequently asked questions
How do I tell if Slack is down or only my workspace?
Check status.slack.com and our live result. If both look fine, ask a coworker on a different network to open the same workspace. If they can, the problem is on your network or device.
Why does Slack work on my phone but not on my work computer?
The phone uses a different network or mobile data. This points to a proxy, firewall or VPN on the work network.
Why are my messages delayed?
A delay usually means the real-time connection is unhealthy. Reload the app and check that the WebSocket domains are allowed.
Does the Slack status page show my specific plan?
It shows platform-wide incidents. Issues that affect a small number of workspaces may not appear, so contact Slack support with your workspace URL if everything else is normal.
Will I lose messages during an outage?
Messages are stored on Slack's servers. If a send fails, copy the text before you reload so you can post it again.