Slack System Status

Incident: Activity badge display issue

2025-09-11T23:06:21-07:00

11:06pm PDT We are investigating an issue where the Activity badge may continue to show an unread count even after all messages have been read. We are actively engaged in resolving this and minimizing any impact. We will share an update as soon as we have more information. We sincerely apologize for any inconvenience this may be causing.

9:20am PDT We’ve identified the cause and are working on a forward fix. In the meantime, users may now try hard-refreshing their Slack app (Cmd/Ctrl + Shift + R) as a workaround to the stuck Activity badge. We’ll be back with another update once we have news to share. Thanks for your patience.

10:53am PDT The issue users experienced with stuck Activity badges has been resolved. If users are experiencing any trouble, they may consider hard-refreshing their app using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux) in order for this fix to be reflected on your end.Again, we’re sorry for any inconvenience this issue may have caused you.

10:59am PDT From 1:50 PM PDT on September 9, 2025, until 7:46 AM PDT on September 12, 2025, some users had an issue where the Activity tab in Slack would show an unread count badge even when there was no new activity.This was caused by a recent backend change that unintentionally prevented unread badges from clearing. We've rolled back the problematic code and pushed out a fix. All affected users should no longer run into this issue. Should any users still be experiencing this, please hard refresh your client (Cmd/Ctrl + Shift + R).

Incident: Unread badge stuck in Activity view

2025-09-15T23:13:15-07:00

11:13pm PDT We are investigating an issue where the Activity badge may continue to show an unread count even after all messages have been read. We are actively engaged in resolving this and minimizing any impact. We will share an update as soon as we have more information. We sincerely apologize for any inconvenience this may be causing.

6:03am PDT We're still investigating this issue and will share an update as soon as we have news. For now, affected users can try a temporary workaround by hard reloading their Slack app (Cmd/Ctrl + Shift + R), as this appears to be related to a previous bug with similar symptoms.

12:27pm PDT We’ve rolled out a fix and Activity badges are now working as expected. If you’re still encountering any trouble, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). Thank you for your patience while we sorted out this issue.

7:36am PDT From September 15, 2025, at around 11:00 PM PDT, through September 18, 2025, at around 9:30 PM PDT, some users may have experienced an issue with unread items in their Activity view. Specifically, the badge indicating unread items would not disappear even after the activity was read.We traced the issue back to a recent change in how the Slack client handles the item row within the Activity view, which introduced this bug. We also determined this was related to a similar badging issue that occurred on September 11, 2025. We rolled back the problematic change, resolving the issue for all affected users.

Incident: Trouble Loading Slack.com

2025-09-17T12:41:17-07:00

12:41pm PDT We're investigating a new incident.Current impact to end users: Some users may experience a Server Error when attempting to load Slack.com.We'll provide an update within 30 minutes including further details on current actions being taken.

12:54pm PDT Current status and actions being taken: We have identified a change that is causing the issue and are preparing a new build, which will be deployed immediately once it's complete. Estimated time to resolution: We estimate the new build to be ready in 30 to 60 minutes. Scope: This issue is only impacting users who are logged in to Slack.com.Current impact to end users: Users who are already logged in to Slack.com are experiencing a Server Error when attempting to load the page. Known workarounds: Affected users can work around this issue by launching an incognito window and logging in.We appreciate your patience as we sort this out.

1:22pm PDT We’re still working on deploying the new build, and don’t have any new information to share at this time. Thanks for sticking with us as we continue to work towards a fix.

1:27pm PDT We’ve released a fix, and Slack.com is back up and running once again. We appreciate your patience while we sorted this out.

7:50am PDT Starting at around 10:42 AM PDT, until around 1:25 PM PDT on September 17, 2025, some users that were logged into their Slack app were unable to access https://slack.com/, instead they were receiving an error message. We identified a recent code change to the logged-in user experience on this page. The change caused the page to fetch an incorrect value for the user, which introduced the error. We reverted the change, resolving the issue for all affected users.

Incident: Issues Opening the Slack App version 25.09.40 on Android

2025-09-20T06:14:38-07:00

6:14am PDT We are currently investigating an issue where some users are experiencing problems opening the application for version 25.09.40 of the Slack app for Android. Once more information becomes available, we’ll provide an update in 30 minutes or sooner, and we’re sorry for any inconvenience this may be causing you.

6:57am PDT Our work on this issue is still ongoing.We are investigating the issue to determine whether it is related to a specific version of the Slack app. We'll be back with another update once we have news to share.

7:04am PDT Our investigations have revealed that users experiencing issues opening the application on Android are using an older version of the Slack app (version 25.09.40.0-90014875) from the Play Store. Users will need to update to the latest version 25.09.40.0-90014876 of the Slack app.We’re sorry for any inconvenience this issue may have caused you.

2:50pm PDT Starting around 7:30 PM PDT until approximately 10:18 PM PDT on September 19, 2025, some users on Android were experiencing app crashes when attempting to launch Slack.At approximately 5:40 PM PDT on September 20, 2025, we received several reports of Android users experiencing this issue and began our incident response process.We traced the issue back to a specific app version, 25.09.40, where users would encounter a crash upon startup. This version contained a bug related to improperly loading elements within the Android app, which caused the crashes. We immediately reverted the change and released a fix, which resolved the issue for all users in the latest app version.However, due to standard app update processes, the fix did not immediately reach some users who were already on the impacted version of Slack for Android, requiring those users to update to the latest version to resolve the issue.

Incident: Clicking Edit in profile causes a grey screen and the menu fails to load.

2025-09-23T06:00:46-07:00

6:00am PDT We are investigating an issue where the menu fails to load when users try to edit their profile. The behaviour occurs for name pronunciation and pronouns under the profile section. All sections from Contact information onwards load the menu as expected. This is impacting the desktop and web users ( Windows and Mac). The Mobile app is not impacted.We are working to resolve the issue and will share an update as soon as we have more information. We apologize for any inconvenience this may be causing.

6:32am PDT We have identified the cause of the issue and are deploying a fix that should resolve the impact for affected users.

6:51am PDT The issue is resolved following the successful deployment of a fix to all affected users. We apologise for any inconvenience this issue may have caused.

1:16pm PDT Starting around 5:00 PM PDT on September 22, 2025 until around 5:52 AM PDT on September 23, 2025, some users on desktop and browser version of Slack were unable to update their user profiles, including their profile photo, name pronunciation, and other link buttons. The options would present as grayed out.A bug related to the profile sidebar originating from an improper backend condition check within the app caused the options to render as disabled. We corrected the logic, resolving the issue for all users.

Incident: Slowness with AI search summaries and general search functionality

2025-09-23T14:32:42-07:00

2:32pm PDT We're currently investigating an issue where some users may observe slowness with AI search summaries and general slowness with search functionality. We will provide an update once more information becomes available. Thanks for sticking with us as we work to resolve this issue.

3:26pm PDT Upon further investigation, we determined users may observe errors in addition to slowness. We identified and are reverting a recent change that caused the issue. While we monitor the progress of the change revert, we are actively increasing the capacity of our search infrastructure. Users may observe improved search latency as we continue our work.Thank you for your patience as we work to resolve this issue. We'll provide and update as soon as we have additional information to share.

4:27pm PDT We’ve successfully reverted the earlier change that was causing this issue. We’ve also completed monitoring capacity usage and latency on our infrastructure, and see that performance has returned to its expected levels. This incident is now resolved. We apologise for any disruption caused to customers and appreciate your patience with this issue.

1:25pm PDT Starting around 12:15 PM PDT until around 4:10 PM PDT on September 23, 2025, some users experienced errors and latency when attempting to query items using the AI search feature in Slack.A backend search system encountered an unexpected spike in processing times, resulting in downstream latency and timeouts when users would attempt to use Slack AI search. We identified the cause of the unexpected processing spike and introduced additional load handling measures to resolve the issue for all users.

Incident: Trouble with custom apps

2025-09-26T17:01:19-07:00

5:01pm PDT We’re investigating reports of some custom built-internal apps not functioning, and returning errors. We’ll be back with an update once we know more.

5:45pm PDT The issue is resolved following the successful deployment of a fix to all affected users. We apologise for any inconvenience this issue may have caused.

9:19am PDT Starting around 2:00 PM PDT until around 5:15 PM PDT on September 26, 2025, some users experienced issues with custom internal-built integrations in Slack. Affected apps would return a "rate_limited" error for conversation related APIs such as "conversations.replies" or "conversations.history".We traced this back to a recent change related to AI-search custom app functionality that inadvertently introduced a rate limiting bug for all custom built apps. This bug was connected to a mis-matched condition logic regarding app types. We reversed this change, resolving the issue for all affected users.

Incident: Search Failures

2025-10-15T09:23:13-07:00

9:23am PDT We’re investigating an issue impacting search. Some searches may not complete or may return partial results. Org and workspace dashboards may also not load correctly at this time. We’re on the case and will provide another update once we have more details to share. Thank you for your patience in the meantime.

