Troubleshooting Tips

How to troubleshoot Slack

If you're having trouble connecting to Slack, this guide can help you narrow down the root cause.

Slack is among the leading team communication platforms in the world. If you or one of your team members is having trouble connecting to Slack, it can quickly grind a workday to a standstill.

By using this guide and a network troubleshooting tool (like PingPlotter), you can identify if the issues with Slack are caused by a problem locally, an issue with your ISP, or with Slack itself.

Before you begin, make sure to check Slack’s service status page for any announced outages or known issues impacting service.

Setting up PingPlotter

To troubleshoot your network connection to Slack using this guide, you will need to download and install the latest version of PingPlotter. A 14-day free trial is always available to help you get started.

For troubleshooting Slack, you can use PingPlotter’s default settings.

What to target

Slack has two destinations you can trace for troubleshooting app connectivity. You will want to start traces to both in order to find the root cause of your issue.

You can click on the links below to automatically launch a PingPlotter trace to Slack’s servers (if the link does not open PingPlotter, you can also enter the IP address of the server into PingPlotter's Target Bar).

Step-by-step instructions

1. Check the status of Slack’s service

If you have not already, check Slack’s service status page to see if they are currently experiencing any known downtime. If so, this is most likely the cause of your issue.

2. Check your general connection

You can quickly identify basic network issues by starting a PingPlotter trace to a reliable target (such as Enter “” Into PingPlotter’s Target Bar and click the green Start button, or use the link below to start tracing automatically.

If you see high latency or packet loss, your network issue may be broader than just Slack. See our guide on solving common network problems to identify what might be the culprit.

3. Check your connection to Slack's servers

You should begin by using Slack’s built-in connection test tool. If the Browser section shows issues, it is highly likely the network is the root cause of your problem.

Using the targets listed above, start tracing to the Slack servers. While the trace runs in PingPlotter, continue to attempt using Slack. If you experience any issues (such as frequent disconnects or messages not sending), check PingPlotter to see if you see any sudden spike in latency or packet loss. Make note of this and continue testing.

We recommend collecting 10 minutes of data at a minimum for the most accurate results. Once you have your PingPlotter results, use the information below to narrow down your issue.

What to look for

There are many issues that could be affecting Slack. Here are some of the most common:

Device completely "down"

Bad local hardware or wiring in PingPlotter

This result would show a bunch of solid red bars from the beginning of the route to the end. It can also start a “hop” or two down the line.

What do I do if I see this?

  • If it’s starting at the very beginning of the trace, try giving your router a reboot.
  • If that doesn’t help, and the pattern persists after you’ve given it a reboot, you may need to look into a replacement router.
  • If the red is starting a hop or two down, contact your ISP.

WiFi interference

Example of wireless interference in PingPlotter

With this, we’ll see some red beginning at the start of the route similar to what we saw with a device being down, but more sporadic. This is normally caused by poor WiFi access point placement or by too many networks broadcasting nearby (apartment complexes are notorious for this).

What do I do if I see this?

  • You can try a router or WiFi access point reboot right off the bat.
  • Switch to a different wireless band. Most WiFi access points these days have dual-band; try to hop onto the other band temporarily.
  • If the above isn’t possible, you may want to look at where you put your router or WiFi access point. Make sure that it is away from metal (including electrical conduit), and is away from televisions, microwaves, and Bluetooth devices like speakers.
  • You may be experiencing saturation on your current WiFi channel. You can research the model of router or WiFi access point you have, and search for “channels”. You might want to set the device to switch channels automatically or search for a channel that isn’t being overused by nearby networks.
  • If that doesn’t shape it up, you can acquire an Ethernet cable and plug your computer directly into your router. We always recommend a wired connection over a wireless one.

Bandwidth saturation

An example of bandwidth saturation in PingPlotter

Normally, the pattern that indicates that you’re overusing your bandwidth would look like the above: an almost sawtooth-like pattern, which may or may not have a clear start and stop point.

What do I do if I see this?

  • Use less bandwidth by limiting your demand on your connection. Close down music streaming, video streaming, and so forth.
  • Throttle your network. This one’s a bit harder. Search for the model of router you have, and add terms like “rate limiting” or “bandwidth limiting”. That should get you to an explanation of how to throttle back the traffic a bit.
  • If this continues to be an issue, you may need to contact your ISP and ask if you have a higher bandwidth tier available to you.

Helpful resources

We've compiled a list of useful links to help you find additional support information.

Do you support remote workers?

When remote workforces have connection trouble PingPlotter Cloud helps you find the problem and get everyone back online fast.

Start a Trial