1. Home
  2. Companies
  3. Slack
  4. 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
Ródos, South Aegean 1
Belo Horizonte, MG 1
Jewar, UP 2
Colorado Springs, CO 1
South Point, Mont Fleuri 1
Bismarck, ND 1
Noida, UP 3
Greater Noida, UP 2
Zahlé, Béqaa 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:

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

  • jeffreytucker
    Jeffrey A Tucker (@jeffreytucker) reported

    @SlackHQ your headphone icon on huddles is a huge annoyance and an invasion of privacy for everyone. Users can turn it off but there should be the ability to shut this down for the whole workspace. We really don't need to know who is talking with whom at any one time.

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

  • PlotnikovDev
    Evgeny (@PlotnikovDev) reported

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

  • kitayoshi_son
    Kitayoshi (@kitayoshi_son) reported

    @alphato_o @SlackHQ Even a sticky banner hanging on the workspace saying “Your workspace will be shutting down” on the chat page would be better. They could even use the UI components for the 90-day limit. Today’s behavior makes it seem like they just don’t care.

  • FluorineHQ
    Fluorine (@FluorineHQ) reported

    @gustaf @SlackHQ Reliability is the floor, not the ceiling. Slack hit the floor and is now adding notification noise to mask it — classic engagement-metric trap. The deeper issue: messaging apps stopped being where work happens and became where work gets talked about. That's the gap worth solving.

  • dhruv2038
    Dhruv (@dhruv2038) reported

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

  • 4kingtheworld
    kingoftheworld (@4kingtheworld) reported

    @antonioventre_ @SlackHQ Hey man, I’d really appreciate help getting Slack restored. I’ve got a company with 40 employees and it’s catastrophic man anything you can do to help Tried dming but it didn’t work

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

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

  • immehmetali
    Mehmet Ali (@immehmetali) reported

    @SlackHQ Context is necessary but not sufficient. The real bottleneck is decision architecture: knowing when to retrieve, when to reason, and when to act. More context doesn't fix a broken agent loop.

  • eoslick
    Evan Oslick (@eoslick) reported

    Anyone know how to gert @SlackHQ support? I've got a bit of a lingering issue that I'm not sure how do deal with due to ownership of Slack deployment.

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

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

  • Aayush0994
    Aayush Desai (@Aayush0994) reported

    @SlackHQ can you please fix the unread notification that does not go away even after reading the message? Thanks!

  • freddiev4
    Freddie Vargus (@freddiev4) reported

    @jeffreyhuber @SlackHQ have Jeff fix this for you pls

Check Current Status