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 |
|---|---|
| New York City, NY | 1 |
| Brest, Brittany | 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:
-
Livleen Gill (@nutritogo) reported@SlackHQ - having a very difficult time with your product as a new customer. No help
-
Caro (@CarolinaLaLopez) reportedThe @SlackHQ glitch in notification numbers is killing my vibe this morning
-
Arun Sharma (@Oxymarun_) reported@SlackHQ came out of a failing 10-person game studio the team needed a way to coordinate that wasn't email they built it for themselves then realized every distributed team on earth had the same problem
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported6:30a Getting eMail down to zero. Planning out the work, so I can work out the plan. Loading support and production into @SlackHQ.
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported8a Loading the team in @SlackHQ, getting eMail down to zero and getting Daniel up for school.
-
Razi Ansari (@RaziAns14640044) reported@SlackHQ should fix the UX of their video player. It's one of the worst pieces of UX I've ever interacted with. It feels like I suddenly landed on some government app. Too messy
-
Max.Y (@maximilianyuen) reported@RealFeatBit @SlackHQ same. and just yesterday they push new AI....wonder is it relevant. no email notification, all connections and their official server status are normal. can open new workspace no problem.
-
Ariel Sterman (@ArielSterman) reportedIs @SlackHQ down? heard it here first.
-
Jimidate (@Jimidvte) reported@SlackHQ, I’m having issues with my mobile notifications. I’ve checked every setting on my phone, uninstalled and reinstalled the app, yet I still don’t receive any push notifications. I’m missing time-sensitive information because I have to open the app before I see any updates.
-
y - alex ⚔️ (@onelonesabre) reported@SlackHQ @question_base can't use these features when your app is down my friend
-
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.
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported8:30a Back at my desk, loading the team up in @SlackHQ with today's assignment, getting eMail down to zero.
-
Domino Mysłowski (@Domino_mys) reportedThere was Pay by Eye, by Ring, by Watch… time to Pay by Juice? 🧃💳 Okay, this one was just a joke created by Callum (FrostyTrollz). But 10 years ago, paying with your watch or ring also sounded ridiculous. A great example of how today’s joke can become tomorrow’s product is.. @SlackHQ The team behind Slack was actually building an online game called Glitch. As the founders later mentioned: “The game was absolutely preposterous.” Eventually, the game failed and was shut down. However, the internal chat tool they built to communicate became more valuable than the game itself. That tool became Slack, now used by millions of teams. 🌱 Follow for more wild growth-hacks
-
Jori Lallo (@jorilallo) reported@pizzaboy @karrisaarinen @SlackHQ It's still the same agent with capability to access everything as the caller user can. If you're calling it in the channel, it has that as context so it will file issue into the project by default and answer questions about the project without you needing to name it separately. If there's situatons where it's not working as intended, would love to get screenshots
-
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