Provider
SlackIncident detail
Trouble loading Slack and saving changes.
Timeline window
to
Get alerted the next time Slack breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
Investigating
We're investigating a new incident. 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.
Monitoring
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.
Monitoring
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.
Monitoring
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.
Monitoring
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.
Monitoring
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.
Monitoring
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.
Monitoring
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.
Monitoring
Systems remain stable, and we haven’t seen the errors return. We’re continuing to restore additional database capacity and are completing a planned change to further strengthen the service. We’ll provide an update in 60 minutes or sooner if additional information becomes available.
Resolved
The issue affecting Slack has been resolved, and users should be able to load Slack, log in, create channels, and save changes as expected. Error rates returned to normal levels at 16:15 UTC and have remained stable since. We’ve also brought additional database capacity online to keep systems healthy. We apologize for any inconvenience this caused. We’re continuing to investigate the cause and will take steps to help prevent this from happening again.
Keep exploring
More from Slack
Neighboring incidents on Slack's timeline and the rest of their record on OutageDeck.