Slack Outage History

Started May 27, 2026, 11:00 PM UTC· resolved May 28, 2026, 03:22 PM UTC

1. investigating May 27, 2026, 11:00 PM UTC

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

2. investigating May 27, 2026, 11:31 PM UTC

   We continue to investigate the issue, and are‌ implementing fixes to restore services. We're starting to see some improvements from the fixes implemented so far. We’ll provide another update as soon as we have more information, and again we are sorry for the inconvenience this is causing.

3. investigating May 28, 2026, 01:03 AM UTC

   Teams continue to implement configuration adjustments and deployment fixes to resolve the issue. All features except for Workflows and Messaging should be recovered. Some lingering impact remains. Users may notice: Empty pills instead of @-mentionDelayed reacjiMismatch in Channel member count and channel membershipSlow loading of messages, user avatars, and unfurlsWe are working with urgency to improve platform stability and reduce impact. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

4. investigating May 28, 2026, 01:41 AM UTC

   We are continuing to work on implementing fixes to fully resolve the issue. Messaging should now be recovered. Users may continue to experience issues with workflow steps completing. Empty pills instead of @-mention; delayed reacji; mismatch in Channel member count and channel membership; and slow loading of messages, user avatars, and unfurls should now all be working properly. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

5. investigating May 28, 2026, 02:17 AM UTC

   Messaging latency has now cleared. Newly triggered workflows should start and complete as normal. Workflows that executed during the impact period ending at approximately 7pm PDT may not have completed. Customers may notice delayed workflow execution for jobs that triggered during the disruption period. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

6. investigating May 28, 2026, 02:46 AM UTC

   Workflow builder jobs that were triggered during the disruption period have been replayed and will complete over the next several hours. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

7. investigating May 28, 2026, 03:22 AM UTC

   Cleanup and recovery efforts continue. Workflow builder job backlogs are being drained. Event subscriptions have been re-enabled. No further impact is expected. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

8. investigating May 28, 2026, 03:55 AM UTC

   We’re glad to inform you that the Workflow Builder job backlogs were cleared and workflow execution has returned to normal. We continue progressing through the final stages of recovery activities across affected service areas as overall platform stability improves. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

9. investigating May 28, 2026, 04:30 AM UTC

   Recovery activities continue, and restoration efforts are progressing well. Platform stability is improving, and no further customer impact is expected. We’ll provide an update in the next 60 minutes or sooner, if additional information becomes available.

10. investigating May 28, 2026, 05:13 AM UTC

    Slack services continue to progress through the final stages of ‌recovery activities to restore functionality across all services. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

11. investigating May 28, 2026, 05:47 AM UTC

    Slack services have largely returned to normal operational levels. Messaging, Workflows, Apps, Integrations, APIs, and Connections have all been restored. We'll continue with the final restoration activities and we'll provide updates as significant developments occur.

12. investigating May 28, 2026, 10:04 AM UTC

    We're investigating a new impact to Slack. Current impact to end users: Slack users are experiencing issues with managing channels, statuses aren't clearing or updating correctly, and edits on Canvas aren't being saved. We'll provide an update within 30 minutes including further details on current actions being taken.

13. investigating May 28, 2026, 10:45 AM UTC

    We continue to investigate the issue and are working with urgency to improve stability and reduce impact. We’ll provide another in 30 minutes or sooner, including further details on current actions being taken. We're sorry for the inconvenience this is causing.

14. investigating May 28, 2026, 11:17 AM UTC

    Users continue to experience issues with their ability to manage channels, Canvas edits not saving, and user statuses not clearing or updating correctly. Investigations are underway. The issues aren't reproducible and we're working to get the IDs to investigate further. We're working with urgency to improve platform stability and reduce impact. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

15. investigating May 28, 2026, 11:46 AM UTC

    We continue to investigate the issue, and are‌ gathering the resources necessary to restore services. We’ll provide another update in 30 minutes or as soon as we have more information, and again we're sorry for the inconvenience this is causing.

16. investigating May 28, 2026, 12:01 PM UTC

    Our work on this issue is still ongoing. Current status and actions being taken: Remediation efforts are underway via configuration adjustments and deployment. We're still working to resolve the issues with Canvas.We'll be back with another update once we have news to share.

17. investigating May 28, 2026, 12:25 PM UTC

    Recovery activities continue, and restoration efforts are progressing well. Slack users should now be able to edit Canvases as the errors have dropped. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

18. investigating May 28, 2026, 12:55 PM UTC

    Remediation efforts via configuration adjustments and deployment are in progress. Users may still run into issues updating their status and managing channels. We’ll provide another update in 30 minutes or as soon as we have more information, and again we are sorry for the inconvenience this is causing.

19. investigating May 28, 2026, 01:35 PM UTC

    Remediation efforts via configuration adjustments and deployment will take several hours to complete to fully resolve channel management and status issues. Slack users may continue to experience intermittent impact. We'll be back with another update in 30 minutes when we have news to share.

20. investigating May 28, 2026, 02:09 PM UTC

    Slack users continue to experience permissions-related issues such as: unable to manage channels, add Canvas to tabs, update statuses, convert public to private channels while we work on a complete restoration. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

21. resolved May 28, 2026, 03:22 PM UTC

    This issue is now resolved for all users. Current status and recent actions taken: We deployed a series of configuration adjustments and infrastructure fixes to restore services. Messaging, Workflows, Apps, and Connections were progressively restored over the last several hours. Some users continued to experience permissions-related issues, including inability to manage channels and Canvas edits not saving, as a result of residual stale cache data. Cache deployment activities completed at 14:13 UTC on May 28, 2026, fully resolving the issue. Scope: This issue affected Slack users globally.Previous impact to end users: Slack users experienced difficulties accessing Slack features, including Messaging, Workflows, Apps, Integrations, APIs, Canvas, and Connections, beginning at 22:21 UTC on May 27, 2026. Following an infrastructure change, a cascading scheduling failure caused widespread service impact across all regions and clients. Slack services largely returned to normal operational levels at 05:45 UTC on May 27, with residual impact that remained during the deployment. A brief issue with Canvas surfaced at 10:00 UTC on May 28‌ that lasted until approximately 12:30 UTC. Required resolution steps: No steps required. We apologize for any disruptions to your day. We'll undertake a full investigation of the incident, establishing the technical trigger, the mechanism of failure, and preventative measures to avoid further disruptions.

Read the full incident report →

Started May 19, 2026, 08:51 PM UTC· resolved May 19, 2026, 10:27 PM UTC

