Kode Health

Warn

Salesforce

We’ve validated the fix, and it’s now progressing through our deployment build pipeline. We expect this process to take approximately three to four hours. Once complete, we'll perform a final round of validation before rolling out the fix to all affected customers. Upon further investigation, we have determined that the start time of the impact is earlier than initially understood. We have now revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We'll provide an update upon completion of the fix or if significant information becomes available.

Last update on May 11, 2026 5:10 PM

Warn

Blacksmith

We implemented a fix and are re-queuing jobs in the backlog

Last update on May 11, 2026 5:10 PM

Warn

Slack

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.

Last update on May 11, 2026 5:10 PM

Warn

Intercom

Update: Continuing investigation Our investigation continues with support from independent external security partners. We continue to find no evidence of unauthorised access to customer data or Intercom accounts. All Intercom services remain fully operational. You are only potentially affected if your developers installed intercom-client@7.0.4 (npm) or intercom-php@5.0.2 during the affected window on April 30. The compromised package versions (intercom-client@7.0.4 and intercom-php@5.0.2) remain removed. Safe versions: intercom-client@7.0.3 and intercom-php@5.0.1. If you do not use these developer packages to interact with the Intercom REST API, you are not impacted. We are keeping this incident open while we complete our remediation and investigation. We will update this page when we are ready to close it out.

Last update on May 11, 2026 5:12 PM