Slack

Starting around 12:13 PM PDT on October 19, 2025, and lasting until around 3:51 PM PDT on October 20, 2025, a significant number of users may have experienced trouble with various features in Slack. This included difficulty loading or editing canvases, starting or ending huddles, connecting to or loading the client, sending messages, loading channels and threads, or using integrations that utilize the Events API. Additionally, some workflows may have triggered multiple times.This issue was the r...

Our mitigation efforts have resolved the majority of stuck huddles. Newly started huddles are working as expected, and we are continuing to clean up the small number of remaining huddles that might be in a stuck state.The issue is resolved. If you are still encountering stuck huddles, please write to feedback@slack.com. We apologize for any inconvenience.

Starting at 8:15 PM PDT on October 21, 2025, until around 1:00 AM PDT on October 22, 2025, some users may have experienced partial search results when querying items in Slack.A backend change unexpectedly initiated a restart job for some services responsible for handling searches. These jobs inadvertently caused the search processing capacity to become temporarily overwhelmed, creating a large backlog of queries. To help mitigate this, we performed a restart of the relevant indexing processes, w...

Between 3:00 AM PDT and 11:00 PM PDT on October 22, 2025, some Slack users experienced trouble with searching. Search results for these users were either missing or only returning partially.A backend indexing job, which processes search results, experienced a backlog of errors. The errors required a large number of job retries, causing the partial results. We implemented a fix by optimizing the retry handling logic, resolving the issue for all affected users.

From 6:00 AM PDT to 9:18 AM PDT on October 22, 2025, some Slack workspaces with EKM (Enterprise Key Management) enabled may have experienced issues with sending messages, uploading files, using Slack Connect, querying search, Slack AI, and using workflows.We traced this back to an unexpected spike in traffic to our backend service responsible for EKM processes, leading to a reduction in service responsiveness. We identified the problematic servers and initiated a restart, restoring full function...

Between approximately 10:00 AM and 4:52 PM PDT on October 29, 2025, some users experienced issues with Slack search. When users tried to search items, the results would not load.We traced the problem back to our search servers, which were hit with a sudden, unexpected surge in memory usage. This increase in usage overloaded the core service responsible for search, preventing it from showing results and creating a large backlog of unprocessed search requests.To mitigate this, we quickly restarted...

Between 1:00 AM PDT and 2:45 AM PDT on November 1, 2025, some users were unable to upload files or create/use canvases in Slack, often resulting in an error.We traced this back to an unexpected spike in error rates for the files.upload API endpoint, caused by database timeouts stemming from an ongoing backend job.We temporarily paused the job to reduce traffic to the affected database and implemented additional logic handling to properly balance volume. This allowed the database to recover and c...

Between 1:00 AM PDT and 2:36 AM PDT on November 1, 2025, some users experienced trouble uploading files, using Slack AI, performing searches, using Slack Connect, or sending and receiving messages.We traced this back to an unexpected spike in error rates for a backend database responsible for handling several Slack functions. This spike was caused by timeouts stemming from an ongoing backend job, resulting in higher-than-expected traffic.We took similar mitigation steps as the related incident w...

Between 8:17 AM PST and 9:22 AM PST on November 3, 2025, some users experienced significant latency in search results across Slack. In some cases, search results were outdated or incomplete.We traced this back to a backend service responsible for processing search requests that experienced a high surge in memory usage. This caused the service to become temporarily unresponsive and stop processing search requests.We restarted the affected services and increased capacity, resolving the issue for a...

From around 3:15 AM PST to 5:13 AM PST on November 5, 2025, some users were unable to use data fields from newly added Salesforce sources in workflows.We traced this to a backend logic error that was attempting to fetch data using too many parameters. We adjusted the logic to use the correct parameters, which resolved the issue for all users.

Between 4:52 PM PST and 7:12 PM PST on November 5, 2025, some users experienced issues with several Slack features, including client loading.We traced this back to an unexpected traffic spike that temporarily overloaded several core Slack services. We implemented mitigation measures to re-stabilize the impacted databases, and full connectivity was restored for all affected users.

Between 4:32 PM PST and 6:24 PM PST on November 6, 2025, some users experienced a variety of issues with Slack services, including loading their application, using huddles, performing searches, and various general connectivity problems.The issue stemmed from a high demand on backend resources, originating from an unexpected spike in traffic to Slack services. We promptly implemented traffic-management mitigation measures to re-stabilize the affected services, reducing the duration of the impact ...

Beginning around 11:00 AM PST and lasting until 2:24 PM PST on November 8, 2025, some enterprise users experienced a blank page when attempting to sign into Slack. Non-enterprise users would have successfully been able to sign into Slack.We traced this issue to a configuration error tied to the workspace directory page (the page users are typically directed to after logging in), which caused incorrect redirects. During the incident, affected users may have successfully accessed Slack by navigati...

Between 10:10 AM PST and 10:25 AM PST on November 10, 2025, some users may have temporarily been unable to connect to Slack or experienced a degree of latency when attempting to use features such as huddles, workflows, or message delivery.We traced this back to a spike in traffic to core backend Slack functions. This traffic temporarily overwhelmed a subset of backend components, leading to brief increase in connection failures. The traffic spike subsided and connectivity was restored for all us...

Between 1:00 AM and 8:00 AM PST on November 12, 2025, some users experienced delays when attempting to use AI features, including message summaries and search.An upstream provider experienced latency with their services, resulting in backend errors for some Slack AI functions. To mitigate the issue, we temporarily routed traffic to a separate version. After the upstream provider resolved their issue, affected Slack AI functionality was successfully restored.

Following a period of monitoring and with user validation now received, this issue has been resolved. We apologize for any inconvenience this issue may have caused.

Starting around 1:45 AM PST until 4:30 AM PST on November 28, 2025, some users encountered connectivity issues, including difficulty accessing and loading their workspaces and receiving "Server error" messages.We traced this issue to a backend database service reaching unexpected capacity limits, which led to a spike in error rates and request timeouts. We immediately increased capacity limits for the affected databases, restoring full functionality and service stability to all impacted services...

Between 11:51 AM PST and 9:10 PM PST on December 2, 2025, some users experienced issues with the Slack search functionality. Affected users may have encountered a range of symptoms, including the display of incorrect search results, missing messages, noticeably degraded or slow performance, and in some cases, a complete failure to load any search content.We traced this back to a temporary, unexpected surge in resource demand that impacted a critical backend service responsible for processing sea...

Between 2:08 PM PST and 2:34 PM PST on December 4, 2025, some users may have experienced 500 errors when trying to open a Canvas. Current status and recent actions taken: We have resolved the issue by reverting a web cache configuration setting that was causing the disruption. Users should no longer be experiencing trouble connecting to or loading Canvases in Slack.Scope: This issue did not affect any specific region, but a percentage of users may have been impacted globally.Previous impact to e...

Beginning around 7:45 PM PST until around 8:11 PM PST on December 4, 2025, some users experienced slow or incomplete searches in Slack.A backend configuration change caused an unexpected spike in queries to a search-related database service. We reversed the backend configuration, which resolved the impact to the search feature. While we managed any temporarily unindexed content, users were able to perform searches in Slack as expected, but some content may have been temporarily missing.We closel...