Monday October 4, 2021

Issue summary:
On October 4, 2021 from around 8:46 a.m. to 3:00 p.m. PDT, some users may have experienced difficulties connecting to Slack.

Due to a third party website's outage, DNS (Domain Name System) resolvers around the internet saw a large increase in traffic as clients tried to get valid DNS results, causing timeouts on some DNS resolvers. Users relying on the impacted DNS resolvers may have experienced errors when connecting Slack and some other web services.

Once the outage was resolved, traffic decreased and affected users were able to connect to Slack.

12:54 PM PST

Thank you for your patience. We've confirmed connectivity has returned to expected levels, and there should no longer be an issue loading Slack.

2:08 PM PST

We've determined that widespread internet issues affecting multiple websites have led to small percentage of users not being able to load Slack. We’re monitoring the situation and will provide an update when we know more.

10:43 AM PST

We're investigating reports that Slack may not be loading for some users. We will provide another update in 30 minutes.

10:07 AM PST

Issue summary:
On October 4, 2021 from around 12:42 p.m. to 2:00 a.m. PDT, customers using iOS devices may have gotten a “browser not supported” error message when attempting to view emails.

This error message was a result of a feature release which was only supported by some browsers. We rolled back this feature, resolving the issue for all affected customers.

10:49 AM PST

We’ve resolved the issue some customers were having on iOS and Slack is back to full functionality. We’re sorry for the disruption this has caused.

2:42 AM PST

We’re still investigating the error some customers may be experiencing on iOS, but we don’t have additional information to share just yet. We’ll be back with more information when it’s available.

6:48 PM PST

Some customers may be experiencing a "browser not supported" error on the iOS mobile app when attempting to view an email message.

We're currently investigating the issue, and will be back with an update shortly.

5:14 PM PST