Is Slack down?

Problems in the last 24 hours

Slack signals over the past 24 hours. The dashed line is the service-wide baseline used to detect unusual activity.

• Service-wide signals
• Service-wide baseline

Most Reported Problems

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

• App Crashing (40%)
• Messaging (20%)
• Connection (20%)
• Video (20%)

Live Outage Map

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

City	Problem Type	Report Time
Township of Evan	Messaging	14 days ago
Township of Evan	App Crashing	15 days ago
Guayaquil	Video	20 days ago
New York City	App Crashing	2 months ago
Brest	Connection	2 months ago
Ródos	Messaging	4 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:

• 
  Krazed 🇵🇸 (@Krazed) reported 4 minutes ago

  @SlackHQ you have a degradation rn? unable to create channels and getting intermittent issues with events

• 
  Teo Vanyo Adiputra (@teostealth) reported 11 minutes ago

  @karrisaarinen @SlackHQ The handoff from Slack discussion to actual tracked issue is where most teams drop the ball - keeping that loop tight is harder than it sounds.

• 
  Element **** (@elementdsj) reported 12 minutes ago

  @SlackHQ @vercel debugging a broken deployment directly from a chat thread is actually beautiful.

• 
  Luke Hutchison (@LukeHutchison) reported 15 minutes ago

  Why we're SaaSmaxxing at Perfect Venue Three months ago I tried vibe coding our way out of half our SaaS stack and racked up a $20k Replit bill. Now we are doing the opposite, doubling down on our existing vendors and adding more to our stack. It started small. A better prospecting tool built in Replit. ICP scoring, competitor signals, enrichment. It "worked," and that was the problem. I could come up with an idea and within minutes a version that "worked" was in front of me. It was a lot of fun at first. Once you see how fast you can build exactly what you want, scope creeps hard. Within weeks I was eyeing our ATS, our feedback board, and parts of HubSpot. Part of me also wanted to try vibe coding because when you're leading a company where "apocalypse" is being added to your industry category, I thought it would be good to know if it was a real threat or just hype. We sell software to restaurants and venues. Homegrown spreadsheets and internal tools have always been our biggest competitor, long before AI. So the real question wasn't "can you build your own?" It was: has that math actually shifted, or does it just feel like it has? But then reality set in. I was quickly reminded of the saying in engineering that "the first 90% of a project takes 90% of the time, and the remaining 10% takes another 90% of the time." Getting a demo working was fast, but feature requests and bugs quickly piled up. Obviously we could put the feature requests in the icebox, but that defeats one of the main goals of custom software: being able to customize it to your business. The problem is that customization requires a customizer. Every field and edge case routed through one person. Me. Next, we explored having an engineer work on building a more sustainable solution. However, the direct cost of that engineer working on an internal tool was much higher than all of our SaaS spend combined. The indirect cost was even higher, because it meant that engineer was not working on our core product and building features that could drive much more revenue than the costs they would be able to reduce, not to mention stronger market positioning. There were also other indirect costs. I was interviewing for a recruiting role and explaining to her that we were moving off Ashby to a vibe coded tool. As soon as the words came out of my mouth, I could tell that decision was a bug and not a feature. The reality is that people have worked with many popular SaaS tools for years. They may not love them, but they know how to work with them, and they can focus on doing their job instead of being a design partner for a vibe coded tool. Another challenge was that growth meant building. Even if we were able to build and maintain a custom solution, it was just for a point in time. As the team and company grew, we needed new functionality. With a SaaS vendor, it is very rare that we would need something they didn't already have. They've been solving for the needs of thousands of businesses for years, it's rare we would really need something that another one of their customers had not come across before. Often we'd have to pay more, but it was as simple as a quick upgrade. With a vibe coded solution, it meant understanding the problem, designing and building a solution, and then maintaining it. So where are we today? We're SaaSmaxxing. We're getting everything we already paid for out of the tools we already have - here is how we're doing it. Use AI to better use our SaaS tools. Instead of seeing the problem as AI vs. SaaS, we're using AI to help us better use the tools we have. One of the most frustrating things about SaaS products is that they can be complex and hard to use, with settings buried and functionality hidden. Help centers only go so far. With Claude, I'm able to explain what I'm trying to do, and it can help me configure our existing tools or find a product that integrates with our existing software and solves the problem. Use vibe coding to prototype functionality we wish we had. When there is functionality that we wish we had with our vendors, we'll vibe code a prototype and then find ways to recreate that functionality with our existing tools. Take the 80/20 and move on. Almost every improvement we wanted had a good-enough version in a product we already paid for. Solving for the last 20% was far more expensive than it was worth. Clearly define the problem. As a business owner, my problem was that it was frustrating to log into all of these different tools to understand what was going on with my business. I now use a tool called Viktor to easily pull information across all of our different tools and send reports to me in Slack. File the feature request. Their roadmap is free engineering. A vendor building it once for a thousand customers beats me building it once for us. Has the build-versus-buy line moved? Yes. Building the feature list is dramatically cheaper than it was two years ago. But the feature list was never the expensive part. Owning it is. For the vast majority of our vendors, the amount we pay is a fraction of the value we get, even in the AI era. Our industry is changing faster than ever, and who knows what functionality new models will bring, but this is where we've landed for now. We're buying @HubSpot, @SlackHQ, Canny, Ashby, etc - and focusing on building Perfect Venue faster than ever with the help of AI. Great work @dharmesh and team on the continued updates!

