Slack is down as outage hits for some users
Your support helps us to tell the story
From reproductive rights to climate change to Big Tech, The Independent is on the ground when the story is developing. Whether it's investigating the financials of Elon Musk's pro-Trump PAC or producing our latest documentary, 'The A Word', which shines a light on the American women fighting for reproductive rights, we know how important it is to parse out the facts from the messaging.
At such a critical moment in US history, we need reporters on the ground. Your donation allows us to keep sending journalists to speak to both sides of the story.
The Independent is trusted by Americans across the entire political spectrum. And unlike many other quality news outlets, we choose not to lock Americans out of our reporting and analysis with paywalls. We believe quality journalism should be available to everyone, paid for by those who can afford it.
Your support makes all the difference.Slack has stopped working for some users, leaving them unable to get into their virtual workplaces.
Users reported they were unable to load the app, and that messages were not being sent or received.
The partial outage happened just as the working day began in the US, and in the middle of the afternoon European time.
On its website, Slack said it was aware of the issue and looking to find the cause.
“We’re investigating the issue where Slack is not loading for some users,” it wrote. “We’re looking into the cause and will provide more information as soon as it’s available.”
Not everyone seemed to be affected by the problems, however, with some able to message as normal.
The outage came just 12 hours after another major outage on the service, which lasted for around an hour. During those problems, Slack users were hit by the same errors.
The company said in an update on its status page that those problems were caused by a “code change” that “inadvertently caused a conflict in the desktop app and web client, preventing a small number of customers from sending messages”. It changed that code back and should have restored service, it said then.
Join our commenting forum
Join thought-provoking conversations, follow other Independent readers and see their replies
Comments