Communication tools
Is Slack down?
Live Slack status, measured independently. We probe 5 Slack endpoints from monitoring regions on every continent and record every outage we detect.
Slack is having problems
Some of our probes are failing. Slack may be partially down or degraded in specific regions.
Checked every minute from 6 regions on every continent.
- Uptime, 24 hoursUptime, last 24 hours
- Uptime, 7 daysUptime, last 7 days
- Uptime, 30 daysUptime, last 30 days
- Website97.93% uptime, 30 days6 regions, 317 to 689 msUnknownp50median response488 msp95slowest 5% of checks609 ms1000 ms500024 h ago12 h agonow
- Slack app98.29% uptime, 30 days6 regions, 320 to 761 msUnknownp50median response541 msp95slowest 5% of checks741 ms1000 ms500024 h ago12 h agonow
- API100% uptime, 30 days6 regions, 156 to 450 msUnknownp50median response255 msp95slowest 5% of checks343 ms500 ms250024 h ago12 h agonow
- Incoming webhooks83.31% uptime, 30 days6 regions, 854 to 10000 msUnknownp50median response2966 msp95slowest 5% of checks3251 ms5000 ms2500024 h ago12 h agonow
- Official status API99.99% uptime, 30 days6 regions, 47 to 212 msUnknownp50median response115 msp95slowest 5% of checks270 ms200 ms100024 h ago12 h agonow
Daily strip:99.9% or better95–99.9%below 95%no data yet
Get notified when Slack goes down
Follow these 5 checks from your own workspace and get alerted through Slack, email, webhooks, or on-call the moment Slack goes down. They don't count against your monitor quota. Free plan, no card required.
About Slack outages
Slack is where many teams receive their alerts, so a Slack incident is doubly dangerous: the tool is down, and the channel you would learn about other outages through is down with it. Slack incidents often affect messaging, notifications, or the API separately.
We probe the website, the Slack web app, the public api.test method, which answers without authentication and reflects API availability directly, and the incoming-webhook endpoint that alert integrations post to.
What we check
Every row is a real monitor in upti.my, running from each of our regions. A failure in some regions marks the row degraded; failures from every region mark it down and open an outage.
| Check | Target | Expects | Interval |
|---|---|---|---|
Website slack.com is unreachable. | httpslack.com | HTTP 200 | 1 min |
Slack app The Slack web app is unreachable. | httpapp.slack.com | HTTP 200 | 2 min |
API The Slack Web API is failing. Incoming webhooks, bots, and alert integrations cannot post. | httpslack.com/api/api.test | HTTP 200 | 1 min |
Incoming webhooks The incoming-webhook endpoint is not answering as expected. Alert integrations that post via webhook fail. | httphooks.slack.com/services/ | Any HTTP response | 2 min |
Official status API Slack's status API is unreachable. | httpslack-status.com/api/v2.0.0/current | HTTP 200 | 5 min |
For component-level detail and incident write-ups from the vendor, see Slack's official status page.
Recent Slack outages we detected
An outage is recorded when a probe fails from every monitoring region and closed when it recovers. Partial and single-region problems show as degraded above but are not listed here.
Slack is up. Is your Slack integration?
The incidents that actually hurt are usually not global outages. They are the parts of your own system that depend on Slack and fail quietly. Here is what teams that rely on Slack monitor on their side.
Do not alert through a single channel
If Slack is your only alert destination, a Slack outage silences every alert. Route critical alerts to a second channel such as email, SMS, or a phone call.
Alert routing and escalationBots and workflows that post to Slack
A scheduled report that fails to post looks the same as one that never ran. Heartbeats on the job distinguish the two.
Heartbeat monitoringSlack status: frequently asked questions
Likely a partial incident. Slack's official page breaks status down into messaging, notifications, search, apps, and more. Our API probe shows whether integrations can still post.
Look at the per-region results above. If our probes fail from every region, Slack has a real outage and it will appear in the outage list. If they succeed everywhere, the problem is most likely on your side: your network, DNS resolver, a browser extension, a corporate proxy, or your own integration. If only some regions fail, Slack may have a regional incident that does not affect you.
Every probe runs at least every five minutes from each monitoring region, and most run every minute. This page refreshes its data every minute. Uptime figures are calculated from all checks across all regions.
Official status is updated by people after an incident is confirmed and often lags the first failures by many minutes; our probes react within a minute or two. In the other direction, we only see public endpoints, so an internal incident may not show on our probes. Use both.
Yes. Use "Notify me about Slack" above: your upti.my workspace follows these exact checks, free plan included, and every outage opens an incident there and routes alerts to Slack, email, webhooks, or on-call. Nothing is duplicated and it doesn't use your monitor quota. Better still, also monitor your own dependency on Slack: the API route, webhook receiver, or scheduled job that calls it, so you learn about the failure that actually affects your users.
Related
Other communication tools
upti.my is not affiliated with Slack. Slack and related marks are the property of their respective owners and are used here only to identify the service being measured. Results reflect the reachability of public endpoints from our monitoring regions and may differ from the vendor's own reporting.