1. monitoring May 19, 2026, 08:51 PM UTC

   We've identified the trigger, causing slow file and emoji uploads in Slack, and have deployed a fix. At this time, we are monitoring the environment to confirm full resolution. - Current status and actions being taken: We've identified a frontend error as the cause of the issue and have deployed a fix. We're actively monitoring our health metrics to confirm the fix has resolved the issue for all users. - Estimated time to resolution: No ETA at this time. - Scope: Users globally may be experiencing this issue. - Current impact to end users: Some users may experience slowness when uploading files and emojis in Slack. Attaching or sending files may be taking longer than expected — or failing to complete in a timely manner. - Known workarounds: No workarounds at this time. We'll provide another update as soon as we have more information to share.

2. resolved May 19, 2026, 10:27 PM UTC

   This issue is now resolved for all users. Current status and recent actions taken: The fix has successfully deployed, and our health metrics have stabilized. The issue is now fully resolved for all affected users. Scope: This wasn't affecting any specific region, but a percentage of users may have been affected globally.Previous impact to end users: Some users may have experienced slowness when uploading files and emojis in Slack. Attaching or sending files may have taken longer than expected — or failed to complete in a timely manner.Required resolution steps: No additional steps are required.We apologize for any disruptions to your day.

Read the full incident report →

Started May 18, 2026, 02:53 PM UTC· resolved May 18, 2026, 02:53 PM UTC

1. resolved May 18, 2026, 02:53 PM UTC

   Some Slack users experienced issues where Huddle AI summaries ‌weren't being generated. Users also appeared to be showing as in a huddle after it had ended. We've fixed both issues. Missing summaries were restored, and the system responsible for showing huddle statuses has been refreshed. If you still notice any users appearing stuck in a huddle, please contact Slack Support. We apologize for the inconvenience and any impact this may have had.

Read the full incident report →

Started May 14, 2026, 02:37 PM UTC· resolved May 14, 2026, 03:34 PM UTC

1. investigating May 14, 2026, 02:37 PM UTC

   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.

2. investigating May 14, 2026, 02:50 PM UTC

   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.

3. identified May 14, 2026, 03:19 PM UTC

   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.

4. resolved May 14, 2026, 03:34 PM UTC

   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.

Read the full incident report →

Started May 08, 2026, 06:31 PM UTC· resolved May 11, 2026, 09:48 PM UTC

1. investigating May 08, 2026, 06:31 PM UTC

   Between approximately 10:55 AM and 11:10 AM PDT, customers using Enterprise Key Management (EKM) may have experienced issues sending messages and loading some channels. Error rates have returned to normal levels and customers should now see expected performance. We are continuing to investigate the underlying cause and monitoring closely. We apologize for the disruption.

2. investigating May 08, 2026, 06:44 PM UTC

   We’re investigating this issue: Current status and actions being taken: We’re seeing renewed, elevated error rates and latency affecting customers using Enterprise Key Management (EKM). Affected customers may experience issues sending messages and loading some channels. Our team is actively investigating this issue.Estimated time to resolution: No ETA at this time.Scope: This is not affecting any specific region, but a percentage of Enterprise Key Management (EKM) customers may experience impact globally.Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading some channels.Known workarounds: No known workarounds at this time. We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

3. investigating May 08, 2026, 07:20 PM UTC

   We’re investigating this issue: Current status and actions being taken: We believe an issue with an upstream provider may be impacting some Slack services. We’re partnering with them to help with our investigation and are waiting on additional details from their analysis. In parallel, we’re actively reviewing the cache configuration to alleviate the impact.Estimated time to resolution: No ETA at this time.Scope: This is not affecting any specific region, but a percentage of Enterprise Key Management (EKM) customers may experience impact globally.Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading some channels.Known workarounds: No known workarounds at this time. We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

4. monitoring May 08, 2026, 07:54 PM UTC

   We’re investigating this issue: Current status and actions being taken: We’ve deployed a fix that has improved our cache hit ratio and are observing recovery in our health metrics. In parallel, we're monitoring for updates from our upstream provider. Affected customers may already be seeing improvements, and we’ll continue to monitor the situation closely until it is fully resolved.Estimated time to resolution: No ETA at this time.Scope: This is not affecting any specific region, but a percentage of Enterprise Key Management customers may experience impact globally.Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading channels. Additionally, they may experience delays with all messaging activity, including notifications and activity feeds.Known workarounds: No known workarounds at this time. We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

5. investigating May 08, 2026, 08:27 PM UTC

   We’re investigating this issue: Current status and actions being taken: We're seeing consistent improvement in our health metrics while our upstream provider has begun implementing a fix on their side. Affected customers may already be seeing improvements, and we’ll continue to monitor the situation closely until it is fully resolved.Estimated time to resolution: No ETA at this time.Scope: This is not affecting any specific region, but a percentage of Enterprise Key Management customers may experience impact globally.Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading channels. Additionally, they may experience delays with all messaging activity, including notifications and activity feeds.Known workarounds: No known workarounds at this time. We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

6. investigating May 08, 2026, 08:57 PM UTC

   We’re investigating this issue: Current status and actions being taken: We continue to monitor the issue as our upstream provider continues their work toward a resolution. Affected customers may already be seeing improvements, and we’ll continue to monitor the situation closely until it is fully resolved.Estimated time to resolution: No ETA at this time.Scope: This is not affecting any specific region, but a percentage of Enterprise Key Management customers may experience impact globally.Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading channels. Additionally, they may experience delays with all messaging activity, including notifications and activity feeds.Known workarounds: No known workarounds at this time. We'll continue to provide updates every 60 minutes until the impact is resolved for all users.

7. investigating May 08, 2026, 09:58 PM UTC

   We’re investigating this issue: Current status and actions being taken: Our upstream provider has implemented a fix and is continuing their investigation. In the meantime, we continue to observe improved health metrics. Affected customers may already be seeing improvements, and we’ll continue to monitor the situation closely until it is fully resolvedEstimated time to resolution: No ETA at this time.Scope: This is not affecting any specific region, but a percentage of Enterprise Key Management customers may experience impact globally.Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading channels. Additionally, they may experience delays with all messaging activity, including notifications and activity feeds.Known workarounds: No known workarounds at this time. We'll continue to provide updates every 60 minutes until the impact is resolved for all users.

