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% Messaging (33%)
  • 33% Connection (33%)

Live Outage Map

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

CityProblem TypeReport Time
New York City App Crashing 29 days 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:

  • loopgantt
    LoopGantt (@loopgantt) reported

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

  • QuinnyPig
    Corey Quinn (@QuinnyPig) reported

    @samlambert @joshmgross It’s almost impossible to mention a bug in Slack and get anyone at @SlackHQ to fix it.

  • gaspardlezin
    Gap | Suby (@gaspardlezin) reported

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

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

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

  • dhruv2038
    Dhruv (@dhruv2038) reported

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

  • digitalandreas
    Andreas Elia (@digitalandreas) reported

    @hugorcd @SlackHQ @github It has been broken for so long they probably think it's a feature internally

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

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

  • karrisaarinen
    Karri Saarinen (@karrisaarinen) reported

    @gustaf @ycombinator @SlackHQ I’d say Slack. Haven’t really experienced those issues you mention. Unless my internet is very bad. iMessage/whatsapp overly phone and counterparty focused so I’m more often wondering if the message actually got delivered or not and if the problem is me or them. Slack is more of a server and it doesn’t send the message if it doesn’t work.

  • MotivatingPeng
    TT 😋 (@MotivatingPeng) reported

    @OpenAIDevs @googledrive @SlackHQ Can we fix Codex.... When it does a context automatically compacted it stops what its doing

  • RaziAns14640044
    Razi Ansari (@RaziAns14640044) reported

    @SlackHQ should fix the UX of their video player. It's one of the worst pieces of UX I've ever interacted with. It feels like I suddenly landed on some government app. Too messy

  • Gerry
    gerry🗯 (@Gerry) reported

    @zquestz @SlackHQ Ask codex to fix it

  • giskyexplorer
    Giuseppe Skyline (@giskyexplorer) reported

    @gustaf @SlackHQ Notifications are the bandaid for broken reliability. WhatsApp stays quiet because it works.

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

    7:30a Getting eMail down to zero, passing out assignments in @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"

  • MarketingMax
    MarketingMax.com (@MarketingMax) reported

    I never call out bad marketing But this is just infuriating. I pay them thousands of dollars a year, have the app installed in my computer, phone, and even iPad … so why did I get this? And why is it not optimized for dark iPhones? Let me know if you need help @SlackHQ @Benioff

  • Krazed
    Krazed 🇵🇸 (@Krazed) reported

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

  • Manoj____Yadav
    Manoj Yadav (@Manoj____Yadav) reported

    @TheNickBigar @CricTalk29 @SlackHQ No it doesn’t track time, you need to tell the time spent via message. Example- worked on X for 30 mins - remind me about checking the production issue around 3 pm The idea is to reduce friction for users on how they track time and tasks

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

    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.

  • iamTRA
    Rohan (@iamTRA) reported

    Slack upload API down? @SlackHQ Cratered team's morning.

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

  • sbilstein
    siggy bilstein (@sbilstein) reported

    @evisdrenova hmm kinda like Kaniko caching locally, but I think the problem is that the industry has broadly gotten used to very slow deploy pipelines. Back when I was at @SlackHQ in like 2018, we used to SCP the monolith across the fleet and deploy in a couple minutes. Containerization is awesome for various reasons but it has gotten an entire generation of developers to just expect builds + deploys to take at least 15 and usually closer to 45. I do wonder how much perf you could squeeze out with replacing BuildKit but I imagine it's already highly optimized. I just *feel* like developers shouldn't have to think so much about why their builds are slow.

  • 202409R
    miya (@202409R) reported

    @ManusAI @SlackHQ This kind of UX that charges users instantly without a clear confirmation step is unacceptable. @ManusAI please fix this and issue a refund. Users should NOT be charged $394 by mistake.

  • alvaisy
    Awais alwaisy (@alvaisy) reported

    @adilmania @SlackHQ what's wrong with slack. bunch of alternatives. each one made money. slack is still stable and useful. i don't have any issue with slakc except limited message history for free users

  • ravilutionx
    Ravi (@ravilutionx) reported

    @SlackHQ @trq212 And a verbosity problem

  • luigiremor
    Luigi ➔ nora.finance (@luigiremor) reported

    @discord @beeper I think I won't have this issue with @SlackHQ...

  • Fusspawn
    Paul Thornton (@Fusspawn) reported

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

  • downtownberlin
    Georg S. Kuklick (@downtownberlin) reported

    @SlackHQ @linear Then fix your MCP server!

  • dbrogdon
    Darrell Brogdon (@dbrogdon) reported

    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.

  • TheMishmashCat
    The Mishmash Cat (@TheMishmashCat) reported

    [1/5] Your #brain cannot multithread. When you switch from writing code to answering a @SlackHQ ping, your prefrontal cortex doesn't execute a clean parallel jump - it triggers an expensive, messy tear-down and rebuild process. You are burning raw compute.