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 (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	6 days ago
Township of Evan	App Crashing	8 days ago
Guayaquil	Video	12 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:

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

  6:30a Back at the home office. Getting eMail down to zero. Planning the day so I can work out the plan. Passing work into @SlackHQ.

• 
  Q (@quionie) reported 6 minutes ago

  @thdxr @SlackHQ ohhh i’m so down for this because this would be MUCH better lol

• 
  Evis Drenova (@evisdrenova) reported 11 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!

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

  8:30a Loading up the team in @SlackHQ and getting eMail down to zero. Planning out the day, so I can work out the plan.

• 
  Chris Munns (@chrismunns) reported 13 minutes ago

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

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

• 
  Bad **** (@TeaseTech) reported 18 minutes ago

  @thdxr @SlackHQ What's the problem?

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

  6a Getting eMail down to zero, loading up the team is @SlackHQ. Planning the day, so I can work the plan.

• 
  John Harnett (@JohnHarnett) reported 19 minutes ago

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

• 
  Evgeny (@PlotnikovDev) reported 21 minutes ago

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

• 
  Conor Bronsdon (@ConorBronsdon) reported 23 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

• 
  Leon (@MozzyFX) reported 26 minutes ago

  Please @SlackHQ can you add a proper GIF selector I need to send better gifs right after I take down production

• 
  Ravi (@ravilutionx) reported 27 minutes ago

  @SlackHQ @trq212 And a verbosity problem

• 
  Andreas Elia (@digitalandreas) reported 28 minutes ago

  @cyberomin @SlackHQ Just to name a few: - Randomly opening channels a few miles up in the chat so I have to go all the way back down again - Right-click context menus are all over the place and inconsistent - Ghost notifications that show up randomly with no notification to go alongside them

• 
  Mike Rochefort 🐧 (@omenosdev) reported 31 minutes ago

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

• 
  FIDENCE MONEY 💰 (@Fidencemoney) reported 31 minutes ago

  @Hyomabtw @SlackHQ @Hyomabtw please how can I get work like virtual assistant,customer care service

• 
  wanderingwanderer (@iceman_ome) reported 39 minutes ago

  .@SlackHQ and @Jira have the weirdest integration possible. Have spent the last 15 mins trying to remove jira app from Slack, but unable to. Can someone more knowledgeable help?

• 
  Ajith Joseph (@theajithjoseph) reported 40 minutes ago

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

• 
  LoopGantt (@loopgantt) reported 41 minutes ago

  @NotionHQ @SlackHQ Channel-scoped agents fix the biggest AI rollout blocker — broad access feels risky to admins. Smart default.

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

  6:30a Getting eMail down to zero. Planning out the work, so I can work out the plan. Loading support and production into @SlackHQ.

• 
  Vortex (@mjparme) reported 44 minutes ago

  @SlackHQ why is there no obvious way to join a channel in Slack? Seems like a huge usability problem, the + sign next to channels creates a channel, but joining one is very elusive

• 
  jbv 🌟 (@jbv) reported 48 minutes ago

  liking the new slack activity view—still getting used to it. One thing: it doesn’t respect the “Just display names” setting. Is a fix coming? 👀 @SlackHQ

• 
  mayberaigan (@mayberayyy) reported 50 minutes ago

  @SlackHQ your app notifications are glitching, please fix it

• 
  𝐎𝐧𝐞𝐓𝐫𝐮𝐞𝐇𝐨𝐦𝐢𝐞(👑,👑) (@OneTrueHomie) reported 50 minutes ago

  isn't this the same problem @PromptQL promised @sama in order to kill @SlackHQ ?

• 
  David Welch (@david_welch) reported 56 minutes ago

  Hey @SlackHQ, there's some talk in the security community about the world is sorta burning down and we need a new space for community discussion. Would you ever donate to help a very highly visible space? You'd be next to names like IBM/Dell/Microsoft/etc. DMs open to chat

• 
  Tyler (@tyhouch) reported 1 hour 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

• 
  SGN (@SGN06380601) reported 1 hour ago

  @SlackHQ i need customer service help and am not getting a response from your agentforce. can you please help?

• 
  Jon Slemp (@Jon_Slemp) reported 1 hour ago

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

• 
  Noah Levin (@nlevin) reported 1 hour ago

  @SlackHQ mobile unread state bugs continue to be quite a painful and frustrating issue… plz fix 🙏

• 
  Element **** (@elementdsj) reported 1 hour ago

  @SlackHQ @vercel debugging a broken deployment directly from a chat thread is actually beautiful.