Skip to main content
Slack

Issues affecting file uploads, message edits, channel renames, and channel creations

Degraded Lasted 57m · started · Slack's page

Level
confirmed
Worst impact
Degraded
Components
Messaging, Files, Apps/Integrations/APIs, Workflows
Down Index
41of 100

What to do

  • Check whether you use Slack Messaging, Files, Apps/Integrations/APIs, Workflows. Check your stack

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

    Anything that failed between 2026-05-14 14:37 UTC and 2026-05-14 15:34 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 4

  1. update

    We're investigating a new incident. Current impact to end users: We’re aware of an issue affecting file uploads, message edits, channel renames, and channel creations. We'll provide an update within 30 minutes including further details on current actions being taken.

    provider

  2. update

    Our work on this issue is still ongoing. Current status and actions being taken: We're investigating reports of slow loading times, errors when updating workflows, editing messages, creating or renaming channels, reactions, and issues with file uploads and third-party integrations. Some users may encounter failures when posting images or using add-ins. We'll be back with another update once we have news to share.

    provider

  3. update

    Our work on this issue is still ongoing. Current status and actions being taken: We've identified a potential cause related to an internal infrastructure component responsible for processing background tasks. Several nodes running this component were experiencing resource exhaustion and CrashLoopBackOff errors, causing connectivity failures to our message queue brokers. A revert of a recent configuration change is currently rolling out and we're seeing signs of improvement — 503 errors are trending down and some impacted pods are stabilizing. We'll continue monitoring the progress. We'll be back with another update once we have news to share. Thank you for your patience.

    provider

  4. update

    The issue affecting multiple features, including file uploads, message edits, and channel management, has been resolved. A fix has been fully deployed, and all systems are functioning normally. If you are still experiencing any trouble, please perform a hard reload of Slack by pressing Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). Mobile users should fully close and relaunch the app. We sincerely apologize for the disruption to your day and appreciate your patience while we worked to sort this out.

    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-6b7d68b294

Is Slack still down?

No, this incident was resolved 2026-05-14 15:34 UTC. For Slack's live state, see https://down.guide/slack.

How long did it last?

57m, from 2026-05-14 14:37 UTC to 2026-05-14 15:34 UTC, by the times Slack posted.

What was affected?

Slack named Messaging, Files, Apps/Integrations/APIs, Workflows.

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.