Saturday September 24, 2016

We've made some configuration changes that we believe should allow all impacted users to once again access Slack. Thank you all for your patience and help in debugging the intermittent and location-sensitive empty DNS responses that have plagued us this weekend. If problems persist and clearing your local machine's DNS caches does not fully fix the problem, please email <a href="mailto:feedback@slack.com">feedback@slack.com</a> for help.

4:59 PM PST

DNS issues are continuing for several countries in Europe and the MIddle East. We are working with our DNS provider to track down the root cause.

A simple work-around is to change your DNS server to an alternate such as google. (see: https://developers.google.com/speed/public-dns/docs/using)

1:42 PM PST

The cause seems to be that some DNS servers in Europe and the Middle East are returning an empty record for slack.com.

Many customers have recovered from this problem as their ISPs refresh their DNS cache. However, we continue to hear a few reports of problems, so leaving this issue marked as open.

A simple work-around is to change your DNS server to an alternate such as google. (see: https://developers.google.com/speed/public-dns/docs/using)

7:26 PM PST

Our DNS provider continues to work on the issue. The cause seems to be that some DNS servers in Europe and the Middle East are returning an empty record for slack.com.

A simple work-around is to change your DNS server to an alternate such as google. (see: https://developers.google.com/speed/public-dns/docs/using)

10:33 AM PST

Our DNS provider is working on the issue, and we are still investigating other options on our end to get everyone back onto Slack as quickly as possible.

7:54 AM PST

Some users are reporting success connecting to slack, but we are still monitoring and investigating the issue. It appears a small upstream DNS propagation issue may have been cached for some users, causing the connection problems. To potentially update your local computer's cache more quickly:

On macOS or Linux (in the Terminal):
dig slack.com +trace

On Windows (in cmd prompt):
nslookup -debug slack.com

Note that your upstream DNS may still not be updated correctly, so we are still investigating to get all users connected.

6:49 AM PST

Some users, primarily in Europe, are having issues connecting to Slack. We're investigating the problem and believe it is a DNS issue.

4:36 AM PST