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

  • SivvyRat
    Travis Peters (@SivvyRat) reported

    @SlackHQ You have no way to provide feedback within your app so... your snap installer has major issues.

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

    8a Loading the team in @SlackHQ, getting eMail down to zero and getting Daniel up for school.

  • Manoj____Yadav
    Manoj Yadav (@Manoj____Yadav) reported

    @TheNickBigar @CricTalk29 @SlackHQ No it doesn’t track time, you need to tell the time spent via message. Example- worked on X for 30 mins - remind me about checking the production issue around 3 pm The idea is to reduce friction for users on how they track time and tasks

  • MotivatingPeng
    TT 😋 (@MotivatingPeng) reported

    @OpenAIDevs @googledrive @SlackHQ Can we fix Codex.... When it does a context automatically compacted it stops what its doing

  • vladoustinov
    Vlad (@vladoustinov) reported

    @MerlinEgalite @SlackHQ The problem is they gave up on product a long time ago haha But yes embedding tools/workflows inside interfaces people are already used to use (slack/email/Notion etc) is the way to go

  • _THE__FUHRER
    VISHAL (@_THE__FUHRER) reported

    @SlackHQ @stewart Stewart Butterfield and his team were developing a game called "Glitch" in 2011 The Glitch was an ambitious and creative multiplayer game, but it struggled to find a large enough playerbase. They had to shut it down on 2012

  • grinich
    Michael Grinich (@grinich) reported

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

  • omenosdev
    Mike Rochefort 🐧 (@omenosdev) reported

    @SlackHQ I've sent a message in via the feedback address, but for 4.50.136 either there's been an undisclosed change of GPG keys used in signing Linux packages or the wrong key was used accidentally. For environments with strict package verification this leads to install errors.

  • mjparme
    Vortex (@mjparme) reported

    @SlackHQ why is there no obvious way to join a channel in Slack? Seems like a huge usability problem, the + sign next to channels creates a channel, but joining one is very elusive

  • ashirsc
    Drew Hirschi (@ashirsc) reported

    @SlackHQ pls never ask me again if I want to DM a thread when I tag someone with no text. This is a terrible feature.

  • jabawack81
    Peval 🇮🇹 🇪🇺 🇬🇧🏳️‍🌈 (@jabawack81) reported

    @gabsmashh Once nearly turned down a job interview because the invite came through @MicrosoftTeams. Spent the whole call trying to casually work out if they used @SlackHQ instead. They did.

  • elementdsj
    Element **** (@elementdsj) reported

    @SlackHQ @vercel debugging a broken deployment directly from a chat thread is actually beautiful.

  • kitlangton
    Kit Langton (@kitlangton) reported

    @ferran9908 @SlackHQ Alas, this one is broken on desktop 😭 Every time a user responds, it disappears.

  • Gr8fulTr8s
    Kelly Carter (@Gr8fulTr8s) reported

    @SlackHQ issues connecting to a new workspace. Where can I get support?

  • 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