We’ve begun partnering with an upstream provider to help with our investigation and are waiting on additional details from their analysis. Emails are still reaching end users, but some may still be delayed. We’ll be back with another update as soon as we receive more information from our partners.

We've identified a new incident that is now resolved for all users. Below is a summary:Between 7:09 AM and 7:28 AM PDT on August 7, 2025, some users may have experienced intermittent errors or latency with several Slack features. This brief issue could have caused delays when performing actions such as searching, messaging, and using administrative tools.An internal health dashboard alerted us to an unusual spike in traffic to one of our backend caching systems, which caused timeout issues. This primarily impacted users on Enterprise Grid, though a number of non-enterprise users may also have been affected.To quickly mitigate the impact, we temporarily redirected traffic away from the problematic caching service to allow it to stabilize. We also implemented additional measures to help reduce the impact of future traffic spikes. Once our internal metrics returned to normal, we reverted traffic back to its standard routes. All features are working as expected.

From around 10:00 AM to 7:52 PM PDT on August 5, 2025, some users were unable to change their vision-assisted themes in Slack. Affected users saw an error code like "REB6E19833F7" when they tried to make a change.The issue was caused by a recent code change that introduced a new configuration check. When a user attempted to change a theme, the app would check a corrupt property and unexpectedly return an error. We identified and reverted the problematic code, restoring functionality for all affected users.

From July 26, 2025 at around 3:00 PM PDT until around 4:32 PM PDT on July 27, 2025, some users in the Asia-Pacific (specifically the Philippines) regions may have encountered trouble connecting to or loading Slack.A regional upstream provider experienced connectivity problems that affected many services, including Slack. We initially investigated this as a Slack-specific incident, but later determined the root cause was with the provider and adjusted our communications to reflect this.

From approximately 5:00 PM PDT on July 25, 2025, until 4:26 PM PDT on July 30, 2025, some users on Enterprise Grid may have experienced unexpected in-app reloads with their Slack desktop and mobile clients.We traced this to a backend process that handles app initialization. This process began incorrectly reading invalid session information, which forced the client to repeatedly refresh in an attempt to get updated data.We identified the problematic code logic and implemented a fix, which resolved the issue. As a workaround, affected users were able to successfully use the Slack web browser client. Additionally, some users reported that clearing the app cache (via Help > Troubleshooting > Clear Cache and Restart on the desktop app) also resolved the issue.