Slack Outage History

Our work on this issue is still ongoing. Current status and actions being taken: We've identified the cause of the issue affecting the Slackbot button in the top navigation bar and have taken steps to address it. The issue is no longer present for affected users. Users who are currently experiencing the issue may need to reload Slack for the fix to take effect. We're continuing to monitor and will provide an update once service has been fully restored.We'll provide another update in 30 minutes until the impact is resolved for all users.

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.

We continue to investigate the issue. Current status and actions being taken: We have identified high resource utilization as a potential trigger. We continue to investigate and determine the best path to resolution.Estimated time to resolution: We don't have the exact resolution time at the moment and will update you once we have additional information.Scope: This is only impacting a small subset of users.Current impact to end users: Some users may experience issues while sending messages and loading message history in Slack.Known workarounds: Users can mitigate the issue by retrying the message sending or loading of message history.We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

Our work on this issue is still ongoing. Current status and actions being taken: We are reviewing additional logs and diagnostic information to determine the best path to resolution.We'll provide another update in 60 minutes until the impact is resolved for all users.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Our work on this issue is still ongoing. Current status and actions being taken: users may be experiencing mTLS errors. We are working to identify the probable cause and alleviate the problem.We'll provide another update in 30 minutes until impact is resolved for all users.

Our work on this issue is still ongoing. Current status and actions being taken: The team is reverting a TLS certificate rotation deployed this morning to restore event and slash command functionality for legacy Salesforce 1.0 apps.We'll provide another update in 30 minutes until impact is resolved for all users.

Our work on this issue is still ongoing. Current status and actions being taken: We are currently reverting a TLS certificate rotation that caused authentication failures and are re-enabling events for affected legacy Salesforce apps to restore full functionality.We'll provide another update in 30 minutes until impact is resolved for all users.

Our work on this issue is still ongoing. Current status and actions being taken: Service restoration is underway with 50% of availability zones recovered; we have successfully reverted the TLS certificate and are manually restarting services to restore event and slash command functionality for all legacy Salesforce 1.0 apps.We'll provide another update in 30 minutes until impact is resolved for all users.

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.

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.

Our work on this issue is still ongoing. Current status and actions being taken: We have identified the source of the ongoing issue related to activity feed and message functionality and are actively working on a fix. We'll provide another update as soon as it becomes available until the impact is resolved for all users.

This issue is now resolved for all users. Current status and recent actions taken: The issue affecting the activity feed and message functionality 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: During the impact, some users experienced issues with the activity feed and messaging, including degraded performance and errors.We apologize for any disruptions to your day.

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.

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.

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.