Skip to main content
Menu
Slack

Incident

Trouble loading Slack and saving changes.

Degraded Lasted 3h 34m · started · Slack's page

DWN-1f78278ab7

Level
confirmed
Worst impact
Degraded
Components
Connectivity, Messaging, Apps/Integrations/APIs, Workspace/Org Administration
Down Index
44of 100

What to do

  • Check whether you use Slack Connectivity, Messaging, Apps/Integrations/APIs, Workspace/Org Administration. Check your stack

    Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 3h 34m it lasted.

    Anything that failed between 2026-11-11 15:24 UTC and 2026-11-11 18:58 UTC may need a replay.
  • Subscribe to Slack's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=slack works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Slack 12

  1. update

    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.

    provider

  2. update

    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.

    provider

  3. update

    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.

    provider

  4. update

    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.

    provider

  5. update

    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.

    provider

  6. update

    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.

    provider

  7. update

    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.

    provider

  8. update

    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.

    provider

  9. update

    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.

    provider

  10. update

    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.

    provider

  11. update

    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.

    provider

  12. update

    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.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-1f78278ab7

Is Slack still down?

No, this incident was resolved 2026-11-11 18:58 UTC. For Slack's live state, see https://down.guide/providers/slack.

How long did it last?

3h 34m, from 2026-11-11 15:24 UTC to 2026-11-11 18:58 UTC, by the times Slack posted.

What was affected?

Slack named Connectivity, Messaging, Apps/Integrations/APIs, Workspace/Org Administration.

What caused it?

Slack hasn't published a root cause. If it does, it shows here.

Where does this come from?

Slack's official status page, https://slack-status.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.