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:
-
Jide (@rhymezx_code) reported@SlackHQ Tell me why Slack desktop is not working on Ubuntu 26.04 ( Resolute Raccoon ) ??? Honestly i have tried o
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported8:30a Got Daniel dropped off and heading back to my office to load the team up in @SlackHQ and get eMail down to zero.
-
GosuCoder (@GosuCoder) reportedSlackbot legit might be one of my favorite uses of AI outside of coding. I use this thing constantly to find past conversations, summarize entire chats, help write responses, look for things I might be forgetting, or even look up past context on a decision or topic. Seriously @SlackHQ this legit improves my life
-
Karri Saarinen (@karrisaarinen) reported@gustaf @ycombinator @SlackHQ What is degrading? WhatsApp imo is not a good example. Can’t even hold login on a desktop, and have to auth with your phone. Sync not super reliable either
-
mewc (@the_mewc) reported@SlackHQ lots of bugs and issues right now. Can't create channels and lots of jankyness. This release is a lot.
-
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.
-
dnd dhmu (@refreshmygrave) reported@advaithj1 @thdxr @SlackHQ bro pls fix ur support for discord no real people reply ever
-
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
-
jimmy hackett (@j1mmyhackett) reportedthe scariest bugs in an agent system aren't the ones that crash loudly. they're the ones that succeed. quietly. and then stop. and you don't find out for three days. this week i shipped `fix(daily): heartbeat + agent-health for the daily-report jobs` (commit 10c954a). the cron had been running. the launchd plist was registered. no errors in the log. but the report wasn't landing in @SlackHQ. it took me longer than i want to admit to realize the job had silently stopped delivering. no crash, no alert, just absence. the mental model i pulled from it: a job that runs is not the same as a job that works. completion and correctness are two different signals, and most infra only monitors the first one. heartbeats fix this. you instrument the output, not just the process. if the report doesn't land by 8:05am, something fires. you stop trusting the scheduler and start verifying the result. this applies way past cron jobs. any pipeline where you only watch for failure will eventually drift silently into uselessness. the absence of an error is not evidence of health. once i wired heartbeats into the @AnthropicAI-powered agent fleet, i found two other jobs that had the same problem. they looked fine. they weren't. if you're running automated jobs and you're not monitoring outputs, you're not monitoring. what's the longest a silent failure ran in your system before you caught it?
-
Peter Garber (@petegarber) reported@Cartidise @OutofGalaxyy The icons might be stupid here but Gchat works pretty well inside of Gmail and this UI actually is OK. The only problem is that Gchat should literally be able to replace @SlackHQ but it’s been ignored.
-
Brad Beckett (@bradbeckett) reportedWith how much sensitive data @SlackHQ stores, it's surprising they don't yet support Passkey login or have a BIMI email verification certificate so their legitimate emails get a blue verified check mark in major email service providers. @digicert pls reach out to them!
-
Teo Vanyo Adiputra (@teostealth) reported@karrisaarinen @SlackHQ The handoff from Slack discussion to actual tracked issue is where most teams drop the ball - keeping that loop tight is harder than it sounds.
-
gerry🗯 (@Gerry) reported@zquestz @SlackHQ Ask codex to fix it
-
Josh Ellithorpe (@zquestz) reportedIt is very obvious that @SlackHQ does absolutely zero QA testing on Linux. You would think they would at least do a basic sanity test. Latest release has a completely broken system tray, and broken desktop icon. Glad I hardly use this crap anymore.
-
Paul Thornton (@Fusspawn) reported@SlackHQ @dorukkavcioglu I miss the old glitch game, had fun with some of your old founders in that :(