[ad_1]
Slack seems to be having issues for some people, with reports of users unable to sign in to the service, receiving errors while attempting to send messages, and unable even access the Slack website. The issue doesn’t seem to affect everyone, and Slack didn’t go so far as to call it an outage on its status page. The differences in experience pointed to a possible routing problem or the even more likely culprit, DNS (it’s still DNS).
At 3:50 p.m. ET, Slack confirmed what we suspected and what others had already figured out – it was DNS.
Some of my colleagues had issues today, while it works well for others (including, unfortunately, me). It’s unclear how widespread the issues are – DownDetector only shows a thousand reports.
The company says it’s working on a fix for the issue, but the crash report page says it’s been in progress since about 12:30 p.m. ET or 9:30 a.m. PT.
If you are still having trouble connecting, you or your ISP may need to flush your cached DNS information. One way to connect if your ISP information has not been updated is to use alternate DNS servers, such as Google’s (8.8.8.8 and 8.8.4.4) or Cloudflare.
We are aware of DNS-related connectivity issues that affect a small subset of users. This issue was caused by our own change and is not related to any third-party DNS software and service. In order to resolve this problem faster, your ISP (Internet Service Provider) will need to empty their DNS record for slack.com. Please contact your networking team to provide them with this information.
We expect all customer connectivity issues to be resolved within the next 24 hours. We know how important it is for people to stay connected and we apologize for this disruption.
If all else fails, maybe the universe is telling you to take a walk or cook something good for yourself. When the chat app finally comes back, it probably will in the blink of an eye – you can just tell your boss that she came back a bit later for you and you’re really trying to message them about it. of this draft, honestly.
Our investigation into this connection issue is still ongoing at this time. We will be back with another update and we apologize for the interruption. Thank you for your great patience. https://t.co/tZUb1TWDEc
– Slack Status (@SlackStatus) September 30, 2021
Updated September 30 at 4:18 p.m. ET: Added information on DNS failures and possible fixes.
[ad_2]
Source link