- Detected by Pingoru
- Jul 28, 2026, 02:13 AM UTC
- Resolved
- Jul 28, 2026, 11:09 PM UTC
- Duration
- 20h 55m
Affected: Apps/Integrations/APIs
Timeline · 3 updates
-
identified Jul 28, 2026, 02:13 AM UTC
We're currently investigating an issue affecting users' ability to receive incoming emails into Slack, caused by some issues with our email ingestion pipeline. We're sorry for any inconvenience this is causing, our team is actively working on a fix and we'll share an update as soon as we have more information.
-
identified Jul 28, 2026, 03:25 AM UTC
We identified the cause of the issue preventing users from receiving incoming emails. We are deploying a fix and will share a further update once deployment and verification are complete.
-
investigating Jul 28, 2026, 03:43 AM UTC
The fix has been successfully deployed, and validation is now complete. The issue preventing users from receiving incoming emails into Slack is fully resolved, and normal service functionality has been restored. We apologize for any disruptions to your day.
Read the full incident report →
- Detected by Pingoru
- Jul 24, 2026, 08:22 AM UTC
- Resolved
- Jul 24, 2026, 10:47 AM UTC
- Duration
- 2h 24m
Affected: Workflows
Timeline · 5 updates
-
investigating Jul 24, 2026, 08:22 AM UTC
We’re aware of an issue affecting Workflows that include 'refer to a message link'. Users with these workflows are unable to send a message to a channel, and will receive an ‘Input Validation Error’ when trying to perform this step. We’re actively investigating this issue and will provide an update in 30 minutes or sooner if more information becomes available.
-
investigating Jul 24, 2026, 08:44 AM UTC
We've engaged our Worklow team to assist in the investigation. Initial analysis appears to show a conflict between specific variables. We’re continuing to work to understand whether this is the trigger of the issue. We’ll provide an update in 30 minutes or sooner if more information becomes available.
-
investigating Jul 24, 2026, 09:08 AM UTC
The Workflow team is currently analyzing whether a recent change may have resulted in the conflict between variables that has been observed. It is expected to take some time to validate whether this is the case. We’ll provide an update in 60 minutes or sooner if more information becomes available.
-
investigating Jul 24, 2026, 09:42 AM UTC
We’ve performed a test of reverting a recent change and this appears to have resolved the issue. We are in the process of performing a production wide revert of this change. This is expected to take some time to complete and we will validate that it is successful. We’ll provide an update in 2 hours or sooner if more information becomes available.
-
resolved Jul 24, 2026, 10:47 AM UTC
We’ve completed the revert of the recent change and have validated that this has brought customers out of impact and can now successfully send a message to a channel using Workflows that include 'refer to a message link'. We apologize for how this incident may have affected you and your business.
Read the full incident report →
- Detected by Pingoru
- Jul 24, 2026, 02:18 AM UTC
- Resolved
- Jul 24, 2026, 03:20 AM UTC
- Duration
- 1h 1m
Affected: Notifications
Timeline · 3 updates
-
investigating Jul 24, 2026, 02:18 AM UTC
Some users are reporting issues with receiving reminders in Slack. We're aware of the issue and are actively investigating. We'll provide an update as soon as more information becomes available. We apologize for any inconvenience this issue is causing you.
-
identified Jul 24, 2026, 02:53 AM UTC
We believe we’ve identified the cause of the issue impacting reminders in Slack. We’ve developed a potential fix for the issue and have deployed a change. We are actively monitoring to confirm that reminders are being delivered as expected. We'll provide an update as more information becomes available.
-
resolved Jul 24, 2026, 03:20 AM UTC
After a period of monitoring, we can see that reminders are now working as expected following the fix deployment. This issue has been resolved as of 03:00 UTC, July 24. We apologize for any inconvenience this issue has caused you.
Read the full incident report →
- Detected by Pingoru
- Jun 26, 2026, 09:12 AM UTC
- Resolved
- Jun 26, 2026, 10:09 AM UTC
- Duration
- 57m
Timeline · 3 updates
-
investigating Jun 26, 2026, 09:12 AM UTC
We're aware of an issue affecting users ability to reach our Slack Support team via the Chat functionality on the Slack Help page. Users will be unable to click on the ‘Chat’ option and will see a ‘Chat is temporarily unavailable. Please send us a message or check back later’ error message. We're working to resolve this issue and will provide an update in 30 minutes or sooner if additional information becomes available.
-
investigating Jun 26, 2026, 09:41 AM UTC
Additional Slack engineers have been engaged and are investigating this issue. As a workaround, if users require support, they can use the ‘Send us a Message’ functionality on the Slack Help Center page here: https://slack.com/intl/en-gb/help/requests/new . A member of the Slack team will then be in touch. We're working to resolve this issue and will provide an update in 30 minutes or sooner if additional information becomes available.
-
resolved Jun 26, 2026, 10:09 AM UTC
We've resolved the issue and users can now use the Chat feature on the Slack Help Center. We performed a configuration change, which brought the feature back online and have validated that it's functioning as expected. We apologize for how this incident may have affected you and your business.
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 10:33 PM UTC
- Resolved
- Jun 18, 2026, 04:14 AM UTC
- Duration
- 5h 41m
Affected: Login/SSO
Timeline · 3 updates
-
investigating Jun 17, 2026, 10:33 PM UTC
Some workspace admins on standalone (non-Enterprise Grid) workspaces may be experiencing an issue where the SSO and authentication configuration page does not display current settings as expected. Admins may see a blank value for the "Require SSO authentication for" field on the admin SSO settings page, which does not accurately reflect the actual backend configuration — SSO settings remain intact and in effect. We are actively investigating this issue and will provide an update as soon as we have more information to share. We apologize for the inconvenience.
-
identified Jun 18, 2026, 01:49 AM UTC
We have identified the trigger and developed a fix. We are currently deploying this fix and expect to resolve the issue shortly. We will provide another update once the deployment is complete. We apologize for the inconvenience.
-
monitoring Jun 18, 2026, 04:14 AM UTC
We have successfully deployed the fix to production and the issue is resolved. The Admin SSO and Authentication Configuration page for standalone workspaces should now display the correct settings. If you continue to see outdated information, refresh the SSO Admin page to load the latest changes.
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 12:38 AM UTC
- Resolved
- Jun 17, 2026, 01:07 AM UTC
- Duration
- 28m
Affected: Messaging
Timeline · 2 updates
-
investigating Jun 17, 2026, 12:38 AM UTC
Some users are having trouble loading Slack. Performing certain actions, channel creation, invitation, and join operations may result in a degraded experience. Thank you for your patience while we continue to investigate the situation.
-
resolved Jun 17, 2026, 01:07 AM UTC
This issue is now resolved for all users. We apologize for any disruptions to your day.
Read the full incident report →
- Detected by Pingoru
- Jun 16, 2026, 03:50 PM UTC
- Resolved
- Jun 22, 2026, 08:39 PM UTC
- Duration
- 6d 4h
Affected: Workflows
Timeline · 6 updates
-
investigating Jun 16, 2026, 03:50 PM UTC
We are aware that some users on the Slack Android app are unable to submit workflow forms that contain a required file upload field. After a file is selected, the Submit button becomes disabled and the form cannot be completed. Users on Slack for iOS and Slack for web are not affected. We are actively investigating the issue and working to identify the root cause. We'll provide an update in 60 minutes or sooner if additional information becomes available.
-
identified Jun 16, 2026, 04:48 PM UTC
We have identified the cause of this issue and confirmed it affects a small subset of users on a single version of the Slack Android app. Users on other Android versions, iOS, and web are not affected. A fix is already available and will begin rolling out to Android users tomorrow. We will provide an update as soon as additional information becomes available.
-
investigating Jun 17, 2026, 07:38 PM UTC
A fix for this issue has been delivered in a new version of the Slack Android app, and rollout has now begun. Android users will start seeing the updated app version become available in the Google Play Store as the rollout progresses. Once updated, users who were experiencing issues submitting workflow forms containing a required file upload field will be able to do so successfully. We will continue to monitor the rollout and provide another update as additional information becomes available.
-
investigating Jun 18, 2026, 10:30 PM UTC
The rollout of the new version of the Slack Android app is ongoing and may take up to several days to fully complete. We continue to monitor the rollout and will provide another update when we have more information to share. Thank you for your patience with us while we work through this.
-
resolved Jun 21, 2026, 05:33 PM UTC
On June 19, 2026 at 13:12 UTC, we completed a rollback of the configuration change, which resolved the notification delivery failure. Push notifications are now functioning normally for Android users. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
-
resolved Jun 22, 2026, 08:39 PM UTC
This issue has been resolved. Android users who were experiencing issues submitting workflow forms containing a required file upload field can now do so successfully. A fix was delivered via a new update to the Slack Android app. Users who are still experiencing this issue should update the Slack app from the Google Play Store to resolve it. No other action is required. We apologize for the inconvenience and thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Jun 16, 2026, 01:19 AM UTC
- Resolved
- Jun 16, 2026, 01:19 AM UTC
- Duration
- —
Affected: Messaging
Timeline · 1 update
-
resolved Jun 16, 2026, 01:19 AM UTC
Some users may have been unable to edit or delete messages in certain channels. We identified and resolved the issue. We apologize for how this issue affected you and your business.
Read the full incident report →
- Detected by Pingoru
- Jun 11, 2026, 10:13 PM UTC
- Resolved
- Jun 11, 2026, 11:15 PM UTC
- Duration
- 1h 2m
Timeline · 3 updates
-
investigating Jun 11, 2026, 10:13 PM UTC
We're aware of an issue affecting the Slack desktop app. Users may find that content in child windows, such as channels or documents opened in a separate window, displays at reduced height. We’ve identified the technical trigger and are deploying a fix. We'll provide an update in 30 minutes or sooner if additional information becomes available.
-
monitoring Jun 11, 2026, 10:43 PM UTC
We’ve deployed a fix and are now performing validations. We'll provide an update in 30 minutes or sooner if additional information becomes available.
-
resolved Jun 11, 2026, 11:15 PM UTC
We've validated that the fix resolved the issue and child windows are now displaying content as expected. You may need to reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux) in order for this fix to be reflected on your end. We're sorry for the disruption this caused to your day.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 08:36 PM UTC
- Resolved
- Jun 11, 2026, 06:39 AM UTC
- Duration
- 10h 3m
Affected: Apps/Integrations/APIs
Timeline · 8 updates
Read the full incident report →
- Detected by Pingoru
- Jun 09, 2026, 03:24 PM UTC
- Resolved
- Jun 10, 2026, 09:43 PM UTC
- Duration
- 1d 6h
Affected: Workspace/Org Administration
Timeline · 8 updates
Read the full incident report →
- Detected by Pingoru
- Jun 08, 2026, 07:00 PM UTC
- Resolved
- Jun 08, 2026, 07:35 PM UTC
- Duration
- 35m
Affected: Login/SSO
Timeline · 2 updates
-
investigating Jun 08, 2026, 07:00 PM UTC
Some users in EMEA may be failing to receive 2FA codes via SMS when logging into Slack. We are investigating the trigger and working to resolve this incident as quickly as possible. We will provide another update in 30 minutes or sooner as we have more details to share.
-
resolved Jun 08, 2026, 07:35 PM UTC
The issue affecting SMS-based two-factor authentication for users in EMEA has been resolved, and all services are now functioning as expected. We have adjusted configuration settings to restore normal service and will continue to monitor the situation to ensure stability. We apologize for how you and your business may have been affected by this. We will perform a full investigation of the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2026, 04:33 PM UTC
- Resolved
- Jun 03, 2026, 05:35 PM UTC
- Duration
- 1h 1m
Affected: Workspace/Org Administration
Timeline · 4 updates
-
investigating Jun 03, 2026, 04:33 PM UTC
We're investigating a new incident. Current impact to end users: Some administrators may be experiencing errors managing members.We'll provide an update within 30 minutes including further details on current actions being taken.
-
investigating Jun 03, 2026, 04:49 PM UTC
We're looking into an issue where some users may be unable to add new members, send invites, or run macros on their workspaces. We're on the case and will provide another update as soon as we have more details to share. We apologize for any disruption to your work. Current impact to end users: Some users may encounter errors when attempting to add or manage members, send invites, or run macros on their workspace. We'll provide an update within 30 minutes or sooner if additional information becomes available.
-
identified Jun 03, 2026, 05:12 PM UTC
We have identified the cause of the issue preventing some workspace admins from adding new members via the Admin page as a recent change and are in the process of rolling back this change. Current impact to end users: Some users may encounter errors when attempting to add or manage members, send invites, or run macros on their workspace. Known workaround: Inviting members via the Slack client workspace menu (workspace name → Invite people to workspace) is currently working as expected. We'll provide an update within 30 minutes or sooner if additional information becomes available.
-
identified Jun 03, 2026, 05:35 PM UTC
The Slack engineering team identified the cause as a recent update that introduced a code change which caused the invite modal to fail when accessed from the Admin page. We rolled back the change and have confirmed the fix is fully deployed and the issue is resolved. Some workspace Admins were unable to add new members to their workspaces via the Manage Members Admin page. In addition, some users attempting to invite people from this page may have encountered an error or been unable to run macros on their workspaces. Workspace Admins should now be able to add new members via the Manage Members admin page. A page refresh may be required. We apologize for the disruption to your work.
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2026, 12:58 AM UTC
- Resolved
- Jun 03, 2026, 01:47 AM UTC
- Duration
- 48m
Affected: ConnectivityMessaging
Timeline · 3 updates
-
investigating Jun 03, 2026, 12:58 AM UTC
We're investigating a new incident. Current impact to end users: Some users may be experiencing trouble loading or connecting to Slack. We're on the case.We'll provide an update within 30 minutes including further details on current actions being taken.
-
investigating Jun 03, 2026, 01:38 AM UTC
Our work on this issue is still ongoing. Current status and actions being taken: we're investigating an issue where some Slack users are experiencing thread loading, client booting, and message delivery failures. We've identified several potential contributing factors and are working to confirm the root cause. Further updates will be shared as the investigation continues.We'll provide another update in 30 minutes until the impact is resolved for all users.
-
resolved Jun 03, 2026, 01:47 AM UTC
This issue is now resolved for all users. Current status and recent actions taken: we've resolved the issue where some Slack users may have experienced message send failures and thread loading issues. We identified and addressed the root cause, and services have been fully restored.We apologize for any disruptions to your day.
Read the full incident report →
- Detected by Pingoru
- Jun 02, 2026, 04:16 PM UTC
- Resolved
- Jun 02, 2026, 04:16 PM UTC
- Duration
- —
Affected: ConnectivityMessaging
Timeline · 1 update
-
resolved Jun 02, 2026, 04:16 PM UTC
Current status: The Slack engineering team investigated connectivity issues that affected some users between approximately 13:30 and 14:00 UTC on June 2, 2026. The issue has been resolved and no further impact has been reported. Scope: Some users, primarily in Europe, may have experienced difficulty loading or sending Slack messages during this window We apologize for any inconvenience this may have caused.
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 02:08 AM UTC
- Resolved
- Jun 01, 2026, 03:05 AM UTC
- Duration
- 57m
Timeline · 3 updates
-
investigating Jun 01, 2026, 02:08 AM UTC
We are currently investigating a partial degradation impacting usergroups. We’ll provide an update as soon as we have more information to share and are sorry for any inconvenience this issue is causing.
-
investigating Jun 01, 2026, 02:38 AM UTC
We continue to investigate the issue and have identified a recent deployment as a likely trigger. Users may experience issues with user groups, including failed @mentions or groups appearing unavailable. We are actively working on restoring functionality and will provide another update as soon as possible.
-
resolved Jun 01, 2026, 03:05 AM UTC
Our investigation has determined that the issue is isolated to a single customer environment and is not impacting the broader service. As a result, this incident will be removed from the status page and we will continue to work directly with the affected customer to address their issue.
Read the full incident report →
- Detected by Pingoru
- May 27, 2026, 11:02 PM UTC
- Resolved
- May 27, 2026, 11:29 PM UTC
- Duration
- 26m
Affected: Login/SSOConnectivityMessagingFilesNotificationsHuddlesSearchApps/Integrations/APIsWorkspace/Org AdministrationWorkflowsCanvases
Timeline · 1 update
-
investigating May 27, 2026, 11:02 PM UTC
The Slack Engineering team is currently investigating severe latency impacting all Slack services. We'll provide an update as soon as we have more information to share and apologize for any inconvenience this is causing.
Read the full incident report →
- Detected by Pingoru
- May 27, 2026, 11:00 PM UTC
- Resolved
- May 28, 2026, 03:22 PM UTC
- Duration
- 16h 21m
Affected: ConnectivityMessagingFilesApps/Integrations/APIsWorkflowsCanvases
Timeline · 21 updates
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 08:51 PM UTC
- Resolved
- May 19, 2026, 10:27 PM UTC
- Duration
- 1h 36m
Affected: Files
Timeline · 2 updates
-
monitoring May 19, 2026, 08:51 PM UTC
We've identified the trigger, causing slow file and emoji uploads in Slack, and have deployed a fix. At this time, we are monitoring the environment to confirm full resolution. - Current status and actions being taken: We've identified a frontend error as the cause of the issue and have deployed a fix. We're actively monitoring our health metrics to confirm the fix has resolved the issue for all users. - Estimated time to resolution: No ETA at this time. - Scope: Users globally may be experiencing this issue. - Current impact to end users: Some users may experience slowness when uploading files and emojis in Slack. Attaching or sending files may be taking longer than expected — or failing to complete in a timely manner. - Known workarounds: No workarounds at this time. We'll provide another update as soon as we have more information to share.
-
resolved May 19, 2026, 10:27 PM UTC
This issue is now resolved for all users. Current status and recent actions taken: The fix has successfully deployed, and our health metrics have stabilized. The issue is now fully resolved for all affected users. Scope: This wasn't affecting any specific region, but a percentage of users may have been affected globally.Previous impact to end users: Some users may have experienced slowness when uploading files and emojis in Slack. Attaching or sending files may have taken longer than expected — or failed to complete in a timely manner.Required resolution steps: No additional steps are required.We apologize for any disruptions to your day.
Read the full incident report →
- Detected by Pingoru
- May 18, 2026, 02:53 PM UTC
- Resolved
- May 18, 2026, 02:53 PM UTC
- Duration
- —
Affected: Huddles
Timeline · 1 update
-
resolved May 18, 2026, 02:53 PM UTC
Some Slack users experienced issues where Huddle AI summaries weren't being generated. Users also appeared to be showing as in a huddle after it had ended. We've fixed both issues. Missing summaries were restored, and the system responsible for showing huddle statuses has been refreshed. If you still notice any users appearing stuck in a huddle, please contact Slack Support. We apologize for the inconvenience and any impact this may have had.
Read the full incident report →
- Detected by Pingoru
- May 14, 2026, 02:37 PM UTC
- Resolved
- May 14, 2026, 03:34 PM UTC
- Duration
- 57m
Affected: MessagingFilesApps/Integrations/APIsWorkflows
Timeline · 4 updates
-
investigating May 14, 2026, 02:37 PM UTC
We're investigating a new incident. Current impact to end users: We’re aware of an issue affecting file uploads, message edits, channel renames, and channel creations.We'll provide an update within 30 minutes including further details on current actions being taken.
-
investigating May 14, 2026, 02:50 PM UTC
Our work on this issue is still ongoing. Current status and actions being taken: We're investigating reports of slow loading times, errors when updating workflows, editing messages, creating or renaming channels, reactions, and issues with file uploads and third-party integrations. Some users may encounter failures when posting images or using add-ins. We'll be back with another update once we have news to share.
-
identified May 14, 2026, 03:19 PM UTC
Our work on this issue is still ongoing. Current status and actions being taken: We've identified a potential cause related to an internal infrastructure component responsible for processing background tasks. Several nodes running this component were experiencing resource exhaustion and CrashLoopBackOff errors, causing connectivity failures to our message queue brokers. A revert of a recent configuration change is currently rolling out and we're seeing signs of improvement — 503 errors are trending down and some impacted pods are stabilizing. We'll continue monitoring the progress. We'll be back with another update once we have news to share. Thank you for your patience.
-
resolved May 14, 2026, 03:34 PM UTC
The issue affecting multiple features, including file uploads, message edits, and channel management, has been resolved. A fix has been fully deployed, and all systems are functioning normally. If you are still experiencing any trouble, please perform a hard reload of Slack by pressing Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). Mobile users should fully close and relaunch the app. We sincerely apologize for the disruption to your day and appreciate your patience while we worked to sort this out.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 06:31 PM UTC
- Resolved
- May 11, 2026, 09:48 PM UTC
- Duration
- 3d 3h
Affected: MessagingFilesNotificationsApps/Integrations/APIs
Timeline · 15 updates
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 12:13 PM UTC
- Resolved
- May 08, 2026, 05:44 PM UTC
- Duration
- 5h 30m
Affected: Connectivity
Timeline · 2 updates
-
identified May 08, 2026, 12:13 PM UTC
Users who are undergoing scheduled Grid Migrations are experiencing extended downtime. Downtime is expected during a Grid Migration however it's taking longer than usual. During the downtime users are unable to access Slack until the migration completes. We've identified an issue with Job Queues, which may be the cause and are investigating this further. The next update will be provided once additional information becomes available.
-
resolved May 08, 2026, 05:44 PM UTC
This issue is now resolved. Current status and actions being taken: We identified database write throttling as the cause of the stalled grid migrations. We applied a drop rule for jobs that were stuck in a retry loop, which has restored normal migration processing. Scope: A small number of enterprise users undergoing grid migrations experienced extended delays in accessing Slack. Current impact to end users: Affected users may have experienced an inability to access Slack during their migration window. Known workarounds: No workarounds needed at this time.We apologize for how this incident affected you and your business.
Read the full incident report →
- Detected by Pingoru
- May 04, 2026, 10:00 AM UTC
- Resolved
- May 04, 2026, 05:37 PM UTC
- Duration
- 7h 37m
Affected: Workflows
Timeline · 4 updates
-
investigating May 04, 2026, 10:00 AM UTC
Some users are experiencing issues with workflows. Triggered workflows may fail to complete, with the first step not executing. We'll provide another update as soon as possible.
-
identified May 04, 2026, 11:43 AM UTC
The investigation identified elevated latency in EU backend services as the cause of workflows not completing. A subset of workflow trigger attempts is impacted, primarily, EU users. Pod restarts have stopped, and error rates are improving. A fix is being prepared and will be deployed shortly. We'll provide another update as soon as possible.
-
monitoring May 04, 2026, 01:08 PM UTC
A fix has been deployed to address the elevated latency in EU backend services. The team is monitoring the environment to ensure service stability and full recovery. We'll provide another update as soon as possible.
-
resolved May 04, 2026, 05:37 PM UTC
This issue is now resolved for all users. Current status and recent actions taken: A fix has been deployed that resolved the underlying cause of this issue. Our health metrics have returned to normal levels and workflows are running as expected.Scope: Users in the EU region — primarily teams based in Central Europe — experienced elevated workflow failure rates.Previous impact to end users: Users may have experienced workflows failing to run, with the first step remaining stuck in an initialized state. Some users in the EU region may also have experienced general slowness when using Slack.Required resolution steps: No steps are required. Workflows should be running normally. If you continue to experience any trouble, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux).We apologize for any disruptions this may have caused to your day.
Read the full incident report →
- Detected by Pingoru
- May 01, 2026, 01:50 AM UTC
- Resolved
- May 01, 2026, 01:50 AM UTC
- Duration
- —
Affected: Search
Timeline · 1 update
-
resolved May 01, 2026, 01:50 AM UTC
At 23:20 UTC, April 30, 2026, a feature disruption began affecting the Slack Search feature for a subset of customers in Japan region. As a result, users were unable to use Search functionality within Slack. We identified that infrastructure changes to our Search cluster caused a number of internal search nodes to become unavailable, which prevented Search queries from routing correctly. We implemented a series of remediation steps, including increasing cluster capacity and restoring affected search shards. We also blocked certain Search traffic to contain secondary impact while the cluster was being recovered. As of 00:45 UTC, May 1, 2026, Slack Search functionality is fully operational. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
Read the full incident report →