Slack Status
Official Slack system status and incident details.
Live Domain Check
Check if Slack is down right now (slack.com). Run a live multi-region check to see whether Slack is offline for everyone or just you.
Get official Slack outage status updates, support links, and targeted troubleshooting steps in one page.
Checking reachability from multiple regions.
Slack incidents can affect login, messaging, search, workflows, and API integrations independently. During partial events, some users or workspaces are impacted while others remain healthy.
For Slack, incident signals are often feature-specific: Workspace loads but messages fail to send. Thread loading and reactions lag behind direct messages. If this matches what you see on slack.com, it usually points to partial degradation instead of a full outage, so confirm with official status updates and a second-network retest.
Slack provides an official status page and status API for programmatic incident checks.
Official Slack system status and incident details.
Official support resources for workspace issues.
Official status API reference for automation workflows.
Monitor real-time social updates and official posts related to Slack outages.
Official teams often post outage status updates and recovery progress through these social channels.
Use these service-specific patterns to identify likely root cause quickly and choose the right next step.
Practical steps to follow when slack.com seems down. Use this checklist to confirm whether Slack is down for everyone or only for you.
Run slack.com in WebsiteDown.org first, then open slack.com in your own browser. If results disagree, the issue is often local rather than global.
Check the official Slack service status page and compare timestamps with your failed checks.
Test related hosts such as slack-status.com, app.slack.com. If they work while slack.com fails, this points to a partial endpoint issue.
Capture final URL, status code, and response time for slack.com, then share those details with Slack support for faster triage and recovery.
Use these local troubleshooting steps after the down-check workflow when Slack seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open slack.com in your current browser, then test in a private window or second browser. If only one session fails, the issue is usually local cache, cookie, or extension state.
Sign out and sign back in one time, then retry the failing action on slack.com. Avoid repeated password or security resets until you confirm this is not a broader Slack issue.
Temporarily disable VPN, proxy, private DNS, and filtering extensions. Then switch between Wi-Fi and mobile data to isolate route-level differences.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Slack support.
Run the automatic multi-region check on this page for slack.com. If most regions fail at the same time, Slack is likely experiencing a broader outage or partial incident.
If only one or two regions fail, the issue is usually local to your network path (DNS resolver, ISP route, VPN/proxy, or firewall). Re-check after 2 to 5 minutes and compare Wi-Fi with mobile data.
Use the Official Status, Support, and Social Channels section above in this order:
Official dashboards are authoritative but can lag during the first minutes of an incident. Combine those sources with this checker to confirm whether Slack is down globally, regionally degraded, or only affecting specific users.
That pattern usually points to path-specific issues rather than a full Slack outage. Common causes include:
Test in a private window, temporarily disable VPN/extensions, and retry from a second network. If one feature fails while the homepage still loads, treat it as a partial incident.
Use this quick triage sequence for slack.com:
This order helps you avoid unnecessary account resets when the Slack issue is provider-side.