Wednesday December 10, 2025

Resolved

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:45 AM PST

Resolved

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:43 AM PST

Update

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:37 AM PST

Investigating

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

11:23 AM PST

Resolved

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 NA180
• Previous impact to end users: Users unable to login from login.salesforce.com
• Required resolution steps: none

We apologize for any disruptions to your day.

11:45 AM PST

Update

(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 NA180
• Current impact to end users: Customers experience issues when logging in through login.salesforce.com
• Known 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:35 AM PST

Investigating

(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:25 AM PST

Resolved

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.

11:48 AM PST

Update

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:41 AM PST

Investigating

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:28 AM PST

Resolved

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.

11:47 AM PST

Update

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:39 AM PST

Investigating

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

11:29 AM PST