8. resolved May 08, 2026, 11:27 PM UTC

   This issue is now resolved for all users. Current status and recent actions taken: Our upstream provider has successfully implemented a fix. Following a period of stable monitoring, all services have been restored. Customers should no longer experience issues accessing Slack.Scope: This issue didn’t affect any specific region, but a percentage of Enterprise Key Management customers may have experienced an impact globally.Previous impact to end users: Customers using Enterprise Key Management (EKM) may have experienced issues sending messages and loading channels. Additionally, they may have experienced delays with all messaging activity, including notifications and activity feeds.Required resolution steps: No additional steps are necessary.We apologize for any disruptions to your day.

9. investigating May 11, 2026, 02:22 PM UTC

   Current status and actions being taken: We’re investigating a recurrence of a previous incident causing elevated errors and high latency for EKM customers. As a precaution, EKM backfills have been paused to reduce load. Teams are evaluating pod scaling and assessing a high-volume load test workload contributing to EKGen traffic. A bridge is active with EKM and EKGen engineers engaged, and third-party infrastructure teams have been re-engaged as a potential contributing factor. Estimated time to resolution: Under investigation. No ETA available at this time. Scope: Customers using Enterprise Key Management (EKM). Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading channels. Additionally, they may experience delays with all messaging activity, including notifications, Workflow, DMs, and activity feeds. Known workarounds: No known workarounds at this time. We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

10. identified May 11, 2026, 03:11 PM UTC

    Current status and actions being taken: We're continuing to investigate elevated error rates affecting a subset of users. We've identified additional load contributing to the issue and have taken steps to reduce it. Estimated time to resolution: Under investigation. No ETA available at this time. Scope: Customers using Enterprise Key Management (EKM) Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading channels. Additionally, they may experience delays with all messaging activity, including notifications, Workflow, DMs, and activity feeds. Known workarounds: No known workarounds at this time. We'll provide another update in 30 minutes or as new information becomes available. We apologize for the disruption.

11. identified May 11, 2026, 04:05 PM UTC

    Current status and actions being taken: We're continuing to investigate elevated error rates affecting a subset of users. We've identified additional load contributing to the issue and have taken steps to reduce it. We've also engaged our third-party vendor to assist in providing additional troubleshooting. Estimated time to resolution: Under investigation. No ETA available at this time. Scope: Customers using Enterprise Key Management (EKM) Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading channels. Additionally, they may experience delays with all messaging activity, including notifications, Workflow, DMs, and activity feeds. Known workarounds: No known workarounds at this time. We'll provide another update in 30 minutes or as new information becomes available. We apologize for the disruption.

12. identified May 11, 2026, 04:38 PM UTC

    Current status and actions being taken: We have identified contributing factors to the issue impacting EKM customers and have taken mitigating actions, including reducing the rate of KMS requests by approximately 50% and increasing cache capacity. We are continuing to monitor closely and are actively investigating the underlying cause in partnership with our third-party provider. Estimated time to resolution: The incident has been stable for over an hour with no new customer-facing impact detected. Scope: Customers using Enterprise Key Management (EKM) Current impact to end users: Customers using Enterprise Key Management (EKM) may have experienced issues sending messages and loading channels. Additionally, they may experience delays with all messaging activity, including notifications, Workflow, DMs, and activity feeds. Known workarounds: No known workarounds at this time. We'll provide another update by 9:50 AM PT. We apologize for the disruption.

13. investigating May 11, 2026, 05:12 PM UTC

    Our work on this issue is still ongoing. Current status and actions being taken: Our monitoring has shown no further instability and we have considered this incident now under control. We are continuing to monitor closely.We'll provide another update should we find any further information of note. We apologize for the disruption.

14. investigating May 11, 2026, 07:02 PM UTC

    Our work on this issue is still ongoing. Current status and actions being taken: Customer impact effectively stopped around 8:00AM PT and has remained stable. Our monitoring has shown no further instability and we have considered this incident now under control. We are continuing to monitor closely and we'll update again when there's another meaningful update to share. We apologize for the disruption.

15. resolved May 11, 2026, 09:48 PM UTC

    Users who rely on Enterprise Key Management (EKM) may have experienced elevated latency and errors across messaging, channel loading, workflows, and file operations starting around 5:55 AM PDT on May 11, 2026. Impact was mitigated and the incident was brought under control at 9:16 AM PDT on May 11, 2026. We've deployed fixes addressing the root cause of the elevated encryption key request load. If you continue to experience trouble, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). We apologize for the disruption and thank you for your patience.

Read the full incident report →

Started May 08, 2026, 12:13 PM UTC· resolved May 08, 2026, 05:44 PM UTC

1. identified May 08, 2026, 12:13 PM UTC

   Users who are undergoing scheduled Grid Migrations are experiencing extended downtime. Downtime is expected during a Grid Migration however it's taking longer than usual. During the downtime users are unable to access Slack until the migration completes. We've identified an issue with Job Queues, which may be the cause and are investigating this further. The next update will be provided once additional information becomes available.

2. resolved May 08, 2026, 05:44 PM UTC

   This issue is now resolved. Current status and actions being taken: We identified database write throttling as the cause of the stalled grid migrations. We applied a drop rule for jobs that were stuck in a retry loop, which has restored normal migration processing. Scope: A small number of enterprise users undergoing grid migrations experienced extended delays in accessing Slack. Current impact to end users: Affected users may have experienced an inability to access Slack during their migration window. Known workarounds: No workarounds needed at this time.We apologize for how this incident affected you and your business.

Read the full incident report →

Started May 04, 2026, 10:00 AM UTC· resolved May 04, 2026, 05:37 PM UTC

1. investigating May 04, 2026, 10:00 AM UTC

   Some users are experiencing issues with workflows. Triggered workflows may fail to complete, with the first step not executing. We'll provide another update as soon as possible.

2. identified May 04, 2026, 11:43 AM UTC

   The investigation identified elevated latency in EU backend services as the cause of workflows not completing. A subset of workflow trigger attempts is impacted, primarily, EU users. Pod restarts have stopped, and error rates are improving. A fix is being prepared and will be deployed shortly. We'll provide another update as soon as possible.

3. monitoring May 04, 2026, 01:08 PM UTC

   A fix has been deployed to address the elevated latency in EU backend services. The team is monitoring the environment to ensure service stability and full recovery. We'll provide another update as soon as possible.

4. resolved May 04, 2026, 05:37 PM UTC

   This issue is now resolved for all users. Current status and recent actions taken: A fix has been deployed that resolved the underlying cause of this issue. Our health metrics have returned to normal levels and workflows are running as expected.Scope: Users in the EU region — primarily teams based in Central Europe — experienced elevated workflow failure rates.Previous impact to end users: Users may have experienced workflows failing to run, with the first step remaining stuck in an initialized state. Some users in the EU region may also have experienced general slowness when using Slack.Required resolution steps: No steps are required. Workflows should be running normally. If you continue to experience any trouble, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux).We apologize for any disruptions this may have caused to your day.

