Trouble loading Slack and saving changes.
Slack users cannot load the app and cannot save preferences or profile changes. Slack also reports errors with login, channel creation, app installation, and workflow publishing. Slack has identified a recent database change as the likely trigger. Error rates returned to normal at 16:15 UTC, and Slack is monitoring its database systems.
State
Active
Started
Ongoing for
2 h 25 min
Worst impact
Degraded
Timeline
8 updatesActive
2 h 25 min 100%
Updates
Times in UTCAs posted by Slack
We’re continuing to monitor our database systems closely and haven’t seen the errors return based on our latest checks. Work to prevent this issue from happening again is still in progress. We’ll provide an update in 60 minutes or sooner if additional information becomes available.
Error rates have been at normal levels as of 16:15 UTC, and users should be able to load Slack, log in, create channels, and save changes. We’re continuing to restore full database redundancy and working on configuration changes to prevent the issue from returning. We’ll provide an update in 30 minutes or sooner if additional information becomes available.
Errors have decreased since about 15:51 UTC, and most users should now be able to load Slack, log in, create channels, and save changes. We’re continuing to stabilize our database systems and taking steps to prevent the issue from returning. We’ll provide an update in 30 minutes or sooner if additional information becomes available.
Since about 15:51 UTC, errors have decreased and many users can load Slack, log in, and save changes again. Some users may still encounter errors while we continue to stabilize our database systems. We’re also taking steps to prevent related databases from running out of storage. We’ll provide an update in 30 minutes or sooner if additional information becomes available.
We’ve identified that some users may also be unable to log in, create channels, install apps, or publish workflows. We’re investigating a recent database change as the likely trigger leading to a database storage capacity issue. We began freeing storage and removed unhealthy database hosts. Some users may continue to see errors. We’re working to prevent related databases from being affected. We’ll provide an update in 30 minutes or sooner if additional information becomes available.
We’re continuing to work on the Slack issue described in our last update. Some users may still encounter errors when loading the app, saving preferences or profile changes, and deactivating members. We’ll provide an update in 30 minutes or sooner if additional information becomes available.
We are investigating an issue where some customers may encounter various errors across Slack, including failures when loading the app, saving preferences or profile changes, and deactivating members. Our team is actively working to resolve the issue, and we'll share our next update in 30 minutes or as soon as more information is available.
We're investigating a new incident. Current impact : Some users may be experiencing delays when loading Slack and when using Slack features. We're working to understand the full impact to users. Our team is actively investigating the issue and is focused on restoring full performance as quickly as possible. We'll provide an update as soon as possible, and not longer than 30 minutes, with further details on the impact and actions being taken.
Affected components
4Slack in the last 90 days
Full historyIncidents in 90 days
1
Days with an incident
1
Median duration
Not enough data
This incident
Not comparable
Follow Slack
Your coding agent knows when Slack is down, and tells you when a failure is theirs, not yours. You can also get Slack incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "slack" and tell me if Slack has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=slack/feed subscribe https://outages.live/feed.xml?providers=slackFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane