https://slack-status.com History of Slack System Status Sun, 19 Oct 2025 14:58:14 -0700 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. Sun, 19 Oct 2025 14:58:14 -0700 https://slack-status.com/2025-10/6a8833fd34080380 https://slack-status.com/2025-10/6a8833fd34080380 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. Sun, 19 Oct 2025 15:06:23 -0700 https://slack-status.com/2025-10/85ebfbc618801e1e https://slack-status.com/2025-10/85ebfbc618801e1e 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. Wed, 19 Nov 2025 07:40:16 -0800 https://slack-status.com/2025-10/51d84290cf5c8e22 https://slack-status.com/2025-10/51d84290cf5c8e22 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. Thu, 23 Oct 2025 15:25:15 -0700 https://slack-status.com/2025-10/2377b835cefc31d5 https://slack-status.com/2025-10/2377b835cefc31d5 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. Thu, 23 Oct 2025 15:51:56 -0700 https://slack-status.com/2025-10/18348954a72f8f34 https://slack-status.com/2025-10/18348954a72f8f34 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. Thu, 23 Oct 2025 15:40:14 -0700 https://slack-status.com/2025-10/65f3383a2d6aebdf https://slack-status.com/2025-10/65f3383a2d6aebdf 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 Thu, 23 Oct 2025 09:29:20 -0700 https://slack-status.com/2025-10/5284833cf8e69243 https://slack-status.com/2025-10/5284833cf8e69243 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. Fri, 31 Oct 2025 17:16:05 -0700 https://slack-status.com/2025-10/a0393e05c080e8c1 https://slack-status.com/2025-10/a0393e05c080e8c1 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. Fri, 07 Nov 2025 09:13:26 -0800 https://slack-status.com/2025-11/d447af6bb8944796 https://slack-status.com/2025-11/d447af6bb8944796 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. Fri, 07 Nov 2025 10:12:40 -0800 https://slack-status.com/2025-11/f473e109f89d88ab https://slack-status.com/2025-11/f473e109f89d88ab 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. Fri, 07 Nov 2025 10:26:32 -0800 https://slack-status.com/2025-11/9e670adc1f1027b8 https://slack-status.com/2025-11/9e670adc1f1027b8 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. Fri, 07 Nov 2025 09:01:33 -0800 https://slack-status.com/2025-11/f27026c1c262acc4 https://slack-status.com/2025-11/f27026c1c262acc4 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. Wed, 19 Nov 2025 07:43:58 -0800 https://slack-status.com/2025-11/d1dd150bcd58a808 https://slack-status.com/2025-11/d1dd150bcd58a808 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. Wed, 19 Nov 2025 07:43:38 -0800 https://slack-status.com/2025-11/66f5fbbfdb8d6f73 https://slack-status.com/2025-11/66f5fbbfdb8d6f73 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. Mon, 10 Nov 2025 15:05:37 -0800 https://slack-status.com/2025-11/08571a258bf8774b https://slack-status.com/2025-11/08571a258bf8774b 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. Wed, 19 Nov 2025 07:44:15 -0800 https://slack-status.com/2025-11/462b08851ea9be3d https://slack-status.com/2025-11/462b08851ea9be3d 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. Mon, 17 Nov 2025 10:57:01 -0800 https://slack-status.com/2025-11/ff446cdfe6fde894 https://slack-status.com/2025-11/ff446cdfe6fde894 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.  Mon, 01 Dec 2025 08:59:47 -0800 https://slack-status.com/2025-11/264957c149bb7b4a https://slack-status.com/2025-11/264957c149bb7b4a 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. Mon, 01 Dec 2025 09:19:37 -0800 https://slack-status.com/2025-11/a1461b28cd54a022 https://slack-status.com/2025-11/a1461b28cd54a022 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. Tue, 09 Dec 2025 09:29:13 -0800 https://slack-status.com/2025-12/0412d30ec3682411 https://slack-status.com/2025-12/0412d30ec3682411 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. Thu, 04 Dec 2025 16:02:04 -0800 https://slack-status.com/2025-12/440eee6e7d7eaa7b https://slack-status.com/2025-12/440eee6e7d7eaa7b 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. Tue, 09 Dec 2025 09:59:01 -0800 https://slack-status.com/2025-12/8bf9e5de10a5d33e https://slack-status.com/2025-12/8bf9e5de10a5d33e 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. Thu, 18 Dec 2025 08:44:51 -0800 https://slack-status.com/2025-12/a8c230d2dfa1ac93 https://slack-status.com/2025-12/a8c230d2dfa1ac93 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. Thu, 18 Dec 2025 08:57:07 -0800 https://slack-status.com/2025-12/a11b08a468a46d3a https://slack-status.com/2025-12/a11b08a468a46d3a 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. Mon, 29 Dec 2025 09:49:52 -0800 https://slack-status.com/2025-12/5d80d3ab17dbca35 https://slack-status.com/2025-12/5d80d3ab17dbca35 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. Wed, 14 Jan 2026 08:10:31 -0800 https://slack-status.com/2026-01/674d66b41c37f510 https://slack-status.com/2026-01/674d66b41c37f510 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. Thu, 29 Jan 2026 08:55:15 -0800 https://slack-status.com/2026-01/81190c41019f3f5e https://slack-status.com/2026-01/81190c41019f3f5e 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 Thu, 15 Jan 2026 11:58:27 -0800 https://slack-status.com/2026-01/ab0deb4e533e3abd https://slack-status.com/2026-01/ab0deb4e533e3abd 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. Thu, 22 Jan 2026 16:13:14 -0800 https://slack-status.com/2026-01/a7a00fec0a3c7e0e https://slack-status.com/2026-01/a7a00fec0a3c7e0e 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. Wed, 28 Jan 2026 10:30:17 -0800 https://slack-status.com/2026-01/6ca50d8bbf466222 https://slack-status.com/2026-01/6ca50d8bbf466222 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. Thu, 29 Jan 2026 09:16:29 -0800 https://slack-status.com/2026-01/549b252c892d0766 https://slack-status.com/2026-01/549b252c892d0766 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. Mon, 02 Feb 2026 09:53:54 -0800 https://slack-status.com/2026-01/6f029c99f2b77bcd https://slack-status.com/2026-01/6f029c99f2b77bcd 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. Fri, 30 Jan 2026 16:58:52 -0800 https://slack-status.com/2026-01/0977b367773e201e https://slack-status.com/2026-01/0977b367773e201e 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. Sat, 31 Jan 2026 18:18:46 -0800 https://slack-status.com/2026-01/827314caf3d6ec25 https://slack-status.com/2026-01/827314caf3d6ec25 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. Mon, 02 Feb 2026 10:23:20 -0800 https://slack-status.com/2026-02/2816c820f3322a13 https://slack-status.com/2026-02/2816c820f3322a13 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. Tue, 03 Feb 2026 09:34:34 -0800 https://slack-status.com/2026-02/52faec0e7f2084ed https://slack-status.com/2026-02/52faec0e7f2084ed 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. Thu, 05 Feb 2026 08:59:54 -0800 https://slack-status.com/2026-02/247421fca4040db4 https://slack-status.com/2026-02/247421fca4040db4 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. Fri, 06 Feb 2026 12:10:01 -0800 https://slack-status.com/2026-02/7bb73bc44ec676f8 https://slack-status.com/2026-02/7bb73bc44ec676f8 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. Tue, 10 Feb 2026 19:22:09 -0800 https://slack-status.com/2026-02/0cb7519d121f7be7 https://slack-status.com/2026-02/0cb7519d121f7be7 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. Thu, 12 Feb 2026 15:46:07 -0800 https://slack-status.com/2026-02/3eb09dfaf67113fc https://slack-status.com/2026-02/3eb09dfaf67113fc 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. Thu, 19 Feb 2026 16:24:56 -0800 https://slack-status.com/2026-02/5fd12c7c0229f7fb https://slack-status.com/2026-02/5fd12c7c0229f7fb 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. Wed, 18 Feb 2026 10:32:00 -0800 https://slack-status.com/2026-02/1e508dc831fd934e https://slack-status.com/2026-02/1e508dc831fd934e 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. Tue, 24 Feb 2026 11:19:19 -0800 https://slack-status.com/2026-02/0736abde1ec2eea0 https://slack-status.com/2026-02/0736abde1ec2eea0 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.  Tue, 24 Feb 2026 20:52:24 -0800 https://slack-status.com/2026-02/fb905e8a457042ba https://slack-status.com/2026-02/fb905e8a457042ba 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. Sun, 01 Mar 2026 12:49:25 -0800 https://slack-status.com/2026-03/a498942c1b812963 https://slack-status.com/2026-03/a498942c1b812963 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.  Wed, 04 Mar 2026 10:41:51 -0800 https://slack-status.com/2026-03/5d92c691d977da03 https://slack-status.com/2026-03/5d92c691d977da03 This issue is now resolved for all users.Current status and recent actions taken: The issue is now resolved, and users should no longer be experiencing any trouble with when using app mentions, migrations, and push notifications. Enterprise Migrations should also be completing as expected.Scope: This issue wasn't affecting any specific region, but a percentage of users may have been affected globally.Previous impact to end users: Developers may have experienced issues in receiving responses when @mentioning an app to execute an action in a Slack channel, org admins may have observed delays with upcoming/planned migrations, and mobile push notifications may have failed to deliver.Required resolution steps: No steps required.We apologize for any disruptions to your day. Fri, 06 Mar 2026 08:44:54 -0800 https://slack-status.com/2026-03/e63ca9cc0d76539c https://slack-status.com/2026-03/e63ca9cc0d76539c This issue is now resolved for all users.Current status and recent actions taken:  We identified the cause as a login routing component that had incorrect entries, which prevented users from being directed to their workspace correctly. A fix has been deployed to address this issue. Previous impact to end users:  Users attempting to log in via SSO may have encountered errors requiring them to refresh their browser multiple times before successfully accessing their workspace. Some users may have experienced a degraded login experience even after gaining access.We apologize for any disruptions to your day. Mon, 09 Mar 2026 12:17:50 -0700 https://slack-status.com/2026-03/0c433efa2ea295fb https://slack-status.com/2026-03/0c433efa2ea295fb We have resolved the issue that was causing users to experience authorization failures when connecting certain third-party integrations to Slack.We apologize for any inconvenience this may have caused and thank you for your patience. Sun, 22 Mar 2026 20:46:08 -0700 https://slack-status.com/2026-03/009e069324bea32e https://slack-status.com/2026-03/009e069324bea32e Intermittent errors when sending messages have been resolved. Additionally, some customers may see inaccurate notification badge counts which can be resolved with a hard reload to clear temporary local cache. Apologies for the trouble today and thank you for your patience. Thu, 26 Mar 2026 09:36:40 -0700 https://slack-status.com/2026-03/8269f159feb011e3 https://slack-status.com/2026-03/8269f159feb011e3 This issue is now resolved for all users.Current status and recent actions taken: We identified a paused job that may have been contributing to the high utilization. This was unpaused, which restored resource availability.Scope: This only affected a small subset of users.Previous impact to end users: Some users may have experienced issues while sending messages and loading message history in Slack between 20:14 PDT and 22:14 PDT.We apologize for any disruptions to your day. Fri, 27 Mar 2026 22:39:55 -0700 https://slack-status.com/2026-03/5e14cc3c13b8ae14 https://slack-status.com/2026-03/5e14cc3c13b8ae14 Following a period of monitoring, our engineering team called this incident resolved as of 01:10 UTC, March 30. We apologize for any inconvenience this issue has caused to users.  Sun, 29 Mar 2026 18:17:35 -0700 https://slack-status.com/2026-03/6da2f3fe8e16319d https://slack-status.com/2026-03/6da2f3fe8e16319d This issue is now resolved for all users.Current status and recent actions taken:  We've completed deploying the fix to address the issue affecting the Slackbot button in the top navigation bar. The Slackbot button is now working as expected. Scope: The issue was introduced for any users on build 121247.Previous impact to end users: The Slackbot button in the top navigation bar may not have been visible to users.Required resolution steps: Users who are still experiencing the issue may need to reload Slack for their experience to return to normal.We apologize for any disruptions to your day. Wed, 01 Apr 2026 07:41:31 -0700 https://slack-status.com/2026-04/3e4a3dd1224c4b7d https://slack-status.com/2026-04/3e4a3dd1224c4b7d