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

  • SaviPabla
    Savi (@SaviPabla) reported

    @trq212 Please @SlackHQ help us. I’m so tired of telling ppl to download. I’ve now started making videos of the html files and then sharing file as well lol

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

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

  • HotForMoot
    Riley Read-Only (@HotForMoot) reported

    Cmon @SlackHQ help the tfr

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

  • quionie
    Q (@quionie) reported

    @thdxr @SlackHQ ohhh i’m so down for this because this would be MUCH better lol

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

    6:30a Quickly getting eMail down to zero, loading the team up in @SlackHQ before a full morning of appointments.

  • ellenjdasilva
    Ellen DaSilva (@ellenjdasilva) reported

    Sketchy behavior: Someone from @SlackHQ joined my company channel last week saying "we're here to help you with the product" (we're not having issues). Then today started pestering me about an overdue invoice (we don't have one). Beyond violating. Shameful behavior @salesforce.

  • sytaylor
    Simon Taylor (@sytaylor) reported

    Dear @SlackHQ and @beehiiv Making ctrl+k NOT be the hyperlink shortcut is deliberate pain inflicated on GDocs and Gsuite users. Please fix.

  • tulumpo
    tulumpo (@tulumpo) reported

    $IOND still in pre-launch. second delay message, 10:31 and now 10:39. this is normal. "All NASDAQ systems are fully operational" is in the message. nothing is broken. direct listings open when price discovery settles, not on a clock. @coinbase, @SlackHQ and @Spotify all opened late too.

  • rhymezx_code
    Jide (@rhymezx_code) reported

    @SlackHQ Tell me why Slack desktop is not working on Ubuntu 26.04 ( Resolute Raccoon ) ??? Honestly i have tried o #Ubuntu

  • Jon_Slemp
    Jon Slemp (@Jon_Slemp) reported

    Bug report for you @SlackHQ — when receiving a DM notification from Agents, and those agents are setup as Slack apps you have to DM directly in an app channel, once you hit a certain number of chats in your history tab you can no longer navigate to the DM directly by clicking the DM notification on mobile. You basically get navigated to a blank screen and effectively chat find the message ever. Please fix. This is a disaster of a bug.

  • grinich
    Michael Grinich (@grinich) reported

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

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

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

  • CSO_Krytos
    KRYTOS (@CSO_Krytos) reported

    @Cal_Irvine @thdxr @SlackHQ threads are terrible

Check Current Status