Slack status: is it down right now?
Our own check of slack.com from Europe and the US, every 3 minutes, with recent history.
slack.com responded. The page answered normally in 250 ms.
slack.com responded.
The page answered normally in 250 ms.
Checked (2 minutes ago) from Europe and the US, automatic every 3 minutes.
Run a website? Get alerts when it goes down. Check my site
This checks the response from slack.com. It does not test playback, login or every Slack feature.
Slack status history
Our own checks from Europe and the US. Green means every check passed, amber means some checks failed, red means most checks in that period failed.
Outages our checks detected
None since Oct 13. A problem has to fail two checks in a row before we record it.
Watch your own site
This page is for their outage. Your own site can fail the same way. See its first check free, then try a paid plan for 7 days (card required).
Monitor my siteabout this service
About Slack
Slack is a team-messaging platform now owned by Salesforce, covering channels, direct messages, huddles (quick voice/video), Canvas (collaborative docs), Connect (external-org channels), Workflow Builder, and a large App directory. Outages typically show up as messages not delivering, file uploads failing, huddles dropping, notifications stopping, or connected apps (GitHub, Jira, Zendesk) disconnecting. Enterprise Grid customers get dedicated status communications. Slack-integrated bots and slash commands are the first things to break when the API degrades, and teams that rely on Slack for on-call alerting feel this immediately.
The official Slack status page is available as a reference. Official pages are useful, but they can lag behind real outages by minutes or hours.
outage patterns
Common Slack outage patterns
Real-time messaging platforms have a distinctive failure mode: separate subsystems can fail independently. The text channel keeps working while voice drops, or push notifications stop arriving while in-app messages still flow. This makes status feel unpredictable to end users who don't realize their issue is one slice of Slack's stack.
The live tool above checks whether the public slack.com endpoint responds from EU and US. It does not send a message, join a call, or validate push delivery, so a green result is only endpoint evidence. Pair it with the provider status reference and a real test of the affected feature.
Common signs Slack is having issues
- Connection drops or "reconnecting" indicators that persist for more than 60 seconds
- Messages sending successfully on one device but not arriving on another
- Push notifications missing or delayed by minutes rather than seconds
- API rate limits hitting earlier than expected for bots and integrations
What to do when Slack is degraded
When Slack is having issues, the fastest signal is multi-region comparison. If both EU and US monitors report problems for slack.com, it's a real outage. If only one region is affected, the issue is likely the regional gateway or a CDN edge. Switching the connection region in client settings (where Slack supports it) often restores service before the platform-wide fix lands.
monitor 24/7
Monitor Slack automatically.
Get independent uptime alerts when the public Slack endpoint fails a confirmed check. Solo and Starter check every 5 minutes; Business and Agency check every 60 seconds.
5-minute checks from Solo
Business and Agency support 60-second uptime checks.
Multi-region
EU & US checks. Catch regional outages.
Alerts where you work
Email and push on every plan, plus team and incident channels by plan.
free first check · 7-day trial, card required · from $15/month
why independent monitoring
Provider status references
and endpoint checks answer different questions.
Independent endpoint evidence
The regional check can show that a public endpoint is failing before or after a provider posts broader incident context. It does not validate every product subsystem.
Scheduled alerts
Monitor Slack on your plan interval and route confirmed endpoint failures through the notification channels available to your workspace.
Multi-region verification
EU and US results can reveal a regional difference in public-endpoint reachability. Confirm the exact workflow and provider region you use.
Historical data
Track Slack uptime over time. See trends, identify recurring issues, and make informed decisions about your dependency.
Frequently asked questions
Is Slack down right now?
See the latest check of slack.com and its timestamp at the top of this page. If Slack is down, you can also check the official status page for extra context.
How do I check if Slack is having issues?
This page checks the public Slack endpoint from EU and US. You can also monitor that endpoint on a schedule and receive confirmed-failure alerts through the channels available on your plan. Test the exact provider feature you use for a complete diagnosis.
How can I get alerted when Slack goes down?
Add slack.com to Visual Sentinel and its first check is free. To keep monitoring, start a 7-day trial (card required) or subscribe now: Solo and Starter check every 5 minutes, Business and Agency every 60 seconds, with email, push and chat alerts.
Where can I find Slack outage context?
The official Slack status page is available as a reference. Official pages are useful, but they can lag behind real outages by minutes or hours. Visual Sentinel checks the public Slack endpoint independently from EU and US. Paid Business and Agency plans support 60-second uptime checks.
Why can I see Slack messages but sending new ones fails?
Slack clients render an optimistic UI, your message appears as "sending" instantly but actually delivers through a write-side service. During write-path outages, messages stack up with the "sending" indicator and eventually show a retry prompt. Read traffic stays fast because it is served from the websocket cache.
Do Slack integrations (like GitHub notifications) retry after an outage?
Most Slack apps use webhooks, which do retry on 5xx for a limited window (usually 1-3 attempts). Missed notifications beyond the retry window are typically lost. Slack does not backfill them; check the source system (GitHub, Jira) for what you missed.
Often checked together with Slack
Chat apps fail in parts (voice, messages, notifications). Compare the ones your group also uses.