Slack broke down at the database layer for 3h 37m on 11 November, leaving some users unable to load the app, log in, create channels or save changes. The fault was on Slack's side, triggered by a database change that ran into storage capacity trouble.
Started
15:24 UTC
Duration
Lasted 3h 37m
Source
IsDown
Next time
Slack is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Apps/Integrations/APIs, Connectivity, Messaging, Workspace/Org Administration
What happened?
Slack's status page opened one incident at 15:24 UTC, describing delays loading the app and using features for some users. By 15:29 the scope had widened to failures loading the app, saving preferences or profile changes, and deactivating members. At 15:55 Slack said the same errors were continuing, with another update promised in 30 minutes. The 16:16 update is the one that names a cause: Slack engineers pointed to a recent database change as the likely trigger for a database storage capacity issue, and said they had begun freeing storage and removing unhealthy database hosts. That update also widened the affected list again, adding login failures, channel creation, app installs and workflow publishing. From 16:27 onward Slack reported errors decreasing, tracing the turnaround to about 15:51 UTC, then declared error rates back to normal levels as of 16:15 UTC in the 17:02 update. The final two updates, at 17:31 and 18:28, describe Slack monitoring its database systems and working on configuration changes and capacity restoration to stop the issue recurring, with no further errors seen. The incident closed after 3h 37m with four components listed as affected: Apps/Integrations/APIs, Connectivity, Messaging, and Workspace/Org Administration. No user reports were filed during the window on this record. Slack's own status page is the only source here, and it carries that weight: it names the suspected trigger but does not publish a post-mortem explaining why the database ran out of storage in the first place.
Learning
This incident sat at the database layer behind Slack's apps, not at the network edge, which is why the symptom list grew in stages as Slack engineers traced the blast radius: login, channel creation, app installs and workflow publishing all got pulled in as the storage problem spread, rather than failing all at once. A check that only pings Slack's front door can come back green while people inside your workspace cannot save a profile change or deactivate a member, because the page loads even as the backend writes fail. That is exactly the kind of gap an uptime check aimed at your own product will never catch, since your endpoints were never the broken part. Slack's history shows this is not rare: 6 incidents in the last 90 days with a median duration of 7 hours 40 minutes, so a provider-side database fault running over three and a half hours is on the shorter end for them. Your own monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.