Read the full incident report →

Started May 01, 2026, 01:50 AM UTC· resolved May 01, 2026, 01:50 AM UTC

1. resolved May 01, 2026, 01:50 AM UTC

   At 23:20 UTC, April 30, 2026, a feature disruption began affecting the Slack Search feature for a subset of customers in Japan region. As a result, users were unable to use Search functionality within Slack. We identified that infrastructure changes to our Search cluster caused a number of internal search nodes to become unavailable, which prevented Search queries from routing correctly. We implemented a series of remediation steps, including increasing cluster capacity and restoring affected search shards. We also blocked certain Search traffic to contain secondary impact while the cluster was being recovered. As of 00:45 UTC, May 1, 2026, Slack Search functionality is fully operational. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

Read the full incident report →

Started Apr 27, 2026, 05:11 PM UTC· resolved Apr 27, 2026, 08:36 PM UTC

1. investigating Apr 27, 2026, 05:11 PM UTC

   Some users have reported issues with thread replies not generating a notification banner. We’re investigating the issue, and have identified a recent deployment as a possible trigger. We apologize for the inconvenience and will report back as more information becomes available.

2. investigating Apr 27, 2026, 06:07 PM UTC

   We’re observing positive signals after rolling back the deployment in test environments. We will complete some final validations before rolling back the deployment in the production environment. Thank you for your patience as we work through this one. We’ll report back once production rollback is completed or if there are substantial updates to share.

3. resolved Apr 27, 2026, 08:36 PM UTC

   We’ve successfully performed a rollback in the production environment, and all systems are now functioning as expected. Users should no longer experience any issues with thread replies not generating a notification banner. We apologize for any inconvenience and appreciate your patience.

Read the full incident report →

Started Apr 23, 2026, 07:27 AM UTC· resolved Apr 23, 2026, 09:50 AM UTC

1. investigating Apr 23, 2026, 07:27 AM UTC

   Some users are having trouble loading Threads in Slack, this is affecting Windows and Chrome users. Users may receive an error asking them to ‘Try Again’. We apologize for the inconvenience and will report back as more information becomes available.

2. investigating Apr 23, 2026, 08:05 AM UTC

   We’re still investigating these issues with Threads not loading. No additional information to share just yet, but we’ll keep you posted as soon as we have an update.

3. resolved Apr 23, 2026, 09:50 AM UTC

   Further investigation confirms that the issue impacting Thread loading has been self- resolved, and our team will continue to investigate to ensure that this doesn’t reoccur. We apologize for the trouble today and thank you for your patience.

Read the full incident report →

Started Apr 21, 2026, 01:46 PM UTC· resolved Apr 21, 2026, 03:47 PM UTC

1. investigating Apr 21, 2026, 01:46 PM UTC

   We're aware of an issue affecting Slack. Some users who have set a custom status to expire at a specific time are finding that their status is not automatically clearing as expected. We're actively investigating and we'll provide an update as soon as we have more information available.

2. resolved Apr 21, 2026, 03:47 PM UTC

   Resolved This issue is now resolved for all users. Current status and recent actions taken: Custom statuses set to expire at a specific time are now clearing as expected. The issue self-resolved when the next scheduled expiration job successfully processed the affected users. Scope: Some external users globally were affected. Users on desktop were impacted; the issue was not reproducible internally or across test workspaces.Previous impact to end users: Some users may have experienced custom statuses that did not automatically clear at their scheduled expiration time.Required resolution steps: No steps required.We apologize for any disruptions to your day.

Read the full incident report →

Started Apr 20, 2026, 09:05 AM UTC· resolved Apr 20, 2026, 09:05 AM UTC

1. resolved Apr 20, 2026, 09:05 AM UTC

   This issue is now resolved for all users. Current status and recent actions taken: We've completed rolling back the change to address the issue impacting core Slack functionality, including launching Slack, sending messages, loading threads, and other related actions. Scope: All Slack enterprise customers.Previous impact to end users: Users experienced issues with channel-related operations, including delays or failures when loading channels or retrieving channel membership lists. We apologize for any disruptions to your day.

Read the full incident report →

Started Apr 10, 2026, 07:09 PM UTC· resolved Apr 10, 2026, 09:44 PM UTC

1. investigating Apr 10, 2026, 07:09 PM UTC

   We're investigating a new incident. Current impact to end users: Some users may experience trouble sending messages. We're investigating the issue and we regret any inconvenience this is causing. We'll provide an update within 30 minutes including further details on current actions being taken.

2. identified Apr 10, 2026, 07:44 PM UTC

   We are actively working to resolve the current platform functionality issues. Current status and actions being taken: We've identified a fix and are actively deploying it across the platform. Once the rollout is complete, we'll monitor system performance to ensure full stability.Estimated time to resolution: No ETA at this time.Scope: This issue isn't affecting any specific region, but a percentage of users may be affected globally.Current impact to end users: Some users may experience trouble sending messages.Known workarounds: No known workarounds at this time. We appreciate your patience as we sort this out.

3. resolved Apr 10, 2026, 08:21 PM UTC

   We are actively working to resolve the current platform functionality issues. Current status and actions being taken: We have processed the affected service PODs to expedite recovery, resulting in significant recovery across the platform. We're now monitoring all systems to ensure performance remains stable.Estimated time to resolution: No ETA at this time.Scope: This issue isn't affecting any specific region, but a percentage of users may be affected globally.Current impact to end users: Some users may experience trouble sending messages.Known workarounds: No known workarounds at this time. We'll continue to provide updates every 60 minutes until the impact is resolved for all users.

4. investigating Apr 10, 2026, 09:22 PM UTC

   We are actively working to resolve the current platform functionality issues. Current status and actions being taken: We're still working toward resolving the issue and to reduce the likelihood of symptoms recurring. We'll continue to monitor internal metrics as we work through this. Estimated time to resolution: No ETA at this time.Scope: This issue isn't affecting any specific region, but a percentage of users may be affected globally.Current impact to end users: Some users may experience trouble sending messages.Known workarounds: No known workarounds at this time. We'll provide the next update upon a significant change in status, or sooner if additional information becomes available.

