Datvero automation observatory · slack-status.com
No. Slack's status page reports all systems operational for Slack: Messaging, Login/SSO, Apps/Integrations/APIs and 8 other components (checked November 6, 2026, 18:10 UTC; this page refreshes every 5 minutes).
Read from Slack's official status API at November 6, 2026, 18:10 UTC. Datvero republishes what Slack states; it is not an independent uptime measurement.
From May 8 to November 6, 2026, slack-status.com lists 30 incidents. Median time from first post to last update, resolved incidents with a stated duration: 2.8 h. Longest: “Trouble Accessing Historical Messages With Custom Data Retention Policies Enabled” (August 13, 2026), 32 days. In the last 30 days: 3 incidents, 0 of them outages.
Retry with a growing delay, send failures to an error workflow, and get alerted when runs stop succeeding. In n8n, every node has a Retry On Fail setting; Make has Break error handlers that retry incomplete executions; Zapier can replay failed runs with Autoreplay. Datvero watches the runs of your n8n, Make and Zapier workflows and alerts you when they fail, whatever the cause.
No. Slack's status page reports all systems operational for Slack: Messaging, Login/SSO, Apps/Integrations/APIs and 8 other components (checked November 6, 2026, 18:10 UTC; this page refreshes every 5 minutes).
From May 8 to November 6, 2026, slack-status.com lists 30 incidents. Median time from first post to last update, resolved incidents with a stated duration: 2.8 h. Longest: “Trouble Accessing Historical Messages With Custom Data Retention Policies Enabled” (August 13, 2026), 32 days. In the last 30 days: 3 incidents, 0 of them outages.
Slack publishes it at https://slack-status.com/. This page republishes its public feed every 5 minutes with timestamps. Datvero is not affiliated with Slack.
When the status page is green but your Slack app or webhook fails, read the HTTP code. If you exceed a rate limit on any of Slack’s HTTP-based APIs, including incoming webhooks, Slack returns HTTP 429 Too Many Requests with a Retry-After header giving the number of seconds until you can retry. That is a limit, not an outage.
The status page lists what Slack has declared. If it is green and you still see errors, read the error code, retry with a growing delay, and check whether the problem is specific to your account, your region or one integration. A green page does not prove that every request to Slack succeeds.
Retry with a growing delay, send failures to an error workflow, and get alerted when runs stop succeeding. In n8n, every node has a Retry On Fail setting; Make has Break error handlers that retry incomplete executions; Zapier can replay failed runs with Autoreplay. Datvero watches the runs of your n8n, Make and Zapier workflows and alerts you when they fail, whatever the cause.
Method: Slack's Status API (slack-status.com/api/v2.0.0, documented at https://docs.slack.dev/reference/slack-status-api/) is read every 5 minutes: the current endpoint for active incidents, the history endpoint for past ones. A duration runs from the first post to the last update of a resolved incident, and is shown only when the incident has at least two posts. Machine readable copy: services.json. HTTP codes: Slack developer docs, Rate limits. Official source: https://slack-status.com/.
Statuses, incident names and texts belong to Slack. Datvero is not affiliated with Slack. A green status page does not mean every workflow that calls Slack succeeds.