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
Ródos, South Aegean 1
Belo Horizonte, MG 1
Jewar, UP 1
Colorado Springs, CO 1
South Point, Mont Fleuri 1
Bismarck, ND 1
Noida, UP 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:

  • vasundhar
    Son of Earth (@vasundhar) reported

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

  • HamidAli
    Hamid Ali (@HamidAli) reported

    Uh is @SlackHQ having issues…? 👀 #Slack

  • AgentAkki
    Akshay (✈️ NYC) (@AgentAkki) reported

    @kurushdubash @patriciosainzr @SlackHQ 👋I work at Slack. Could you share a screenshot or more details on what's not working?

  • teenmd
    Sophia Yen MD (@teenmd) reported

    .@SlackHQ Why don't you have human service agents? You are a GIANT company used by many. The only contact us is via a webform?

  • TheMishmashCat
    The Mishmash Cat (@TheMishmashCat) reported

    [1/5] Your #brain cannot multithread. When you switch from writing code to answering a @SlackHQ ping, your prefrontal cortex doesn't execute a clean parallel jump - it triggers an expensive, messy tear-down and rebuild process. You are burning raw compute.

  • iceman_ome
    wanderingwanderer (@iceman_ome) reported

    .@SlackHQ and @Jira have the weirdest integration possible. Have spent the last 15 mins trying to remove jira app from Slack, but unable to. Can someone more knowledgeable help?

  • kyukxs
    Mutatyo (@kyukxs) reported

    New Slack Design is terrible. @SlackHQ can I revert to a previous version just a few updates from this one!

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

  • franferbel
    F. Fernández-Beltrán (@franferbel) reported

    Hey @SlackHQ — it’s been 3 days waiting for a response from your Help Center. For a platform that sells efficiency and seamless communication, this feels… ironic. Is this really the standard for customer support? 🤔

  • loopgantt
    LoopGantt (@loopgantt) reported

    @NotionHQ @SlackHQ Channel-scoped agents fix the biggest AI rollout blocker — broad access feels risky to admins. Smart default.

  • johancutych
    Johan Cutych (@johancutych) reported

    first you need to fix the rate limits @SlackHQ

  • danmazy1
    Dan Mazy (@danmazy1) reported

    @SlackHQ I'm the sole owner of a paid workspace. Changed my number + email, so recovery doesn't work. I can verify via billing/credit card. Support can't help. Can't log in, can't add employees. There has to be a manual verification process. Please escalate.

  • yongqianme
    YQ (@yongqianme) reported

    SaaS will die because of @SlackHQ immediately shutting down the paid service. Self-hosted service with agent is the future!

  • mayberayyy
    mayberaigan (@mayberayyy) reported

    @SlackHQ your app notifications are glitching, please fix it

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

Check Current Status