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
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:
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 |
|---|---|
| Ródos, South Aegean | 1 |
| Belo Horizonte, MG | 1 |
| Jewar, UP | 1 |
| Colorado Springs, CO | 1 |
| South Point, Mont Fleuri | 1 |
| Bismarck, ND | 1 |
| Noida, UP | 1 |
| Greater Noida, UP | 1 |
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:
-
Dan Mazy (@danmazy1) reported@SlackHQ I'm the sole owner of a paid workspace. Changed my number + email, so recovery doesn't work. I can verify via billing/credit card. Support can't help. Can't log in, can't add employees. There has to be a manual verification process. Please escalate.
-
Giuseppe Skyline (@giskyexplorer) reported@gustaf @SlackHQ Notifications are the bandaid for broken reliability. WhatsApp stays quiet because it works.
-
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.
-
Rushabh Shah (@beingrushabh07) reportedHi @SlackHQ, I’ve been unable to launch or load the iOS app for the past few hours. I have already tried logging out and back in, as well as a full uninstall and reinstall, but the issue persists. This is significantly impacting my work could you please look into this?
-
Jon ShapeShift (@JonShapeShift) reported@lorenzodoteth @SlackHQ Having same issue, driving me nuts
-
Abhishek (@abhi__katiyar) reported@peduarte @SlackHQ Mental model to help people make right choices “all your communication will become public record if your company gets subpoenaed”
-
Aadii (@AadityaPasayat) reported@raidingAI @SlackHQ @slashyai I am sorry to say, but u don't have taste, either the editor. R eyes go from left to right, common sense. Btw I can help u get taste
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported7:30a Getting eMail down to zero. Planning out my day in Google Calendar. Loading the team in @SlackHQ with today's website production and support.
-
Wouter Witvoet (@wwitvoet) reported@SlackHQ Been trying to migrate to Slack Enterprise Grid since January 28, only get non-descriptive errors and can't get anyone from your team on a Zoom for 15 mins to do the config. No help from support apart from reiterating the same URLs for SAML. What can you do to help?
-
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.
-
Kevin (@kevin0connell) reported@SlackHQ I can also replicate this problem
-
Taksh Shah (@takshshahh) reportedSomeone 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
-
Riley Read-Only (@HotForMoot) reportedCmon @SlackHQ help the tfr
-
A-Yo! despises APC (@AyomideAdenowo1) reported@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.
-
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