CheckWebsiteNow

Live status check

Is Slack down right now?

We check slack.com from one measurement point when you open this page. This shows what we saw, not a worldwide verdict.

A fresh check of slack.com runs in your browser. If no result appears, run the check on the start page.

Our last check

Not checked yet — a fresh check starts when you open this page.

About Slack problems

Slack problems can show up as messages that do not send, a workspace that will not connect or huddles without sound. Check the Slack status page first, then compare the desktop app with Slack in a browser to see whether only one of them fails. Company networks with strict proxies or firewalls can block the live connection Slack needs.

Official information

Slack official status page (verified )

Our check and Slack's own status page can disagree. We test from one location and read only the homepage response. The provider reports what it knows about its own systems, such as sign-in, apps or single regions. A site can answer our check while one feature is broken, and a regional problem can affect one location but not another.

Slack help pages

How this check works

  • One measurement location (single-self-hosted-probe), not a worldwide test.
  • We read only the response headers of the HTTPS homepage; page content and features are not tested.
  • We follow at most 5 HTTPS redirects and check every new address again.
  • The whole check stops after 10 seconds.
  • Results are reused for 60 seconds; this page refreshes its saved check at most every 10 minutes.

Full method and limits

Typical Slack problems

An editorial list of typical problems, not based on live user reports.

  • Messages do not send If Slack marks messages as not sent or keeps reconnecting, the live connection to Slack is being interrupted, for example by a proxy, firewall or unstable network. Guide: ERR_CONNECTION_RESET
  • App stuck on connecting When the Slack app cannot reach Slack's servers at all, try another network to see whether your current network blocks it. Guide: ERR_CONNECTION_TIMED_OUT
  • Too many requests from an app or bot Slack's Web API answers 429 with a Retry-After header when an app sends too many requests, so the integration should wait that long before retrying. Guide: 429 Too Many Requests
  • Company sign-in loops Workspaces with single sign-on send you through your company's login page, so a loop there can come from old cookies for that login provider or for slack.com. Guide: ERR_TOO_MANY_REDIRECTS
  • Huddle has no audio Slack huddles need microphone permission for the Slack app or browser, so check the system privacy settings and the selected audio device.

General fixes: Meetings and work chat

  1. Check microphone and camera access Make sure the app may use the microphone and camera in your system privacy settings, and pick the right devices in the app.
  2. Join from the browser If the desktop app will not connect, open the meeting or workspace in a browser. This shows whether the app or the network is the problem.
  3. Use a steady connection Calls need a stable connection. Move closer to the router or use a cable, and pause large downloads during the call.
  4. Ask about network rules Company and school networks may block calls or live connections. Your IT team can tell you whether the service is allowed.

Check another website

One measurement point. Results explain what we saw, not a worldwide verdict.