Monday January 31, 2022

Incident

Slack not fully loading for some customers.

Issue summary:
At 1:02 AM PST on January 31, 2022, a regional back end server responsible for caching channel, member, and emoji data crashed and failed to restart correctly. As a result, Slack workspaces hosted on that server were unable to load these types of data.

We deactivated the server and reassigned all of the affected teams to a healthy host by 10:10 AM PST on January 31, 2022. Doing so has resolved this issue for the impacted users and we've confirmed that all of our regional servers are working as expected.

2:40 PM PST

Customers affected by connectivity issues should no longer be having trouble. We've rolled out a fix and have confirmed Slack is back to normal. Apologies for the disruption we caused, and thank you for your patience.

10:23 AM PST

We are continuing to investigate the connectivity issue, but we don't have additional information just yet. We'll be back in 30 minutes with another update.

9:40 AM PST

We don't have any new information to share at this time but we're working to get things back to normal as quickly as possible. Thank you for your patience.

8:58 AM PST

We've isolated the problem and we're focused on getting Slack working again as soon as possible. Thank you for your continued patience.

8:23 AM PST

No additional news to share just yet, but we're focused on getting things back to normal as quickly as we can. We apologize for the continued trouble.

7:50 AM PST

We're continuing to investigate the issues with slowness in loading features, but there's no new updates to share at the moment. Our teams are focused on getting things up and running as soon as possible, and we'll be back in 30 minutes with another update.

7:22 AM PST

Some users seem to be experiencing connectivity issues within Slack, including slowness in loading features and applications, and delays in seeing channels, message and sidebar content.

We're on the case, and we'll provide another update once we have more information to share.

6:38 AM PST

Services affected

Connectivity

Status

Incident