Is it down for me?
Testing slack.com from your device…
Most checked
Not listed? Type its address, like example.com, to check it now.
Our last check from one location (UtiBox server · Newark, US) found it answering normally in 110 ms.
Testing slack.com from your device…
Slack is up. Total time to the final page on our latest check.
Thanks, you said it works
0 answers in the last 24 hours · 0 problem reports
One answer per person, counted for 24 hours.
No answers in the last 24 hours
Only our server so far. The regional checks run when the page opens.
No posts yet. Be the first to say how Slack is working for you.
Our latest check, step by step. Tap a step to open its full record.
Our main check runs from Newark, US. Run the same test from up to 3 internet providers in another country to see whether slack.com is blocked or broken there.
Press Ctrl + Shift + R (⌘ + Shift + R on a Mac).
Rules out extensions and stored cookies.
Move from Wi-Fi to mobile data, or the other way round.
Windows: ipconfig /flushdns · macOS: sudo dscacheutil -flushcache
They can block or reroute requests.
A wrong clock breaks secure connections.
| Date | Problem | Duration | Peak reports | Status |
|---|---|---|---|---|
| No confirmed incidents recorded for Slack. | ||||
What people say about Slack, in their own words, kept apart from our own checks.
Live counts · real numbers, refreshed with the page
Posts are public after a quick review. Don’t share personal details or links.
No posts yet.
Be the first to say how Slack is working for you.
No posts of this type yet.
That’s every post from the last 30 days.
One answer per person, counted for 24 hours.
Having one of these? Tap it to start a report.
What Slack status says about its own service, read from its public status page. A separate signal from our own check and from what people report.
Read from the official feed · the provider last updated it .
What Slack status reports about Slack. A site can answer our own check while the provider reports a problem with one of its features, and the other way round.
Status information is provided by the service operator. UtiBox is independent and isn’t affiliated with Slack. It may not reflect regional or account-specific problems.
None reported for Slack in the last report we read.
No maintenance is planned for Slack in the last report we read.
Our first successful read in this window was on 9 Nov 2026.
28 resolved updates since May 2026 · last one 11 Nov 2026 (3 h 34 min)
“The issue affecting Slack has been resolved, and users should be able to load Slack, log in, create channels, and save changes as expected. Error rates returned to normal levels at 16:15 UTC and have remained stable since. We’ve also brought additional database capacity online to keep systems healthy. We apologize for any inconvenience this caused. We’re continuing to investigate the cause and will take steps to help prevent this from happening again.”
“Some Slack customers experienced disrupted real-time connections, delayed message delivery, and errors loading conversation history on October 22, 2026, starting at 16:08 UTC. A large number of active connections closed at once and then reconnected, which briefly strained the services customers rely on to send and read messages. By 16:26 UTC, connections had reconnected and service had returned to normal. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and…”
“Some users may have experienced trouble logging into Slack. We identified the trigger and resolved the issue and restored access. We’re sorry for the disruption.”
“We've rolled out an updated version of the Slack iOS app to all impacted customers. Channels now open without the app closing unexpectedly. Users who are still experiencing this issue should update the Slack IOS app from the app store Store to resolve it.We apologize for the inconvenience and thank you for your patience.”
“A messaging integration briefly caused some free-plan workspaces to exceed their daily messaging limit, blocking them from sending messages. We took action to lift the sending block for all affected free-plan workspaces, and have confirmed messaging is now restored. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.”
“Some customers experienced blurry images that couldn't be downloaded across all clients, affecting files uploaded before a recent file storage update. We deployed a fix restoring proper file access, and confirmed it resolved the issue for affected customers. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.”
“This incident has been resolved. The engineering team has confirmed that the fix has been successfully deployed.We apologize for any disruptions this may have caused to your day.”
“We've completed restoring shared files for all remaining affected workspaces and restored and verified all affected data. If you still can't see previous content, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). Thank you for your patience while we sorted out this issue.”
“We've completed the rollback of the recent change that was the trigger of the issue. The Search bar and Admin dashboard is restored for all users.We apologize for the inconvenience caused to you and your business.”
“The fix has been successfully deployed, and validation is now complete. The issue preventing users from receiving incoming emails into Slack is fully resolved, and normal service functionality has been restored.We apologize for any disruptions to your day.”
“We’ve completed the revert of the recent change and have validated that this has brought customers out of impact and can now successfully send a message to a channel using Workflows that include 'refer to a message link'.We apologize for how this incident may have affected you and your business.”
“After a period of monitoring, we can see that reminders are now working as expected following the fix deployment. This issue has been resolved as of 03:00 UTC, July 24. We apologize for any inconvenience this issue has caused you. ”
“We've resolved the issue and users can now use the Chat feature on the Slack Help Center. We performed a configuration change, which brought the feature back online and have validated that it's functioning as expected. We apologize for how this incident may have affected you and your business.”
“We have successfully deployed the fix to production and the issue is resolved. The Admin SSO and Authentication Configuration page for standalone workspaces should now display the correct settings. If you continue to see outdated information, refresh the SSO Admin page to load the latest changes.”
“This issue is now resolved for all users.We apologize for any disruptions to your day.”
“This issue has been resolved. Android users who were experiencing issues submitting workflow forms containing a required file upload field can now do so successfully. A fix was delivered via a new update to the Slack Android app. Users who are still experiencing this issue should update the Slack app from the Google Play Store to resolve it. No other action is required. We apologize for the inconvenience and thank you for your patience.”
“Some users may have been unable to edit or delete messages in certain channels. We identified and resolved the issue. We apologize for how this issue affected you and your business.”
“We've validated that the fix resolved the issue and child windows are now displaying content as expected. You may need to reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux) in order for this fix to be reflected on your end. We're sorry for the disruption this caused to your day.”
“We've resolved the issue that prevented customers from using the Slack Gmail add-on. The fix has been successfully deployed; health metrics have stabilized, and the Gmail add-on is now fully operational for all affected users.We apologize for any inconvenience this may have caused.”
“We've resolved an issue that could cause incorrect email address tokens to appear when users pasted multiple email addresses into the member invite flow. In some cases, pasted email addresses were incorrectly matched to existing members with similar email addresses, requiring users to manually correct the entries before proceeding.We identified the cause of the issue and deployed a fix to ensure email addresses are now matched correctly when pasted into the invite flow. The issue is resolved for all affected users.If you're still experiencing any trouble, please reload Slack using Command +…”
“The issue affecting SMS-based two-factor authentication for users in EMEA has been resolved, and all services are now functioning as expected. We have adjusted configuration settings to restore normal service and will continue to monitor the situation to ensure stability. We apologize for how you and your business may have been affected by this. We will perform a full investigation of the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.”
“The Slack engineering team identified the cause as a recent update that introduced a code change which caused the invite modal to fail when accessed from the Admin page. We rolled back the change and have confirmed the fix is fully deployed and the issue is resolved.Some workspace Admins were unable to add new members to their workspaces via the Manage Members Admin page. In addition, some users attempting to invite people from this page may have encountered an error or been unable to run macros on their workspaces.Workspace Admins should now be able to add new members via the Manage Members…”
“This issue is now resolved for all users.Current status and recent actions taken: we've resolved the issue where some Slack users may have experienced message send failures and thread loading issues. We identified and addressed the root cause, and services have been fully restored.We apologize for any disruptions to your day.”
“Current status: The Slack engineering team investigated connectivity issues that affected some users between approximately 13:30 and 14:00 UTC on June 2, 2026. The issue has been resolved and no further impact has been reported.Scope: Some users, primarily in Europe, may have experienced difficulty loading or sending Slack messages during this windowWe apologize for any inconvenience this may have caused.”
“Our investigation has determined that the issue is isolated to a single customer environment and is not impacting the broader service. As a result, this incident will be removed from the status page and we will continue to work directly with the affected customer to address their issue.”
“This issue is now resolved for all users.Current status and recent actions taken: We deployed a series of configuration adjustments and infrastructure fixes to restore services. Messaging, Workflows, Apps, and Connections were progressively restored over the last several hours. Some users continued to experience permissions-related issues, including inability to manage channels and Canvas edits not saving, as a result of residual stale cache data. Cache deployment activities completed at 14:13 UTC on May 28, 2026, fully resolving the issue. Scope: This issue affected Slack users…”
“This issue is now resolved for all users.Current status and recent actions taken: The fix has successfully deployed, and our health metrics have stabilized. The issue is now fully resolved for all affected users. Scope: This wasn't affecting any specific region, but a percentage of users may have been affected globally.Previous impact to end users: Some users may have experienced slowness when uploading files and emojis in Slack. Attaching or sending files may have taken longer than expected — or failed to complete in a timely manner.Required resolution steps: No additional steps are…”
“Some Slack users experienced issues where Huddle AI summaries weren't being generated. Users also appeared to be showing as in a huddle after it had ended.We've fixed both issues. Missing summaries were restored, and the system responsible for showing huddle statuses has been refreshed. If you still notice any users appearing stuck in a huddle, please contact Slack Support. We apologize for the inconvenience and any impact this may have had.”
No updates of this kind.
From Slack status’s public status history. UtiBox keeps the official updates it reads for 180 days.
At our last check from UtiBox server · Newark, US, Slack was up and answering normally. The page refreshes the check automatically.
The official status page (slack-status.com) reports “Operational” for Slack. We read it every few minutes. It’s separate from our own check of the slack.com website above, so the two can differ.
If it’s up here but not for you, the problem is usually local: your connection, DNS, a browser extension, a VPN or a block on your network. Try the fixes on this page, then the Is It My Internet? check.
Our server requests slack.com and looks at every layer: DNS, the connection, the TLS certificate, the HTTP answer, redirects and the page content. We also check it from up to 12 locations in other countries, using two free probe networks (Globalping and check-host.net), so a regional outage can show here too.
A result is shared for 60 seconds when the site is up and 30 seconds when it has problems, then checked again. You can refresh it yourself after 30 seconds.
Yes. Use “Alert me when it’s back” and we’ll send one email when our check reaches it again. Guests confirm their address first.
UtiBox is free because of ads. Google and its partners use cookies to show, limit and measure ads, Google Analytics, Ahrefs Web Analytics and Microsoft Clarity show us how the site is used, and we use a few essential cookies to run the site.
Keep forms secure (ubsid) and remember that you’ve seen this notice (ub_consent). Things you ask us to remember, like light or dark mode and closed banners, are part of this.
UtiBox is free because of ads. Google AdSense and its partners use cookies to show, limit and measure ads. To change how Google personalises the ads you see, use Google’s My Ad Center. To opt out of personalised ads from many companies, visit aboutads.info or youronlinechoices.eu.
Google Analytics counts visits and shows us which pages and tools people use, so we can improve them. It sets _ga cookies. In the EEA, the UK and Switzerland it stores nothing unless you agree. To opt out on any site, use Google’s opt-out browser add-on. Ahrefs Web Analytics counts visits without cookies: it stores nothing on your device and never keeps your IP address; block analytics.ahrefs.com to opt out. Microsoft Clarity records clicks and scrolling for heatmaps and replays, with the tool area and what you type blanked out; block clarity.ms to opt out.