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 |
|---|---|
| Guayaquil, Guayas | 1 |
| 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:
-
Drew Hirschi (@ashirsc) reported@SlackHQ pls never ask me again if I want to DM a thread when I tag someone with no text. This is a terrible feature.
-
Adil Mania. (@adilmania) reported@NebulaAI @safizaq @SlackHQ discord integration is kinda broken, like i keep having "nebula" links showing, if you can fix that, that will be perfect.
-
jimmy hackett (@j1mmyhackett) reportedthe most dangerous bug isn't the one that crashes. it's the one that says 'all good' when it isn't. i had a checker that was supposed to flag a problem. it was reporting green. every single run. turns out it was checking the documentation of the thing it was hunting, not the thing itself. so whenever the problem existed and was documented, the checker saw the doc, said 'found it, it's tracked', and moved on. confident. wrong. this happened twice in the same week in two different places. a report card that shipped one of its four answers unconditionally regardless of the actual data. a monitor that was asserting schema state it had never actually read. both passed. both lied. the lesson i keep relearning: a check that can't fail toward a confident opposite is not a check. it's a placebo. the question isn't 'does this run without error.' the question is 'what would this have to see to fire, and can it actually see that thing.' if the answer to 'can it see it' is 'well, kind of, it reads the notes about it'. you don't have a checker. you have a script that reads its own homework. @SlackHQ kept posting green cards. @AnthropicAI's Claude Code kept summarising them as healthy. everything looked fine. nothing was. what's the quietest false-green you've shipped?
-
matt taylor (@mattployed) reportedslack going down for 30 minutes was like the apocalypse for tech startups @SlackHQ PLEASE dont scare me like that again
-
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?
-
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.
-
Jon Slemp (@Jon_Slemp) reportedBug report for you @SlackHQ — when receiving a DM notification from Agents, and those agents are setup as Slack apps you have to DM directly in an app channel, once you hit a certain number of chats in your history tab you can no longer navigate to the DM directly by clicking the DM notification on mobile. You basically get navigated to a blank screen and effectively chat find the message ever. Please fix. This is a disaster of a bug.
-
Otto Hilska (@mutru) reported@SlackHQ The new Activity view is an amazing improvement. One thing that would make it better: the same thread can appear multiple times (for example the original post and a reply). It would help to allow deduplicating threads from the list.
-
mr.tipton (@mrtipton_art) reported@pizzaboy @SlackHQ Nah, I’m that guy. Gotta fix it
-
dnd dhmu (@refreshmygrave) reported@advaithj1 @thdxr @SlackHQ bro pls fix ur support for discord no real people reply ever
-
Leon (@MozzyFX) reportedPlease @SlackHQ can you add a proper GIF selector I need to send better gifs right after I take down production
-
Tulip 🌷 ☮️ (@imTulip) reportedIs @SlackHQ down?
-
Douglas Liscano (@douglas2428) reported@MatthewAry @github @SlackHQ Yes, we have the same problem today
-
Sophia Yen MD (@teenmd) reported.@SlackHQ Why don't you have human service agents? You are a GIANT company used by many. The only contact us is via a webform?
-
Corey Quinn (@QuinnyPig) reported@samlambert @joshmgross It’s almost impossible to mention a bug in Slack and get anyone at @SlackHQ to fix it.