Slack outages and problems
User reports, last 24 hours
16 reports in total, counted in 15-minute windows
No problem reports came in for Slack in the last hour, and at this time of day there are usually almost none. Over the last 24 hours there were 16 reports. Worldwide, most recent reports were about app (65%) and website (12%). The last spike in reports was 42 h ago and lasted 19 min. These are user reports from the US, where most people report Slack problems.
Around the world right now: normal in 71 other countries. By country
- NormalClose to the usual level24 h · 16 reports
- ElevatedMore than 1.5 times the usual levelNone in this chart
- OutageMore than twice the usual level and far above the day's averageNone in this chart
- Usual levelWhat a usual day sees at that timeAlmost none at this time of day
In the past 24 hours, 16 user reports came in for Slack. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.
The busiest 15-minute window had 3 reports, about 18 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
Slack in November 2026
- Problem reports in November
- 4,892
Monthly report for November 2026
What went wrong
What people said was wrong in recent problem reports for Slack worldwide.
Share of 17 recent reports that said what was wrong, from every country listed below.
Slack reports around the world
In the last 24 hours, 52 problem reports about Slack came in from 7 countries. Right now reports are at the usual level in every country.
- Outage now
- Problems now
- Normal
| Country | Now | Last hour | 24 hours |
|---|---|---|---|
| The US numbers above | Normal | 4 | 42 |
| The UK | Normal | 0 | 2 |
| Canada | Normal | 0 | 2 |
| The Philippines | Normal | 0 | 2 |
| Paraguay | Normal | 0 | 2 |
| Mexico | Normal | 0 | 1 |
| Saudi Arabia | Normal | 0 | 1 |
| Germany | Normal | 0 | 0 |
| Australia | Normal | 0 | 0 |
| The Netherlands | Normal | 0 | 0 |
| France | Normal | 0 | 0 |
| Poland | Normal | 0 | 0 |
Each country's status compares its reports with the usual level there. 60 more countries had 0 reports in the last 24 hours. Map outlines: Natural Earth.
Slack problem spikes, last 30 days
In the last 30 days, Slack had 13 outage spikes and 10 periods of elevated reports. The longest lasted 6 h 44 min, on 12 November.
- Sat 24 Oct: 0 reports
- Sun 25 Oct: 0 reports
- Mon 26 Oct: 0 reports
- Tue 27 Oct: 0 reports
- Wed 28 Oct: 31 reports
- Thu 29 Oct: 69 reports
- Fri 30 Oct: 66 reports
- Sat 31 Oct: 12 reports
- Sun 1 Nov: 8 reports
- Mon 2 Nov: 64 reports
- Tue 3 Nov: 71 reports
- Wed 4 Nov: 83 reports
- Thu 5 Nov: 68 reports
- Fri 6 Nov: 78 reports
- Sat 7 Nov: 11 reports
- Sun 8 Nov: 7 reports
- Mon 9 Nov: 91 reports
- Tue 10 Nov: 61 reports
- Wed 11 Nov: 845 reports (outage spike that day)
- Thu 12 Nov: 975 reports (outage spike that day)
- Fri 13 Nov: 598 reports (outage spike that day)
- Sat 14 Nov: 89 reports
- Sun 15 Nov: 25 reports
- Mon 16 Nov: 409 reports (outage spike that day)
- Tue 17 Nov: 528 reports (outage spike that day)
- Wed 18 Nov: 406 reports (outage spike that day)
- Thu 19 Nov: 264 reports (outage spike that day)
- Fri 20 Nov: 180 reports (elevated reports that day)
- Sat 21 Nov: 29 reports
- Sun 22 Nov: 2 reports
-
Elevated reports
Fri 20 Nov, 18:01–18:20Lasted 19 min11peak reports
-
Outage
Thu 19 Nov, 21:45–23:21Lasted 1 h 36 min17peak reports
-
Outage
Thu 19 Nov, 18:34–19:10Lasted 36 min19peak reports
-
Elevated reports
Thu 19 Nov, 17:01–17:50Lasted 48 min11peak reports
-
Outage
Thu 19 Nov, 15:50–16:37Lasted 47 min14peak reports
-
Elevated reports
Wed 18 Nov, 23:10–23:31Lasted 21 min11peak reports
-
Elevated reports
Wed 18 Nov, 22:23–22:42Lasted 20 min10peak reports
-
Outage
Wed 18 Nov, 20:55–21:22Lasted 28 min12peak reports
15 earlier spikes in this period.
By country
In the last 20 days, most Slack problem reports came from the US (4,965), Japan (609) and the UK (532). The US had the most days at outage level: 7 of 20. The latest outage spike was on Thursday 19 November, in the US.
- The US7 outage days4,965
- Japan1 outage day609
- The UK2 outage days532
- Canada1 outage day326
- IndiaNo spikes229
- AustraliaNo spikes193
- BrazilNo spikes137
- Germany1 outage day109
- Outage spike
- Elevated reports
- Normal
- No data yet
Each square is one day. It turns red when reports stayed at outage level for half an hour or more, and amber when they stayed above the usual level for an hour or more. The number on the right is the country's total since 3 November 2026, when country history starts. A wider gap marks a Monday. Point at a square, or tap it, for that day's numbers. Days run from midnight to midnight, Central European time.
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. Monthly reports for all services
How to fix Slack not working
Slack is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach slack.com over your own connection, right now. Nothing is sent to us or stored.
Reload the window
Press Ctrl+R on Windows or Linux, Cmd+R on Mac; that reloads the interface without signing you out, and it clears a sidebar stuck on a spinner or a message box that will not send. If the whole app feels frozen, quit it from the menu and open it again. Ten seconds, usually enough.
Check which workspace you are in
Click the workspace name at the top left. A wrong account makes channels, DMs and saved items look like they vanished, and messages you send land somewhere you are not reading. Sign out from that same menu and sign back in to reset the session for that workspace only.
Clear the local cache
On the desktop app, open Help > Troubleshooting > Clear Cache and Restart. The app rebuilds its local copy of messages and files, which fixes search results that come back empty and calls that hang while connecting; expect a slow first minute on a large workspace. Check the official status page at https://slack-status.com/ before you go further, because a service-wide problem will not respond to anything on your machine.
Rule out your network, then reinstall
A VPN, corporate proxy or firewall can block the connection the app holds open, so switch to a phone hotspot and see whether it connects; if it does, the problem is on your network, not in the app. When a clean network fails too, uninstall the desktop app and install it again, and look through the help centre at https://slack.com/help for account-level fixes such as a workspace that needs an admin to restore access.
While Slack is down: what to use instead
- Microsoft Teams Teams helps if your company already runs Microsoft 365, because channels and calls stay available there.
- Google Chat Google Chat fits a Google Workspace team that needs direct messages and rooms, so it covers quick coordination while Slack is out.
- Discord Discord works for a small group that needs voice and text, though it is a separate space from work.
- Email Email works when Slack does not.
Fix Slack on Windows, Mac, Android and iPhone
Slack on Windows
- Fix
- Clear the Slack desktop app cache by going to Help > Troubleshooting > Clear Cache and Restart. If you are using the web version, try clearing your browser's cookies and temporary files.
- Check
- Check if the Slack Windows app displays a 'Connecting...' banner at the top of the window. You can also visit the official Slack Status page to see if there is a known service outage.
ping slack.comTest whether Slack's servers replynslookup slack.comCheck that Slack's DNS resolvestracert slack.comTrace where the connection dropsipconfig /flushdnsClear the DNS cache, then reloadSlack on Mac
- Fix
- Force quit the Slack app by pressing Option-Command-Esc, then relaunch it. If the issue persists, clear the app cache from the Help menu or temporarily disable any active VPNs.
- Check
- Look for a persistent loading spinner or connection error message within the Slack Mac app. Alternatively, try accessing Slack through Safari or Chrome to rule out a desktop client issue.
ping -c 4 slack.comTest whether Slack's servers replynslookup slack.comCheck that Slack's DNS resolvestraceroute slack.comTrace where the connection dropssudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reloadSlack on Android
- Fix
- Go to Settings > Apps > Slack > Storage and tap 'Clear Cache'. If Slack still won't load, check the Google Play Store to ensure you have the latest version of the app installed.
- Check
- Open the Slack app and see if you receive a 'Connecting' notification at the top of your chat list. You can also test if Slack works on mobile data instead of Wi-Fi to rule out local network issues.
Slack on iPhone and iPad
- Fix
- Force close the Slack app by swiping up from the bottom of your screen and sliding the app preview away, then reopen it. If that fails, delete and reinstall Slack from the App Store.
- Check
- Check if Slack shows a 'Connecting' spinner at the top of your channel list on your iPhone or iPad. You can also check if other internet-reliant apps are functioning normally on your device.
Biggest Slack problems so far
-
1
422reports in 15 min
-
2
101reports in 15 min
-
3
OutageLasted 2 h 27 min32reports in 15 min
Ranked by the most problem reports in one 15-minute window. Our archive started on 5 October 2026, so earlier problems are not counted. Times are Central European time.
Problems at the same time as Slack
In the last 30 days, all 23 of Slack's spikes in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
Most often at the same time
- ADP23 times
- Microsoft Copilot23 times
- Microsoft Outlook22 times
- Zelle22 times
- Microsoft 36522 times
- Microsoft Store22 times
How many of Slack's spikes overlapped one of theirs.
During the latest spike
Slack: Fri 20 Nov, 18:01 to 18:20
- Microsoft Outlook, outage,12 Nov 17:42 to 21 Nov 13:37
- PlayStation Network, outage,17 Nov 09:05 to 21 Nov 01:17
- Belastingdienst, outage,04:43 to 19:52
- Salt, outage,06:59 to 23:55
- Xfinity by Comcast, outage,07:23 to 19:38
- Unibet, outage,08:14 to 19:53
- 32Red, outage,09:27 to 19:52
- Chase, outage,11:43 to 21 Nov 06:50
97 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
When people report Slack problems
The busiest hour for reports about Slack is 18:00 to 19:00 Central European time, and the busiest day is Wednesday.
By hour of the day
- 00:00 to 01:00: 2.2 reports on an average day
- 01:00 to 02:00: 1.6 reports on an average day
- 02:00 to 03:00: 1.4 reports on an average day
- 03:00 to 04:00: 1.5 reports on an average day
- 04:00 to 05:00: 0.65 reports on an average day
- 05:00 to 06:00: 0.89 reports on an average day
- 06:00 to 07:00: 0.63 reports on an average day
- 07:00 to 08:00: 0.73 reports on an average day
- 08:00 to 09:00: 0.22 reports on an average day
- 09:00 to 10:00: 0.24 reports on an average day
- 10:00 to 11:00: 0.23 reports on an average day
- 11:00 to 12:00: 0.28 reports on an average day
- 12:00 to 13:00: 0.6 reports on an average day
- 13:00 to 14:00: 1.4 reports on an average day
- 14:00 to 15:00: 3 reports on an average day
- 15:00 to 16:00: 4.2 reports on an average day
- 16:00 to 17:00: 4.3 reports on an average day
- 17:00 to 18:00: 5.6 reports on an average day
- 18:00 to 19:00: 6.2 reports on an average day
- 19:00 to 20:00: 5.2 reports on an average day
- 20:00 to 21:00: 4.2 reports on an average day
- 21:00 to 22:00: 3.3 reports on an average day
- 22:00 to 23:00: 2.7 reports on an average day
- 23:00 to 00:00: 2.3 reports on an average day
By day of the week
- Monday: 56 reports on an average Monday
- Tuesday: 54 reports on an average Tuesday
- Wednesday: 91 reports on an average Wednesday
- Thursday: 61 reports on an average Thursday
- Friday: 87 reports on an average Friday
- Saturday: 20 reports on an average Saturday
- Sunday: 6.4 reports on an average Sunday
Each bar is the average number of user reports in that hour, or on that day of the week, from 45 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.
What happens when Slack goes down
Slack is a team messaging app built around channels, direct messages, huddles, and file sharing, and many workplaces run daily coordination through it. An outage interrupts the quick back-and-forth that keeps projects moving, from a one-line question in a channel to a scheduled call.
The first sign is usually a message you cannot send or a channel that keeps loading, while notifications arrive late or not at all. Huddles may fail to connect, and file uploads or app integrations can stop working. Shared channels with outside organizations can break while internal chat still works. Problems are often partial: one workspace or a single region can be affected while other people carry on.
Slack IP address, servers and network
- IPv4 addresses
- 18.159.197.225
Show all 6
- 3.68.124.168
- 3.68.124.95
- 3.68.170.153
- 3.68.175.98
- 52.29.238.212
- IPv6
- Not offered
- Network
- AS16509 · Amazon.com, Inc., registered in the United States
- Served through
- Amazon Web Services
- DNS hosted by
- Amazon Route 53
- HTTPS certificate
- Issued by Let's Encrypt, valid until 5 Jan 2027 (43 days)
- HTTP/3
- Supported
- Our check
- Answered in 216 ms
Checked from our server in Frankfurt, Germany, 41 h ago, for slack.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.
Checked from 12 places around the world
All 12 locations got an answer from slack.com. Fastest from Frankfurt (154 ms), slowest from Los Angeles (2,210 ms). Every location connected through Amazon.com, Inc. (AS16509), using 11 different addresses.
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up | 154 ms | 3.68.124.168 |
| ViennaAustria | Up | 195 ms | 18.159.197.225 |
| MilanItaly | Up | 221 ms | 3.68.124.168 |
| ParisFrance | Up | 164 ms | 18.168.172.238 |
| AmsterdamNetherlands | Up | 187 ms | 3.68.124.95 |
| MadridSpain | Up | 230 ms | 18.134.215.41 |
| WarsawPoland | Up | 271 ms | 3.68.175.98 |
| DallasUSA | Up | 176 ms | 3.143.53.1 |
| Los AngelesUSA | Up | 2,210 ms | 44.234.235.93 |
| São PauloBrazil | Up | 174 ms | 54.94.183.148 |
| SingaporeSingapore | Up · HTTP 302 | 256 ms | 18.136.169.56 |
| TokyoJapan | Up · HTTP 302 | 176 ms | 35.74.58.174 |
Checked with check-host.net from its servers in these cities 41 h ago, for slack.com. Time is how long each server took to load the page.
Slack FAQ
Is Slack down right now?
Why does Slack stay on 'Connecting to Slack' on desktop?
Why are my Slack messages showing a red exclamation mark?
Why do Slack notifications stop arriving on my phone?
Why can't I join a Slack workspace from an invite link?
Why does a Slack huddle or call drop or have no audio?
Service updates from @SlackHQ
No posts about problems from @SlackHQ in the last 14 days. The latest is from .
Contact Slack support
- Official status pageslack-status.com
- Help centreslack.com/help
- Websiteslack.com
- X (Twitter)x.com/SlackHQ
Tip: when Slack is down, its official status page is the quickest way to confirm the cause and see when a fix is expected.
About Slack
- Category
- Team Collaboration
- Founded
- 2013
- Country
- United States
How we track Slack
The status on this page comes from user-submitted problem reports for Slack, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Slack, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. This is separate from Slack's official status page: user reports tend to show a problem early, while the official page confirms the cause. If the two disagree, check both.