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.

Incident: Slack login, workspaces loading failures, and general Slack functionality issues

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.

Incident: Trouble with Search

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

Incident: Slack Canvas Outage

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.

Incident: Slow or incomplete Slack searches

From 7:12 AM to 4:50 PM PST on December 8, 2025, some users encountered a "Something's fishy!" error when loading&nbsp; 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.

Incident: Issues loading or viewing threads

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.

Incident: Trouble running workflows

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.

Incident: Issue loading threads in Slack

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.

Incident: Trouble with Slack - General Slack functionality issues

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.

Incident: Trouble with adding payment methods

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

Incident: Trouble loading Slack, messages, or canvas

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.

Incident: Trouble loading Slack and performing actions

Email delivery has returned to normal and all services are operating as expected. Thank you for your patience while we worked through this issue.&nbsp;We apologize for how this issue may have affected you and your business.

Notice: Upstream provider issue causing email delivery delays

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.

Incident: Issue loading activity feed in Slack

This issue is now resolved.&nbsp;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.

Incident: Trouble connecting to Salesforce Channels

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.

Incident: Events errors related to Salesforce Automation application

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.

Incident: Users on Free, Trial, or Pro plans may see the workspaces appearing blurred out

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.&nbsp;We apologize for any disruptions to your day.

Incident: Users unable to create or edit workflows

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.

Incident: Windows desktop notification issues

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.

Incident: App History and Chat Tab Not Loading

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.

Incident: Issue with scheduled workflows

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.

Incident: Unable to Install Apps to Workspaces

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.

Incident: Trouble Accessing Slack

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.

Incident: Users unable to access Slack using various browsers

This issue is now resolved for all users.Current status and recent actions taken: We reverted the change that triggered the issue.&nbsp;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.&nbsp;We apologize for any disruptions to your day.

Incident: Issues generating Incoming Webhooks

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.

Is Slack down?

Slack status is UP

Lastest published events

Incident: Scheduled Grid Migrations are experiencing extended downtime

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

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

Slack Services, Components and Regions

Recent Slack events

Incident: Slack login, workspaces loading failures, and general Slack functionality issues

Incident: Trouble with Search

Incident: Slack Canvas Outage

Incident: Slow or incomplete Slack searches

Incident: Issues loading or viewing threads

Incident: Trouble running workflows

Get your FREE account now,
5 monitors included!

Is Slack down?

Slack status is UP

Lastest published events

Incident: Scheduled Grid Migrations are experiencing extended downtime

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

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

Slack Services, Components and Regions

Recent Slack events

Incident: Slack login, workspaces loading failures, and general Slack functionality issues

Incident: Trouble with Search

Incident: Slack Canvas Outage

Incident: Slow or incomplete Slack searches

Incident: Issues loading or viewing threads

Incident: Trouble running workflows

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!