1. Home
  2. Companies
  3. Slack
Slack

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.

  • 33% App Crashing (33%)
  • 33% Connection (33%)
  • 33% Video (33%)

Live Outage Map

The most recent Slack outage reports came from the following cities:

CityProblem TypeReport Time
Guayaquil Video 4 days ago
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
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:

  • jorgemdsto
    Jorge Modesto (@jorgemdsto) reported

    @peduarte Yes @SlackHQ messed something up recently. Search is terrible now.

  • j1mmyhackett
    jimmy hackett (@j1mmyhackett) reported

    the 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?

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

  • m_salman_afzal
    Salman (@m_salman_afzal) reported

    @SlackHQ But whether they decide to act on it will depend how much they prioritize the issue. And this is what open source could become as well. We can only report but only their agent factories can now contribute. So, it kind of is closed source since no one is now reading the 100k loc

  • FredsDaily
    HOURLY LIFE of Fred Campos (@FredsDaily) reported

    8:30a Back at my desk, loading the team up in @SlackHQ with today's assignment, getting eMail down to zero.

  • _bhuvanesh_
    Bhuvanesh Sridharan (@_bhuvanesh_) reported

    as much hate @MicrosoftTeams gets, at least the meeting chat and other chats are on the same platform. Absence of synergy between @SlackHQ chat and Google meet is such a pet peeve. Non issue in grand scheme but still bothering whenever people send links in gmeet.

  • Kipnis_a
    Assaf Kipnis (@Kipnis_a) reported

    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

  • loopgantt
    LoopGantt (@loopgantt) reported

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

  • CarolinaLaLopez
    Caro (@CarolinaLaLopez) reported

    The @SlackHQ glitch in notification numbers is killing my vibe this morning

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

  • rhymezx_code
    Jide (@rhymezx_code) reported

    @SlackHQ Tell me why Slack desktop is not working on Ubuntu 26.04 ( Resolute Raccoon ) ??? Honestly i have tried o #Ubuntu

  • gaspardlezin
    Gap | Suby (@gaspardlezin) reported

    Can someone please buy @SlackHQ and shut it down? This platform is horrible.

  • jorilallo
    Jori Lallo (@jorilallo) reported

    @pizzaboy @karrisaarinen @SlackHQ It's still the same agent with capability to access everything as the caller user can. If you're calling it in the channel, it has that as context so it will file issue into the project by default and answer questions about the project without you needing to name it separately. If there's situatons where it's not working as intended, would love to get screenshots

  • petegarber
    Peter Garber (@petegarber) reported

    @Cartidise @OutofGalaxyy The icons might be stupid here but Gchat works pretty well inside of Gmail and this UI actually is OK. The only problem is that Gchat should literally be able to replace @SlackHQ but it’s been ignored.

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

  • karrisaarinen
    Karri Saarinen (@karrisaarinen) reported

    @gustaf @ycombinator @SlackHQ What is degrading? WhatsApp imo is not a good example. Can’t even hold login on a desktop, and have to auth with your phone. Sync not super reliable either

  • rodrigoberriel
    Rodrigo Berriel (@rodrigoberriel) reported

    @thdxr @SlackHQ unbelievable right? terrible ux

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

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

  • alexei_sid
    Alex Sidorenko (@alexei_sid) reported

    @Moore_Irish @salesforce @SlackHQ Pricing changes that reduce admin control while pushing AI features rarely improve outcomes. The real test: does the AI actually help teams make faster, better decisions, or is it just another feature tax masquerading as innovation?

  • Gerry
    gerry🗯 (@Gerry) reported

    @zquestz @SlackHQ Ask codex to fix it

  • elementdsj
    Element **** (@elementdsj) reported

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

  • bkwebster
    Brandon Karl Webster (@bkwebster) reported

    @adilmania @SlackHQ Better alternatives exist - it’s used abundantly because of the mindshare and scale. The only replacement would be a totally new and obvious form factor that leads to the same outcome in a better way - not a better alternative to the same problem.

  • udaysubbarayan
    Uday Subbarayan (@udaysubbarayan) reported

    @SlackHQ Pl don’t hide the URL’s. Your recent overdoing here is creating problems Thanks

  • ConorBronsdon
    Conor Bronsdon (@ConorBronsdon) reported

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

  • trentdotsol
    trent.sol (@trentdotsol) reported

    @cavemanloverboy @alessandrod @SlackHQ i did. it's the ones who won't that are the problem

  • IncredibleTrade
    IT (@IncredibleTrade) reported

    Is @SlackHQ mobile app down?

  • SivvyRat
    Travis Peters (@SivvyRat) reported

    @SlackHQ You have no way to provide feedback within your app so... your snap installer has major issues.

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

  • GaryMcMillianTX
    Gary McMillian (@GaryMcMillianTX) reported

    @SlackHQ You need to fix your search before moving on to AI.

  • theodormarcu
    Theodor Marcu (@theodormarcu) reported

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