Is Slack down?
Right now
Partly. Slack is degraded.
Slack for iOS closing unexpectedly when opening channels.
Read from slack-status.com · every 120s
For agents
proceed
Proceed, expect slow or flaky responses.
GET upbutler.com/status/slack/status.agent.json
MCP: upstream_status {"service":"slack"}
Messaging, the Web API, webhooks and apps. If your alerts go to Slack, a Slack incident is an alerting incident.
What Slack reports
Degraded· 1 open incident
Taken as is from Slack's own status API. Incident titles and component names below are theirs.
Open slack-status.comUpButler's independent probe
Web API is answeringHTTP 200 · 281 ms
One request without credentials to slack.com every two minutes. An answer shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.
Checked · up since 2026-10-10 01:24 UTC
Open at Slack
- Slack for iOS closing unexpectedly when opening channelsinvestigating · impact minor
Since · Connectivity
An updated version of the Slack iOS app that fixes the crash was approved and began rolling out gradually. Customers who download the updated version from the app store can now open channels without the app closing unexpectedly. We'll provide an update once additional information becomes available.
Text written by Slack, shown unchanged.
Slack components
1 of 1 not operational
- ConnectivityDegraded
Slack incidents, last 90 days
No finished incidents on record yet since 2026-10-10. UpButler keeps what Slack publishes for 90 days from the day it starts tracking a service.
Tell your outage from Slack's
Declare that your project depends on Slack. When one of your monitors fails while Slack has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- slackcurl -s https://upbutler.com/status/slack/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "slack",
"verdict": "proceed",
"status": "degraded",
"reason": "Slack for iOS closing unexpectedly when opening channels",
"retryAfterSec": null,
"incident": {
"title": "Slack for iOS closing unexpectedly when opening channels",
"url": "https://slack-status.com/2026-10/a0cfb0208a1d2032"
},
"probe": {
"state": "up",
"statusCode": 200
}
}Questions
- Is Slack down right now?
- Partly. As of 2026-10-10 05:08 UTC, Slack is degraded, with an open incident: "Slack for iOS closing unexpectedly when opening channels". This page reads the status again every 2 minutes.
- Where does this status come from?
- From Slack's own status API at https://slack-status.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Slack's words.
- What does UpButler's own Slack check prove?
- Every two minutes UpButler sends one request without credentials to the Slack Web API (slack.com). Any answer from the edge, usually HTTP 200, shows that DNS, TLS and routing work. It does not prove that authenticated requests succeed, so it can say "reachable" while Slack reports degraded service. It is useful the other way round: when the probe fails before their status page changes.
- How can my agent or app check Slack status?
- Fetch https://upbutler.com/status/slack/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"slack"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Slack's?
- Add "slack" to the dependencies of your UpButler workspace. When one of your monitors fails while Slack has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in messaging and realtime
UpButler is not affiliated with Slack. Status and incident text belong to Slack and are read from their public status source; the probe result is UpButler's own measurement.