5. resolved Apr 10, 2026, 09:44 PM UTC

   This issue is now resolved for all users. Current status and recent actions taken: After monitoring system performance and infrastructure stability, we have confirmed that all Slack features are operating within expected levels. Users should no longer experience any issues when sending messages. Scope: This issue wasn't affecting any specific region, but a percentage of users may have been affected globally.Previous impact to end users: Some users may have experienced trouble sending messages.Required resolution steps: No additional steps are required. We apologize for any disruptions to your day.

Read the full incident report →

Started Apr 09, 2026, 07:58 AM UTC· resolved Apr 09, 2026, 07:29 PM UTC

1. investigating Apr 09, 2026, 07:58 AM UTC

   We're investigating a new incident. Current impact to end users: Some users may be experiencing trouble with Slackbot responses. Other Slack functionality that leverages AI services may also be experiencing issues. We're on the case and we'll provide an update within 30 minutes including further details on current actions being taken.

2. resolved Apr 09, 2026, 08:28 AM UTC

   Our work on this issue is still ongoing. Current status and actions being taken: Users may continue to experience trouble with Slackbot responses and other Slack AI-powered features. We've identified the trigger as a third-party infrastructure issue and are working with the provider to resolve this issue. We'll provide another update in 30 minutes until the impact is resolved for all users.

3. resolved Apr 09, 2026, 08:59 AM UTC

   Our work on this issue is still ongoing. Users may continue to experience intermittent trouble with Slackbot responses and other Slack AI-powered features such as Search Answers, Meeting Notes, and Translation. Current status and actions being taken: We remain engaged with our third-party provider. We'll provide another update in 60 minutes until the impact is resolved for all users.

4. resolved Apr 09, 2026, 09:51 AM UTC

   Current status and actions being taken: We're continuing to engage with our third-party provider to find a solution. We're also exploring multiple avenues on our side to try to alleviate impact on Slackbot and AI-powered features until the upstream issue is resolved. We'll provide another update in 60 minutes until the impact is resolved for all users.

5. resolved Apr 09, 2026, 10:54 AM UTC

   Current status and actions being taken: We've taken steps to try to reduce the impact on Slackbot and its response capabilities. Customers may notice signs of improvement, however, the impact may still be intermittent until full resolution. Other AI-powered features, including Search Answers, Meeting Notes, and Translation, are still experiencing issues due to the ongoing upstream problem. We're investigating similar alleviative actions for these features. We'll provide another update in 60 minutes until the impact is resolved for all users.

6. resolved Apr 09, 2026, 11:56 AM UTC

   Current status and actions being taken: We're continuing to engage with our third-party provider to find a solution. No further alleviative actions have been undertaken since our last update. We'll provide another update in 60 minutes until the impact is resolved for all users.

7. identified Apr 09, 2026, 12:58 PM UTC

   Current status and actions being taken: We believe we've identified an issue that's still causing impact to occur even after our upstream provider has resolved impact from their end. We expect a code fix to take at least an hour to complete and pass through various test environments. We'll provide another update in 60 minutes.

8. monitoring Apr 09, 2026, 01:59 PM UTC

   Current status and actions being taken: We've begun deploying the code fix to production. Once complete we'll begin monitoring the performance of Slackbot, as well as our other AI-powered features. We'll provide another update in 60 minutes.

9. investigating Apr 09, 2026, 02:52 PM UTC

   Current status and actions being taken: The code fix hasn't successfully addressed the impact and we're resuming our investigations. We'll provide another update in 60 minutes.

10. identified Apr 09, 2026, 03:55 PM UTC

    Current status and actions being taken: Upon further review, we've identified issues with secondary caching and are currently working on a configuration fix. In parallel, we're continuing to investigate and assess several solutions to restore ‌services. We'll provide another update in 60 minutes.

11. monitoring Apr 09, 2026, 05:11 PM UTC

    Current status and actions being taken: We’ve deployed a configuration fix, resulting in significant improvements to Slackbot success rates and health metrics. We're now monitoring the situation as we investigate a secondary cache issue that may be contributing to intermittent errors or degraded workflow performance. We'll provide another update in 60 minutes.

12. investigating Apr 09, 2026, 06:13 PM UTC

    Current status and actions being taken: We've deployed an emergency fix to address the issues contributing to intermittent errors with Slackbot and Workflows. We're now seeing significant recovery across all affected services and are continuing to monitor the situation closely to ensure performance remains stable. We'll provide another update in 60 minutes.

13. resolved Apr 09, 2026, 07:29 PM UTC

    Current status and recent actions taken: After monitoring system performance and infrastructure stability, we have confirmed that all Slack features are operating within expected levels. This incident is now resolved and users should no longer experience any issues with Slackbot, AI Features, or workflows. We apologize for any disruptions to your day.

Read the full incident report →

Started Apr 01, 2026, 01:01 PM UTC· resolved Apr 01, 2026, 02:41 PM UTC

1. identified Apr 01, 2026, 01:01 PM UTC

   We’re aware of an issue introduced in build 121247 that affects the Slackbot button in the top navigation bar. As a result, the button may no longer be visible to users. We've identified a fix and are performing a rollback to restore the button for all affected users. We will provide an update in 30 minutes, or sooner if additional information becomes available. Thank you for your patience while we continue to investigate the situation.

2. resolved Apr 01, 2026, 01:44 PM UTC

   Our work on this issue is still ongoing. Current status and actions being taken: We've identified the cause of the issue affecting the Slackbot button in the top navigation bar and have taken steps to address it. The issue is no longer present for affected users. Users who are currently experiencing the issue may need to reload Slack for the fix to take effect. We're continuing to monitor and will provide an update once service has been fully restored.We'll provide another update in 30 minutes until the impact is resolved for all users.

3. resolved Apr 01, 2026, 02:37 PM UTC

   This issue is now resolved for all users. Current status and recent actions taken: We've completed deploying the fix to address the issue affecting the Slackbot button in the top navigation bar. The Slackbot button is now working as expected. Scope: The issue was introduced for any users on build 121247.Previous impact to end users: The Slackbot button in the top navigation bar may not have been visible to users.Required resolution steps: Users who are still experiencing the issue may need to reload Slack for their experience to return to normal. We apologize for any disruptions to your day.

Read the full incident report →

Started Mar 29, 2026, 10:38 PM UTC· resolved Mar 30, 2026, 01:17 AM UTC

1. investigating Mar 29, 2026, 10:38 PM UTC

   We're investigating a new incident. Current impact to end users: Some users may experience elevated error rates and message-related degradations when sending and receiving messages across the Slack platformTeams are actively engaged to identify the root cause and remediate the service impact and will provide updates as information is available. We apologize for the inconvenience and will continue sharing updates as they become available.

