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
Jewar, UP 1
Colorado Springs, CO 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:

  • alexandercranga
    Alexander Cranga (@alexandercranga) reported

    /copy from Claude -> paste in Slack -> doesn’t keep the formatting. @SlackHQ please fix

  • undefined_blog
    Sen Yang (@undefined_blog) reported

    our slack workspace has been deleted for no reason, no nofication nor verification, please reach out and help @SlackHQ

  • TeaseTech
    Bad **** (@TeaseTech) reported

    @thdxr @SlackHQ What's the problem?

  • 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

  • Jimidvte
    Jimidate (@Jimidvte) reported

    @SlackHQ, I’m having issues with my mobile notifications. I’ve checked every setting on my phone, uninstalled and reinstalled the app, yet I still don’t receive any push notifications. I’m missing time-sensitive information because I have to open the app before I see any updates.

  • disismohi
    Mohi (@disismohi) reported

    @SlackHQ: 40% less merge queue time, CI type-checking down from 7.5 minutes to 1.25 minutes. Canva: 58s to first error in the editor down to 4.8s.

  • 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? 🤔

  • karrisaarinen
    Karri Saarinen (@karrisaarinen) reported

    @gustaf @ycombinator @SlackHQ What is degrading? WhatsApp imo is not a good example. Can’t even hold login on a desktop, and have to auth with your phone. Sync not super reliable either

  • todotodo17731
    Tabish (@todotodo17731) reported

    @SlackHQ please improve your Software... 70-80% time we face audio issue.. I think your Software in not production Ready... Why ******* companies using such Software... Hello hwllo Hello .. *******... M I Audioable.... Hello can u hear me.

  • alexei_sid
    Alex Sidorenko (@alexei_sid) reported

    @Moore_Irish @salesforce @SlackHQ Pricing changes that reduce admin control while pushing AI features rarely improve outcomes. The real test: does the AI actually help teams make faster, better decisions, or is it just another feature tax masquerading as innovation?

  • nlevin
    Noah Levin (@nlevin) reported

    @SlackHQ mobile unread state bugs continue to be quite a painful and frustrating issue… plz fix 🙏

  • MozzyFX
    Leon (@MozzyFX) reported

    Please @SlackHQ can you add a proper GIF selector I need to send better gifs right after I take down production

  • j1mmyhackett
    jimmy hackett (@j1mmyhackett) reported

    the scariest bugs in an agent system aren't the ones that crash loudly. they're the ones that succeed. quietly. and then stop. and you don't find out for three days. this week i shipped `fix(daily): heartbeat + agent-health for the daily-report jobs` (commit 10c954a). the cron had been running. the launchd plist was registered. no errors in the log. but the report wasn't landing in @SlackHQ. it took me longer than i want to admit to realize the job had silently stopped delivering. no crash, no alert, just absence. the mental model i pulled from it: a job that runs is not the same as a job that works. completion and correctness are two different signals, and most infra only monitors the first one. heartbeats fix this. you instrument the output, not just the process. if the report doesn't land by 8:05am, something fires. you stop trusting the scheduler and start verifying the result. this applies way past cron jobs. any pipeline where you only watch for failure will eventually drift silently into uselessness. the absence of an error is not evidence of health. once i wired heartbeats into the @AnthropicAI-powered agent fleet, i found two other jobs that had the same problem. they looked fine. they weren't. if you're running automated jobs and you're not monitoring outputs, you're not monitoring. what's the longest a silent failure ran in your system before you caught it?

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

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

Check Current Status