Slack System Status

Incident: Issues with login

2025-11-08T14:20:44-08:00

2:20pm PST We're investigating an issue where some users are seeing a blank page when attempting to log in to Slack. If you encounter a blank page, please revisit Salesforce enterprise orgs. The login page for all your workspaces should then appear.We apologize for the inconvenience and will continue sharing updates as they become available.

2:55pm PST Mitigation efforts are underway.Current status and actions being taken: We identified the cause of the issue and have initiated remediation efforts, which appear to be successful. We continue to monitor our progress as our work unfolds.We apologize for the inconvenience and will continue sharing updates as they become available.

3:17pm PST This issue is now resolved. Users should be able to log in to Slack without encountering a blank page. We apologize for the disruption this may have caused to your day.

Outage: Testing Templates

2025-11-14T00:09:06-08:00

12:09am PST We're investigating a new incident.Current impact to end users: This is Just testing. Please ignore it.We'll provide an update within 30 minutes including further details on scope and actions being taken to resolve the issue.

12:09am PST This issue is now resolved for all users.Current status and recent actions taken: <What actions we've taken leading to the resolution, any ongoing actions that may be relevant to customers, any elaboration or clarification on the "resolved" status if needed>Scope: <Roughly what percentage of users were impacted; which categories of users, regions, devices, etc. were impacted>Previous impact to end users: <Describe the symptoms impacted users may have experienced, which functionality or features were affected, relevant error messages, etc.>Required resolution steps: <Any steps users should take for the issue to be resolved on their end>We apologize for any disruptions to your day.

Incident: Trouble with search

2025-11-19T05:15:48-08:00

5:15am PST We’re investigating an issue impacting search. We’re on the case and will provide another update once we have more details to share. Thank you for your patience in the meantime.

5:17am PST <Summarize any notable changes from the previous update OR if there aren't changes from the previous update, specifically state that here.>Current status and actions being taken: <What actions we're currently taking in our investigation or remediation efforts; are we trying to identify the cause, have identified the cause, preparing to ship a fix, etc.>Estimated time to resolution: <Rough timeframe in which impact might be resolved, if we have an estimate.>Scope: <Roughly what percentage of users are impacted; which categories of users, regions, devices, etc. are impacted; absolute number of errors and/or impacted users can be included ONLY IF sending email to ONE customer>Current impact to end users: <Describe the symptoms impacted users may experience, which functionality or features are affected, relevant error messages, etc.>Known workarounds: <Any steps users could take to continue using Slack or impacted features before the issue is fully resolved>We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

5:21am PST This issue is now resolved for all users.Current status and recent actions taken: Restarted the server.We apologize for any disruptions to your day.

Incident: Trouble with Search

2025-12-02T12:34:33-08:00

12:34pm PST We're investigating a new incident.Current impact to end users: We are currently investigating reports of search functionality issues in Slack. Users may experience increased latency or errors when attempting to search.We'll provide an update within 30 minutes including further details on current actions being taken.

1:00pm PST US region customers are currently experiencing search functionality issues due to Solr out-of-memory errors following a search index update. The incident affects search performance, with customers seeing either complete search failures or elevated latency with partial results.Teams are actively engaged and attempting to swap back to the previous stable index without force loading.We'll provide an update within 30 minutes, including further details on current actions being taken.Issue: The Engineering team became aware of a feature degradation impacting Search functionality. The issue was triggered following a scheduled update to the search index, which resulted in resource exhaustion and instability across the search cluster. Our team has provisioned maximum additional infrastructure capacity to stabilize the environment and is actively working to revert the system to the previous stable search index.Impact: During this time, the majority of customers in the US region may experience significant degradation. Symptoms include search queries "hanging" (timeouts), high latency, or search returning incomplete/partial results. Next Update: Check the status page for updates. An update will be posted to the incident thread in 30 minutes, or sooner if additional information becomes available.

Incident: Issues with login

2025-12-10T11:23:17-08:00

11:23am PST Some users may be unable to log into Slack. We apologize for the inconvenience and will continue sharing updates as they become available.

11:37am PST Stuff is broken, we're sorry.Current status and actions being taken: We're working on it, I promise. Estimated time to resolution: Yes. Some time.Scope: I'm going to sayyyyyyyyy 50% of people are probably borked. Every region, all devices, you're probably having a hard time. Current impact to end users: Users try to press log in and you get an infinite spinner. Known workarounds: Nothing known right now, please still keep buying Slack in the meantime kthx.We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

