【Lena Paul - The Next Morning】

UPDATE: Sept. 7,Lena Paul - The Next Morning 2018, 2:54 p.m. ET Slack has returned for all. From the company: "Everyone should be able to connect to their workspace again now. We're very sorry for the disruption to your day, and appreciate your patience while we got things fixed up on our end."

We hope you enjoyed the freedom while you had it. Now back to work!

UPDATE: Sept. 7, 2018, 2:35 p.m. ET Slack is back for some users after being down for about 25 minutes. It's still not working for many though, so if you're one of the lucky ones experiencing some Slack silence, take advantage. Slack's latest statement:

"We have confirmed widespread connectivity issues for all workspaces. Things should be on the rise again, but we'll let you know when everything is back to normal."

Original story:

Surprise! Slack is down again, and office workers are discovering new, innovative ways to communicate. Like with their mouths.

Slack users began getting the "Slack couldn't send this message" notification around 2:14 p.m. ET on Friday.

Employees are seemingly falling back to old methods of communication -- in some desperate scenarios, using the dreaded Google Hangouts application.

Slack has been replying to some users on Twitter, but posted the outage to the Slack System Page as of 2:26 p.m. ET.

The popular message app stated, "We're investigating problems with connectivity at this time. We're sorry for the interruption and will keep you posted as soon as we have an update."

A third-party website that lets people report outages called outage.report began showing the issue with over 100 alerts in the past 20 minutes before Slack updated their own page. Reports have climbed since then.

And as you might expect, given the flurry of tweets last time Slack stopped working, users are heading to Twitter to talk about their newfound freedom.

This Tweet is currently unavailable. It might be loading or has been removed.

This Tweet is currently unavailable. It might be loading or has been removed.

This Tweet is currently unavailable. It might be loading or has been removed.