2. identified Mar 29, 2026, 11:30 PM UTC

   We’re continuing to investigate the issue. We have identified two affected shards that are becoming overloaded, causing elevated query failures and message-related degradations. We are in the process of testing a potential fix. We’ll provide the next update once new information becomes available.

3. monitoring Mar 30, 2026, 12:29 AM UTC

   A fix has been deployed to the affected shards. ProcessMessage jobs had been paused, and these have now been unpaused on the affected shards. We are monitoring performance to assess whether the shards have returned to expected performance levels.

4. monitoring Mar 30, 2026, 01:17 AM UTC

   Following a period of monitoring, our engineering team called this incident resolved as of 01:10 UTC, March 30. We apologize for any inconvenience this issue has caused to users.

Read the full incident report →

Started Mar 28, 2026, 04:12 AM UTC· resolved Mar 28, 2026, 05:39 AM UTC

1. investigating Mar 28, 2026, 04:12 AM UTC

   We're investigating a new incident. Current impact to end users: Some users may experience issues while sending messages and loading message history in Slack. We'll provide an update within 30 minutes including further details on current actions being taken.

2. resolved Mar 28, 2026, 04:42 AM UTC

   We continue to investigate the issue. Current status and actions being taken: We have identified high resource utilization as a potential trigger. We continue to investigate and determine the best path to resolution.Estimated time to resolution: We don't have the exact resolution time at the moment and will update you once we have additional information.Scope: This is only impacting a small subset of users.Current impact to end users: Some users may experience issues while sending messages and loading message history in Slack.Known workarounds: Users can mitigate the issue by retrying the message sending or loading of message history.We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

3. resolved Mar 28, 2026, 05:19 AM UTC

   Our work on this issue is still ongoing. Current status and actions being taken: We are reviewing additional logs and diagnostic information to determine the best path to resolution.We'll provide another update in 60 minutes until the impact is resolved for all users.

4. resolved Mar 28, 2026, 05:39 AM UTC

   This issue is now resolved for all users. Current status and recent actions taken: We identified a paused job that may have been contributing to the high utilization. This was unpaused, which restored resource availability.Scope: This only affected a small subset of users.Previous impact to end users: Some users may have experienced issues while sending messages and loading message history in Slack between 20:14 PDT and 22:14 PDT.We apologize for any disruptions to your day.

Read the full incident report →

Started Mar 26, 2026, 03:40 PM UTC· resolved Mar 26, 2026, 04:36 PM UTC

1. investigating Mar 26, 2026, 03:40 PM UTC

   We are aware of an issue impacting Slack. As a result, some customers may be unable to load certain features, including activity and notification badge counts, and may encounter errors when using the service. We are working to resolve this as our highest priority, and we'll provide another update in 30 minutes.

2. investigating Mar 26, 2026, 04:07 PM UTC

   The team is investigating the issue and have rolled back a recent feature change to reduce load on affected systems. We are also actively increasing infrastructure capacity to restore normal service levels. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. resolved Mar 26, 2026, 04:36 PM UTC

   Intermittent errors when sending messages have been resolved. Additionally, some customers may see inaccurate notification badge counts which can be resolved with a hard reload to clear temporary local cache. Apologies for the trouble today and thank you for your patience.

Read the full incident report →

Started Mar 23, 2026, 02:40 AM UTC· resolved Mar 23, 2026, 03:46 AM UTC

1. investigating Mar 23, 2026, 02:40 AM UTC

   We are aware that customers are receiving authorization failure errors when trying to connect to the Slack MCP server. We are currently investigating the issue and will provide an update as soon as more information becomes available. We're very sorry for any inconvience this may be causing your business.

2. investigating Mar 23, 2026, 03:05 AM UTC

   We continue to investigate the issue. At this time, it appears the impact is affecting users of certain third party Slack integrations. We’ll continue to provide updates as more information becomes available, and we apologize for any inconvenience this may be causing.

3. resolved Mar 23, 2026, 03:46 AM UTC

   We have resolved the issue that was causing users to experience authorization failures when connecting certain third-party integrations to Slack. We apologize for any inconvenience this may have caused and thank you for your patience.

Read the full incident report →

Started Mar 09, 2026, 03:02 AM UTC· resolved Mar 09, 2026, 07:17 PM UTC

1. investigating Mar 09, 2026, 03:02 AM UTC

   Some users may experience trouble logging into Slack. We’re on the case and will provide another update once we have more details to share. We’re sorry for the disruption.

2. identified Mar 09, 2026, 03:43 AM UTC

   Our work on this issue is still ongoing. Current status and actions being taken: Some users are experiencing intermittent SSO login failures when trying to access their Slack workspace. Our team is investigating the cause of this issue and working to resolve it as quickly as possible.We'll be back with another update once we have news to share.

3. resolved Mar 09, 2026, 04:29 AM UTC

   Our work on this issue is still ongoing. Current status and actions being taken: the team continues investigating. We'll provide another update in 60 minutes until impact is resolved for all users.

4. investigating Mar 09, 2026, 05:22 AM UTC

   Current status and recent actions taken: Single Sign-On (SSO) login functionality has been fully restored. Following the deployment of a fix by our engineering team, users are now able to log in normally and without any issues.Scope: Previous impact to end users: customers were experiencing intermittent Single Sign-On (SSO) error accessing Slack workspaces.Required resolution steps: NA

5. identified Mar 09, 2026, 07:19 AM UTC

   This issue has resurfaced and we're actively engaged to resolve the issue as quickly as possible. Current status and actions being taken: We have identified the trigger ‌cause and are working on a comprehensive fix to prevent this from happening again. Estimated time to resolution: We are working urgently to resolve this issue as quickly as possible.Scope: A subset of Enterprise customers using Single Sign-On (SSO) are experiencing intermittent login issues. This is not affecting all users within impacted organizations, and the issue may vary by session. Current impact to end users: Users attempting to log in via SSO may encounter errors requiring them to refresh their browser multiple times before successfully accessing their workspace. Some users may experience a degraded login experience even after gaining access.Known workarounds: We do not have any workarounds at this time.We'll continue to provide updates as significant progress is made.

6. resolved Mar 09, 2026, 07:17 PM UTC

   This issue is now resolved for all users. Current status and recent actions taken: We identified the cause as a login routing component that had incorrect entries, which prevented users from being directed to their workspace correctly. A fix has been deployed to address this issue. Previous impact to end users: Users attempting to log in via SSO may have encountered errors requiring them to refresh their browser multiple times before successfully accessing their workspace. Some users may have experienced a degraded login experience even after gaining access.We apologize for any disruptions to your day.

