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 |
|---|---|
| Township of Evan, KS | 2 |
| Guayaquil, Guayas | 1 |
| New York City, NY | 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:
-
tulumpo (@tulumpo) reported$IOND still in pre-launch. second delay message, 10:31 and now 10:39. this is normal. "All NASDAQ systems are fully operational" is in the message. nothing is broken. direct listings open when price discovery settles, not on a clock. @coinbase, @SlackHQ and @Spotify all opened late too.
-
Bhuvanesh Sridharan (@_bhuvanesh_) reportedas much hate @MicrosoftTeams gets, at least the meeting chat and other chats are on the same platform. Absence of synergy between @SlackHQ chat and Google meet is such a pet peeve. Non issue in grand scheme but still bothering whenever people send links in gmeet.
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported6:30a Got eMail down to zero, and started the team with assignments in @SlackHQ.
-
Ari Dehkordi (@arashdehkordiHQ) reported@karrisaarinen @SlackHQ Did Linear do this before agents? I tried project-level Slack channels at my org and found it works for enterprise engagements nicely, but breaks down at feature/epic level projects for our SaaS. There's a granularity sweet spot, too fine and context switching costs spike. Too coarse and projects blur. Plus no project is actually isolated in small teams, so cross-project conversations forced more people onto each channel and productive engagement suffered. I get the AI context-confinement angle, but curious what other benefits you're seeing?
-
Peval 🇮🇹 🇪🇺 🇬🇧🏳️🌈 (@jabawack81) reported@gabsmashh Once nearly turned down a job interview because the invite came through @MicrosoftTeams. Spent the whole call trying to casually work out if they used @SlackHQ instead. They did.
-
Pavel Zagorodnikh (@pavzagor) reported@SlackHQ you should really fix your reactions search its such a pain to remember the names of emojis. Look at what folks at @raycast and @telegram do 👀
-
Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported@purionx @SlackHQ @salesforce tables in slack would genuinely help, wild that it took this long to even be a request
-
ImagineArt (@ImagineArt_X) reported@SlackHQ @SlackHQ cute, but can you fix the "copying emojis from slack to somewhere else please"
-
Assaf Kipnis (@Kipnis_a) reportedClaude is the best corporate CYA buddy I used to have full CYA files with records of messages, emails and things I did - I was terrible at keeping those and people took advantage of that. With Claude and @meetgranola - I have canonical record of all conversations, @SlackHQ messages, emails, canonical decisions - everything Oh, you say I didnt do something? I didnt respond? Here come the receipts
-
jimmy hackett (@j1mmyhackett) reportedi shipped a report that posted a PDF to @SlackHQ with buttons to approve or flag it. worked great in testing. turns out every single report was re-sharing the exact same file. Next.js had cached the upload URL on the first request and just kept reusing it. so every property got the same PDF. same charts. same data. looked fine in the message. was completely wrong. the fix was straightforward once i saw it. but i only saw it because i added logging on the upload path and watched what Slack was actually returning. without that i would have kept assuming the reports were right. this is the thing that keeps biting me. i build something, it posts, the message looks correct, and i ship it. but "the message looks correct" is not the same as "the data is correct". i need the system to surface the difference, not just tell me a message was sent. the reports now work the way they were supposed to. one message per property, each with its own PDF, two models reading it and leaving grades in the thread. the buttons are how you reply to the report, not how you open it. but i almost shipped a monitoring system that was monitoring nothing. it was just confidently showing me the same snapshot on repeat. what is the dumbest caching bug you have hit in ****?
-
Akshay (✈️ NYC) (@AgentAkki) reported@RTFern @SlackHQ Sorry about that, Ryan! I work at slack. Tell me more about what’s not working for you?
-
Noah Levin (@nlevin) reported@SlackHQ mobile unread state bugs continue to be quite a painful and frustrating issue… plz fix 🙏
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported6a Getting eMail down to zero, loading up the team is @SlackHQ. Planning the day, so I can work the plan.
-
Savi (@SaviPabla) reported@trq212 Please @SlackHQ help us. I’m so tired of telling ppl to download. I’ve now started making videos of the html files and then sharing file as well lol
-
Travis Peters (@SivvyRat) reported@SlackHQ You have no way to provide feedback within your app so... your snap installer has major issues.