Issues affecting file uploads, message edits, channel renames, and channel creations
View the provider incident record →Current answer
Slack experienced a minor incident: Issues affecting file uploads, message edits, channel renames, and channel creations. The last provider record was marked Resolved; its current state cannot be verified.
The notice publication date does not establish the outage start.
Looking for an update now? Check the current status, or follow Slack for future changes.
Affected Components
Messaging
Files
Apps/Integrations/APIs
Workflows
Incident Timeline
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.
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.
May 14, 2026 at 3:34 PM UTC
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.
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.
May 14, 2026 at 3:19 PM UTC
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.
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.
May 14, 2026 at 2:50 PM UTC
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.
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.
May 14, 2026 at 2:37 PM UTC
Was your business affected by this Slack outage?
Follow Slack and route available status alerts to email or a team channel.