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 |
|---|---|
| Zahlé, Béqaa | 1 |
| Noida, UP | 2 |
| Jewar, UP | 1 |
| Greater Noida, UP | 1 |
| Birmingham, England | 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:
-
Sharon Akinyi (@SharonA01558624) reported@SlackHQ We are having issues with sending or receiving messages on Slack. We have raised a ticket but no response from the Support team. It's been more than 48hours. We start work in a couple of hours!!
-
Zev Zoldan (@ZevZoldan) reportedHot take for the AI founders knocking @SlackHQ: Slack doesn’t have a “communication problem.” Teams do. Most “ignored messages” aren’t about noise, attention spans, or channel chaos. It’s because Slack messages have zero structure. No timing. No follow-through. No visibility. Just text thrown into the void and a prayer. The second you add structure — forms, confirmations, simple logic — everything changes. People actually respond. Leaders stop guessing. Teams stop resending the same message 12 times. Slack doesn’t need fewer messages. It needs smarter ones. That’s what we’re building with @TryThreadly.
-
Peter Dedene (@dedene) reported@tobi +1000 to this 🙌 Please @SlackHQ, we are practically begging for this fix at this point
-
Matt Makai | Full Stack Python | Plushcap (@fullstackpython) reportedHow is @SlackHQ’s video & audio file transcription still so inaccurate? Just use @AssemblyAI or give us an option to use a different provider rather the terrible model you’ve got. It’s frustrating to post a video and the default transcription subtitle is riddled with errors
-
Matthew Cassinelli (@mattcassinelli) reported@samhenrigold So good. I wish this was accounted for when opening Spotlight from the Home Screen so they were distinct, that’s the only reason I don’t unless I have two sets (which do account for each other). Also lol @ @SlackHQ having an old Siri Shortcut donation whose image is broken
-
37chairs (@37chairs) reported@jarredsumner @SlackHQ please no. slack absolutely does not need even one more feature. I realize this is more of a fix than a feature but pencils down, walk away, stop touching it.
-
Openfort (@openfort_hq) reported@aseemk @SlackHQ hey can you send us a dm and we'll try to fix this>
-
asd (@0xANDREAS) reported@peduarte @SlackHQ Is that a problem? Companies need to have this access for compliance & legal reasons. Don’t assume anything private stays private if it’s shared over company platforms :)
-
Ekim (@mikvjpev) reported@RealFeatBit @SlackHQ Have the same issues. Our workspace doesnt exist anymore
-
Saleem Malkana (@smalkana) reported@nlevin @SlackHQ Totally fair. We want to fix this bug and ones like it, overall keeping a high quality bar across Slack. We think we've found and patched this: can you hard reload Slack (Cmd + Shift + R), 2x if needed, and LMK if this is resolved? If not, we'd love device logs to help us get this fixed. DM'ing you now 🙏🏽
-
Maverick_Reports (@MaverickReports) reportedAnyone using clawdbot? Seeing loads of videos on how its so easy to use - 8 hrs in & still can't get @xai to run. Grok has give me an amended .json file which fails. Tried to run Clawdbot in @SlackHQ (too complicated, gave up) switched to @discord now working & getting the following error - any help would be really appreciated: Agent failed before reply: No API key found for provider "xai". Auth store: C:\Users\NAME.clawdbot\agents\main\agent\auth-profiles.json (agentDir: C:\Users\NAME.clawdbot\agents\main\agent). Configure auth for this agent (clawdbot agents add <id>) or copy auth-profiles.json from the main agentDir. Logs: clawdbot logs --follow
-
Tony Dehnke - building 12v.Biz 🧰 & more (@tonydehnke) reported@yongfook Weird you had some many issues. My last few have gone really well. The most annoying app is @SlackHQ which sucks as it makes you log into each space again. Hopefully your next one goes better!
-
Eric Novak (@EricRNovak) reported@SlackHQ is down fyi @downrightnow
-
Satwick (@satiwick1) reportedHave spent 40 mins trying to change my old email to a new one on @SlackHQ to join a new shared channel. For every action @SlackHQ makes me login with 2-factor authentication & then never maintains state in the same browser window. And then I get locked out for too many logins!!!
-
Brian (@talkerbrian) reportedWhy does @SlackHQ offer spell check without offering suggestions to fix basic typos?