We've resolved an issue that could cause incorrect email address tokens to appear when users pasted multiple email addresses into the member invite flow. In some cases, pasted email addresses were incorrectly matched to existing members with similar email addresses, requiring users to manually correct the entries before proceeding.We identified the cause of the issue and deployed a fix to ensure email addresses are now matched correctly when pasted into the invite flow. The issue is resolved for all affected users.If you're still experiencing any trouble, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). We apologize for the disruption and appreciate your patience.

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.

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.

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.

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 windowWe apologize for any inconvenience this may have caused.

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.

This issue is now resolved for all users.Current status and recent actions taken: We deployed a series of configuration adjustments and infrastructure fixes to restore services. Messaging, Workflows, Apps, and Connections were progressively restored over the last several hours. Some users continued to experience permissions-related issues, including inability to manage channels and Canvas edits not saving, as a result of residual stale cache data. Cache deployment activities completed at 14:13 UTC on May 28, 2026, fully resolving the issue. Scope: This issue affected Slack users globally.Previous impact to end users: Slack users experienced difficulties accessing Slack features, including Messaging, Workflows, Apps, Integrations, APIs, Canvas, and Connections, beginning at 22:21 UTC on May 27, 2026. Following an infrastructure change, a cascading scheduling failure caused widespread service impact across all regions and clients. Slack services largely returned to normal operational levels at 05:45 UTC on May 27, with residual impact that remained during the deployment. A brief issue with Canvas surfaced at 10:00 UTC on May 28‌ that lasted until approximately 12:30 UTC.  Required resolution steps: No steps required.We apologize for any disruptions to your day. We'll undertake a full investigation of the incident, establishing the technical trigger, the mechanism of failure, and preventative measures to avoid further disruptions. 

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. 

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.

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.

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.

Users who rely on Enterprise Key Management (EKM) may have experienced elevated latency and errors across messaging, channel loading, workflows, and file operations starting around 5:55 AM PDT on May 11, 2026. Impact was mitigated and the incident was brought under control at 9:16 AM PDT on May 11, 2026.We've deployed fixes addressing the root cause of the elevated encryption key request load. If you continue to experience trouble, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). We apologize for the disruption and thank you for your patience.

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. 

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.

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

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.

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.

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.

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.

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.