9:49am PDT This issue is now resolved for all users.Current status and recent actions taken: We restarted the problematic pods, which restored full functionality to the search function for all impacted users. Scope: About 20% percent of search queries were failing, but may have succeeded on retry. We apologize for any disruptions to your day.

2:58pm PDT Starting around 8:30 AM PDT until around 9:18 AM PDT on October 15, 2025, some users may have experienced issues querying searches in Slack. Searching for messages, files, people, channels, and internal or external users were returning unexpected errors or failing. Some admin dashboards that relied on search functionality may have also experienced issues loading.A backend system responsible for processing search queries experienced a large influx of traffic, causing the spike in errors. We identified the problematic jobs and implemented steps to restart them, resolving the issue for all affected users.

Incident: Potential Errors Loading Messages/Threads

2025-10-15T10:29:32-07:00

10:29am PDT Users may experience errors when loading messages or threads. We’re on the case and will provide another update in 30 minutes or sooner if we have more details to share. Thank you for your patience in the meantime.

10:57am PDT This issue is now resolved for all users.Current status and recent actions taken: We identified a scheduled job that was causing the issue. We paused this job, and our health metrics are now showing consistent improvement. Users should no longer experience errors when loading messages or threads.Scope: This was not affecting any specific region, but a percentage of users may have been affected globally.Previous impact to end users: Some users may have experienced errors when loading messages or threads.Required resolution steps: No actions needed.We apologize for any disruptions to your day.

3:06pm PDT Between approximately 9:30 AM and 10:14 AM PDT on October 15, 2025, some users experienced slowness or errors when loading messages and threads in Slack.The issue was caused by an unexpected spike in traffic on a specific database, triggered by an ongoing backend job. We We implemented measures to process any related backlog and immediately paused the problematic job, which resolved the issue.

Outage: Trouble loading Slack, using canvas, huddles, and other features.

2025-10-20T01:15:40-07:00

1:15am PDT Users may be experiencing intermittent difficulties with Slack, such as loading threads and canvases, sending messages, and using huddles.We're investigating this and we will be back with an update as soon as possible.

1:47am PDT Users are experiencing intermittent issues with Slack, including but not limited to sending messages, loading channels, using canvases and huddles.We're continuing to investigate and we'll be back with an update as soon as we have more information.

2:20am PDT Our investigation is ongoing. We have determined that several core Slack services are currently affected by an issue originating with an upstream provider.Current status and actions being taken: We are continuing to investigate the full impact and are implementing necessary steps to mitigate the impact. Several features remain affected. We're continuing to partner with our upstream provider to resolve the issue.Estimated time to resolution: No ETA is available at this time.Scope: Users globally may be experiencing issues with several Slack features.Current impact to end users: Many features, including canvas, huddles, and the loading of content such as messages, channels, or threads, may not be working as expected. Some emails such as those related to two-factor authentication, may also have trouble delivering to users.Known workarounds: No known workaround at this time.We appreciate your patience as we sort this out and will provide the next update in 30-minutes.

2:55am PDT Our work on this issue is still ongoing, but we're seeing signs of recovery.Current status and actions being taken: We're continuing to partner with our upstream provider to resolve the issue, but have implemented some steps to help mitigate impact. We are observing signs of recovery, but some impacted features may still encounter failures.Current impact to end users: Many features, including canvas, receiving emails related to logging in, SSO, huddles, and the loading of content such as messages, channels, or threads may be returning to normal, but we're still monitoring our health metrics.We'll be back with another in 30-minutes.

3:28am PDT We're still working to fully resolve this issue, but continue to observe signs of recovery.Current status and actions being taken: We're continuing to monitor for updates from our upstream provider, but continue to see improvements in features such as huddles, login, SSO, and loading content such as messages/channels. However, we're still investigating some errors related to canvas.Current impact to end users: Users may see improvement with features such as huddles, logins (including SSO), and loading messages, channels, and threads. Some actions related to canvas may be successful, but this feature is still impacted as we are observing elevated error rates.We'll be back with another update once we have news to share.

4:25am PDT This issue is now resolved for all users.Current status and recent actions taken: Our upstream partners have resolved the issue that impacted several Slack features. Scope: Users globally may have experienced errors across impacted features.Previous impact to end users: Trouble connecting to or loading Slack, huddles, canvas, login/SSO, and receiving emails, such as those related to two-factor authentication. Users may have experienced issues loading messages, channels, or threads.Required resolution steps: Affected users should re-attempt any action that returned an error. It's also encouraged to hard-reload their Slack app using Cmd/Ctrl + Shift + R.We apologize for any disruptions to your day.

9:20am PDT We're reopening this issue as some users are beginning to report general trouble with Slack. We've determined these reports are still related to the ongoing issue with an upstream provider.Current status and actions being taken: We're continuing to investigate additional reports of issues with Events API, workflows, and some connectivity issues.Estimated time to resolution: None at this time.Scope: Users globally may encounter some trouble in Slack.Current impact to end users: Some users may encounter trouble loading or connecting to Slack, scheduled workflows triggering multiple times, or latency with Events API.Known workarounds: No known workarounds at this time.We appreciate your patience as we sort this out and will be back with another update once we have news to share.

10:08am PDT We continue to monitor the issue as our upstream provider continues their work toward a resolution.Current status and actions being taken: Some users are experiencing duplicate workflow triggers and some general latency with Slack features. We're continuing to monitor health metrics and partner with our upstream provider as they work to resolve this.We'll continue to provide updates as we have news to share. We appreciate your patience.

3:58pm PDT This issue is now resolved for all users.Current status and recent actions taken: Our upstream provider have confirmed the issue has been resolved and our health metrics have shown consistent improvement. Users should no longer experience trouble with Slack features.Scope: Users globally may have encountered trouble with Slack.Previous impact to end users: Users may have experienced duplicated workflows triggering and some general latency with Slack features.Required resolution steps: No required steps, but it's recommended to hard reload your Slack app if you're experiencing any trouble by pressing Cmd/Ctrl + Shift + RWe apologize for any disruptions to your day.

2:44pm PDT 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 result of an ongoing incident with an upstream cloud infrastructure vendor. The upstream provider immediately began working to mitigate the issue. We also took additional steps to reduce the impact on affected features, such as routing traffic to different database service regions.At around 3:35 AM PDT on October 20, 2025, our upstream partners informed us that the affected services were showing signs of improvement, and our health metrics supported this assessment. Based on this, we communicated at approximately 4:25 AM that the issue may have been resolved for users. However, we later observed a continued spike in errors, which prompted us to re-engage our status site communication processes.We continued monitoring our health metrics while the upstream provider worked to fully resolve the issue. Once resolution was confirmed, we restored normal traffic paths, resolving the issue for all users.

Incident: Trouble with huddles

2025-10-20T07:56:24-07:00

7:56am PDT We're currently investigating an issue where some users remain stuck in a huddle after attempting to leave. This is related to an ongoing issue with an upstream provider. We'll share an update as soon as we have more news.

8:25am PDT We're continuing to monitor this issue and have identified the cause is related to an upstream provider issue that is actively being worked on. We've also determined that some actions, such as huddle transcripts, are currently affected. We'll be back with another update once we have news to share.

10:11am PDT We're continuing to monitor this issue as our upstream provider continues their work. We'll provide another update once we have more news to share. This issue is related to a separate incident, and you can find updates on it here: https://slack-status.com/2025-10/51d84290cf5c8e22.

4:34pm PDT We have determined that new huddles are ending properly. We are actively working to remediate any existing huddles that are in a bad or stuck state. We will provide another update as soon as we have news to share. We appreciate your patience while we continue to sort this out.

7:34am PDT Our remediation efforts are still ongoing as we continue to work toward cleaning up any huddles that are in a bad state. We'll be back with another update once this work is complete. Thank you for your continued patience.

3:25pm PDT 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.

Incident: Search Failures

2025-10-21T22:02:36-07:00

10:02pm PDT We’re investigating an issue impacting Search. Some users may experience issues while searching for recent messages or files. We have identified the issue and are actively working on a fix. We’ll share another update in 30 minutes or sooner if more information becomes available. Thank you for your patience.

10:48pm PDT We're continuing to investigate an issue that’s affecting Slack’s Search functionality. Users may experience issues when searching for recent messages or files, or see incorrect results when using keywords or searching within channels. We’ll share another update in 30 minutes or sooner if more information becomes available. Thank you for your patience.

11:35pm PDT We’ve identified an issue affecting Search across messages and files. Some users may be unable to find recent content, see incomplete or unexpected results when using keywords, or experience errors while searching within channels. Our engineering team has determined that part of the system responsible for handling search requests is currently unhealthy, which is preventing new content from appearing in search results. We’re actively restarting affected services to restore normal performance. We’ll share another update in 30 minutes or sooner as progress continues. Thank you for your patience while we work to resolve this issue.

