Slack Outage Map
The map below depicts the most recent cities worldwide where Slack users have reported problems and outages. If you are having an issue with Slack, make sure to submit a report below
The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.
Slack users affected:
Slack is a cloud-based set of proprietary collaboration tools and services. It's meant for teams and workplaces, can be used across multiple devices and platforms.
Most Affected Locations
Outage reports and issues in the past 15 days originated from:
| Location | Reports |
|---|---|
| Brest, Brittany | 1 |
| Ródos, South Aegean | 1 |
| Belo Horizonte, MG | 1 |
| Jewar, UP | 1 |
| Colorado Springs, CO | 1 |
| South Point, Mont Fleuri | 1 |
Community Discussion
Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.
Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.
Slack Issues Reports
Latest outage, problems and issue reports in social media:
-
IT (@IncredibleTrade) reportedIs @SlackHQ mobile app down?
-
Caro (@CarolinaLaLopez) reportedThe @SlackHQ glitch in notification numbers is killing my vibe this morning
-
jbv 🌟 (@jbv) reportedliking the new slack activity view—still getting used to it. One thing: it doesn’t respect the “Just display names” setting. Is a fix coming? 👀 @SlackHQ
-
Cass Anderson (@casspa) reported@Yonar87 @SlackHQ same issue here. Just sent them an email. Their status landing page says they've been 100% find this quarter which makes me think maybe they just don't update that page?
-
Rob Swift (@RobSwish) reported@AgentAkki @SlackHQ Restarting doesn't help, and I mentioned this in the dms, it seems so weird to basically have 2 dm lists.
-
Vlad (@vladoustinov) reported@MerlinEgalite @SlackHQ The problem is they gave up on product a long time ago haha But yes embedding tools/workflows inside interfaces people are already used to use (slack/email/Notion etc) is the way to go
-
JIM EVANS (@JEVANSCPM) reported@SlackHQ @slack_community not sure what happened and on who’s side, but after your recent update I’m having major issues opening your program. (Mac OS)
-
Kevin (@kevin0connell) reported@SlackHQ I can also replicate this problem
-
dnd dhmu (@refreshmygrave) reported@advaithj1 @thdxr @SlackHQ bro pls fix ur support for discord no real people reply ever
-
Code Guru 🌞 (@hicodeguru) reportedhey @SlackHQ even after an year this issue still there i cant hear voice of joined person - he drops it and then rejoin - now it works and the new ui for start hudle - not good, extra clicks :( sometime i forgot to actually start
-
Paul Thornton (@Fusspawn) reported@SlackHQ @dorukkavcioglu I miss the old glitch game, had fun with some of your old founders in that :(
-
Mike Rochefort 🐧 (@omenosdev) reported@SlackHQ I've sent a message in via the feedback address, but for 4.50.136 either there's been an undisclosed change of GPG keys used in signing Linux packages or the wrong key was used accidentally. For environments with strict package verification this leads to install errors.
-
Cathryn (@cathrynlavery) reported@Shopify @klaviyo @SlackHQ The Non-Technical Technical Dictionary, Day 2: Frontend & Backend Every app has a front of house and a back of house. Same as a restaurant. The frontend is what you see and touch. Think of Amazon, or any website you use. → The menu bar, the buttons, the search box. Everything on screen is just a list of things you're allowed to ask for. That's the menu, the dining room, the host stand. But nothing on that menu is actually happening at your table. When you hit "Buy Now," it's like placing an order with a waiter. He walks it back, the kitchen cooks it, and he brings it out when it's ready. The backend = the kitchen. You'll find database, business logic, server. Anything heavy (pulling your order history, processing a payment, sending an email) happens back there. The frontend only handles what fits at the table: how the buttons look, what color the page is, the small animations etc. Think Michelin star. They're not torching your steak tableside. They need the walk-in, the grill, the prep station, the sous chef. Software is the same. The interesting work needs the full kitchen. When a service like Cloudflare or AWS goes down and takes half the internet with it, that's a backend problem. The ghost kitchen caught fire and every restaurant relying on it went dark. A frontend problem is the one you've seen a hundred times: a button that won't click, text piled on top of an image, a page that looks broken on your phone. Frontend is form, where backend is function.
-
Stache (@stacheFonzi) reportedIt's from 2011, but I still miss Glitch. It was a browser based MMO based on collecting and crafting. Crazily enough it was made by the company that went on to rebrand and make @SlackHQ. The messaging system in the game became the basis for Slack.
-
FCT (@fightcopytrolls) reportedFacepalm: @SlackHQ still uses crosswalks and motorcycles during login to annoy humans and entertain AI.