Is Slack down?
Checks passingchecked moments ago
Our checks of Slack pass from all 10 regions we check.
As of Oct 11, 2026, 8:33 PM UTC, RealUptime's checks of Slack passed in all 10 regions that returned a reading.
Our checks of Slack did not fail from two or more distant regions in the 64 days we have checked it (since Aug 8, 2026). This does not show Slack works for users.
Email me when our checks of Slack fail from two or more distant regions
Slack reports: Minor incident (“Slack for iOS closing unexpectedly when opening channels”)
This is Slack's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.
Slack response time, by region
Check your own site while you wait on Slack
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Slack -- it cannot diagnose Slack's own systems.
What we measured, function by function
Slack answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.
- WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
What our checks show, and what people reported
- North AmericaChecks passingUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 88msstatus code: 200checked: Oct 11, 2026, 8:32 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Slack normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestChecks passinglatency: 1048msstatus code: 200checked: Oct 11, 2026, 8:33 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Slack normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralChecks passinglatency: 1184msstatus code: 200checked: Oct 11, 2026, 8:32 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Slack normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- CanadaChecks passinglatency: 1072msstatus code: 200checked: Oct 11, 2026, 8:32 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Slack normally. We do not have enough reports from Canada to say anything about what people there are seeing.
- South AmericaChecks passinglatency: 274msstatus code: 200checked: Oct 11, 2026, 8:31 PM UTC0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Slack normally. We do not have enough reports from South America to say anything about what people there are seeing.
- EuropeChecks passingEurope, UK
- EuropeChecks passinglatency: 1107msstatus code: 200checked: Oct 11, 2026, 8:33 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Slack normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKChecks passinglatency: 264msstatus code: 200checked: Oct 11, 2026, 8:31 PM UTC0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Slack normally. We do not have enough reports from UK to say anything about what people there are seeing.
- Asia PacificChecks passingAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 372msstatus code: 200checked: Oct 11, 2026, 8:32 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Slack normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaChecks passinglatency: 309msstatus code: 200checked: Oct 11, 2026, 8:31 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Slack normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- AustraliaChecks passinglatency: 259msstatus code: 200checked: Oct 11, 2026, 8:33 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Slack normally. We do not have enough reports from Australia to say anything about what people there are seeing.
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using Slack, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Slack yet, which is not evidence that nothing is wrong.
Recent probe events
No probe events on record yet for Slack.
check entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring Slack since August 8, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for Slack covering any window you pick, with our check readings and Slack's own claim at the time, side by side.
Full check history for Slack: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.
Put this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/slack)<a href="https://realuptime.io/outages/slack"><img src="https://realuptime.io/outages/slack/badge.svg?days=30" alt="Slack uptime by RealUptime's checks"></a>The badge shows the share of our checks that passed over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.
How our checks compare with Slack's stated SLA
At or above your target
Our checks of Slack failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.
Our checks show no gap in this period. That does not rule out one you saw.
These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from Slack's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.
What we check
What our check can and cannot see
A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.
Host checked: slack.com