12:30am PDT The services are being restarted in batches, and all new jobs have been paused until the search infrastructure stabilizes. We are also monitoring the metrics to restore the indexing functionality. We’ll share an update in 30 minutes or sooner as progress continues.

12:48am PDT Service restarts have been completed. The cluster hosting the Search services looks healthy, and the engineering team is monitoring. We are in the process of recovery, and a full recovery is expected soon. No additional information to share just yet, but we'll keep you posted as soon we have an update.

1:18am PDT Our Search success has recovered, and Search is back to normal. Paused jobs were resumed. No additional actions are required on your end. Thank you for your patience while we sorted out this issue.

3:51pm PDT 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, which fully restored search functionality for all affected users.A subset of users affected by the backlog may have encountered ongoing partial search results, we outlined the related incident here: https://slack-status.com/2025-10/65f3383a2d6aebdf.

Incident: Search Failures

2025-10-22T04:11:51-07:00

4:11am PDT We've noticed that the Slack Search functionality issue has resurfaced, and we're investigating. A subset of users is seeing Search indexing failures for messages, files, reactions, stars, and pins. This issue affects both private and public channels. We appreciate your patience while we work to resolve this issue.

5:28am PDT We're continuing to investigate an issue that has resurfaced which affects the Search functionality.Some users may be unable to find recent content, see incomplete or unexpected results when using keywords, or experience errors while searching within channels. We’ve identified residual impact from a previous incident and are working to restore functionality.We’ll share another update in 30 minutes or sooner as progress continues. Thank you for your patience while we work to resolve this issue.

7:24am PDT We're continuing the investigation into the issue that’s affecting Slack’s Search functionality. Users may still experience issues when searching for recent messages or files, or may see incorrect results when using keywords or searching within channels. We’ll share another update as more information becomes available. Thank you for your patience.

1:27pm PDT We've identified the cause and have implemented a fix that restored some search functionality. We're still working to resolve an underlying issue connected to older content (like older messages) not appearing in search results. We'll provide an update once that fix is applied. Thanks again for your patience in the meantime.

7:15am PDT We identified the cause of the issue and implemented a fix that restored the search functionality for both public and private channels.We are sorry for any inconvenience caused during this incident.

3:40pm PDT 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.

Incident: Intermittent trouble with file previews and sending messages for EKM users

2025-10-22T08:02:50-07:00

8:02am PDT We're investigating a new incident.Current impact to end users: Users may see inconsistent errors when attempting to send messages in Slack, and some file previews/thumbnails may have trouble loading.We'll provide an update within 30 minutes including further details on current actions being taken.

8:25am PDT We're continuing to investigate this issue, but have identified the root cause as being related to Enterprise Key Management (EKM) servicing issues. We are also observing some signs of improvement with message sending, but we continue to work toward a full resolution.Current status and actions being taken: We've identified the root cause and are focused on resolving the EKM servicing issues.Estimated time to resolution: None at this time.Scope: Enterprise orgs with EKM services enabled.Current impact to end users: Some users may experience trouble loading file previews/thumbnails and sending or receiving messages, including threads.Known workarounds: None at this time.We'll be back with another update in 30 minutes or sooner.

9:00am PDT Our work on this issue is still ongoing, but no major updates to provide at this time.Current status and actions being taken: We're currently working toward a path to fully resolve the issue, but continue to observe signs of improvement.We'll provide another update in 30 minutes until impact is resolved for all users.

9:25am PDT This issue is now resolved for all users.Current status and recent actions taken: We've addressed the problematic backend services and success rates have returned to normal. Our health metrics confirm affected featuers are operational.Scope: A small number of enterprise users with EKM enabled.Previous impact to end users: Some users may have seen trouble sending or receiving messages, including threads, as well as uploading files (or viewing previews/thumbnails).Required resolution steps: No required steps.We apologize for any disruptions to your day.

9:29am PDT 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 functionality to the EKM backend services.While our initial communication indicated issues related to sending messages and file uploads, our follow up reviews have identified additional features that were also affected, including:Slack ConnectSearchSlack AIWorkflows

Incident: Trouble with search

2025-10-29T10:32:11-07:00

10:32am PDT We’re investigating an issue where some users are having trouble searching in Slack. We’ll be back with another update once we know more.

10:42am PDT We're continuing to investigate an incident and have increased our response urgency.Current impact to end users: Some users may experience issues related to search, including some admin dashboards such as “Manage members”.We'll be back with another update in 30 minutes. Thanks for your patience.

11:13am PDT Our investigation is still ongoing Current status and actions being taken: We’re continuing our investigation into the search related errors to identify potential causes.Estimated time to resolution: No time to available.Scope: A number of search queries may be failing for users globally. Current impact to end users: Issues with search functionality in Slack, including AI Search and some admin dashboards such as “Manage members”.Known workarounds: No known workarounds at this time.We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

11:40am PDT Our work on this issue is ongoing, but we are showing signs of recovery with the affected search features.Current Status and Actions: We identified a spike in backend search requests. To help mitigate the impact, we've adjusted request traffic, leading to signs of recovery. We're continuing to monitor as our work progresses.We'll provide another update once impact is resolved for all users.

2:00pm PDT Our work on this issue is still ongoing, but we have no new information to share just yet.Current status and actions being taken: We continue to observe signs of recovery, and some search functionality may be back to normal. However, some users may still experience intermittent issues, such as missing search results. We're still working hard to resolve the issue entirely.We'll be back with another update once we have news to share.

6:28pm PDT We’ve been able to restore search functionality to affected users, but are continuing to work through a backlog of incomplete search jobs.Current status and actions being taken: During this issue, a related backend job related to search indexing queued a number of unprocessed jobs. We’re actively working to process these requests so search results appear correctly.Scope: A number of search queries were failing for users globally.Current impact to end users: Search functionality has been restored, but some results may not appear or appear incorrectly as we work to clear the backlog.Known workarounds: No known workarounds at this time.We’ll be back with another update once the search jobs are complete.

11:09am PDT We are continuing to work on remediating the search backlog. Users should see ongoing improvement in search functionality as this work progresses.Current status and actions being taken: We are continuing to process and clear the backlog of search jobs that were incomplete as they were queued during the incident's impact period. Once cleared, older messages and content from that specific time will appear normally. New content (and content prior to this incident) is already appearing as normal in search queries.We'll provide another update once the issue is fully resolved for all users.

9:51am PDT This issue is now resolved for all users.Current status and recent actions taken: The search job backlog has caught up to a healthy state. Users should now see expected results when searching for content in Slack.Scope: A subset of global users experienced issues with the search functionality.Previous impact to end users: Search results were inconsistent, missing, or out of order. Certain admin dashboards, such as "Manage members," were also affected.Required resolution steps: No steps required.We apologize for any disruptions to your day.

5:16pm PDT 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 the search processes and added more capacity to handle the heavy load and clear the backlog.By around 4:52 PM PDT, search functionality began displaying some results as expected. However, users still couldn't find items that were posted during the incident until we finished processing the entire backlog. This final processing step took longer, and the search service was fully caught up and returning all results by around 4:19 PM PDT on October 31, 2025.

Incident: File upload errors

2025-11-01T03:13:11-07:00

3:13am PDT At around 1:00 AM PDT on November 1, 2025, we observed an error related to file upload. Users experienced issues while uploading files. This problem was caused by an ongoing incident triggered by a migration job running on the database. The issue self-resolved, consequently fixing the file upload problem. The issue was resolved at 2:45 AM PDT.We've adjusted this entry to properly reflect impact & resolution timestamps. We apologize for any confusion.

9:13am PST 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 correctly serve requests, resolving the issue for all affected users.

Incident: Issue with Files endpoint, SlackAI, Search, Messaging, and SlackConnect functionality

2025-11-01T03:47:44-07:00

3:47am PDT At approximately 1:00 AM PDT on November 1, 2025, some users may have experienced issues with the Files endpoint, SlackAI, Search, Messaging, and Slack Connect functionality. The issue was caused by a database job that resulted in high CPU utilization on the database. Stopping this job reduced CPU usage to within threshold limits, which resolved the issue. The issue was resolved at 2:36 AM PDT. We've adjusted this entry to properly reflect impact & resolution timestamps. We apologize for any confusion.

