Slack status: messaging issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Slack reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Slack users through our website.

• App Crashing (33%)
• Messaging (33%)
• Connection (33%)

Live Outage Map

The most recent Slack outage reports came from the following cities:

City	Problem Type	Report Time
New York City	App Crashing	18 days ago
Brest	Connection	1 month ago
Ródos	Messaging	3 months ago
Belo Horizonte	Connection	3 months ago
Jewar	App Crashing	3 months ago
Colorado Springs	Messaging	3 months ago

Full Outage Map

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:

• 
  Karri Saarinen (@karrisaarinen) reported 10 minutes ago

  @gustaf @ycombinator @SlackHQ I’d say Slack. Haven’t really experienced those issues you mention. Unless my internet is very bad. iMessage/whatsapp overly phone and counterparty focused so I’m more often wondering if the message actually got delivered or not and if the problem is me or them. Slack is more of a server and it doesn’t send the message if it doesn’t work.

• 
  jimmy hackett (@j1mmyhackett) reported 14 minutes ago

  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?

• 
  Agustín Ruiz (@aguscruiz) reported 15 minutes ago

  Hi @SlackHQ, can you please fix this notification dot issue? It's been bothering me for like a month or more already. It shows that I have something unread when I don't. Even hovering on it makes the dot go away when there's something unread. It's very annoying for people with "unread anxiety" like me lol. Thank you 🫶

• 
  Richard Casimir (@NWFreeZone) reported 20 minutes ago

  @xsupport @slackHQ X links on slack (android) Still not working. All other sites redirect properly from slack. Just NOT X.

• 
  JM (@merklejosh) reported 21 minutes ago

  @SlackHQ There seems to be a bug in your Version 4.50.140 app (Mac) where if you have open a New message and you try to then click in the Search bar, you can't – it just flashes. Can you please fix this. It's very annoying. Thanks!

• 
  noah (@noahsolomon) reported 24 minutes ago

  @hiiinternet @SlackHQ It’s a big problem actually

• 
  Leon (@MozzyFX) reported 25 minutes ago

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

• 
  Antonio Ventre (@antonioventre_) reported 27 minutes ago

  @resulvol @RealFeatBit @SlackHQ Sure guys anyone who need help can text be and they’ll restore your access for 30 days so you can still work on the account while the migrate

• 
  Cathryn (@cathrynlavery) reported 27 minutes ago

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

• 
  Alex Oppenheimer (@Alexoppenheimer) reported 27 minutes ago

  @SlackHQ I can't login to even contact support. I am in an infinite 2FA loop. And I am being overcharged. Needless to say, I am not happy.

• 
  Captain (@Cap039) reported 28 minutes ago

  @SlackHQ One recent Slack regression: If you edit a post that contains a link, the link preview disappears. Please fix this 🙏

• 
  Johan Cutych (@johancutych) reported 29 minutes ago

  first you need to fix the rate limits @SlackHQ

• 
  🇹🇼 Phillip Haydon 🇹🇼 (@philliphaydon) reported 32 minutes ago

  Its really disappointing that @SlackHQ status page suggests its up, when it's clearly down and you can get up to date status from X users who are reporting the same issues.

• 
  Taksh Shah (@takshshahh) reported 32 minutes ago

  Someone at @SlackHQ needs to fix how they deal with markdown. Its markdown but not really? Pasting stuff from elsewhere sometimes preserves formatting, sometimes doesnt? I had to do workarounds when working with API, but pasting content from claude in the messagebox is terrible

• 
  Jori Lallo (@jorilallo) reported 32 minutes ago

  @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

• 
  Vortex (@mjparme) reported 33 minutes ago

  @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

• 
  Riley Read-Only (@HotForMoot) reported 33 minutes ago

  Cmon @SlackHQ help the tfr

• 
  HOURLY LIFE of Fred Campos (@FredsDaily) reported 38 minutes ago

  6a Getting eMail down to zero, loading up the team is @SlackHQ. Planning the day, so I can work the plan.

• 
  Q (@quionie) reported 39 minutes ago

  @thdxr @SlackHQ ohhh i’m so down for this because this would be MUCH better lol

• 
  Jimidate (@Jimidvte) reported 43 minutes ago

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

• 
  HOURLY LIFE of Fred Campos (@FredsDaily) reported 45 minutes ago

  7:30a Getting eMail down to zero and loading up the team in @SlackHQ.

• 
  Rodrigo Berriel (@rodrigoberriel) reported 47 minutes ago

  @thdxr @SlackHQ unbelievable right? terrible ux

• 
  A-Yo! despises APC (@AyomideAdenowo1) reported 47 minutes ago

  @daniielezeh @SlackHQ Bruhhh, valid question 😭 I've been having issues with the ******* video playback. I didn't even know it was possible to have worse video playback than twitter.

• 
  TT 😋 (@MotivatingPeng) reported 50 minutes ago

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

• 
  Chris Munns (@chrismunns) reported 54 minutes ago

  somehow @SlackHQ filtering of channels/DMs for last 30 days active hasn't worked for me for months. is this just a broken feature or have I done a thing.

• 
  Fluorine (@FluorineHQ) reported 54 minutes ago

  @gustaf @SlackHQ Reliability is the floor, not the ceiling. Slack hit the floor and is now adding notification noise to mask it — classic engagement-metric trap. The deeper issue: messaging apps stopped being where work happens and became where work gets talked about. That's the gap worth solving.

• 
  HOURLY LIFE of Fred Campos (@FredsDaily) reported 55 minutes ago

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

• 
  Rab Memari (@rabmemari) reported 55 minutes ago

  @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

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

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

• 
  LANGERIUS (@Langerius) reported 59 minutes ago

  @BarknTuncer @SlackHQ yeah notification sync issues are still surprisingly common