Slack is the messaging app many companies use in place of internal email: channels, direct messages, huddles for quick calls, file sharing and apps that post updates into conversations. Each company or community has its own workspace, usually with an address under slack.com.
The live check on this page requests slack.com from a neutral server. It reports whether Slack’s main site and sign-in pages answer, which tells you if the platform is broadly up. The real-time messaging connection that the app holds open is separate, and the Slack status site lists that and other parts one by one.
How Slack connects and where it breaks
Slack’s app keeps a continuous connection to Slack’s servers so new messages arrive instantly. That connection is more fragile than loading a web page. A VPN that resets long-lived connections, a captive Wi-Fi portal in a hotel or a laptop waking from sleep can break it while the website still loads. The app then shows a connecting banner, messages stop arriving and sent messages turn red.
On top of that, every workspace is configured by its owners. Single sign-on, allowed file types, retention rules and which apps are installed differ from one workspace to the next. A problem that hits only one of your workspaces is very often a setting there.
Slack fault finder
| What you see | Likely cause | What to try |
|---|---|---|
| Connecting banner stays on | Real-time connection dropped | Quit and reopen Slack, leave the VPN |
| Message marked as failed | Message did not reach Slack | Retry when the connection returns |
| Notifications stopped | Do not disturb, OS settings, or a notification incident | Check the bell menu and system settings |
| Huddle has no audio | Media traffic blocked | Try without VPN or another network |
| Sign-in loops to company login | Single sign-on problem | Contact your IT team |
A quick routine for Slack
- Look at the status above
If the check fails, the issue is on Slack’s side; your messages will send when it recovers.
- Open Slack in a browser
If the web version works and the desktop app does not, the app needs a restart or its cache cleared from the Help menu.
- Restart the app fully
On macOS, quit from the menu bar; on Windows, quit from the system tray icon.
- Check notification settings
Do not disturb schedules and per-channel settings silence more alerts than outages do.
- Sign out and back in
This refreshes the session and fixes many workspaces that stop syncing after a password change.
Busy hours and plan limits
Slack traffic follows the working week. Monday mornings, the start of the day in North America and Europe, and moments when many people return from a holiday weekend put the most load on connections and notifications. Separate from load, plan limits cause confusion: a free workspace that hides older history looks like data loss but is a plan restriction, and upgrading the plan makes the messages visible again.
Reading the result for Slack
A reachable result means slack.com and the sign-in pages answer normally. Messaging, file uploads, search and notifications run on their own systems, so one of them can lag while the site is fine; the status site names the affected part. A slow result usually matches channels that load late and a desktop app that takes a long time to switch workspaces. When the check passes and only your company’s workspace misbehaves, ask a colleague on a different network to try. If it works for them, your network or VPN is the most likely cause.
Slack’s own connection test
Slack runs a connection test at slack.com/help/test. You sign in to a workspace, and it checks whether your network can reach the addresses Slack needs, including the WebSocket connections that carry live messages, with a backup route if the primary fails. A warning on the WebSocket lines while the rest passes is the classic sign of a company proxy or security tool that decrypts traffic and breaks long-lived connections. That points at your network, and Slack’s help pages list the domains a network administrator needs to allow. Antivirus and ad-blocking software can interfere in the same way, so switching them off for a minute is a fair test. Run it twice.
When the test passes at home and fails at the office, send the result to IT. It tells them more than a description of the banner does. For the wider question of whether Slack is down for everyone, the step-by-step guide to telling an outage from a local problem follows the same logic as the check above.
Official Slack help
- Slack System Statusslack-status.com
- Slack Help Centerslack.com/help
- Slack Status on X@SlackStatus
Questions about Slack
Why does Slack keep showing a connecting banner?
The app lost its real-time connection to Slack and is trying to restore it. Network changes, a sleeping laptop and VPNs that drop long connections are common reasons. Quit and reopen the app. If it persists on several networks, check the Slack status site for a connectivity incident.
Why did my message fail to send?
A message with a red warning did not reach Slack's servers. Click it to retry once your connection is back. If the message contains a large file or many links, it may take longer, and some workspaces block certain file types or external links.
Why can I not find older messages?
Free Slack workspaces only show a limited period of message history, and anything older is hidden until the workspace upgrades. On paid plans, administrators can set retention rules that delete older messages. Neither is an outage.
Why can I sign in to one Slack workspace but not another?
Each workspace has its own sign-in rules. One may use email and password while another requires your company's single sign-on. If the company login fails, the identity provider or your account there is the likely cause, not Slack.
Do Slack huddles fail differently from messages?
Yes. Huddles use separate audio and video connections that firewalls and VPNs block more often than messaging. If messages work and huddles do not, test without the VPN and check whether your network allows the media traffic Slack lists in its help center.
Where can I see Slack incidents?
Slack runs a status site that lists components such as messaging, connections, file uploads, notifications and huddles, along with incident history. Slack also posts during larger incidents on its status account on X.