Slack status: messaging issues and outage reports

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.

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:

• 
  Salman (@m_salman_afzal) reported 5 minutes ago

  no meaningful way to contribute. Just like closed source/proprietary software, you can report issues, but whether it gets fixed or not depends upon the creator. For example, there are couple of issue that I reported to @SlackHQ regarding screen sharing popups,

• 
  Darrell Brogdon (@dbrogdon) reported 9 minutes ago

  Yesterday 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.

• 
  IT (@IncredibleTrade) reported 11 minutes ago

  Is @SlackHQ mobile app down?

• 
  Subrat Prasad (@humbledshuttler) reported 11 minutes ago

  @SlackHQ please fix huddles on android.

• 
  Dan (@pizzaboy) reported 12 minutes ago

  @karrisaarinen @SlackHQ Hey @karrisaarinen are the new project slack channels scoped to just that project I.e if you use the Linear slack bot in the channel will it only have access to issues and data from that project? I found that to be an issue a couple of months ago that the bot wasn’t able to be scoped down? Or was this a skill issue on my end

• 
  HOURLY LIFE of Fred Campos (@FredsDaily) reported 12 minutes ago

  7:30a Getting eMail down to zero, passing out assignments in @SlackHQ

• 
  Aadii (@AadityaPasayat) reported 13 minutes ago

  @raidingAI @SlackHQ @slashyai I am sorry to say, but u don't have taste, either the editor. R eyes go from left to right, common sense. Btw I can help u get taste

• 
  matt taylor (@mattployed) reported 14 minutes ago

  slack going down for 30 minutes was like the apocalypse for tech startups @SlackHQ PLEASE dont scare me like that again

• 
  Cathryn (@cathrynlavery) reported 16 minutes ago

  @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.

• 
  Paul Thornton (@Fusspawn) reported 17 minutes ago

  @SlackHQ @dorukkavcioglu I miss the old glitch game, had fun with some of your old founders in that :(

• 
  Evgeny (@PlotnikovDev) reported 18 minutes ago

  @adilmania @SlackHQ What problem with slack? We use slack and discord.

• 
  Assaf Kipnis (@Kipnis_a) reported 20 minutes ago

  Claude 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

• 
  Tyler (@tyhouch) reported 23 minutes ago

  yo @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

• 
  Dhruv (@dhruv2038) reported 31 minutes ago

  Is @SlackHQ broken today - I am using Focus mode - seems like the emoticons are breaking.

• 
  HOURLY LIFE of Fred Campos (@FredsDaily) reported 32 minutes ago

  7:30a Getting eMail down to zero and loading up the team in @SlackHQ.

• 
  mewc (@the_mewc) reported 39 minutes ago

  @SlackHQ lots of bugs and issues right now. Can't create channels and lots of jankyness. This release is a lot.

• 
  Mohi (@disismohi) reported 42 minutes ago

  @SlackHQ: 40% less merge queue time, CI type-checking down from 7.5 minutes to 1.25 minutes. Canva: 58s to first error in the editor down to 4.8s.

• 
  Conor Bronsdon (@ConorBronsdon) reported 44 minutes ago

  .@SlackHQ is building for multiplayer AI: tag a coding agent into a Slack conversation and it spins up a coding channel: everyone in that convo gets a live dev environment, diffs post as artifacts, and the channel winds down when the task is done. With the launch of Slack Code, Claudeforce, their MCP and more, Slack is putting Agents in the channels where teams already work, not simply in a private chat with one person. Their position is that the whole team should be able to watch, steer, and review what the agent does. Slack Chief Product Officer Jaime DeLanghe joined me on @chain_ofthought to explain how Slack is building a team AI environment, what happens mechanically when a code channel is created, why Anthropic pushes so much of its code through Slack, how the channel permission model became the agent context model, and what has to change in engineering culture when the whole team is steering one agent. I think Slack is the platform best positioned to become the context harness where enterprise agents run: agents that see what the team discusses, permissions that already exist, and a cultural opportunity hiding inside every multiplayer coding session. Chapters: (0:00) Slack as an IDE and a GitHub for your team (0:29) Who is Jaime DeLanghe (1:21) The reaction to the Slack Code launch (5:30) Why coding agents belong in a context-rich environment (6:08) Engineers now manage agents, not copy-paste code (7:24) The permission model: agents get the channel's context (11:44) What happens when a code channel is created (15:00) Why Anthropic pushes so much code through Slack (19:14) Steering one agent with many people: culture decides (24:54) Slackbot, skills, and MCPs: agents go where the work is (30:53) The solo terminal vs. agents in social spaces (33:53) Org charts and ownership when agents join the team (39:33) Learning loops and shared agent memory (42:39) Citations, recency, and accidental knowledge management (46:50) Context bloat and multi-pass search for agents (50:01) How Jaime uses Slackbot as CPO (52:38) Slack Code is V1 of multiplayer AI

• 
  Evis Drenova (@evisdrenova) reported 46 minutes ago

  @sbilstein @SlackHQ yeah to your earlier point i think it depends at what layer you want to attack it i.e. rust builds are slow, caching can help but github actions is trash for it, but blacksmith isn't bad, is there a generic solution you can use that *just works* on any CI? alternatively, go after the actual docker execution layer but not clear to me how much of a bottleneck that actually is vs. language specific idiosyncrasies buildkit is pretty optimized from what i've heard but i generally agree with make it fast and stupidly easy to use!

• 
  LANGERIUS (@Langerius) reported 48 minutes ago

  @BarknTuncer @SlackHQ yeah notification sync issues are still surprisingly common

• 
  Rahul Chetia (@ayoImNotTrippin) reported 49 minutes ago

  @SlackHQ there’s a widespread issue with slack today. Not sure about Mac but my entire team with windows seems to be impacted. Slack becomes irresponsive on windows a few minutes in. Tried ‘repair’ and force close, but no help there. We are using app in our phones to communicate.

• 
  GosuCoder (@GosuCoder) reported 49 minutes ago

  Slackbot 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

• 
  Alexander Cranga (@alexandercranga) reported 54 minutes ago

  /copy from Claude -> paste in Slack -> doesn’t keep the formatting. @SlackHQ please fix

• 
  Ravi (@ravilutionx) reported 55 minutes ago

  @SlackHQ @trq212 And a verbosity problem

• 
  Josh Ellithorpe (@zquestz) reported 56 minutes ago

  It 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.

• 
  🇹🇼 Phillip Haydon 🇹🇼 (@philliphaydon) reported 56 minutes ago

  Its 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.

• 
  Gustaf Alströmer (@gustaf) reported 58 minutes ago

  @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.

• 
  Georg S. Kuklick (@downtownberlin) reported 1 hour ago

  @SlackHQ @linear Then fix your MCP server!

• 
  Krazed 🇵🇸 (@Krazed) reported 1 hour ago

  @SlackHQ you have a degradation rn? unable to create channels and getting intermittent issues with events

• 
  Kurush Dubash (@kurushdubash) reported 1 hour ago

  @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