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 | 1 day ago |
|
Township of Evan
|
App Crashing | 3 days ago |
 Guayaquil
|
Video | 8 days ago |
|
New York City
|
App Crashing | 1 month ago |
 Brest
|
Connection | 2 months ago |
 Ródos
|
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:
-
noah (@noahsolomon) reported@hiiinternet @SlackHQ It’s a big problem actually
-
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.
-
y - alex ⚔️ (@onelonesabre) reported@SlackHQ @question_base can't use these features when your app is down my friend
-
Angelo 🇵🇷 (@ngeloxyz) reported@chrismunns @SlackHQ lmao its broken for me too I am using Railway's client for Slack now + Beeper for DMs.
-
April Underwood (@aunder) reportedIn this day and age of infosec threats, this subject line from @SlackHQ is a bad call. After the brief cortisol spike that someone using the name Miles Davis had joined our Slack, I scrolled down, and then just wondered why on earth I would want this in my work communication tool.
-
Akshay (✈️ NYC) (@AgentAkki) reported@kurushdubash @patriciosainzr @SlackHQ 👋I work at Slack. Could you share a screenshot or more details on what's not working?
-
Akshay (✈️ NYC) (@AgentAkki) reported@RobSwish @SlackHQ Does restarting the app fix it?
-
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 🫠
-
🇹🇼 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.
-
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.
-
ImagineArt (@ImagineArt_X) reported@SlackHQ @SlackHQ cute, but can you fix the "copying emojis from slack to somewhere else please"
-
Akshay (✈️ NYC) (@AgentAkki) reported@RTFern @SlackHQ Sorry about that, Ryan! I work at slack. Tell me more about what’s not working for you?
-
kzer_AI (@kzer_ai) reported@OpenAI @linear @SlackHQ The agent that pulls context from docs, email, chats, and code to update your Linear ticket: "status: someone else's problem"
-
trent.sol (@trentdotsol) reported@cavemanloverboy @alessandrod @SlackHQ i did. it's the ones who won't that are the problem
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported6:30a Quickly getting eMail down to zero, loading the team up in @SlackHQ before a full morning of appointments.
-
VISHAL (@_THE__FUHRER) reported@SlackHQ @stewart Stewart Butterfield and his team were developing a game called "Glitch" in 2011 The Glitch was an ambitious and creative multiplayer game, but it struggled to find a large enough playerbase. They had to shut it down on 2012
-
Domino Mysłowski (@Domino_mys) reportedThere was Pay by Eye, by Ring, by Watch… time to Pay by Juice? 🧃💳 Okay, this one was just a joke created by Callum (FrostyTrollz). But 10 years ago, paying with your watch or ring also sounded ridiculous. A great example of how today’s joke can become tomorrow’s product is.. @SlackHQ The team behind Slack was actually building an online game called Glitch. As the founders later mentioned: “The game was absolutely preposterous.” Eventually, the game failed and was shut down. However, the internal chat tool they built to communicate became more valuable than the game itself. That tool became Slack, now used by millions of teams. 🌱 Follow for more wild growth-hacks
-
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.
-
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.
-
Subrat Prasad (@humbledshuttler) reported@SlackHQ please fix huddles on android.
-
Darrell Brogdon (@dbrogdon) reportedYesterday I signed up for a service. Today, all my @SlackHQ had a notification asking if I wanted to connect some bot of that service to my Slack accounts. One thing has nothing to do with the other, as far as I'm concern. If this keeps up, I'll delete all of my Slack accounts.
-
mr.tipton (@mrtipton_art) reported@pizzaboy @SlackHQ Nah, I’m that guy. Gotta fix it
-
Caro (@CarolinaLaLopez) reportedThe @SlackHQ glitch in notification numbers is killing my vibe this morning
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported6:30a Got eMail down to zero, and started the team with assignments in @SlackHQ.
-
Mohammad Romman (@MohammadRoman8) reported@SlackHQ are you guys shutting down? It’s been more than a week I’ve been contacting you guys. Support isn’t responding at all
-
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. 🙏🏻
-
matt taylor (@mattployed) reportedslack going down for 30 minutes was like the apocalypse for tech startups @SlackHQ PLEASE dont scare me like that again
-
Evgeny (@PlotnikovDev) reported@adilmania @SlackHQ What problem with slack? We use slack and discord.
-
Theodor Marcu (@theodormarcu) reportedPutting an agent in Slack creates a very different 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.
-
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