Thursday December 4, 2025
Incident
Slow or incomplete Slack searches
Summary
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 closely monitored internal health metrics for a period of time to ensure the issue was fully resolved by December 5, 2025 at around 1:10 PM PST.
9:59 AM PST
This issue is resolved as of 10:11 PST for all users.
- Current status and recent actions taken: Message indexing jobs have completed, affected users should now begin to see messages sent during the incident impact time to appear in search results.
- Scope: Users globally may have experienced search-related issues
- Previous impact to end users: Searching in Slack would result in timeouts or missing messages.
- Required resolution steps: No required steps.
We apologize for any disruptions to your day.
1:10 PM PST
Search functionality has been restored, but our full mitigaion work is still ongoing.
- Current status and actions being taken: We're currently re-processing a backlog of unindexed messages via backend jobs. This work is still ongoing and expected to take some time. Messages sent between approximately 7:45 PM PST on December 4, 2025 and 12:17 AM PST on December 5, 2025 may be temporarily missing from search results. We're working to process this backlog.
We'll be back with another update once we have news to share.
9:34 AM PST
- Current status and actions being taken: The search functionality resurfaced and is now operating as expected for older messages, and any new messages during the incident may not appear in search results. Our teams are actively reprocessing these messages, which may take several hours to ensure they are fully indexed and searchable.
We will provide the next update as soon as we have significant progress to share.
3:31 AM PST
Our work on this issue is still ongoing.
- Current status and actions being taken: Search functionality has been restored and we are now working on indexing any recent messages that may not yet be searchable.
We will share an update once this process is complete.
11:10 PM PST
Our work on this issue is still ongoing. At this time, we have no new information to provide.
Thank you for your patience while our team works diligently to restore full functionality. We will share another update as soon as we have news.
10:20 PM PST
Our work on this issue is still ongoing, but no new information to share just yet.
We appreciate your patience and will be back with another update as soon as we have news to share.
9:33 PM PST
Our work on this issue is still ongoing.
- Current status and actions being taken: Slack searches may be slow or incomplete for some users. Recently posted messages may not be searchable. We are working to address this as quickly as we can.
- Estimated time to resolution: No estimate to provide at this time.
- Scope: Slow search responses.
- Current impact to end users: Users may experience latency when using the search function, while recent messages may not be available in search results.
- Known workarounds: No workaround at this time.
We'll provide another update in 30 minutes until impact is resolved for all users.
9:04 PM PST
Our work on this issue is still ongoing.
- Current status and actions being taken: We have confirmed this issue is affect search functionality only, we are trying to identify the cause.
We'll provide another update in 30 minutes until impact is resolved for all users.
8:32 PM PST
Users may be experiencing delays with certain actions in Slack, and Slack may be responding slowly. We're actively looking in to this, and we'll share another update as soon as we have more information. We appreciate your patience in the meantime.
8:24 PM PST
Features affected
Search
Status
Incident