Slack Outage History

Started Feb 18, 2026, 02:02 PM UTC· resolved Feb 18, 2026, 06:32 PM UTC

1. investigating Feb 18, 2026, 02:02 PM UTC

   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.

2. identified Feb 18, 2026, 02:55 PM UTC

   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.

3. resolved Feb 18, 2026, 06:32 PM UTC

   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.

Read the full incident report →

Started Feb 18, 2026, 10:44 AM UTC· resolved Feb 20, 2026, 12:24 AM UTC

1. identified Feb 18, 2026, 10:44 AM UTC

   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.

2. identified Feb 18, 2026, 12:26 PM UTC

   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.

3. investigating Feb 19, 2026, 01:24 AM UTC

   We're continuing to investigate this issue. We'll keep you updated as we learn more.

4. identified Feb 19, 2026, 07:57 PM UTC

   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.

5. resolved Feb 20, 2026, 12:24 AM UTC

   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.

Read the full incident report →

Started Feb 12, 2026, 11:04 PM UTC· resolved Feb 12, 2026, 11:46 PM UTC

1. investigating Feb 12, 2026, 11:04 PM UTC

   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.

2. resolved Feb 12, 2026, 11:46 PM UTC

   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.

Read the full incident report →

Started Feb 11, 2026, 01:37 AM UTC· resolved Feb 11, 2026, 03:22 AM UTC

1. investigating Feb 11, 2026, 01:37 AM UTC

   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.

2. identified Feb 11, 2026, 02:22 AM UTC

   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.

3. resolved Feb 11, 2026, 03:22 AM UTC

   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.

Read the full incident report →

Started Feb 06, 2026, 11:16 AM UTC· resolved Feb 06, 2026, 08:10 PM UTC

1. investigating Feb 06, 2026, 11:16 AM UTC

   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.

2. investigating Feb 06, 2026, 01:08 PM UTC

   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.

3. monitoring Feb 06, 2026, 03:51 PM UTC

   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.

4. resolved Feb 06, 2026, 08:10 PM UTC

   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.

Read the full incident report →

Started Feb 05, 2026, 12:51 PM UTC· resolved Feb 05, 2026, 04:59 PM UTC

1. investigating Feb 05, 2026, 12:51 PM UTC

   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.

2. identified Feb 05, 2026, 01:51 PM UTC

   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.

3. resolved Feb 05, 2026, 04:59 PM UTC

   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.

Read the full incident report →

Started Feb 03, 2026, 02:38 PM UTC· resolved Feb 03, 2026, 05:34 PM UTC

1. identified Feb 03, 2026, 02:38 PM UTC

   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.

2. resolved Feb 03, 2026, 05:34 PM UTC

   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.

Read the full incident report →

Started Feb 02, 2026, 11:05 AM UTC· resolved Feb 02, 2026, 06:23 PM UTC

1. investigating Feb 02, 2026, 11:05 AM UTC

   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.

2. resolved Feb 02, 2026, 06:23 PM UTC

   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.

Read the full incident report →

Started Feb 01, 2026, 12:35 AM UTC· resolved Feb 01, 2026, 02:18 AM UTC

1. investigating Feb 01, 2026, 12:35 AM UTC

   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.

2. identified Feb 01, 2026, 01:23 AM UTC

   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.

3. resolved Feb 01, 2026, 02:15 AM UTC

   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.

Read the full incident report →

Started Jan 30, 2026, 10:15 PM UTC· resolved Jan 31, 2026, 12:58 AM UTC

1. investigating Jan 30, 2026, 10:15 PM UTC

   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. resolved Jan 30, 2026, 10:38 PM UTC

   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. resolved Jan 30, 2026, 11:14 PM UTC

   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.

4. resolved Jan 30, 2026, 11:40 PM UTC

   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.

5. resolved Jan 31, 2026, 12:09 AM UTC

   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.

6. resolved Jan 31, 2026, 12:58 AM UTC

   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.

Read the full incident report →

Started Jan 30, 2026, 03:52 PM UTC· resolved Feb 02, 2026, 05:53 PM UTC

1. investigating Jan 30, 2026, 03:52 PM UTC

   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.

2. investigating Jan 30, 2026, 04:25 PM UTC

   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.

3. investigating Jan 30, 2026, 04:57 PM UTC

   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.

4. investigating Jan 30, 2026, 05:32 PM UTC

   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.

5. investigating Jan 30, 2026, 05:58 PM UTC

   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. investigating Feb 02, 2026, 02:54 AM UTC

   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.

7. resolved Feb 02, 2026, 05:53 PM UTC

   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.

Read the full incident report →

Started Jan 23, 2026, 05:03 AM UTC· resolved Jan 29, 2026, 05:16 PM UTC

1. investigating Jan 23, 2026, 05:03 AM UTC

   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.

2. resolved Jan 23, 2026, 05:43 AM UTC

   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.

3. resolved Jan 23, 2026, 06:47 AM UTC

   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.

4. resolved Jan 29, 2026, 05:16 PM UTC

   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.

Read the full incident report →

Started Jan 22, 2026, 10:00 PM UTC· resolved Jan 28, 2026, 06:30 PM UTC

1. investigating Jan 22, 2026, 10:00 PM UTC

   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.

2. resolved Jan 23, 2026, 08:09 AM UTC

   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.

Read the full incident report →

Started Jan 22, 2026, 07:43 PM UTC· resolved Jan 23, 2026, 12:13 AM UTC