• 
  Evis Drenova (@evisdrenova) reported 16 minutes ago

  @sbilstein @SlackHQ yeah to your earlier point i think it depends at what layer you want to attack it i.e. rust builds are slow, caching can help but github actions is trash for it, but blacksmith isn't bad, is there a generic solution you can use that *just works* on any CI? alternatively, go after the actual docker execution layer but not clear to me how much of a bottleneck that actually is vs. language specific idiosyncrasies buildkit is pretty optimized from what i've heard but i generally agree with make it fast and stupidly easy to use!

• 
  Ash (@edweirdsnowman) reported 18 minutes ago

  @SlackHQ slack huddles has had video audio sync issues since it’s been launched. Please deploy at least 7 agents to fix this immediately.

• 
  Ravi (@ravilutionx) reported 20 minutes ago

  @SlackHQ @trq212 And a verbosity problem

• 
  Rahul Chetia (@ayoImNotTrippin) reported 22 minutes ago

  @SlackHQ there’s a widespread issue with slack today. Not sure about Mac but my entire team with windows seems to be impacted. Slack becomes irresponsive on windows a few minutes in. Tried ‘repair’ and force close, but no help there. We are using app in our phones to communicate.

• 
  Bad **** (@TeaseTech) reported 23 minutes ago

  @thdxr @SlackHQ What's the problem?

• 
  Mohammad Romman (@MohammadRoman8) reported 24 minutes ago

  @SlackHQ are you guys shutting down? It’s been more than a week I’ve been contacting you guys. Support isn’t responding at all

• 
  mewc (@the_mewc) reported 27 minutes ago

  @SlackHQ lots of bugs and issues right now. Can't create channels and lots of jankyness. This release is a lot.

• 
  ImagineArt (@ImagineArt_X) reported 27 minutes ago

  @SlackHQ @SlackHQ cute, but can you fix the "copying emojis from slack to somewhere else please"

• 
  Georg S. Kuklick (@downtownberlin) reported 28 minutes ago

  @SlackHQ @linear Then fix your MCP server!

• 
  Ari Dehkordi (@arashdehkordiHQ) reported 29 minutes ago

  @karrisaarinen @SlackHQ Did Linear do this before agents? I tried project-level Slack channels at my org and found it works for enterprise engagements nicely, but breaks down at feature/epic level projects for our SaaS. There's a granularity sweet spot, too fine and context switching costs spike. Too coarse and projects blur. Plus no project is actually isolated in small teams, so cross-project conversations forced more people onto each channel and productive engagement suffered. I get the AI context-confinement angle, but curious what other benefits you're seeing?

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

  7:30a Back home, getting the boys up, getting eMail down to zero, loading the team up with today's support and production website work (in @SlackHQ).

• 
  Sammie (@nexgencoded) reported 34 minutes ago

  @SlackHQ really said what if your coworker wasn't annoying enough?? now you can add an AI coding agent to the group chat @Claude fix this 30 seconds later claude: PR opened greg from accounting: why is there a PR claude: I have no idea who Greg is....

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

  8:30a Back at my desk, loading the team up in @SlackHQ with today's assignment, getting eMail down to zero.

• 
  Otto Hilska (@mutru) reported 35 minutes ago

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

• 
  Vish (@vish_sh_) reported 40 minutes ago

  @SlackHQ Slack bot requires a proper fix first.

• 
  Sam Pullara (@sampullara) reported 40 minutes ago

  @thdxr @SlackHQ No one wants all replies to show up in the channel. It is a terrible defauu.

• 
  Brad Beckett (@bradbeckett) reported 40 minutes ago

  With how much sensitive data @SlackHQ stores, it's surprising they don't yet support Passkey login or have a BIMI email verification certificate so their legitimate emails get a blue verified check mark in major email service providers. @digicert pls reach out to them!

• 
  Taha Tesser (@TahaTesser) reported 41 minutes ago

  @KhalidWarsa @SlackHQ Because each workspace has own login. Even if you login on one device. You cannot sync all those workspaces under one account on another device

• 
  y - alex ⚔️ (@onelonesabre) reported 43 minutes ago

  @SlackHQ @question_base can't use these features when your app is down my friend

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

  6:30a Back at the home office. Getting eMail down to zero. Planning the day so I can work out the plan. Passing work into @SlackHQ.

• 
  🇹🇼 Phillip Haydon 🇹🇼 (@philliphaydon) reported 47 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.

• 
  wanderingwanderer (@iceman_ome) reported 53 minutes ago

  .@SlackHQ and @Jira have the weirdest integration possible. Have spent the last 15 mins trying to remove jira app from Slack, but unable to. Can someone more knowledgeable help?

• 
  Theodor Marcu (@theodormarcu) reported 55 minutes ago

  Putting an agent in Slack creates a very different UX problem: it has to know when to shut up We spent a lot of time tuning when Devin should speak, stay quiet, or move work into a separate channel. Devin was the first agent to support Slack natively, so it was great to bring 2 years of those learnings to @SlackHQ for the Slack Code launch.

• 
  Leon (@MozzyFX) reported 57 minutes ago

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

• 
  knut (@kmelve) reported 58 minutes ago

  Now that @SlackHQ Code is a thing, will they finally ship Glitch out of flash?

• 
  Uday Subbarayan (@udaysubbarayan) reported 59 minutes ago

  @SlackHQ Pl don’t hide the URL’s. Your recent overdoing here is creating problems Thanks