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.

  • 42% App Crashing (42%)
  • 33% Messaging (33%)
  • 17% Connection (17%)
  • 8% Sign in (8%)

Live Outage Map

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

CityProblem TypeReport Time
Brest Connection 20 days ago
Ródos Messaging 2 months ago
Belo Horizonte Connection 2 months ago
Jewar App Crashing 2 months ago
Colorado Springs Messaging 2 months ago
South Point Sign in 2 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:

  • PlotnikovDev
    Evgeny (@PlotnikovDev) reported

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

  • franferbel
    F. Fernández-Beltrán (@franferbel) reported

    Hey @SlackHQ — it’s been 3 days waiting for a response from your Help Center. For a platform that sells efficiency and seamless communication, this feels… ironic. Is this really the standard for customer support? 🤔

  • Jordy_vD_
    Jordy.app (@Jordy_vD_) reported

    . @SlackHQ slack gets a lot of things right, but the iOS app’s search functionality is very bad. Can I please chat with someone who can then hopefully fix it?

  • edweirdsnowman
    Ash (@edweirdsnowman) reported

    @SlackHQ slack huddles has had video audio sync issues since it’s been launched. Please deploy at least 7 agents to fix this immediately.

  • Watching1776
    TheHardTruth (@Watching1776) reported

    @SlackHQ You need to fix that app so it stops putting people into Auto Silence repeatedly without touching anything. Your code is trash

  • JustSteveKing
    JustSteveKing (@JustSteveKing) reported

    @heyandras @SlackHQ I had the same issue, but it's like $3.50 or something per user a month - so for just me it was easier to pay it

  • maddada
    M. Yahia (@maddada) reported

    @aaditsh @adilmania @SlackHQ Same, it's 10 times better than discord, teams, hangout, zoom, etc. Not sure about newer apps but I literally have 0 issues with slack. It's really good with connect too if you work with external companies, beats email by light years.

  • TeaseTech
    Bad **** (@TeaseTech) reported

    @thdxr @SlackHQ What's the problem?

  • AgentC_006
    Chimene | Dantown (@AgentC_006) reported

    @thdxr @SlackHQ It’s always weird that you cannot actively reply to messages on Slack. The experience feels broken.

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

  • Oxymarun_
    Arun Sharma (@Oxymarun_) reported

    @SlackHQ came out of a failing 10-person game studio the team needed a way to coordinate that wasn't email they built it for themselves then realized every distributed team on earth had the same problem

  • MatthewGattozzi
    Matthew Gattozzi 📷 Ads/Videos/Photos for Brands (@MatthewGattozzi) reported

    @RomanEcom @SlackHQ My HK clients dealing with the same issue

  • philliphaydon
    🇹🇼 Phillip Haydon 🇹🇼 (@philliphaydon) reported

    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.

  • 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

  • nutritogo
    Livleen Gill (@nutritogo) reported

    @SlackHQ - having a very difficult time with your product as a new customer. No help

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

  • grinich
    Michael Grinich (@grinich) reported

    @SlackHQ Please fix the rate limits. The current Slack API is practically useless since you reduced them.

  • darcy_jpa
    Darcy (@darcy_jpa) reported

    @SlackHQ @linear @cursor_ai Slack is a garbage product. Everything about it is trash. The reliability is trash, the support is trash, and the way you handle users is absolute trash. Impressive how consistently terrible you manage to be.

  • takshshahh
    Taksh Shah (@takshshahh) reported

    Someone at @SlackHQ needs to fix how they deal with markdown. Its markdown but not really? Pasting stuff from elsewhere sometimes preserves formatting, sometimes doesnt? I had to do workarounds when working with API, but pasting content from claude in the messagebox is terrible

  • IncredibleTrade
    IT (@IncredibleTrade) reported

    Is @SlackHQ mobile app down?

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

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

  • kzer_ai
    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"

  • AgentAkki
    Akshay (✈️ NYC) (@AgentAkki) reported

    @RobSwish @SlackHQ Does restarting the app fix it?

  • Beryl2021
    Beryl (@Beryl2021) reported

    @SlackHQ Same here. Our workspace is also showing as deleted and we're locked out. Billing is up to date and no one on our team triggered this. Glad to know we're not the only ones, but this is a major glitch. We’ve already reached out to support but haven't heard back yet 😢

  • disismohi
    Mohi (@disismohi) reported

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

  • teostealth
    Teo Vanyo Adiputra (@teostealth) reported

    @karrisaarinen @SlackHQ The handoff from Slack discussion to actual tracked issue is where most teams drop the ball - keeping that loop tight is harder than it sounds.

  • loopgantt
    LoopGantt (@loopgantt) reported

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

  • SGN06380601
    SGN (@SGN06380601) reported

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

  • dedene
    Peter Dedene (@dedene) reported

    @tobi +1000 to this 🙌 Please @SlackHQ, we are practically begging for this fix at this point

  • HamidAli
    Hamid Ali (@HamidAli) reported

    Uh is @SlackHQ having issues…? 👀 #Slack