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. &nbsp;Scope: Some users may have experienced issues accessing Direct Messages or Multi-person Direct Messages.Required resolution steps: No additional steps are required.&nbsp;We apologize for any inconvenience this brought to your day.

Incident: Issue with Slack Direct Messaging

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.&nbsp;

Incident: Slack Email Delivery Feature Degradation

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

Incident: Issue with Slack Search feature

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.&nbsp;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.&nbsp;

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

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.

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

This issue is now resolved for all users.Current status and recent actions taken:&nbsp; 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.&nbsp;Previous impact to end users:&nbsp; 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.

Incident: Intermittent SSO login errors accessing Slack workspace.

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.

Incident: Authorization Failure Errors Connecting to the Slack MCP Sever

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.

Incident: Trouble connecting to Slack

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:&nbsp;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.

Incident: Issues while sending messages and loading message history is impacting some users

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.&nbsp;

Incident: Issue with Sending and Receiving Messages

This issue is now resolved for all users.Current status and recent actions taken:&nbsp; 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.&nbsp;Scope:&nbsp;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.

Incident: Slackbot button in the top navigation is disappearing

Current status and recent actions taken:&nbsp; After monitoring system performance and infrastructure stability, we have confirmed that all Slack features are operating within expected levels. This incident is now resolved and users should no longer experience any issues with Slackbot, AI Features, or workflows.We apologize for any disruptions to your day.

Incident: Trouble with Slackbot and AI-powered features

This issue is now resolved for all users.Current status and recent actions taken: After monitoring system performance and infrastructure stability, we have confirmed that all Slack features are operating within expected levels. Users should no longer experience any issues when sending messages.&nbsp;Scope: This issue 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 trouble sending messages.Required resolution steps: No additional steps are required.We apologize for any disruptions to your day.

Incident: Trouble Sending Messages

This issue is now resolved for all users.Current status and recent actions taken:&nbsp; We've completed rolling back the change to address the issue impacting core Slack functionality, including launching Slack, sending messages, loading threads, and other related actions.&nbsp;Scope: All Slack enterprise customers.Previous impact to end users: Users experienced issues with channel-related operations, including delays or failures when loading channels or retrieving channel membership lists. &nbsp;We apologize for any disruptions to your day.

Incident: Users may experience delays due to increased load on bychan keyspace affecting system performance

ResolvedThis issue is now resolved for all users.Current status and recent actions taken: Custom statuses set to expire at a specific time are now clearing as expected. The issue self-resolved when the next scheduled expiration job successfully processed the affected users.&nbsp;Scope: Some external users globally were affected. Users on desktop were impacted; the issue was not reproducible internally or across test workspaces.Previous impact to end users: Some users may have experienced custom statuses that did not automatically clear at their scheduled expiration time.Required resolution steps: No steps required.We apologize for any disruptions to your day.

Incident: Custom status not expiring

Further investigation confirms that the issue impacting Thread loading has been self- resolved, and our team will continue to investigate to ensure that this doesn’t reoccur. We apologize for the trouble today and thank you for your patience.

Incident: Slack Threads Not Loading

We’ve successfully performed a rollback in the production environment, and all systems are now functioning as expected. Users should no longer experience any issues with thread replies not generating a notification banner.We apologize for any inconvenience and appreciate your patience.

Incident: Users May Not Receive Notifications on Slack Thread Replies

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.&nbsp;

Incident: Slack Search Feature Disruption - Japan region

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.

Incident: Slow behaviour in Slack

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.&nbsp;Scope: A small number of enterprise users undergoing grid migrations experienced extended delays in accessing Slack.&nbsp;Current impact to end users: Affected users may have experienced an inability to access Slack during their migration window.&nbsp;Known workarounds: No workarounds needed at this time.We apologize for how this incident affected you and your business.&nbsp;

Incident: Scheduled Grid Migrations are experiencing extended downtime

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.

Incident: EKM customers were previously experiencing issues with channel loading and message delivery

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.&nbsp;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.&nbsp; We sincerely apologize for the disruption to your day and appreciate your patience while we worked to sort this out.

Incident: Issues affecting file uploads, message edits, channel renames, and channel creations

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.&nbsp;We apologize for the inconvenience and any impact this may have had.

Incident: Huddle AI summaries not being generated

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.&nbsp;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:&nbsp;No additional steps are required.We apologize for any disruptions to your day.

Incident: Trouble uploading files and emojis in Slack

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.&nbsp;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. &nbsp;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.&nbsp;

Incident: Trouble with Slack - General Slack functionality issues

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.

Incident: Partial Degradation Impacting Usergroups

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.

Incident: Connectivity Issues Affecting Some Users in Europe

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.

Incident: Trouble connecting or loading Slack

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.

Incident: Administrators may experience errors in member management.

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.&nbsp;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.

Incident: Some users unable to sign in

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.

Incident: Trouble adding multiple users to channels

We've resolved the issue that prevented customers from using the Slack Gmail add-on. The fix has been successfully deployed; health metrics have stabilized, and the Gmail add-on is now fully operational for all affected users.We apologize for any inconvenience this may have caused.

Incident: Trouble with Gmail add-on Integration

We've validated that the fix resolved the issue and child windows are now displaying content as expected.&nbsp;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.

Incident: Child windows displaying content at half height

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.

Incident: Slack Messaging issue

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.&nbsp;We apologize for the inconvenience and thank you for your patience.

Incident: Trouble submitting workflow forms with file attachments on Android.

This issue is now resolved for all users.We apologize for any disruptions to your day.

Incident: Trouble performing some actions

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.

Incident: Trouble loading SSO configuration settings for some workspace admins

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. &nbsp;We apologize for how this incident may have affected you and your business.

Incident: Chat functionality unavailable on Slack Help page

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.&nbsp;

Incident: Receiving reminders in Slack issue

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.

Incident: Issue sending messages to channels via certain Workflows

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.

Incident: Feature Degradation Affecting the Receipt of Emails in Slack

We've completed the rollback of the recent change that was the trigger of the issue. The Search bar and Admin dashboard&nbsp; is restored for all users.We apologize for the inconvenience caused to you and your business.

Incident: Trouble Using Search Bar For Some Admins

We're continuing to work on restoring messages, message edits, and file shares for a limited number of workspaces that were affected by an issue with custom data retention settings. We've fixed what triggered the issue and are running data recovery using backup restoration methods. Custom retention settings have been restored for impacted channels, and we're gradually re-enabling retention jobs.We will provide another update as additional information becomes available.

Is Slack down?

Slack status is UNKNOWN

Lastest published events