Slack status: messaging issues and outage reports
No problems detected
If you are having issues, please submit a report below.
Full Outage Map
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.
Problems in the last 24 hours
The graph below depicts the number of Slack reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.
At the moment, we haven't detected any problems at Slack. Are you experiencing issues or an outage? Leave a message in the comments section!
Most Reported Problems
The following are the most recent problems reported by Slack users through our website.
- App Crashing (50%)
- Connection (50%)
Live Outage Map
The most recent Slack outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 New York City
|
App Crashing | 1 month ago |
 Brest
|
Connection | 2 months ago |
 Ródos
|
Messaging | 3 months ago |
 Belo Horizonte
|
Connection | 3 months ago |
 Jewar
|
App Crashing | 3 months ago |
|
Colorado Springs
|
Messaging | 3 months ago |
Full Outage Map
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:
-
Giuseppe Skyline (@giskyexplorer) reported@gustaf @SlackHQ Notifications are the bandaid for broken reliability. WhatsApp stays quiet because it works.
-
John Harnett (@JohnHarnett) reported@cyberomin @digitalandreas @SlackHQ If you've filed a bug with them on the last 5 years and arent a big co then you'd know. They dont fix stuff just because it's broken.
-
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?
-
Kurush Dubash (@kurushdubash) reported@SlackHQ can you please revert your most recent update, it is so bad. This is terrible for anyone who is inbox 0. Please don't make me use Teams
-
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!
-
Ajith Joseph (@theajithjoseph) reportedFriday thought. @stewart raised $17 million to build a video game. 3 years of work! 40 people. And almost nobody wanted to play it. He shut it down in December 2012 and laid off most of the team. The only thing left standing was the chat tool they'd built to talk to each other while working on it. That tool was @SlackHQ. @salesforce bought it for $27.7 billion. The thing you're building in the quiet stretch isn't wasted. Sometimes it turns out to be the actual product.
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported7:30a Getting eMail down to zero and loading up the team in @SlackHQ.
-
Chris Munns (@chrismunns) reportedsomehow @SlackHQ filtering of channels/DMs for last 30 days active hasn't worked for me for months. is this just a broken feature or have I done a thing.
-
Tyler (@tyhouch) reportedyo @SlackHQ please add support for viewing .html files in chat. everyones tossing these around and the download->open in chrome friction is slowing me down bigtime
-
duh (@qudnesa) reported@SlackHQ @question_base why not fix your own agent first?
-
Mike Rochefort 🐧 (@omenosdev) reported@SlackHQ I've sent a message in via the feedback address, but for 4.50.136 either there's been an undisclosed change of GPG keys used in signing Linux packages or the wrong key was used accidentally. For environments with strict package verification this leads to install errors.
-
Rob Swift (@RobSwish) reported@AgentAkki @SlackHQ Restarting doesn't help, and I mentioned this in the dms, it seems so weird to basically have 2 dm lists.
-
Rodrigo Berriel (@rodrigoberriel) reported@thdxr @SlackHQ unbelievable right? terrible ux
-
Gustaf Alströmer (@gustaf) reported@karrisaarinen @ycombinator @SlackHQ I'm experiencing reliability issues with Slack. Message's aren't sent. Messages can't be deleted. App not loading properly. I haven't had any of those issues with Whatsapp ever to be honest. Messages on iPhone is even worse. It's nearly unusable for me.
-
Kit Langton (@kitlangton) reported@ferran9908 @SlackHQ Alas, this one is broken on desktop 😭 Every time a user responds, it disappears.
-
Cathryn (@cathrynlavery) reported@Shopify @klaviyo @SlackHQ The Non-Technical Technical Dictionary, Day 2: Frontend & Backend Every app has a front of house and a back of house. Same as a restaurant. The frontend is what you see and touch. Think of Amazon, or any website you use. → The menu bar, the buttons, the search box. Everything on screen is just a list of things you're allowed to ask for. That's the menu, the dining room, the host stand. But nothing on that menu is actually happening at your table. When you hit "Buy Now," it's like placing an order with a waiter. He walks it back, the kitchen cooks it, and he brings it out when it's ready. The backend = the kitchen. You'll find database, business logic, server. Anything heavy (pulling your order history, processing a payment, sending an email) happens back there. The frontend only handles what fits at the table: how the buttons look, what color the page is, the small animations etc. Think Michelin star. They're not torching your steak tableside. They need the walk-in, the grill, the prep station, the sous chef. Software is the same. The interesting work needs the full kitchen. When a service like Cloudflare or AWS goes down and takes half the internet with it, that's a backend problem. The ghost kitchen caught fire and every restaurant relying on it went dark. A frontend problem is the one you've seen a hundred times: a button that won't click, text piled on top of an image, a page that looks broken on your phone. Frontend is form, where backend is function.
-
Neil Chudleigh (@neilsuperduper) reported.@SlackHQ this message pops whenever i try to do any navigation. persists across restarts. also please fix the search results ↓ keypress issue, the first ↓ is being eaten by the system so when I am moving fast I am constantly going to the wrong place you need to make sure bugs like this dont continue, you have serious competition coming that is going to take business from you if you continue to let your product rot.
-
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
-
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.
-
siggy bilstein (@sbilstein) reported@evisdrenova hmm kinda like Kaniko caching locally, but I think the problem is that the industry has broadly gotten used to very slow deploy pipelines. Back when I was at @SlackHQ in like 2018, we used to SCP the monolith across the fleet and deploy in a couple minutes. Containerization is awesome for various reasons but it has gotten an entire generation of developers to just expect builds + deploys to take at least 15 and usually closer to 45. I do wonder how much perf you could squeeze out with replacing BuildKit but I imagine it's already highly optimized. I just *feel* like developers shouldn't have to think so much about why their builds are slow.
-
Rab Memari (@rabmemari) reported@chriskim_dev @Teknium No problem. I think its more of a @SlackHQ problem, but happy to check if I can fix it in Hermes and push a PR
-
🇹🇼 Phillip Haydon 🇹🇼 (@philliphaydon) reportedIts really disappointing that @SlackHQ status page suggests its up, when it's clearly down and you can get up to date status from X users who are reporting the same issues.
-
A-Yo! despises APC (@AyomideAdenowo1) reported@daniielezeh @SlackHQ Bruhhh, valid question 😭 I've been having issues with the ******* video playback. I didn't even know it was possible to have worse video playback than twitter.
-
Vish (@vish_sh_) reported@SlackHQ Slack bot requires a proper fix first.
-
Travis Peters (@SivvyRat) reported@SlackHQ You have no way to provide feedback within your app so... your snap installer has major issues.
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported7:30a Getting eMail down to zero, passing out assignments in @SlackHQ
-
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
-
Greg Boyd / WGBOYD (@gregboyd) reported@SlackHQ What are the chances we can cut down the number of clicks to start a huddle from four to say… one? Driving me crazy. 🙏🏻
-
Dhruv (@dhruv2038) reportedIs @SlackHQ broken today - I am using Focus mode - seems like the emoticons are breaking.
-
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.