On July 26 from 05:00 a.m. PDT, some users began to experience connectivity issues. This was determined to have been caused in part by a code change published the night before. While reverting this change and attempting to recover from its downstream effects, users began to experience failures while sending messages as an unintended side effect. As a result, we rolled back this attempted fix and began applying it again, this time more slowly, bringing full recovery to impacted users by 10:25 a.m. PDT.
2:27 PM PST
Things should be back to normal and users should no longer see issues connecting. If you're still having troubles, let us know at email@example.com.
10:25 AM PST
We're seeing signs of recovery and users should see improvements. We'll let you know when things are fully back to normal.
10:07 AM PST
We don't have any further updates right now, but thank you for your patience while we continue towards a solution.
9:37 AM PST
We’re still working to fix the varying issues that have been impacting some workspaces. We hope to have the issue fully resolved as soon as possible.
9:07 AM PST
We're getting close to a solution, but we aren't in the clear just yet.
8:37 AM PST
Users may see varying symptoms including missing channels and troubles loading messages. Thanks for sticking with us through this.
8:07 AM PST
We're still investigating an issue with connections and we don't have any news to share just yet.
7:37 AM PST
Some folks may see issues connecting to Slack and symptoms may vary for users. We’re currently investigating and will have more information shortly. Thank you for your patience.
7:07 AM PST