Wednesday December 8, 2021

Issue summary:
From December 7 at around 8:00 a.m. PST to December 13, 2021 at around 1:49 p.m. PST, some customers experienced issues with calls and huddles.

Following a service provider's outage, stale requests in our database prevented some users from joining new calls and huddles, while stale cached data caused some users to appear active in both.

We manually cleared stale calls and huddles from our backend, restoring functionality and dislodging stuck user statuses.

4:26 PM PST

We believe the issue with users appearing in a huddle after it has ended should now be resolved for all customers. If you continue to have any trouble please try reloading Slack (press Command/Control + Shift + R). You can also reach out to us at feedback@slack.com if the issue persists.

3:00 AM PST

We’re continuing to work towards resolving this issue for the very small number of users who are still impacted. We appreciate your continued patience, and will let you know as soon as we have another update to share.

3:36 PM PST

While we have deployed a fix, some customers may continue to appear in a huddle once a huddle has ended. We are continuing to investigate this issue and will keep you updated.

8:01 AM PST

We've deployed a fix, and customers should no longer be experiencing this issue. If you continue to have any trouble, please let us know via feedback@slack.com

10:28 PM PST

We are still investigating the huddles issue that's causing the huddles status to remain as well as the inability to join new huddles.

10:28 AM PST

Some users may be unable to initiate new huddles in addition to appearing on previous huddles after they have left. We're investigating this issue and we thank you for your continued patience.

9:21 AM PST

Some users may appear to still be on a huddle once the huddle has ended. We’re investigating the issue and will be back with an update shortly. Thank you for your patience.

8:11 AM PST

Issue summary:
On December 8, 2021 from around 5:00 p.m. PST, to 8:15 p.m. PST, users in South Korea who’ve enabled 2FA via SMS were receiving incomplete messages and were unable to login to Slack.

After a thorough investigation, we found that this occurred when the user’s language was set to Korean. This impacted carriers which prevented the 2FA messages from being delivered successfully in Korean.

A fix has been deployed to force the language of the message to English. This will ensure the full messages are delivered to enable log in.

8:06 AM PST

We’re happy to report that customers should no longer have issues with receiving 2FA codes when the language is set to Korean.

Apologies for the disruption, and thank you for your patience.

8:34 PM PST

We are continuing to investigate issues with receiving 2FA codes when the language is set to Korean. Customers using English should be receiving 2FA codes correctly. Our apologies for the disruption.

6:14 PM PST

Some customers in Korea aren't receiving 2FA codes set to Korean, or they may be receiving 2FA codes with garbled text.

We're investigating now and will be back with more information as soon as it's available, or in 30 minutes.

5:46 PM PST