90 days uptime
99.625%
86 of 90 days clean · 8h 5m total downtime
All windows
Last resolved incident
Earlier today · lasted 10h 3m · Major
6/10/2026, 8:36:35 PM · resolved 6/11/2026, 6:40:28 AM · Resolved
6/9/2026, 3:24:39 PM · resolved 6/9/2026, 8:25:19 PM · Investigating
6/8/2026, 7:00:00 PM · resolved 6/8/2026, 7:40:17 PM · Resolved
6/3/2026, 4:33:16 PM · resolved 6/3/2026, 5:40:36 PM · Resolved
Official status page: https://slack-status.com (opens in new tab)
Live status pill for Slack. Updates automatically — no maintenance, no API key.
PREVIEW
Drop into any HTML page — README, docs, vendor homepage. No iframe, no dependencies.
<script src="https://checkupstream.com/embed/badge.js?service=slack"></script>Self-contained, CSP-friendly. Theme + size are query params; revalidates every 60s.
<iframe src="https://checkupstream.com/embed/slack" style="border:0;width:260px;height:44px" loading="lazy" title="Slack status badge"></iframe>GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
[](https://checkupstream.com/reliability/slack)Useful for status-page composers (Notion, Slab, custom dashboards) that accept image URLs.
https://checkupstream.com/embed/slack/badge.svgSlack is currently Operational. CheckUpstream tracks Slack in real-time across the official status page, RSS / Atom feeds, and community telemetry — refresh this page for the latest reading.
Slack's last resolved incident started earlier today and lasted 10h 3m (a partial outage).
Looking for the live "is Slack down" view? See the Slack Status page.
Slack's 30-day customer-perceived uptime is 99.625%. The figure is weighted (full-outage = 1.0, degraded = 0.3) so component blips don't collapse the score the way a raw incident-count would.
Sign up to CheckUpstream and add Slack to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection — covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Slack's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.