Read the full incident report →

Started Mar 05, 2026, 02:56 PM UTC· resolved Mar 06, 2026, 04:44 PM UTC

1. investigating Mar 05, 2026, 02:56 PM UTC

   We're aware of an issue impacting the completion of ongoing enterprise migrations, resulting in longer than expected downtime. In efforts to resolve the issue we're increasing processing capacity and have deployed code changes to address the delayed job processing. We'll provide an update when we next have additional information.

2. resolved Mar 05, 2026, 07:36 PM UTC

   We've identified additional impact where developers may observe no responses when @mentioning an application. This incident extends impact to Grid migrations and iOS push notifications may not deliver. Current status and actions being taken: We continue to investigate potential triggers in recent deployments for this issue.Scope: This will impact any developers @mentioning an app in a Slack channel, upcoming/planned migrations, and iOS notifications.Current impact to end users: Developers may not receive responses when @mentioning an app to execute an action in a Slack channel, org admins will observe delays with upcoming/planned migrations, and iOS push notifications may not deliver.Known workarounds: No known workarounds.We appreciate your patience as we sort this out. We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

3. resolved Mar 05, 2026, 08:07 PM UTC

   We’re still actively investigating this issue, but we don’t have any new information to share at this time. Thanks for sticking with us as we continue to work towards a fix. We'll provide another update in 30 minutes until impact is resolved for all users.

4. resolved Mar 05, 2026, 08:40 PM UTC

   We're actively working to resolve the current platform functionality issues. Current status and actions being taken: We’re continuing to investigate the underlying trigger and have noticed an improvement in health metrics with Push notifications.Estimated time to resolution: No ETA at this time.Scope: This issue isn't affecting any specific region, but a percentage of users may be affected.Current impact to end users: Developers may not receive responses when @mentioning an app to execute an action in a Slack channel, org admins will observe delays with upcoming/planned migrations, and mobile push notifications may not deliver.Known workarounds: No known workarounds at this time. We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

5. resolved Mar 05, 2026, 09:14 PM UTC

   We're actively working to resolve the current platform functionality issues. Current status and actions being taken: We're currently working on a fix to block dispatch jobs while increasing resources to expedite processing.Estimated time to resolution: No ETA at this time.Scope: This issue isn't affecting any specific region, but a percentage of users may be affected.Current impact to end users: Developers may not receive responses when @mentioning an app to execute an action in a Slack channel, org admins will observe delays with upcoming/planned migrations, and mobile push notifications may not deliver.Known workarounds: No known workarounds at this time. We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

6. resolved Mar 05, 2026, 09:46 PM UTC

   We're actively working to resolve the current platform functionality issues. Current status and actions being taken: Our investigation continues, and we're progressing toward a fix. Estimated time to resolution: No ETA at this time.Scope: This issue isn't affecting any specific region, but a percentage of users may be affected.Current impact to end users: Developers may not receive responses when @mentioning an app to execute an action in a Slack channel, org admins will observe delays with upcoming/planned migrations, and mobile push notifications may not deliver.Known workarounds: No known workarounds at this time. We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

7. resolved Mar 05, 2026, 10:20 PM UTC

   We're actively working to resolve the current platform functionality issues. Current status and actions being taken: We've increased resources to expedite processing and are continuing to monitor the situation. We're currently observing improved health metrics.Estimated time to resolution: No ETA at this time.Scope: This issue isn't affecting any specific region, but a percentage of users may be affected.Current impact to end users: Developers may not receive responses when @mentioning an app to execute an action in a Slack channel, org admins will observe delays with upcoming/planned migrations, and mobile push notifications may not deliver.Known workarounds: No known workarounds at this time. We'll continue to provide updates every 60 minutes until the impact is resolved for all users.

8. resolved Mar 05, 2026, 11:27 PM UTC

   We're actively working to resolve the current platform functionality issues. Current status and actions being taken: Our platform is currently processing the message backlog, and we're observing improvements in our health metrics.Estimated time to resolution: No ETA at this time.Scope: This issue isn't affecting any specific region, but a percentage of users may be affected.Current impact to end users: Developers may not receive responses when @mentioning an app to execute an action in a Slack channel, org admins will observe delays with upcoming/planned migrations, and mobile push notifications may not deliver.Known workarounds: No known workarounds at this time. We'll continue to provide updates every 60 minutes until the impact is resolved for all users.

9. monitoring Mar 06, 2026, 12:35 AM UTC

   We are seeing improvements and working toward full resolution. Current status and actions being taken: We have cleared the message backlog and restored normal processing. Most activity has now completed, and the remaining work is progressing as expected. We will continue monitoring as the remaining scheduled activity runs. Estimated time to resolution: No ETA at this time.Scope: This issue isn't affecting any specific region, but a percentage of users may be affected.Current impact to end users: Developers may not receive responses when @mentioning an app to execute an action in a Slack channel, org admins will observe delays with upcoming/planned migrations, and mobile push notifications may not deliver.Known workarounds: No known workarounds at this time. We will provide the next update as we make further progress or if significant developments occur.

10. resolved Mar 06, 2026, 04:44 PM UTC

    This issue is now resolved for all users. Current status and recent actions taken: The issue is now resolved, and users should no longer be experiencing any trouble with when using app mentions, migrations, and push notifications. Enterprise Migrations should also be completing as expected.Scope: This issue wasn't affecting any specific region, but a percentage of users may have been affected globally.Previous impact to end users: Developers may have experienced issues in receiving responses when @mentioning an app to execute an action in a Slack channel, org admins may have observed delays with upcoming/planned migrations, and mobile push notifications may have failed to deliver.Required resolution steps: No steps required.We apologize for any disruptions to your day.

Read the full incident report →

Started Mar 02, 2026, 08:50 AM UTC· resolved Mar 04, 2026, 06:41 PM UTC

1. investigating Mar 02, 2026, 08:50 AM UTC

   We’ve noted that International Data Residency (IDR) users in the Middle East (Dubai) region may experience degraded search performance or search failures. Services for other users in the region are operating normally. We're aware of a vendor issue affecting multiple availability zones in the region. We are actively engaged in restoring the services as quickly as possible.

2. investigating Mar 02, 2026, 02:47 PM UTC

   Our work on this issue is still ongoing. Current status and actions being taken: International Data Residency (IDR) users continue to experience search issues due to an ongoing regional incident. We're working with a third-party vendor to restore service... We don’t have an ETA but it’s likely to take at least a day for service to be restored. We continue to monitor the situation closely and will provide updates as more information becomes available.