1. investigating Jan 22, 2026, 07:43 PM UTC

   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.

2. identified Jan 22, 2026, 08:28 PM UTC

   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.

3. resolved Jan 22, 2026, 10:18 PM UTC

   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.

Read the full incident report →

Started Jan 15, 2026, 07:41 PM UTC· resolved Jan 15, 2026, 07:58 PM UTC

1. resolved Jan 15, 2026, 07:41 PM UTC

   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

Read the full incident report →

Started Jan 14, 2026, 09:24 PM UTC· resolved Jan 29, 2026, 04:55 PM UTC

1. investigating Jan 14, 2026, 09:24 PM UTC

   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. resolved Jan 14, 2026, 10:03 PM UTC

   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.

3. resolved Jan 14, 2026, 10:37 PM UTC

   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.

4. resolved Jan 14, 2026, 11:04 PM UTC

   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.

5. resolved Jan 14, 2026, 11:19 PM UTC

   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.

6. resolved Jan 29, 2026, 04:55 PM UTC

   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.

Read the full incident report →

Started Dec 24, 2025, 12:33 AM UTC· resolved Dec 29, 2025, 05:49 PM UTC

1. investigating Dec 24, 2025, 12:33 AM UTC

   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.

2. resolved Dec 24, 2025, 02:04 AM UTC

   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

3. resolved Dec 29, 2025, 05:49 PM UTC

   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.

Read the full incident report →

Started Dec 15, 2025, 05:14 PM UTC· resolved Dec 18, 2025, 04:57 PM UTC

1. investigating Dec 15, 2025, 05:14 PM UTC

   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.

2. identified Dec 15, 2025, 06:25 PM UTC

   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.

3. resolved Dec 15, 2025, 09:51 PM UTC

   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.

4. resolved Dec 18, 2025, 04:57 PM UTC

   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.

Read the full incident report →

Started Dec 08, 2025, 11:23 PM UTC· resolved Dec 18, 2025, 04:44 PM UTC

1. investigating Dec 08, 2025, 11:23 PM UTC

   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.

2. resolved Dec 09, 2025, 06:55 AM UTC

   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.

3. resolved Dec 09, 2025, 04:55 PM UTC

   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.

4. investigating Dec 09, 2025, 05:34 PM UTC

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

5. identified Dec 18, 2025, 04:44 PM UTC

   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.

Read the full incident report →

Started Dec 05, 2025, 04:24 AM UTC· resolved Dec 09, 2025, 05:59 PM UTC

1. investigating Dec 05, 2025, 04:24 AM UTC

   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.

2. resolved Dec 05, 2025, 04:32 AM UTC

   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.

3. resolved Dec 05, 2025, 05:04 AM UTC

   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.

4. investigating Dec 05, 2025, 05:33 AM UTC

   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.

5. investigating Dec 05, 2025, 06:20 AM UTC

   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.

6. investigating Dec 05, 2025, 07:10 AM UTC

   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.

7. investigating Dec 05, 2025, 11:31 AM UTC

   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.

8. investigating Dec 05, 2025, 05:34 PM UTC

   Search functionality has been restored, but our full mitigaion work is still ongoing. Current status and actions being taken: We're currently re-processing a backlog of unindexed messages via backend jobs. This work is still ongoing and expected to take some time. Messages sent between approximately 7:45 PM PST on December 4, 2025 and 12:17 AM PST on December 5, 2025 may be temporarily missing from search results. We're working to process this backlog.We'll be back with another update once we have news to share.

9. resolved Dec 05, 2025, 09:10 PM UTC

   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.

10. resolved Dec 09, 2025, 05:59 PM UTC

    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.

Read the full incident report →

Started Dec 04, 2025, 11:43 PM UTC· resolved Dec 05, 2025, 12:02 AM UTC

1. resolved Dec 04, 2025, 11:43 PM UTC

   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.

Read the full incident report →

Started Dec 02, 2025, 08:08 PM UTC· resolved Dec 09, 2025, 05:29 PM UTC

1. investigating Dec 02, 2025, 08:08 PM UTC

   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.

2. investigating Dec 02, 2025, 08:44 PM UTC

   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.

3. identified Dec 02, 2025, 09:12 PM UTC

   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.

4. investigating Dec 02, 2025, 09:46 PM UTC

   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.

5. investigating Dec 02, 2025, 10:15 PM UTC

   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.

6. monitoring Dec 02, 2025, 10:47 PM UTC

   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.

7. investigating Dec 02, 2025, 11:17 PM UTC

   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.

8. monitoring Dec 02, 2025, 11:58 PM UTC

   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.

9. resolved Dec 03, 2025, 12:41 AM UTC

   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.

10. monitoring Dec 03, 2025, 01:09 AM UTC

    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.

11. resolved Dec 03, 2025, 05:59 AM UTC

    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.

12. resolved Dec 09, 2025, 05:29 PM UTC

    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.

Read the full incident report →

Started Nov 28, 2025, 10:44 AM UTC· resolved Dec 01, 2025, 05:19 PM UTC

1. investigating Nov 28, 2025, 10:44 AM UTC

   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.

2. identified Nov 28, 2025, 11:16 AM UTC

   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. investigating Nov 28, 2025, 11:46 AM UTC

   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. investigating Nov 28, 2025, 12:18 PM UTC

   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.

5. investigating Nov 28, 2025, 12:54 PM UTC

   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.

6. resolved Dec 01, 2025, 05:19 PM UTC

   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.

Read the full incident report →