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 (40%)
- Messaging (20%)
- Connection (20%)
- Video (20%)
Live Outage Map
The most recent Slack outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 Township of Evan
|
Messaging | 7 days ago |
|
Township of Evan
|
App Crashing | 8 days ago |
 Guayaquil
|
Video | 13 days ago |
|
New York City
|
App Crashing | 1 month ago |
 Brest
|
Connection | 2 months ago |
 Ródos
|
Messaging | 4 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:
-
noah (@noahsolomon) reported@hiiinternet @SlackHQ It’s a big problem actually
-
Dhruv (@dhruv2038) reportedIs @SlackHQ broken today - I am using Focus mode - seems like the emoticons are breaking.
-
🇹🇼 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.
-
ImagineArt (@ImagineArt_X) reported@SlackHQ @SlackHQ cute, but can you fix the "copying emojis from slack to somewhere else please"
-
SGN (@SGN06380601) reported@SlackHQ i need customer service help and am not getting a response from your agentforce. can you please help?
-
Akshay (✈️ NYC) (@AgentAkki) reported@RobSwish @SlackHQ Does restarting the app fix it?
-
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.
-
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.
-
mr.tipton (@mrtipton_art) reported@pizzaboy @SlackHQ Nah, I’m that guy. Gotta fix it
-
Jake Mor (@jakemor) reportedcan someone at @SlackHQ please for the love of god fix drag and drop to attach a file? how has this been an issue for months without anyone realizing? Steps to reproduce: Drag file to attach. Nothing happens. no file attached.
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported8a Loading the team in @SlackHQ, getting eMail down to zero and getting Daniel up for school.
-
Violeta Poole (@PooleViole45138) reported@dabit3 @SlackHQ Building software entirely inside Slack sounds like a recipe for turning every bug fix into a group chat debate.
-
Alex Oppenheimer (@Alexoppenheimer) reported@SlackHQ I can't login to even contact support. I am in an infinite 2FA loop. And I am being overcharged. Needless to say, I am not happy.
-
IT (@IncredibleTrade) reportedIs @SlackHQ mobile app down?
-
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.
-
Björne 🇸🇪🏋️♂️ (@SilchQuatch) reported@QuinnyPig @SlackHQ Every single unwarranted notification births months of hate inside of me. Literally anti-ads for me, any pattern of it and I immediately remove the service. I guess it has to work or it wouldn't be done?
-
gerry🗯 (@Gerry) reported@zquestz @SlackHQ Ask codex to fix it
-
TT 😋 (@MotivatingPeng) reported@OpenAIDevs @googledrive @SlackHQ Can we fix Codex.... When it does a context automatically compacted it stops what its doing
-
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
-
Theodor Marcu (@theodormarcu) reportedPutting an agent in Slack creates a very different type of UX problem: it has to know when to shut up We spent a lot of time tuning when Devin should speak, stay quiet, or move work into a separate channel. Devin was the first agent to support Slack natively, so it was great to bring 2 years of those learnings to @SlackHQ for the Slack Code launch.
-
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.
-
Taha Tesser (@TahaTesser) reported@KhalidWarsa @SlackHQ Because each workspace has own login. Even if you login on one device. You cannot sync all those workspaces under one account on another device
-
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?
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported7:30a Getting eMail down to zero, passing out assignments in @SlackHQ
-
The Mishmash Cat (@TheMishmashCat) reported[1/5] Your #brain cannot multithread. When you switch from writing code to answering a @SlackHQ ping, your prefrontal cortex doesn't execute a clean parallel jump - it triggers an expensive, messy tear-down and rebuild process. You are burning raw compute.
-
LoopGantt (@loopgantt) reported@NotionHQ @SlackHQ Channel-scoped agents fix the biggest AI rollout blocker — broad access feels risky to admins. Smart default.
-
Fluorine (@FluorineHQ) reported@gustaf @SlackHQ Reliability is the floor, not the ceiling. Slack hit the floor and is now adding notification noise to mask it — classic engagement-metric trap. The deeper issue: messaging apps stopped being where work happens and became where work gets talked about. That's the gap worth solving.
-
Jason Alco (@jason_alco) reported@SlackHQ Our team loves the platform, but we really need to fix the mark unread feature. It’s been broken for years now. First, you should be able to mark a channel as unread without opening the channel and selecting a message. Second, half the time marking a message as unread doesn’t work. I have to go message by message, trying over and over until one works. Please fix this, thank you 🫠
-
Subrat Prasad (@humbledshuttler) reported@SlackHQ please fix huddles on android.
-
Ellen DaSilva (@ellenjdasilva) reportedSketchy behavior: Someone from @SlackHQ joined my company channel last week saying "we're here to help you with the product" (we're not having issues). Then today started pestering me about an overdue invoice (we don't have one). Beyond violating. Shameful behavior @salesforce.