3. monitoring Mar 02, 2026, 10:47 PM UTC

   Our work on this issue is still ongoing. Current status and actions being taken: International Data Residency (IDR) customers continue to experience search disruptions due to a regional incident affecting our third-party provider, Amazon Web Services. This issue is related to the broader Salesforce incident currently underway. We are actively working to restore service, but there is no estimated time of recovery. Conditions at the impacted facilities, including loss of power and cooling, continue to affect progress. We are closely monitoring the situation, and will provide further updates as new information becomes available.Current impact to end users: International Data Residency (IDR) users in the Middle East (Dubai) region may experience degraded search performance or search failures. Services for other users in the region are operating normally. We continue to monitor the situation closely and will provide updates as more information becomes available.

4. investigating Mar 03, 2026, 08:30 PM UTC

   Our work on this issue is still ongoing. Current status and actions being taken: We are currently managing a severe physical infrastructure incident in the Middle East following significant damage to regional data centers. While one facility remains operational, we are continuing to work closely with AWS to resolve current data access issues and restore full service, with a major recovery milestone expected within the next 24 hours. This recovery will resolve current data access issues where some older files and database records remain temporarily unreachable. Our teams are prioritizing the restoration of missing data shards and database records as quickly as safety protocols allow. Current impact to end users: International Data Residency (IDR) users in the Middle East (Dubai) region may experience degraded search performance or search failures. Services for other users in the region are operating normally. We continue to monitor the situation closely and will provide updates as more information becomes available.

5. resolved Mar 04, 2026, 06:41 PM UTC

   This issue with a third party vendor impacts only a subset of IDR customers. Current status and recent actions taken: We are staying engaged with our International Data Residency (IDR) customers on a path to recovery. Scope: Isolated to a subset of IDR customers.Previous impact to end users: Severe degradation to services only impacting IDR customers.Required resolution steps: Remain engaged with our IDR customers until they are fully recovered.

Read the full incident report →

Started Mar 01, 2026, 02:23 PM UTC· resolved Mar 01, 2026, 08:49 PM UTC

1. investigating Mar 01, 2026, 02:23 PM UTC

   We are currently experiencing an issue with the Slack Search feature. Users may encounter errors or delays when attempting to use Search. We’re actively investigating, and will update as soon as we know more.

2. resolved Mar 01, 2026, 08:49 PM UTC

   The issue with slow or incomplete search results in Slack is now resolved for all users as of 19:53 UTC on March 1, 2026. We apologize for any disruptions to your day.

Read the full incident report →

Started Feb 25, 2026, 12:26 AM UTC· resolved Feb 25, 2026, 04:52 AM UTC

1. investigating Feb 25, 2026, 12:26 AM UTC

   We're aware of an issue where some users are unable to receive email confirmation codes and invites from Slack. As a result, these users cannot complete email login processes or accept invitations. We are currently investigating the cause. We’re actively working on multiple resolution paths. We'll provide an update in 60 minutes or sooner if additional information becomes available.

2. investigating Feb 25, 2026, 01:17 AM UTC

   Our work on this issue is still ongoing. We have seen that some emails that are not designated as ‘blocked’ are automatically being blocked. This issue persists even when these email addresses are added to specific Allow Lists. Our priority is to fully understand the technical issue behind email delivery, to enable us to restore service to customers as quickly as possible. We'll be back with another update once we have news to share.

3. investigating Feb 25, 2026, 02:33 AM UTC

   Our work on this issue continues. Our investigation has identified that emails are being blocked by a suppression list subtype where our internal suppression checks aren't aligning for certain accounts. Even when affected addresses are added to our Allow List, the issue persists.We can confirm that this issue is not a global suppression issue, and the issue relates only to those emails affected by the suppression list subtype identified.We’re actively working to identify which sending accounts are not being accurately covered by these suppression checks, and to implement a fix that will restore email delivery for our affected users.We'll be back with another update once we have news to share.

4. monitoring Feb 25, 2026, 03:26 AM UTC

   Our work on this issue continues. We've ‌further identified that the cause relates to a missing data field in our email validation system, which has been causing messages to be incorrectly blocked. We’ve developed and deployed a fix that is currently being rolled out across our infrastructure. We expect the fix to be fully deployed within the hour, when testing and validation will begin.The fix is expected to restore email services to all impacted users. We'll provide an update once the deployment is complete and we've confirmed service restoration.

5. investigating Feb 25, 2026, 04:38 AM UTC

   Our work on this issue continues. The fix deployment across all production infrastructure is expected to take a further 30 minutes. Initial testing shows that email delivery functionality working as expected following configuration changes on impacted accounts. We’ll provide a final update once full deployment and validation has been completed.

6. resolved Feb 25, 2026, 04:52 AM UTC

   Our work on this issue has concluded. We’ve tested and validated the fix deployment, and can see previously impacted accounts now receiving emails, as intended.The incident has been resolved as of 04:40 UTC, February 25This is the final update for this incident. We apologize for any inconvenience to our users for this issue.

Read the full incident report →

Started Feb 24, 2026, 02:36 PM UTC· resolved Feb 24, 2026, 07:19 PM UTC

1. investigating Feb 24, 2026, 02:36 PM UTC

   We're aware of an issue impacting direct message functionality. Users are unable to add people to multi-person direct messages, and some users are experiencing errors when attempting to send messages. We're investigating the cause and will update you as soon as we have more information.

2. monitoring Feb 24, 2026, 03:04 PM UTC

   Increased load on a messaging-related service has been identified as the cause of the issue. We have reduced the load, and are working to restore full messaging functionality. Additional capacity has also been added to prevent further impact. We’re actively monitoring performance and continuing to work to ensure full recovery. We’ll provide another update as soon as possible. Thank you for your patience and understanding.

3. investigating Feb 24, 2026, 03:24 PM UTC

   Users should now be able to add people to group direct messages and send messages. We continue to monitor the service closely to ensure ongoing stability. We’ll provide another update if there are any changes. Thank you for your patience.

4. resolved Feb 24, 2026, 07:19 PM UTC

   This issue is now resolved. Current status and recent actions taken: Further investigation of this issue has determined that Slack systems and services are operating within specifications and remain stable. Scope: Some users may have experienced issues accessing Direct Messages or Multi-person Direct Messages. Required resolution steps: No additional steps are required. We apologize for any inconvenience this brought to your day.

Read the full incident report →