Slack status: messaging issues and outage reports
No problems detected
If you are having issues, please submit a report below.
Full Outage Map
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.
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.
At the moment, we haven't detected any problems at Slack. Are you experiencing issues or an outage? Leave a message in the comments section!
Most Reported Problems
The following are the most recent problems reported by Slack users through our website.
- App Crashing (33%)
- Messaging (33%)
- Connection (22%)
- Sign in (11%)
Live Outage Map
The most recent Slack outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 New York City
|
App Crashing | 10 days ago |
 Brest
|
Connection | 30 days ago |
 Ródos
|
Messaging | 2 months ago |
 Belo Horizonte
|
Connection | 2 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:
-
Signal House (@SignalHouseSMS) reported@SlackHQ @notion the only repetitive question saved here that matters is 'is the otp service still down.' second only to 'is the otp service still down for everyone or just me'
-
TheHardTruth (@Watching1776) reported@SlackHQ You need to fix that app so it stops putting people into Auto Silence repeatedly without touching anything. Your code is trash
-
Caro (@CarolinaLaLopez) reportedThe @SlackHQ glitch in notification numbers is killing my vibe this morning
-
Savi (@SaviPabla) reported@trq212 Please @SlackHQ help us. I’m so tired of telling ppl to download. I’ve now started making videos of the html files and then sharing file as well lol
-
mr.tipton (@mrtipton_art) reported@pizzaboy @SlackHQ Nah, I’m that guy. Gotta fix it
-
trent.sol (@trentdotsol) reported@cavemanloverboy @alessandrod @SlackHQ i did. it's the ones who won't that are the problem
-
TT 😋 (@MotivatingPeng) reported@OpenAIDevs @googledrive @SlackHQ Can we fix Codex.... When it does a context automatically compacted it stops what its doing
-
Razi Ansari (@RaziAns14640044) reported@SlackHQ should fix the UX of their video player. It's one of the worst pieces of UX I've ever interacted with. It feels like I suddenly landed on some government app. Too messy
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported8:30a Loading up the team in @SlackHQ and getting eMail down to zero. Planning out the day, so I can work out the plan.
-
noah (@noahsolomon) reported@hiiinternet @SlackHQ It’s a big problem actually
-
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
-
KRYTOS (@CSO_Krytos) reported@Cal_Irvine @thdxr @SlackHQ threads are terrible
-
Sen Yang (@undefined_blog) reportedour slack workspace has been deleted for no reason, no nofication nor verification, please reach out and help @SlackHQ
-
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.
-
Chimene | Dantown (@AgentC_006) reported@thdxr @SlackHQ It’s always weird that you cannot actively reply to messages on Slack. The experience feels broken.
-
RyanMeyer (@RyanDMeyer) reported@jedcli @SlackHQ HK company, US billing. suddenly shut off and Slack has zero customer service. No phone number, no live chat, nothing... submit an email and wait and pray apparently. What ********.
-
Adil Mania. (@adilmania) reported@NebulaAI @safizaq @SlackHQ discord integration is kinda broken, like i keep having "nebula" links showing, if you can fix that, that will be perfect.
-
rushikesh (@ivadapav) reported@SlackHQ down. What's next?
-
Ravi (@ravilutionx) reported@SlackHQ @trq212 And a verbosity problem
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported7:30a Getting email down to zero and loading both the website support and production teams in @SlackHQ.
-
Fluorine (@FluorineHQ) reported@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.
-
Johan Cutych (@johancutych) reportedfirst you need to fix the rate limits @SlackHQ
-
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?
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported7:30a Getting eMail down to zero and loading up the team in @SlackHQ.
-
Kleptocracy (@lfdoyfydoydtd) reported@salesforce @SlackHQ Instead of buying other crappy software companies, create the best sales rep. SFDC 1.0>2.0>3.0... ITS ALL SO BROKEN. Broken company that had a chance to replace salespeople but didn’t use the data and systems they already had to make it happen with agents. WTF is agentforce?
-
Rohan (@iamTRA) reportedSlack upload API down? @SlackHQ Cratered team's morning.
-
Ash (@edweirdsnowman) reported@SlackHQ slack huddles has had video audio sync issues since it’s been launched. Please deploy at least 7 agents to fix this immediately.
-
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 🫠
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported6a Getting eMail down to zero, loading up the team is @SlackHQ. Planning the day, so I can work the plan.
-
Jon Slemp (@Jon_Slemp) reportedBug report for you @SlackHQ — when receiving a DM notification from Agents, and those agents are setup as Slack apps you have to DM directly in an app channel, once you hit a certain number of chats in your history tab you can no longer navigate to the DM directly by clicking the DM notification on mobile. You basically get navigated to a blank screen and effectively chat find the message ever. Please fix. This is a disaster of a bug.