Skip to main content
Slack logo

Is Slack Down?

No — Slack is up

Reachable from all 18 checked regions

Average response time: 633ms

Last checked · checks run every 30 minutes

Official status page: https://slack-status.com

Slack uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
556ms
Avg response, 30 days

Measured from multiple regions every 30 minutes. Percentages count only checks that returned an availability answer — 49 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

49-day clean streak
Aug 14: 100.00% uptime, 877 checks
Aug 15: 100.00% uptime, 850 checks
Aug 16: 100.00% uptime, 866 checks
Aug 17: 100.00% uptime, 870 checks
Aug 18: 100.00% uptime, 937 checks
Aug 19: 100.00% uptime, 914 checks
Aug 20: 100.00% uptime, 835 checks
Aug 21: 100.00% uptime, 806 checks
Aug 22: 100.00% uptime, 857 checks
Aug 23: 100.00% uptime, 833 checks
Aug 24: 100.00% uptime, 785 checks
Aug 25: 100.00% uptime, 877 checks
Aug 26: 100.00% uptime, 859 checks
Aug 27: 100.00% uptime, 858 checks
Aug 28: 100.00% uptime, 856 checks
Aug 29: 100.00% uptime, 857 checks
Aug 30: 100.00% uptime, 852 checks
Aug 31: 100.00% uptime, 850 checks
Sep 1: 100.00% uptime, 853 checks
Sep 2: 100.00% uptime, 752 checks
Sep 3: 100.00% uptime, 722 checks
Sep 4: 100.00% uptime, 673 checks
Sep 5: 100.00% uptime, 658 checks
Sep 6: 100.00% uptime, 759 checks
Sep 7: 100.00% uptime, 694 checks
Sep 8: 100.00% uptime, 898 checks
Sep 9: 100.00% uptime, 849 checks
Sep 10: 100.00% uptime, 873 checks
Sep 11: 100.00% uptime, 866 checks
Sep 12: 100.00% uptime, 816 checks
Aug 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
604ms
DNS 0ms TCP 9ms TLS 11ms TTFB 335ms
arn
582ms
DNS 0ms TCP 23ms TLS 25ms TTFB 306ms
bom
1446ms
DNS 0ms TCP 3ms TLS 7ms TTFB 890ms
cdg
624ms
DNS 0ms TCP 17ms TLS 18ms TTFB 331ms
dfw
321ms
DNS 0ms TCP 26ms TLS 29ms TTFB 239ms
ewr
169ms
DNS 0ms TCP 7ms TLS 9ms TTFB 147ms
fra
630ms
DNS 0ms TCP 3ms TLS 4ms TTFB 311ms
gru
255ms
DNS 0ms TCP 2ms TLS 7ms TTFB 242ms
iad
140ms
DNS 1ms TCP 2ms TLS 5ms TTFB 132ms
jnb
1348ms
DNS 0ms TCP 26ms TLS 29ms TTFB 674ms
lax
496ms
DNS 0ms TCP 31ms TLS 33ms TTFB 342ms
lhr
770ms
DNS 0ms TCP 2ms TLS 5ms TTFB 458ms
nrt
885ms
DNS 1ms TCP 4ms TLS 6ms TTFB 441ms
ord
218ms
DNS 0ms TCP 9ms TLS 12ms TTFB 175ms
sin
1388ms
DNS 0ms TCP 2ms TLS 4ms TTFB 944ms
sjc
534ms
DNS 0ms TCP 23ms TLS 25ms TTFB 338ms
syd
743ms
DNS 0ms TCP 1ms TLS 4ms TTFB 542ms
yyz
249ms
DNS 0ms TCP 16ms TLS 19ms TTFB 199ms

What Slack does

Slack is a business communication platform used by millions of teams for messaging, file sharing, and collaboration. It organizes conversations into channels and supports direct messages, voice calls, and integrations with thousands of third-party tools. Slack is owned by Salesforce and is a core productivity tool for remote and hybrid teams.

What an outage looks like

During a Slack outage, messages may fail to send or appear delayed by minutes or hours. The desktop and mobile apps may show connection errors or a perpetual loading screen. File uploads stall, notifications stop arriving, and integrations with tools like Jira, GitHub, and PagerDuty stop delivering alerts.

What to do about it

Check status.slack.com for official incident reports. While Slack is down, fall back to email or an alternative communication tool for urgent matters. Slack messages sent during outages are typically delivered once service is restored, so your messages should not be permanently lost.

Is it down for everyone, or just you?

If this page says Slack is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Slack outage FAQ

Will my messages be lost if Slack goes down while I'm typing?
Messages that you've already sent but haven't been delivered will be queued and delivered once Slack recovers. However, if you're mid-typing and the app crashes, the unsent message in the compose box may be lost. Slack's draft feature preserves most unsent messages, but it's not guaranteed during outages.
How do I know if Slack is down or it's just my connection?
First, check your internet connection by loading another website. Then visit status.slack.com from your browser. If you can reach other sites but not Slack, and the status page confirms an incident, Slack is down. The Slack app will also display a yellow or red connection banner at the top of the window.
Do Slack integrations work during an outage?
No, integrations that rely on Slack's API will fail during an outage. This includes bot messages, webhook deliveries, and notifications from tools like GitHub, PagerDuty, and Jira. Most integration platforms queue failed deliveries and retry them after Slack recovers.
What should my team use when Slack is down?
Have a backup communication plan before outages happen. Email is the most reliable fallback. Some teams keep a secondary tool like Microsoft Teams or Discord available. For incident response, phone calls or SMS via tools like PagerDuty ensure critical alerts are never missed.
Does Slack have an uptime SLA?
Slack offers a 99.99% uptime SLA for Enterprise Grid customers, with service credits if that threshold isn't met. Business+ and Pro plans do not have a formal SLA. Slack's historical uptime is generally very high, with most incidents being brief and partial.

How we measure this

  • We request Slack's public endpoint every 30 minutes from Fly.io regions across six continents — the most recent check ran from 18 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Slack publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Slack goes down

This page refreshes every 30 minutes. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required