1. Home
  2. ❯
  3. Companies
  4. ❯
  5. Slack
  6. ❯
  7. Outage Map
Slack

Slack Outage Map

The map below depicts the most recent cities worldwide where Slack users have reported problems and outages. If you are having an issue with Slack, make sure to submit a report below

Loading map, please wait...

The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.

Slack users affected:

Less
More
Check Current Status

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.

Most Affected Locations

Outage reports and issues in the past 15 days originated from:

Location Reports
Township of Evan, KS 1
Guayaquil, Guayas 1
New York City, NY 1
Brest, Brittany 1
Check Current Status

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:

  • m_salman_afzal
    Salman (@m_salman_afzal) reported

    no meaningful way to contribute. Just like closed source/proprietary software, you can report issues, but whether it gets fixed or not depends upon the creator. For example, there are couple of issue that I reported to @SlackHQ regarding screen sharing popups,

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

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

  • IncredibleTrade
    IT (@IncredibleTrade) reported

    Is @SlackHQ mobile app down?

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

  • omenosdev
    Mike Rochefort 🐧 (@omenosdev) reported

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

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

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

  • downtownberlin
    Georg S. Kuklick (@downtownberlin) reported

    @SlackHQ @linear Then fix your MCP server!

  • Fusspawn
    Paul Thornton (@Fusspawn) reported

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

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

  • j1mmyhackett
    jimmy hackett (@j1mmyhackett) reported

    the most dangerous bug isn't the one that crashes. it's the one that says 'all good' when it isn't. i had a checker that was supposed to flag a problem. it was reporting green. every single run. turns out it was checking the documentation of the thing it was hunting, not the thing itself. so whenever the problem existed and was documented, the checker saw the doc, said 'found it, it's tracked', and moved on. confident. wrong. this happened twice in the same week in two different places. a report card that shipped one of its four answers unconditionally regardless of the actual data. a monitor that was asserting schema state it had never actually read. both passed. both lied. the lesson i keep relearning: a check that can't fail toward a confident opposite is not a check. it's a placebo. the question isn't 'does this run without error.' the question is 'what would this have to see to fire, and can it actually see that thing.' if the answer to 'can it see it' is 'well, kind of, it reads the notes about it'. you don't have a checker. you have a script that reads its own homework. @SlackHQ kept posting green cards. @AnthropicAI's Claude Code kept summarising them as healthy. everything looked fine. nothing was. what's the quietest false-green you've shipped?

  • merklejosh
    JM (@merklejosh) reported

    @SlackHQ There seems to be a bug in your Version 4.50.140 app (Mac) where if you have open a New message and you try to then click in the Search bar, you can't – it just flashes. Can you please fix this. It's very annoying. Thanks!

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

  • trentdotsol
    trent.sol (@trentdotsol) reported

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

Check Current Status