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 |
|---|---|
| Birmingham, England | 1 |
| Greenville, SC | 1 |
| Morsang-sur-Orge, Île-de-France | 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:
-
Nanda Kishore Kapa (@dunlop9) reported@SlackHQ This morning, I am not able to download files that were shared in slack. It appears to be a cloud issue. Can you look into it?
-
кαяεη (@c1r3n) reported@SlackHQ hello!is there an issue with the huddle option? it is not working
-
Darcy (@darcy_jpa) reported@SlackHQ @linear @cursor_ai Slack is a garbage product. Everything about it is trash. The reliability is trash, the support is trash, and the way you handle users is absolute trash. Impressive how consistently terrible you manage to be.
-
Yariv Ashkenazy (@YarivAshkenazy) reported@Premauj @SlackHQ Classic Slack... Always buggy. Are you or your company building software? I'm building a work messaging app purpose-built for software-building companies. Would love a quick chat about the problems you or your company have with Slack!
-
chimpp 🐒 (@WhoeverTheFuk) reported@SlackHQ down?
-
Fabian (@ffabbianr) reported@AmenaiSabuwala @SlackHQ This must be ragebait, right? You redesigned a Splash Screen into a login screen, those are separate things.
-
Aadriyaan (@Peace_full_in) reported@SlackHQ what's wrong with you? Why suddenly my account is showing deactivated and I can't even login back ?
-
Mehmet Ali (@immehmetali) reported@SlackHQ Context is necessary but not sufficient. The real bottleneck is decision architecture: knowing when to retrieve, when to reason, and when to act. More context doesn't fix a broken agent loop.
-
Precious (@Premauj) reportedAm I the only one @SlackHQ has been giving wrong notification counts??? Huddles you've left are still showing; new messages don't display on time. Especially on Mac. You people should fix up o
-
Disky.eth (@OxDisky) reportedI just learned you can basically see all @SlackHQ profile images publicly without the need for authenticated request. Isn't this both a #privacy issue and security issue? I mean, you can basically fetch them from ca.slack-edge dot com. #slack #privacyprotection
-
Simon Taylor (@sytaylor) reportedDear @SlackHQ and @beehiiv Making ctrl+k NOT be the hyperlink shortcut is deliberate pain inflicated on GDocs and Gsuite users. Please fix.
-
Erik Rasmussen 👨💻🇺🇸🇪🇸 (@erikras) reportedI have a huge hug and a bottomless 🍺 budget for whoever coded the "Make a @linear issue from this @SlackHQ thread" workflow, especially with the bidirectional comment syncing. 🫡
-
Brandon (@brandooonndd) reported🚨 @cursor_ai just dropped Automations always-on AI coding agents that run 24/7, triggered by GitHub PRs, Slack messages, or timers. They handle security audits, auto-approve low-risk PRs & fix bugs overnight. The future of dev just shipped. @github @SlackHQ #AIcoding #Cursor
-
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
-
$lostmidas (cc/acc) (@lostmidas) reported@chintanturakhia @linear @SlackHQ curious if you’ve played with n8n for this yet. feels like you could also auto-ship product ops stuff (daily product metrics to slack/notion, sync linear issues to gcal, kill manual status updates, etc.). tried anything like that?