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

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

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

    8:30a Got Daniel dropped off and heading back to my office to load the team up in @SlackHQ and get eMail down to zero.

  • j1mmyhackett
    jimmy hackett (@j1mmyhackett) reported

    i shipped a report that posted a PDF to @SlackHQ with buttons to approve or flag it. worked great in testing. turns out every single report was re-sharing the exact same file. Next.js had cached the upload URL on the first request and just kept reusing it. so every property got the same PDF. same charts. same data. looked fine in the message. was completely wrong. the fix was straightforward once i saw it. but i only saw it because i added logging on the upload path and watched what Slack was actually returning. without that i would have kept assuming the reports were right. this is the thing that keeps biting me. i build something, it posts, the message looks correct, and i ship it. but "the message looks correct" is not the same as "the data is correct". i need the system to surface the difference, not just tell me a message was sent. the reports now work the way they were supposed to. one message per property, each with its own PDF, two models reading it and leaving grades in the thread. the buttons are how you reply to the report, not how you open it. but i almost shipped a monitoring system that was monitoring nothing. it was just confidently showing me the same snapshot on repeat. what is the dumbest caching bug you have hit in ****?

  • theodormarcu
    Theodor Marcu (@theodormarcu) reported

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

  • mrtipton_art
    mr.tipton (@mrtipton_art) reported

    @pizzaboy @SlackHQ Nah, I’m that guy. Gotta fix it

  • IncredibleTrade
    IT (@IncredibleTrade) reported

    Any issues with @SlackHQ

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

  • trentdotsol
    trent.sol (@trentdotsol) reported

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

  • HamidAli
    Hamid Ali (@HamidAli) reported

    Uh is @SlackHQ having issues…? 👀 #Slack

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

  • rodrigoberriel
    Rodrigo Berriel (@rodrigoberriel) reported

    @thdxr @SlackHQ unbelievable right? terrible ux

  • ngeloxyz
    Angelo 🇵🇷 (@ngeloxyz) reported

    @chrismunns @SlackHQ lmao its broken for me too I am using Railway's client for Slack now + Beeper for DMs.

  • mutru
    Otto Hilska (@mutru) reported

    @SlackHQ The new Activity view is an amazing improvement. One thing that would make it better: the same thread can appear multiple times (for example the original post and a reply). It would help to allow deduplicating threads from the list.

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

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

Check Current Status