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 27 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:

  • zquestz
    Josh Ellithorpe (@zquestz) reported

    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.

  • iamTRA
    Rohan (@iamTRA) reported

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

  • imTulip
    Tulip 🌷 ☮️ (@imTulip) reported

    Is @SlackHQ down?

  • pizzaboy
    Dan (@pizzaboy) reported

    @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

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

  • rabmemari
    Rab Memari (@rabmemari) reported

    @chriskim_dev @Teknium No problem. I think its more of a @SlackHQ problem, but happy to check if I can fix it in Hermes and push a PR

  • hollowvox
    Jose Urquiza (@hollowvox) reported

    We're about to start letting our employees fix their own bugs with @v0 and @SlackHQ. Why report a bug to another system when you can send it straight to v0? All I have to do is review the PR and merge it in. So confident in the models and the platform that I can go hands off.

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

  • jbv
    jbv 🌟 (@jbv) reported

    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

  • AyomideAdenowo1
    A-Yo! despises APC (@AyomideAdenowo1) reported

    @daniielezeh @SlackHQ Bruhhh, valid question 😭 I've been having issues with the ******* video playback. I didn't even know it was possible to have worse video playback than twitter.

  • SilchQuatch
    Björne 🇸🇪🏋️‍♂️ (@SilchQuatch) reported

    @QuinnyPig @SlackHQ Every single unwarranted notification births months of hate inside of me. Literally anti-ads for me, any pattern of it and I immediately remove the service. I guess it has to work or it wouldn't be done?

  • TahaTesser
    Taha Tesser (@TahaTesser) reported

    @KhalidWarsa @SlackHQ Because each workspace has own login. Even if you login on one device. You cannot sync all those workspaces under one account on another device

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

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

  • theajithjoseph
    Ajith Joseph (@theajithjoseph) reported

    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.

  • grinich
    Michael Grinich (@grinich) reported

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

  • david_welch
    David Welch (@david_welch) reported

    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

  • arashdehkordiHQ
    Ari Dehkordi (@arashdehkordiHQ) reported

    @karrisaarinen @SlackHQ Did Linear do this before agents? I tried project-level Slack channels at my org and found it works for enterprise engagements nicely, but breaks down at feature/epic level projects for our SaaS. There's a granularity sweet spot, too fine and context switching costs spike. Too coarse and projects blur. Plus no project is actually isolated in small teams, so cross-project conversations forced more people onto each channel and productive engagement suffered. I get the AI context-confinement angle, but curious what other benefits you're seeing?

  • iceman_ome
    wanderingwanderer (@iceman_ome) reported

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

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

  • ArielSterman
    Ariel Sterman (@ArielSterman) reported

    Is @SlackHQ down? heard it here first.

  • YouPulseX
    Paul Sant · Telecodex (@YouPulseX) reported

    @pizzaboy @karrisaarinen @SlackHQ Then "project channel" is a default, not a scope. The issue list command still follows the caller's workspace visibility.

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

    7:30a Back home, getting the boys up, getting eMail down to zero, loading the team up with today's support and production website work (in @SlackHQ).

  • trentdotsol
    trent.sol (@trentdotsol) reported

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

  • Langerius
    LANGERIUS (@Langerius) reported

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

  • theodormarcu
    Theodor Marcu (@theodormarcu) reported

    Putting an agent in Slack creates a very different type of 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.

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

    7:30a Getting email down to zero and loading both the website support and production teams in @SlackHQ.

  • 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

  • neilsuperduper
    Neil Chudleigh (@neilsuperduper) reported

    .@SlackHQ this message pops whenever i try to do any navigation. persists across restarts. also please fix the search results ↓ keypress issue, the first ↓ is being eaten by the system so when I am moving fast I am constantly going to the wrong place you need to make sure bugs like this dont continue, you have serious competition coming that is going to take business from you if you continue to let your product rot.

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

  • jakemor
    Jake Mor (@jakemor) reported

    can someone at @SlackHQ please for the love of god fix drag and drop to attach a file? how has this been an issue for months without anyone realizing? Steps to reproduce: Drag file to attach. Nothing happens. no file attached.