10:12am PST 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 we reported on (https://slack-status.com/2025-11/d447af6bb8944796): We temporarily paused the problematic jobs to reduce traffic to the affected database and implemented logic adjustments to handle this high traffic more efficiently. Once the database recovered, all affected functionality was restored to users.

Incident: Search Failures

2025-11-03T09:31:24-08:00

9:31am PST We’re investigating an issue impacting Search. Some users may experience significant delays, or the search bar may become unresponsive/stuck loading when searching for recent messages or files. We have identified the issue and are actively working on a fix. We’ll share another update in 60 minutes or sooner if more information becomes available. Thank you for your patience.

10:02am PST As of 09:22 AM PST, our Search functionality has recovered, and Search is back to normal. To mitigate this issue, we restarted the impacted services and shards. The cluster hosting the Search services is now healthy. No additional actions are required on your end. Thank you for your patience while we sorted out this issue.

10:26am PST 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 all affected users.

Incident: Workflow Builder Data Sources

2025-11-05T05:03:04-08:00

5:03am PST At approximately 3:15 AM PST, we became aware of an issue with External Trigger Schedule Logic runs that are not working as expected. New Data Sources will be unavailable in the Workflow Builder until the first schema sync completes.We’ll share another update as more information becomes available. Thank you for your patience.

5:30am PST We identified the cause of the issue and deployed a code fix to resolve it. The schema sync jobs are now running correctly.The incident impacted new data source connections. Existing workflows and notifications were working normally.

9:01am PST 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.

Outage: Slack Connectivity issue

2025-11-05T17:26:22-08:00

5:26pm PST We are investigating an issue where customers are reporting being unable to connect to Slack services or are receiving errors if they are already connected. We are actively pursuing a number of activities to restore connectivity and services to customers. We will provide an update in 30 minutes or as soon as new information becomes available.

5:56pm PST We have restored service for all impacted customers. We’re continuing the investigation to more fully understand the cause. With services now restored, this will be the final update for this incident. We apologize for any inconvenience this incident may have caused you or your business.

10:20am PST 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.

Outage: Trouble connecting to or loading Slack

2025-11-06T16:53:49-08:00

4:53pm PST We're investigating a new incident.Current impact to end users: Some users may experience issues connecting to or loading Slack.We'll provide an update within 30 minutes including further details on current actions being taken.

5:30pm PST We’re seeing signs of recovery, and users may successfully connect and load Slack, but we’re actively investigating the root cause.Current status and actions being taken: Slack may be usable once again, but we're actively investigating root cause and monitoring our health metrics.Estimated time to resolution: No time to share.Scope: Users globally may have had trouble connecting to Slack.Current impact to end users: Users may be able to connect to Slack again, but we're still assessing root cause.Known workarounds: None. We’ll continue to provide updates every 30 minutes until the impact is resolved for all users.

6:14pm PST Current status and actions being taken: We have identified the cause and continue to work on the fix. Some users may experience success in loading or connecting to Slack, but we're investigating additional traffic that may contribute to connection trouble. Some users may experience slowness with Slack. We're continuing to monitor our health metrics as we work to ensure affected services remain operational.Estimated time to resolution: None.Scope: Users globally may have trouble connecting to Slack.Current impact to end users: Users may be unable to connect to Slack.Known workarounds: None.We appreciate your patience as we sort this out. The next update will be made when new information becomes available.

6:47pm PST We're observing ongoing signs of connectivity issues, including trouble searching and latency in performing actions in Slack, such as loading messages or channels. We're actively investigating and working to resolve the issue.Current status and actions being taken: We've identified the cause of the issue and are working to resolve it. Users may experience additional trouble when using Slack. Estimated time to resolution: No estimated time.Scope: Users globally may be experiencing issues with Slack.Current impact to end users: Users may experience issues loading or connecting to Slack, performing searches, and performing actions like sending messages or loading channels.Known workarounds: No known workarounds.We appreciate your patience as we sort this out. We’ll provide an update in 30 minutes or as new information becomes available.

7:09pm PST Our work on this issue is still ongoing, but no news to share.Current status and actions being taken: We're still working to implement full mitigation steps to resolve the issue for users.We'll provide another update in 30 minutes until impact is resolved for all users.

7:42pm PST We have implemented steps to mitigate the impact and continue to monitor our health metrics.Current status and actions being taken: We've implemented mitigation steps to reduce impact. Affected services may be functional for users, but we're continuing to monitor for any spikes in performance issues.Estimated time to resolution: No estimated time.Scope: Users globally may be experiencing issues with Slack.Current impact to end users: Users may experience issues loading or connecting to Slack, performing searches, and taking actions like sending messages or loading channels.Known workarounds: No known workarounds.We appreciate your patience as we sort this out. We’ll provide an update in 30 minutes or as new information becomes available.

8:16pm PST Our work on this issue is still ongoing.Current status and actions being taken: We're still monitoring our health metrics as we work to implement full mitigation steps. Additionally, we're still seeing signs of improvement, but we continue to work to fully resolve the issue.We'll provide another update in 30 minutes or as new information becomes available.

8:51pm PST Our work on this issue is still ongoing, but no news to share.Current status and actions being taken: We're still working to implement full mitigation steps to resolve the issue for users. We'll provide another update in 30 minutes or as new information becomes available.

9:15pm PST This issue is now resolved for all users.Current status and recent actions taken: The issue has been resolved as of 04:57 UTC, and all services and metrics are now operating at normal levels.Scope: Users globally were experiencing issues with Slack.Previous impact to end users: Users may have experienced issues loading or connecting to Slack, performing searches, and performing actions like sending messages or loading channels.Required resolution steps: NoneWe apologize for any disruptions to your day.

10:25am PST 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 and resolving the issue for all users by 6:24 PM PST.While the affected services returned to normal operation around 6:24 PM PST, we continued monitoring the issue out of an abundance of caution to ensure our health metrics indicated a period of sustained full recovery. We officially communicated that the issue was fully resolved at around 9:15 PM PST.

Incident: Some users unable to sign in

2025-11-08T14:26:02-08:00

2:26pm PST We're investigating an issue where some users are seeing a blank page when attempting to log in to Slack.If you encounter a blank page, please go to slack.com in your browser and select your workspace. The login page for all your workspaces should then appear.We apologize for the inconvenience and will continue sharing updates as they become available.

3:05pm PST Mitigation efforts are underway.Current status and actions being taken: We identified the cause of the issue and have initiated remediation efforts, which appear to be successful. We continue to monitor our progress.We apologize for the inconvenience and will continue sharing updates as they become available.

3:20pm PST This issue is now resolved. Users should no longer see a blank page. We apologize for the disruption this may have caused to your day.

3:05pm PST 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 navigating directly to https://app.slack.com as a temporary workaround.To quickly mitigate the impact, we rolled Slack back to a confirmed working version, resolving the issue for all users.

Outage: Trouble connecting to or loading Slack

2025-11-10T10:26:37-08:00

10:26am PST We're investigating a new incident.Current impact to end users: Some users may have trouble connecting to or loading Slack.We'll provide an update within 30 minutes including further details on current actions being taken.

11:05am PST We've identified the cause and are seeing signs of improvement. Users may be able to connect to Slack again, but we're still working toward a full resolution.Current status and actions being taken: We're continuing to monitor our health metrics as we work to mitigate full impact and help reduce the likelihood of this recurring.Estimated time to resolution: No current time to share.Scope: A small number of users may have temporarily been unable to connect to Slack; other users may have remained connected but experienced performance delays.Current impact to end users: Some users may be able to connect to Slack once again. Previously, affected users encountered issues connecting to or loading Slack, or experienced delays in completing actions (e.g., sending messages, performing searches, or using workflows).Known workarounds: No known steps to share.We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

11:39am PST Our work on this issue is still ongoing and our health metrics continue to indicate improvement.Current status and actions being taken: Affected users may be able to connect and use Slack as normal, but we continue to closely monitor as we work to fully resolve this.We'll provide another update in 30 minutes until impact is resolved for all users, we appreciate your patience as we sort this out.

12:00pm PST Our work on this issue is still ongoing, though we have no new updates to share just yet.Current status and actions being taken: We’re continuing to work toward a full resolution and continue to see successful connection to Slack services.We'll provide another update once this is resolved for all users.

12:32pm PST This issue is now resolved for all users.Current status and recent actions taken: Our health metrics indicate that users are no longer impacted. We’ve also implemented additional steps to help reduce the likelihood of this issue recurring.Scope: A small number of users may have experienced issues connecting to or loading Slack, while other users may have remained connected, but experienced issues completing some actions.Previous impact to end users: Trouble connecting to or loading Slack, sending or receiving messages, and issues with some features like search or workflows.Required resolution steps: No steps to share.We apologize for any disruptions to your day.

9:19am PST 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 users by around 10:25 AM PST. To mitigate the risk of reoccurrence, we adjusted backend traffic routing rules to relieve affected systems and continued closely monitoring our health metrics. We determined the issue was fully resolved and necessary measures were in place by 12:30 PM PST.We continue to implement additional measures to reduce the likelihood of this recurring in the future.

Incident: Slowness in AI Search Answers and AI Explain

2025-11-12T07:19:03-08:00

7:19am PST Customers using AI search are experiencing delays. AI generated summaries are slow in returning results. Other search functionality in Slack is working as expected. We are actively investigating the cause of the issue.We will update you as soon as we have more information.

8:05am PST We are continuing to investigate the issue affecting AI Search for users. We’ve engaged our infrastructure partner to help mitigate the issue. Other search functionality in Slack continues to work as expected.We will continue to provide updates as we make progress.

10:23am PST We resolved the issue users were experiencing with delayed Search AI. We apologize for the trouble.

10:57am PST 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.

Incident: Some users unable to sign in

2025-11-20T15:30:10-08:00

3:30pm PST Some users may experience trouble logging into Slack. We’re on the case and will provide another update once we have more details to share. We’re sorry for the disruption.

4:01pm PST We’ve identified a database authentication change that we believe caused this issue. We’ve reverted this change and via testing, believe users can now log in as expected to Slack services. We are currently validating this and will provide an update as soon as we have more to share.

4:09pm PST 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.

Incident: Slack login, workspaces loading failures, and general Slack functionality issues

2025-11-28T02:44:43-08:00

2:44am PST We are currently investigating an issue where a subset of users may be unable to log into Slack or use certain features. We apologise for the inconvenience and will provide another update as soon as we have more details to share.

3:16am PST We have identified an unhealthy database that is contributing to the current issue. We are working on restoring the database to a healthy state, which we anticipate will resolve the problem.We will update you as soon as we have more information.

3:46am PST We are actively working to resolve the current platform functionality issues, which have evolved to include connectivity problems, workspace loading failures, and server errors for some users. Our current efforts remain focused on restoring the unhealthy database identified earlier.We will update you as soon as we have more information.

4:18am PST We’ve also noticed instances getting out of memory errors, causing system instability. We are provisioning the service to larger and more stable servers. We continue to monitor everything for stability. We will update you as soon as we have more information.

4:54am PST Service has been fully restored for all affected users. The database connection issue, which was caused by high memory usage, was resolved by upscaling server capacity. All Slack features and functionalities are now loading correctly. We apologize for the disruption and thank you for your patience while we resolved this incident.

9:19am PST 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.

Incident: Trouble with Search

2025-12-02T12:08:32-08:00

12:08pm PST We're investigating a new incident.Current impact to end users: We are currently investigating reports of search functionality issues in Slack. Users may experience increased latency or errors when attempting to search.We'll provide an update within 30 minutes including further details on current actions being taken.

12:44pm PST Our investigation is still ongoing.Current status and actions being taken: We're currently investigating search related errors to determine a path to resolution. Some results may appear for some users, but we're still investigating.Estimated time to resolution: No estimate to provide at this time.Scope: Users that are not-IDR (International Data Residency) globally may experience trouble.Current impact to end users: Users may experience latency in Search, or results may not appear for some users.Known workarounds: No workarounds to offer.We appreciate your patience as we sort this out.

1:12pm PST We identified the cause but our work on this issue is still ongoing.Current status and actions being taken: We are seeing signs of improvement with overall search functionality. Some new messages may not appear in search results as message indexing is currently experiencing latency. We are actively working to restore message indexing and fully resolve the issue.We'll be back with another update once we have news to share.

1:46pm PST Our work on this issue is still ongoing, but no new information to share just yet.Current status and actions being taken: We're still working to fully resolve the search issues, including indexing. Users may still experience latency when querying new messages/content, but older content should appear in search results.We appreciate your patience and will be back with another update once we have news to share.

2:15pm 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.

2:47pm PST Our work on this issue is still ongoing.Current status and actions being taken: We have restored the system to a stable state. Re-running the search queries should now proceed without error. We are monitoring the results closely.We appreciate your patience and will be back with another update as soon as we have news to share.

3:17pm PST Our work on this issue is still ongoing.Current status and actions being taken: We have restored the system to a stable state. Re-running the search queries should now proceed without error. We continue to closely monitor the results.We appreciate your patience and will be back with another update as soon as we have news to share.

3:58pm PST Our work on this issue is still ongoing.Current status and actions being taken: Search queries and real-time indexing are now functioning as expected. We are currently backfilling messages that accumulated during the incident. While new content is searchable immediately, messages sent during the downtime will not appear in search results until the replay process is complete. We expect this to take some time and are monitoring progress closely.We appreciate your patience and will be back with another update as soon as we have news to share.

4:41pm PST Our work on this issue is still ongoing.Current status and actions being taken: We’re continuing to make progress on the backfill operation and are monitoring it closely. Search queries and real-time indexing are back to normal, and new content is immediately searchable.We'll provide another update in 30 minutes until impact is resolved for all users.

5:09pm PST Our work on this issue is still ongoing.Current status and actions being taken: The backfill operation is progressing well and is expected to finish in approximately 4 hours. We are monitoring the situation closely. We’ll provide the next update as soon as the backfill completes or if any significant developments arise.

9:59pm PST This issue is now resolved for all users. At around 9:10 PM PST, we fully resolved the search functionality issues impacting message indexing and the visibility of new content.Current status and actions taken: Search performance has fully recovered, and new messages are now indexing as expected. All content, both new and previously delayed, should now appear in search results without latency. System metrics have stabilised, and no further errors are being observed.Next steps: Our teams will conduct a thorough investigation to determine the technical trigger, identify the root cause, and implement preventive measures to prevent similar issues in the future. We apologise for any disruptions to your day.We edited this post to clarify next steps and adjust the resolution timestamp to PST timezone.

9:29am PST 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 search results. We increased resources for this service to mitigate impact and stabilize the search functionality, however, during this time, a backlog of unindexed content was created. This backlog prevented content from appearing in search results for some users.To resolve this, we began re-processing the accumulated backlog of unindexed content back into our search systems. Once the indexing process was complete, all messages and content shared during the initial impact window became fully searchable, resolving the issue for all users.

Incident: Slack Canvas Outage

2025-12-04T15:43:36-08:00

3:43pm PST 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 end users: Users experienced issues loading and accessing Canvases.Required resolution steps: NoneThis issue is now resolved for all users. We’re sorry for the disruption we brought to your day.

Incident: Slow or incomplete Slack searches

2025-12-04T20:24:45-08:00

8:24pm 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:32pm 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.

9:04pm 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:33pm 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.

10:20pm 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.

11:10pm 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.

3:31am 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.

9:34am 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.

1:10pm 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 issuesPrevious 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.

9:59am PST 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.

Incident: Issues loading or viewing threads

2025-12-08T15:23:58-08:00

3:23pm PST We are aware of an issue currently impacting threads. Our teams are investigating, and we will provide more information as soon as it’s available. We’re very sorry for any inconvenience this is causing.

10:55pm PST Our work on this issue is still ongoing.Current status and actions being taken: We have no additional news to share at this time, but we’re focused on getting things back to normal as quickly as possible.We'll be back with another update as soon as we have news to share.

8:55am PST We've identified the cause of the issue and implemented a fix. We're currently monitoring internal health metrics & user reports, but will provide an update once we've determined this issue is fully resolved. We appreciate your patience as we sort this out.

9:34am PST We've resolved the issue with threads not loading for some users. We apologize for any disruptions to you day.

8:44am PST From 7:12 AM to 4:50 PM PST on December 8, 2025, some users encountered a "Something's fishy!" error when loading threads or experienced delays or a blank screen when loading specific channels in Slack.We identified the cause as a recent configuration change that triggered unexpected rate limiting on backend components responsible for fetching message data for threads. We reverted the problematic change, resolving the issue for all users.

Incident: Trouble running workflows

2025-12-15T09:14:00-08:00

9:14am PST Users may experience issues when attempting to trigger a workflow using the Jira Cloud connector. We're investigating and will let you know as soon as we have more information.

10:25am PST Our work on this issue is still ongoing.Current status and actions being taken: Jira Cloud workflow connector is experiencing failures where Get Domain URL and List Atlassian Domains API calls are running into '500 errors'.Create issue functionality is also failing with '400 errors'.The investigation into the cause of these errors is ongoing.We'll be back with another update as soon as we have news to share.

1:51pm PST This issue is now resolved for all users.Current status and recent actions taken: This incident is considered all clear and required no action to be taken by Slack to alleviate the problem.Scope: We have determined that this issue was related to an incident experienced by the vendor, and it is now resolved.Previous impact to end users: Users experienced issues when attempting to trigger a workflow using the Jira Cloud connector.Required resolution steps: No additional steps are necessary.We apologize for any inconvenience this may have caused to your day.

8:57am PST Starting at around 7:00 AM until 12:10 PM PST on December 15, 2025, some users may have experienced issues triggering or using workflows containing the Jira connector or the Jira Cloud app in Slack.An upstream provider encountered an issue that resulted in trouble using the Jira connector. Once the upstream provider resolved the issue, the app returned to normal functionality.

Incident: Issue loading threads in Slack

2025-12-23T16:33:39-08:00

4:33pm PST We are aware of an issue currently impacting threads. Our teams are investigating, and we will provide more information as soon as it’s available. We regret any inconvenience this is causing.

6:04pm PST This issue is now resolved for all users.Current status and recent actions taken: Threads should now load normally for all impacted users. To restore normal thread performance, we redirected traffic away from the affected database shard and then scaled up its capacity.Scope: A small number of users may have had trouble with threads.Previous impact on end users: Threads may have failed to load or resulted in a "Something's fishy!" error message.Required resolution steps: No additional steps are necessary.We apologize for any inconvenience this may have caused to your day

9:49am PST Between 1:05 PM and 5:26 PM PST on December 23, 2025, some users may have encountered a "Something's fishy!" error when attempting to load message threads.We traced this to a backend job that consumed an excessive amount of system resources, leading to a portion of a database becoming unresponsive. To mitigate, we optimized the resource allocation for these background tasks and restarted the affected database segments, resolving the issue for affected users.

Incident: Trouble with Slack - General Slack functionality issues

2026-01-08T14:34:31-08:00

2:34pm PST We are currently investigating an issue where a subset of users may experience difficulties accessing Slack features. Some users may experience failed message sends, loading errors, or other intermittent failures across the platform. We apologise for the inconvenience and will provide another update as soon as we have more details to share.

3:13pm PST We are actively working to resolve the current platform functionality issuesCurrent status and actions being taken: Our engineering teams have identified a configuration change as the potential cause affecting our edge infrastructure. We have started remediating impact across some regions and are continuing these efforts across the remaining regions.Estimated time to resolution: No ETA at this time.Scope: This issue does not affect any specific region, but a percentage of users may be impacted globally.Current impact to end users: Some users may experience failed message sends, loading errors, or other intermittent failures.Known workarounds: No known workarounds at this time.We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

3:40pm PST This issue is now resolved for all users.Current status and recent actions taken: We have successfully remediated all affected regions by restarting the impacted services to restore functionality to the affected features. Users should no longer experience issues sending messages, loading Slack, or experiencing general functionality issues.Scope: This issue did not affect any specific region, but a percentage of users may have been impacted globally.Previous impact to end users: Some users may have experienced failed message sends, loading errors, or other intermittent failures.Required resolution steps: No steps required.We apologize for any disruptions to your day.

8:10am PST Starting around 11:50 AM PST until around 3:15 PM PST on January 8, 2026, some users experienced a variety of performance issues in Slack, such as significant delays or a total inability to send and receive messages, load channels, or view threads.We traced this to a routine backend configuration job which unexpectedly caused some services to reload or become unresponsive. To mitigate the impact, we promptly paused the problematic job and restarted the affected services, resolving the issue for all users.

Incident: Trouble with adding payment methods

2026-01-14T13:24:36-08:00

1:24pm PST We're investigating a new incident.Current impact to end users: We’re aware of an issue impacting some users’ ability to add payment methods. Our teams are investigating, and we’ll provide an update in 30 minutes or sooner if additional information becomes available.

2:03pm PST We are actively working to resolve this issue.Current status and actions being taken: We have identified a configuration change as the potential cause of this issue and have performed a rollback to mitigate customer impact. We'll continue to monitor internal metrics as we work through this.Estimated time to resolution: No ETA at this time.Scope: This issue does not affect any specific region, but a small percentage of users attempting to add a new payment method during checkout may be impacted globally.Current impact to end users: Some users may encounter a “Something’s gone wrong” error when attempting to add payment methods during checkout.Known workarounds: No known workarounds at this time.We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

2:37pm PST We are actively working to resolve this issue.Current status and actions being taken: In addition to the initial rollback, we are now deploying a fix to prevent any recurrence of this issue. While we work towards a full resolution and continue to monitor internal metrics, user impact remains mitigated.Estimated time to resolution: No ETA at this time.Scope: This issue does not affect any specific region, but a small percentage of users attempting to add a new payment method during checkout may be impacted globally.Current impact to end users: Some users may encounter a “Something’s gone wrong” error when attempting to add payment methods during checkout.Known workarounds: No known workarounds at this time.We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

3:04pm PST We are actively working to resolve this issue.Current status and actions being taken: We are continuing to deploy the fix and are monitoring the situation closely to ensure a complete resolution.Estimated time to resolution: No ETA at this time.Scope: This issue does not affect any specific region, but a small percentage of users attempting to add a new payment method during checkout may be impacted globally.Current impact to end users: Some users may encounter a “Something’s gone wrong” error when attempting to add payment methods during checkout.Known workarounds: No known workarounds at this time.We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

3:19pm PST This issue is now resolved for all users.Current status and recent actions taken: We have deployed a fix, which has successfully resolved the issue.Scope: This issue did not affect any specific region, but a small percentage of users attempting to add a new payment method during checkout may have been impacted globally.Previous impact to end users: Some users may have encountered a “Something’s gone wrong” error when attempting to add payment methods during checkout.Required resolution steps: No additional steps are necessary.We apologize for any disruptions to your day.

8:55am PST From 12:07 PM PST until 1:30 PM PST on January 14, 2026, some users were unable to add payment methods to their Slack billing pages.A recent backend change to our payment processing configuration unexpectedly added a new required field, causing errors when attempting to add the methods. We reversed the field requirement, resolving the issue for all users.

Incident: Trouble loading Slack, messages, or canvas

2026-01-15T11:41:34-08:00

11:41am PST This issue is now resolved.Current status and recent actions taken: Affected users may have experienced performance issues in Slack.Scope: This issue did not affect any specific region, but a small percentage of users may have been impacted globally.Previous impact to end users: The majority of errors were retired successfully, but small number of users may have experienced errors when performing various tasks in Slack. Required resolution steps: No steps required.We apologize for any disruptions to your day

Incident: Trouble loading Slack and performing actions

2026-01-22T11:43:53-08:00

11:43am PST Some users are having trouble performing certain actions related to App Management, such as; Create New App from https://api.slack.com/appsShow button to reveal the client secret Unable to install or delete internal appAttempting to edit event subscriptions, Enable Events view has an indefinite loading wheelThank you for your patience while we continue to investigate the situation.

12:28pm PST Our work on this issue is still ongoing.Current status and actions being taken: We have identified the cause and are working on a fix.We'll be back with another update once we have news to share.

2:18pm PST This issue is now resolved for all users.Current status and recent actions taken: We have completed deployment of a fix for this issue.Previous impact to end users: Some users were having trouble performing certain actions related to App ManagementRequired resolution steps: No additional steps are required from users.We apologize for any disruptions to your day.

Notice: Upstream provider issue causing email delivery delays

2026-01-22T14:00:30-08:00

2:00pm PST An upstream provider is experiencing issues that are causing delays in some email delivery. We’ll be back with an update once things are resolved on their end.

12:09am PST Email delivery has returned to normal and all services are operating as expected. Thank you for your patience while we worked through this issue. We apologize for how this issue may have affected you and your business.

Incident: Issue loading activity feed in Slack

2026-01-22T21:03:16-08:00

9:03pm PST We’re investigating a Feature Degradation affecting a number of users. Some users may be unable to load their activity feed and may encounter the following error message: “Something’s fishy! Slack can’t seem to load your activity feed. ”We’ll provide updates as soon as possible, as more information becomes available. We apologize for any inconvenience this may cause.

9:43pm PST Our work on this issue is still ongoing.Current status and actions being taken: We have identified the source of the ongoing issue related to activity feed and message functionality and are actively working on a fix.We'll provide another update as soon as it becomes available until the impact is resolved for all users.

10:47pm PST This issue is now resolved for all users.Current status and recent actions taken: The issue affecting the activity feed and message functionality has been resolved. We’ve taken steps to prevent this from happening again, and all systems are now operating normally.Previous impact to end users: During the impact, some users experienced issues with the activity feed and messaging, including degraded performance and errors.We apologize for any disruptions to your day.

9:16am PST Starting 8:27 PM PST until 10:01 PM PST on January 22, 2026, some users experienced issues loading activity feed in Slack.We traced this to a backend resource that unexpectedly hit capacity limits. This resulted in activity feed processes no longer serving traffic. We promptly adjusted the configuration and increased capacity limits for the backend resource, resolving the issue for all affected users.

Incident: Trouble connecting to Salesforce Channels

2026-01-30T07:52:19-08:00

7:52am PST We're aware of an issue where users may notice Salesforce channels renamed with a "ZC:" or alternative prefix and can't see channel discussions. Additionally, canvases on these channels may only appear in the Files section instead of at the top of the affected channel. We're actively looking into this and will update as soon as we know more.

8:25am PST The teams have identified the issue as being caused by a recent code change. We're reverting the change. We’ll provide an update in 30 minutes, or sooner if additional information becomes available.

8:57am PST The team has reverted the change and deployed it in a staging environment. We’ll share another update in 30 minutes or sooner as progress continues. Thank you for your patience while we work to resolve this issue.

9:32am PST The change has been rolled back and is now scheduled to be deployed to the production environment. We’ll share another update in 30 minutes or sooner as progress continues. Thank you for your patience while we work to resolve this issue.

9:58am PST Salesforce Slack channel creation is now working properly after the deployment of the fix to the production environment. We're currently clearing cached channel data to fully restore functionality for Salesforce channels created during the incident. We apologize for the trouble, but appreciate you bearing with us as we work to get things back in order.

6:54pm PST Salesforce Slack channel creation remains stable and operational. We are actively restoring functionality for the impacted Salesforce channels. Users may need to reload their Slack clients to see the restored features.We apologize for the trouble and appreciate your patience as we complete the restoration process.

9:53am PST This issue is now resolved. Current status and recent actions taken: The change has been rolled back and most channels are restored.Scope: A small number of users may have noticed Salesforce channels renamed with a "ZC:" or alternative prefix and could not see channel discussions.Required resolution steps: No additional steps are necessary.We apologize for the disruptions to your business.

Incident: Events errors related to Salesforce Automation application

2026-01-30T14:15:09-08:00

2:15pm PST We're investigating a new incident.Current impact to end users: Users may experience failures in events receiving the error "dispatch-unknown-error"We'll provide an update within 30 minutes, including further details on current actions being taken.

2:38pm PST Our work on this issue is still ongoing.Current status and actions being taken: users may be experiencing mTLS errors. We are working to identify the probable cause and alleviate the problem.We'll provide another update in 30 minutes until impact is resolved for all users.

3:14pm PST Our work on this issue is still ongoing.Current status and actions being taken: The team is reverting a TLS certificate rotation deployed this morning to restore event and slash command functionality for legacy Salesforce 1.0 apps.We'll provide another update in 30 minutes until impact is resolved for all users.

3:40pm PST Our work on this issue is still ongoing.Current status and actions being taken: We are currently reverting a TLS certificate rotation that caused authentication failures and are re-enabling events for affected legacy Salesforce apps to restore full functionality.We'll provide another update in 30 minutes until impact is resolved for all users.

4:09pm PST Our work on this issue is still ongoing.Current status and actions being taken: Service restoration is underway with 50% of availability zones recovered; we have successfully reverted the TLS certificate and are manually restarting services to restore event and slash command functionality for all legacy Salesforce 1.0 apps.We'll provide another update in 30 minutes until impact is resolved for all users.

4:58pm PST This issue is now resolved for all users.Current status and recent actions taken: We have successfully reverted a TLS certificate that caused authentication failures and re-enabled events for affected legacy Salesforce apps to restore full functionality.Previous impact to end users: Users may have experienced mTLS errors.Required resolution steps: No steps required.We apologize for any disruptions to your day.

Incident: Users on Free, Trial, or Pro plans may see the workspaces appearing blurred out

2026-01-31T16:35:11-08:00

4:35pm PST We’re investigating a Feature Degradation affecting a number of users. Some users on Free, Trial, or Pro plans may see the workspaces appearing blurred out. We’ll provide updates as soon as possible, as more information becomes available. We apologize for any inconvenience this may cause.

5:23pm PST Our work on this issue is still ongoing.Current status and actions being taken: We have identified the source of the ongoing issue related to he workspaces appearing blurred out and are actively working on a fix.We'll be back with another update once we have news to share.

6:15pm PST This issue is now resolved for all users.Current status and recent actions taken: The issue affecting the workspaces appearing blurred out has been resolved. We’ve taken steps to prevent this from happening again, and all systems are now operating normally.Previous impact to end users: Some users on Free, Trial, or Pro plans might have seen the workspaces appearing blurred out.Required resolution steps: No steps required.We apologize for any disruptions to your day.

Incident: Users unable to create or edit workflows

2026-02-02T03:05:35-08:00

3:05am PST Users may be encountering an issue when editing an existing workflow. Creating a workflow remains unaffected. We're investigating this issue and are working to understand the situation further. We'll let you know as soon as we have more details to share.

10:23am PST This issue is now resolved for all users.Current status and recent actions taken: We have rolled out a fix and the workflow executions are successful and new workflow setup works.Scope: This issue affected the desktop version where edits made to workflows (steps and triggers) could not be saved.Required resolution steps: No required steps, if users are experiencing any trouble, they may consider hard-refreshing their app via Cmd/Ctrl + Shift + R. We apologize for any disruptions to your day.

Incident: Windows desktop notification issues

2026-02-03T06:38:37-08:00

6:38am PST We've identified an issue affecting Windows desktop notifications for some Slack users. After updating to the latest release, users may still hear notification sounds, but the notification pop-ups aren't appearing on their screens. We're working on rolling back the release to resolve the issue and will provide an update as soon as more information becomes available.

9:34am PST We have rolled back the release and this has resolved the notification issue Windows users were experiencing. We apologize for the inconvenience and appreciate your patience as we sorted this out.

Incident: App History and Chat Tab Not Loading

2026-02-05T04:51:35-08:00

4:51am PST We are investigating an issue where the App History and Chat tabs are not loading for users. Users may see a blank screen when attempting to access these tabs. This issue affects desktop and web versions of Slack. We have confirmed that the issue does not appear on mobile, so customers are encouraged to use mobile as a workaround. We apologize for the inconvenience and will report back as more information becomes available.

5:51am PST We've identified a link between a recent change and the current issue. We are preparing a fix for the issue for affected users. We appreciate your continued patience as we work to resolve this.

8:59am PST We've deployed a fix, which has successfully fixed the issue, and the incident is now resolved. If users are experiencing any trouble, they may consider hard-refreshing their app via Cmd/Ctrl + Shift + R. We apologize for any inconvenience caused and thank you for your patience.

Incident: Issue with scheduled workflows

2026-02-06T03:16:47-08:00

3:16am PST We're aware of an issue affecting scheduled workflows that include a Send a message step. Users may experience authentication errors preventing these workflows from executing as expected. Other workflow types, such as link trigger workflows, don't appear to be affected at this time. We’re actively investigating, and will update as soon as we know more.

5:08am PST We’ve identified a likely cause and a fix is in progress. We’ll update once it's deployed and we can confirm that scheduled workflows that include a Send a message step are fully operational again. We appreciate your patience while we work to resolve this.

7:51am PST The fix has been deployed and we’re monitoring to see if scheduled workflows that include a Send a message step are now operating successfully. We’ll update as soon as we know more.

12:10pm PST We've validated that the fix was successful, and the authentication errors users were experiencing with scheduled workflows are now resolved. We apologize for any disruptions to your day and appreciate your patience as we sorted this out.

Incident: Unable to Install Apps to Workspaces

2026-02-10T17:37:58-08:00

5:37pm PST We are currently investigating an issue affecting users' ability to install third-party apps to Slack workspaces. When attempting to authorize apps, users may encounter a blank screen that prevents the installation from completing.We are actively working to identify the cause, and are exploring multiple paths to resolution. We apologize for any inconvenience this is causing for users.

6:22pm PST We've identified the issue impacting third-party app installations and have taken steps to restore service. Early signs indicate that users should now be able to install and authorize apps to their workspaces.We're continuing to monitor the situation closely and will provide another update once we confirm full resolution.

7:22pm PST This incident is declared resolved. Users can now install and authorize third-party apps to their Slack workspaces.We apologize for any inconvenience this may have caused.

Incident: Trouble Accessing Slack

2026-02-12T15:04:06-08:00

3:04pm PST We're investigating a new incident.Current impact to end users: We are aware of an issue currently impacting a subset of Slack workspaces. We are actively investigating this issue.We'll provide an update within 30 minutes including further details on current actions being taken.

3:46pm PST This issue is now resolved for all users.Current status and recent actions taken: We have deployed a fix, which has successfully resolved the issue.Scope: This affected a portion of GovSlack users.Previous impact to end users: Users may have encountered “500“ errors when attempting to access their workspaces.Required resolution steps: No steps required.We apologize for any disruptions to your day.

Incident: Users unable to access Slack using various browsers

2026-02-18T02:44:08-08:00

2:44am PST We're aware of an issue where users using specific antivirus software can't access Slack while using a Chrome browser. As a result, users may encounter connection errors preventing them from logging in or accessing their Slack workspaces. We're investigating the cause of this connectivity issue. We'll provide an update as soon as additional information becomes available.

4:26am PST We've identified that the issue isn't unique to Chrome, and that the conflict with antivirus software can occur across multiple browser versions. Thanks for sticking with us as we continue to investigate.

5:24pm PST We're continuing to investigate this issue. We'll keep you updated as we learn more.

11:57am PST We've identified that users can add their Slack workspace URLs to the trusted URLs in their antivirus application as a viable workaround.Thanks for sticking with us as we continue to investigate. We'll provide an update as we learn more.

4:24pm PST Current status and recent actions taken: Further investigation of this issue has determined that Slack systems and services are operating within specifications and that the issue is due to a conflict with some antivirus applications.Scope: Some users may have experienced issues accessing Slack services via their web browser due a conflict with their antivirus.Required resolution steps: Users should add their Slack workspace URL to the trusted URLs in their antivirus application.We apologize for any inconvenience this brought to your day.

Incident: Issues generating Incoming Webhooks

2026-02-18T06:02:18-08:00

6:02am PST Incoming Webhooks may silently fail to generate when installing Apps which offer this feature. We're investigating and will keep you updated as we make progress.

6:55am PST We've identified a recent change that may be triggering the issue and are working to revert this. We'll be back with an update once this completes.

10:32am PST This issue is now resolved for all users.Current status and recent actions taken: We reverted the change that triggered the issue. Scope: This issue impacted users from all regions, impacting both new installations and reinstalls of apps, affecting developers who reinstall apps to generate new webhooks.Previous impact to end users: Incoming Webhooks may have silently failed to generate when installing Apps which offer this feature. We apologize for any disruptions to your day.

Incident: Issue with Slack Direct Messaging

2026-02-24T06:36:56-08:00

6:36am PST We're aware of an issue impacting direct message functionality. Users are unable to add people to multi-person direct messages, and some users are experiencing errors when attempting to send messages. We're investigating the cause and will update you as soon as we have more information.

7:04am PST Increased load on a messaging-related service has been identified as the cause of the issue. We have reduced the load, and are working to restore full messaging functionality. Additional capacity has also been added to prevent further impact.We’re actively monitoring performance and continuing to work to ensure full recovery. We’ll provide another update as soon as possible. Thank you for your patience and understanding.

7:24am PST Users should now be able to add people to group direct messages and send messages. We continue to monitor the service closely to ensure ongoing stability. We’ll provide another update if there are any changes. Thank you for your patience.

11:19am PST This issue is now resolved.Current status and recent actions taken: Further investigation of this issue has determined that Slack systems and services are operating within specifications and remain stable. Scope: Some users may have experienced issues accessing Direct Messages or Multi-person Direct Messages.Required resolution steps: No additional steps are required. We apologize for any inconvenience this brought to your day.

Incident: Slack Email Delivery Feature Degradation

2026-02-24T16:26:58-08:00

4:26pm PST We're aware of an issue where some users are unable to receive email confirmation codes and invites from Slack. As a result, these users cannot complete email login processes or accept invitations. We are currently investigating the cause. We’re actively working on multiple resolution paths. We'll provide an update in 60 minutes or sooner if additional information becomes available.

5:17pm PST Our work on this issue is still ongoing.We have seen that some emails that are not designated as ‘blocked’ are automatically being blocked. This issue persists even when these email addresses are added to specific Allow Lists. Our priority is to fully understand the technical issue behind email delivery, to enable us to restore service to customers as quickly as possible. We'll be back with another update once we have news to share.

6:33pm PST Our work on this issue continues.Our investigation has identified that emails are being blocked by a suppression list subtype where our internal suppression checks aren't aligning for certain accounts. Even when affected addresses are added to our Allow List, the issue persists.We can confirm that this issue is not a global suppression issue, and the issue relates only to those emails affected by the suppression list subtype identified.We’re actively working to identify which sending accounts are not being accurately covered by these suppression checks, and to implement a fix that will restore email delivery for our affected users.We'll be back with another update once we have news to share.

7:26pm PST Our work on this issue continues.We've ‌further identified that the cause relates to a missing data field in our email validation system, which has been causing messages to be incorrectly blocked. We’ve developed and deployed a fix that is currently being rolled out across our infrastructure. We expect the fix to be fully deployed within the hour, when testing and validation will begin.The fix is expected to restore email services to all impacted users. We'll provide an update once the deployment is complete and we've confirmed service restoration.

8:38pm PST Our work on this issue continues.The fix deployment across all production infrastructure is expected to take a further 30 minutes. Initial testing shows that email delivery functionality working as expected following configuration changes on impacted accounts. We’ll provide a final update once full deployment and validation has been completed.

8:52pm PST Our work on this issue has concluded.We’ve tested and validated the fix deployment, and can see previously impacted accounts now receiving emails, as intended.The incident has been resolved as of 04:40 UTC, February 25This is the final update for this incident. We apologize for any inconvenience to our users for this issue.

Incident: Issue with Slack Search feature

2026-03-01T06:23:32-08:00

6:23am PST We are currently experiencing an issue with the Slack Search feature. Users may encounter errors or delays when attempting to use Search.We’re actively investigating, and will update as soon as we know more.

12:49pm PST The issue with slow or incomplete search results in Slack is now resolved for all users as of 19:53 UTC on March 1, 2026.We apologize for any disruptions to your day.

Incident: Degraded Search Performance for Dubai IDR Users – Middle East (Dubai) Region

2026-03-02T00:50:16-08:00

12:50am PST We’ve noted that International Data Residency (IDR) users in the Middle East (Dubai) region may experience degraded search performance or search failures. Services for other users in the region are operating normally. We're aware of a vendor issue affecting multiple availability zones in the region. We are actively engaged in restoring the services as quickly as possible.

6:47am PST Our work on this issue is still ongoing.Current status and actions being taken: International Data Residency (IDR) users continue to experience search issues due to an ongoing regional incident. We're working with a third-party vendor to restore service... We don’t have an ETA but it’s likely to take at least a day for service to be restored.We continue to monitor the situation closely and will provide updates as more information becomes available.

2:47pm PST Our work on this issue is still ongoing.Current status and actions being taken: International Data Residency (IDR) customers continue to experience search disruptions due to a regional incident affecting our third-party provider, Amazon Web Services. This issue is related to the broader Salesforce incident currently underway. We are actively working to restore service, but there is no estimated time of recovery. Conditions at the impacted facilities, including loss of power and cooling, continue to affect progress. We are closely monitoring the situation, and will provide further updates as new information becomes available.Current impact to end users: International Data Residency (IDR) users in the Middle East (Dubai) region may experience degraded search performance or search failures. Services for other users in the region are operating normally. We continue to monitor the situation closely and will provide updates as more information becomes available.

12:30pm PST Our work on this issue is still ongoing.Current status and actions being taken: We are currently managing a severe physical infrastructure incident in the Middle East following significant damage to regional data centers. While one facility remains operational, we are continuing to work closely with AWS to resolve current data access issues and restore full service, with a major recovery milestone expected within the next 24 hours. This recovery will resolve current data access issues where some older files and database records remain temporarily unreachable. Our teams are prioritizing the restoration of missing data shards and database records as quickly as safety protocols allow. Current impact to end users: International Data Residency (IDR) users in the Middle East (Dubai) region may experience degraded search performance or search failures. Services for other users in the region are operating normally. We continue to monitor the situation closely and will provide updates as more information becomes available.

10:41am PST This issue with a third party vendor impacts only a subset of IDR customers.Current status and recent actions taken: We are staying engaged with our International Data Residency (IDR) customers on a path to recovery. Scope: Isolated to a subset of IDR customers.Previous impact to end users: Severe degradation to services only impacting IDR customers.Required resolution steps: Remain engaged with our IDR customers until they are fully recovered.

Incident: Issues with App Mentions, Grid Migrations, and Notifications

2026-03-05T06:56:18-08:00

6:56am PST We're aware of an issue impacting the completion of ongoing enterprise migrations, resulting in longer than expected downtime. In efforts to resolve the issue we're increasing processing capacity and have deployed code changes to address the delayed job processing. We'll provide an update when we next have additional information.

11:36am PST We've identified additional impact where developers may observe no responses when @mentioning an application. This incident extends impact to Grid migrations and iOS push notifications may not deliver.Current status and actions being taken: We continue to investigate potential triggers in recent deployments for this issue.Scope: This will impact any developers @mentioning an app in a Slack channel, upcoming/planned migrations, and iOS notifications.Current impact to end users: Developers may not receive responses when @mentioning an app to execute an action in a Slack channel, org admins will observe delays with upcoming/planned migrations, and iOS push notifications may not deliver.Known workarounds: No known workarounds.We appreciate your patience as we sort this out. We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

12:07pm PST We’re still actively investigating this issue, but we don’t have any new information to share at this time. Thanks for sticking with us as we continue to work towards a fix.We'll provide another update in 30 minutes until impact is resolved for all users.

12:40pm PST We're actively working to resolve the current platform functionality issues.Current status and actions being taken: We’re continuing to investigate the underlying trigger and have noticed an improvement in health metrics with Push notifications.Estimated time to resolution: No ETA at this time.Scope: This issue isn't affecting any specific region, but a percentage of users may be affected.Current impact to end users: Developers may not receive responses when @mentioning an app to execute an action in a Slack channel, org admins will observe delays with upcoming/planned migrations, and mobile push notifications may not deliver.Known workarounds: No known workarounds at this time.We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

1:14pm PST We're actively working to resolve the current platform functionality issues.Current status and actions being taken: We're currently working on a fix to block dispatch jobs while increasing resources to expedite processing.Estimated time to resolution: No ETA at this time.Scope: This issue isn't affecting any specific region, but a percentage of users may be affected.Current impact to end users: Developers may not receive responses when @mentioning an app to execute an action in a Slack channel, org admins will observe delays with upcoming/planned migrations, and mobile push notifications may not deliver.Known workarounds: No known workarounds at this time.We'll continue to provide updates every 30 minutes until the impact is resolved for all users.