11:43am PST This issue is now resolved for all users.Current status and recent actions taken: <What actions we've taken leading to the resolution, any ongoing actions that may be relevant to customers, any elaboration or clarification on the "resolved" status if needed>Scope: <Roughly what percentage of users were impacted; which categories of users, regions, devices, etc. were impacted>Previous impact to end users: <Describe the symptoms impacted users may have experienced, which functionality or features were affected, relevant error messages, etc.>Required resolution steps: <Any steps users should take for the issue to be resolved on their end>We apologize for any disruptions to your day.

11:45am PST This issue is now resolved for all users.Current status and recent actions taken: <What actions we've taken leading to the resolution, any ongoing actions that may be relevant to customers, any elaboration or clarification on the "resolved" status if needed>Scope: <Roughly what percentage of users were impacted; which categories of users, regions, devices, etc. were impacted>Previous impact to end users: <Describe the symptoms impacted users may have experienced, which functionality or features were affected, relevant error messages, etc.>Required resolution steps: <Any steps users should take for the issue to be resolved on their end>We apologize for any disruptions to your day.

Incident: Issues with login

2025-12-10T11:25:24-08:00

11:25am PST (test) Some users may be unable to log into Slack. We apologize for the inconvenience and will continue sharing updates as they become available.

11:35am PST (template test)<Summarize any notable changes from the previous update OR if there aren't changes from the previous update, specifically state that here.>Current status and actions being taken: Customers continue to have issues when logging in from login.salesforce.com. The team continues to investigate.Estimated time to resolution: there is currently no ETA.Scope: All customers from NA180Current impact to end users: Customers experience issues when logging in through login.salesforce.comKnown workarounds: Log in to your mydomain or direct instance URL.We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

11:45am PST This issue is now resolved for all users.Current status and recent actions taken: Issue has been resolved. Temporary network outage.Scope: All users on NA180Previous impact to end users: Users unable to login from login.salesforce.comRequired resolution steps: noneWe apologize for any disruptions to your day.

Incident: Test Incident - TestTestTest

2025-12-10T11:28:48-08:00

11:28am PST We're investigating a new incident.Current impact to end users: Users across all regions may experience intermittent failures to load or create Slack Canvases.We'll provide an update within 30 minutes including further details on scope and actions being taken to resolve the issue.

11:41am PST We continue to investigate failures to load or create Slack Canvases.Current status and actions being taken: Our Slack engineering team is investigating failures within the primary database of our Canvus hosting shard.Estimated time to resolution: Not available at this time.Scope: 100% of users across all regions worldwide, intermittent failures that may succeed upon retry.Current impact to end users: Users across all regions may intermittently experience failures loading or creating Slack Canvases.Known workarounds: No known workarounds.We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

11:48am PST This issue is now resolved for all users.Current status and recent actions taken: The Slack Engineering team determined that the primary database became unavailable but failed to gracefully migrate traffic to the secondary partition. Our team performed a manual failover of traffic to the secondary partition.Scope: 100% of users across all regions, intermittent failures to load or create Slack Canvases.Previous impact to end users: During the impact period, users across all regions may have experienced intermittent failures to load or create Slack Canvases.Required resolution steps: You may need to restart your Slack client to restore functionality.We apologize for any disruptions to your day.

Incident: This is a new test incident

2025-12-10T11:29:11-08:00

11:29am PST The team is currently investigating an issue where users may experience difficulty leaving a huddle once it has been initiated.

11:39am PST The team has identified a possible cause and a fix in currently in work.Current status and actions being taken: A recent change has been identified as the possible cause of this incident and a rollback has been initiated.Estimated time to resolution: The rollback is estimated to take up to 20 minutes.Scope: Only users who have initiated huddles in the past 2 hours are currently affected.Current impact to end users: Users may not be able to leave an initiated huddle. Known workarounds: Log out of Slack and log back in to close the huddle.We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

11:47am PST This issue is now resolved for all users.Current status and recent actions taken: A recent change was rolled back to resolve this incident.Scope: Only users who had initiated huddles in the past 2 hours were affected.Previous impact to end users: Users may not be able to leave an initiated huddle. Required resolution steps: No additional resolution steps are required.We apologize for any disruptions to your day.

Incident: New EDIT - Increased HTTP 5xx errors resulting in trouble accessing Canvases

2026-02-17T13:45:29-08:00

1:45pm PST We are aware of an issue where users may observe increased HTTP 5xx errors in the form of different failure scenarios across Slack services. We are investigating the root cause and a well defined impacted experience with the highest priority, and apologize for any inconvenience this is causing for users. EDIT EDIT EDIT!

1:48pm PST Update #1

Incident: Test Incident 2

2026-02-17T13:49:27-08:00

1:49pm PST Test Details

Incident: TEST SLACK DM not working as expected

2026-02-24T08:30:44-08:00

8:30am PST We're investigating a new incident.Current impact to end users: Slack DM issuesWe'll provide an update within 30 minutes including further details on scope and actions being taken to resolve the issue.