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 2
Colorado Springs, CO 1
South Point, Mont Fleuri 1
Bismarck, ND 1
Noida, UP 2
Greater Noida, UP 1
Zahlé, Béqaa 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:

  • pizzaboy
    Dan (@pizzaboy) reported

    @karrisaarinen @SlackHQ Hey @karrisaarinen are the new project slack channels scoped to just that project I.e if you use the Linear slack bot in the channel will it only have access to issues and data from that project? I found that to be an issue a couple of months ago that the bot wasn’t able to be scoped down? Or was this a skill issue on my end

  • rabmemari
    Rab Memari (@rabmemari) reported

    @chriskim_dev @Teknium No problem. I think its more of a @SlackHQ problem, but happy to check if I can fix it in Hermes and push a PR

  • MohschinoKhan
    AK (@MohschinoKhan) reported

    @daveamsterdam20 @SlackHQ Same issue here wtf is going on!! @SlackHQ

  • immehmetali
    Mehmet Ali (@immehmetali) reported

    @SlackHQ Context is necessary but not sufficient. The real bottleneck is decision architecture: knowing when to retrieve, when to reason, and when to act. More context doesn't fix a broken agent loop.

  • johancutych
    Johan Cutych (@johancutych) reported

    first you need to fix the rate limits @SlackHQ

  • trentdotsol
    trent.sol (@trentdotsol) reported

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

  • JonShapeShift
    Jon ShapeShift (@JonShapeShift) reported

    @lorenzodoteth @SlackHQ Having same issue, driving me nuts

  • ItsPatrickU
    PatrickUllrich (@ItsPatrickU) reported

    @karrisaarinen @linear @SlackHQ Linear coding agent when? 👀 currently handing it off to another service but be nice to skip the extra step.

  • mavexpress1
    Mav (@mavexpress1) reported

    @SlackHQ you need to look into your app. The whole communication functionality is terrible, and it Lags alot

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

    7:30a Getting eMail down to zero. Planning out my day in Google Calendar. Loading the team in @SlackHQ with today's website production and support.

  • iamTRA
    Rohan (@iamTRA) reported

    Slack upload API down? @SlackHQ Cratered team's morning.

  • mikvjpev
    Ekim (@mikvjpev) reported

    @RealFeatBit @SlackHQ Have the same issues. Our workspace doesnt exist anymore

  • alvaisy
    Awais alwaisy (@alvaisy) reported

    @adilmania @SlackHQ what's wrong with slack. bunch of alternatives. each one made money. slack is still stable and useful. i don't have any issue with slakc except limited message history for free users

  • kanute
    Liger Wealth Management (@kanute) reported

    Thinking about ditching @SlackHQ just because unfurling sucks so bad. Seems like this has been an issue for years. Spent way too much time trying to get reliable unfurling when my @openclaw bot posts.

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

Check Current Status