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 2
Guayaquil, Guayas 1
New York City, NY 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:

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

    6:30a Got eMail down to zero, and started the team with assignments in @SlackHQ.

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

  • GaryMcMillianTX
    Gary McMillian (@GaryMcMillianTX) reported

    @SlackHQ You need to fix your search before moving on to AI.

  • stacheFonzi
    Stache (@stacheFonzi) reported

    It's from 2011, but I still miss Glitch. It was a browser based MMO based on collecting and crafting. Crazily enough it was made by the company that went on to rebrand and make @SlackHQ. The messaging system in the game became the basis for Slack.

  • kurushdubash
    Kurush Dubash (@kurushdubash) reported

    @SlackHQ can you please revert your most recent update, it is so bad. This is terrible for anyone who is inbox 0. Please don't make me use Teams

  • jorgemdsto
    Jorge Modesto (@jorgemdsto) reported

    @peduarte Yes @SlackHQ messed something up recently. Search is terrible now.

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

  • refreshmygrave
    dnd dhmu (@refreshmygrave) reported

    @advaithj1 @thdxr @SlackHQ bro pls fix ur support for discord no real people reply ever

  • udaysubbarayan
    Uday Subbarayan (@udaysubbarayan) reported

    @SlackHQ Pl don’t hide the URL’s. Your recent overdoing here is creating problems Thanks

  • cathrynlavery
    Cathryn (@cathrynlavery) reported

    @Shopify @klaviyo @SlackHQ The Non-Technical Technical Dictionary, Day 2: Frontend & Backend Every app has a front of house and a back of house. Same as a restaurant. The frontend is what you see and touch. Think of Amazon, or any website you use. → The menu bar, the buttons, the search box. Everything on screen is just a list of things you're allowed to ask for. That's the menu, the dining room, the host stand. But nothing on that menu is actually happening at your table. When you hit "Buy Now," it's like placing an order with a waiter. He walks it back, the kitchen cooks it, and he brings it out when it's ready. The backend = the kitchen. You'll find database, business logic, server. Anything heavy (pulling your order history, processing a payment, sending an email) happens back there. The frontend only handles what fits at the table: how the buttons look, what color the page is, the small animations etc. Think Michelin star. They're not torching your steak tableside. They need the walk-in, the grill, the prep station, the sous chef. Software is the same. The interesting work needs the full kitchen. When a service like Cloudflare or AWS goes down and takes half the internet with it, that's a backend problem. The ghost kitchen caught fire and every restaurant relying on it went dark. A frontend problem is the one you've seen a hundred times: a button that won't click, text piled on top of an image, a page that looks broken on your phone. Frontend is form, where backend is function.

  • pavzagor
    Pavel Zagorodnikh (@pavzagor) reported

    @SlackHQ you should really fix your reactions search its such a pain to remember the names of emojis. Look at what folks at @raycast and @telegram do 👀

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

  • vasundhar
    Son of Earth (@vasundhar) reported

    @SlackHQ there is issue with your cache where you store message send failure and likes

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

  • NATE9169
    a Nate da Novenchi 🐂🀄️ (@NATE9169) reported

    @adjohu @SlackHQ The crypto community loves the idea of Wild Static, do you have a solana wallet we can donate to to help fund you vision?

Check Current Status