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
Brest, Brittany 1
Ródos, South Aegean 1
Belo Horizonte, MG 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:

  • mikvjpev
    Ekim (@mikvjpev) reported

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

  • jorilallo
    Jori Lallo (@jorilallo) reported

    @pizzaboy @karrisaarinen @SlackHQ It's still the same agent with capability to access everything as the caller user can. If you're calling it in the channel, it has that as context so it will file issue into the project by default and answer questions about the project without you needing to name it separately. If there's situatons where it's not working as intended, would love to get screenshots

  • openfort_hq
    Openfort (@openfort_hq) reported

    @aseemk @SlackHQ hey can you send us a dm and we'll try to fix this>

  • hollowvox
    Jose Urquiza (@hollowvox) reported

    We're about to start letting our employees fix their own bugs with @v0 and @SlackHQ. Why report a bug to another system when you can send it straight to v0? All I have to do is review the PR and merge it in. So confident in the models and the platform that I can go hands off.

  • heathermhuang
    heatherm.eth (@heathermhuang) reported

    @SlackHQ need urgent help our active Slack workspace suddenly got deleted.

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

  • jason_alco
    Jason Alco (@jason_alco) reported

    @SlackHQ Our team loves the platform, but we really need to fix the mark unread feature. It’s been broken for years now. First, you should be able to mark a channel as unread without opening the channel and selecting a message. Second, half the time marking a message as unread doesn’t work. I have to go message by message, trying over and over until one works. Please fix this, thank you 🫠

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

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

    6:30a Getting eMail down to zero. Planning out the work, so I can work out the plan. Loading support and production into @SlackHQ.

  • CarolinaLaLopez
    Caro (@CarolinaLaLopez) reported

    The @SlackHQ glitch in notification numbers is killing my vibe this morning

  • 67steinip
    Steini (@67steinip) reported

    @kitayoshi_son @SlackHQ We've sent 2 emails so far nothing, they arent going to respond to you because this is a MASS event, you arent alone, we didnt even get the email people talk about and some others say that as well, we just got wiped. I don't think they will help you.

  • AzmyBlog
    Azmy (@AzmyBlog) reported

    @lennysan @SlackHQ @aunder The strobe light thing is so real. The person presenting has been inside the problem for weeks. The reviewer walks in cold. And it's not really a flaw in the exec ..... it's just structural. That gap exists at every level in every review setting. The actual skill is learning to rebuild context for the reviewer quickly, instead of assuming they're already there with you.

  • rodrigoberriel
    Rodrigo Berriel (@rodrigoberriel) reported

    @thdxr @SlackHQ unbelievable right? terrible ux

  • asifmghafoor
    Asif (@asifmghafoor) reported

    Hi @SlackHQ out workspace (Spacious) has been deleted by mistake - no notification or emails or anything. We need this restored with history. Can someone please help? We have sent several support requests over the past few hours and no one has responded

  • bkwebster
    Brandon Karl Webster (@bkwebster) reported

    @adilmania @SlackHQ Better alternatives exist - it’s used abundantly because of the mindshare and scale. The only replacement would be a totally new and obvious form factor that leads to the same outcome in a better way - not a better alternative to the same problem.

Check Current Status