Salesforce incident

Our investigations have highlighted that the impact radius is broader than initially understood. Please refer to https://status.salesforce.com/generalmessages/20000254 for all further communications a

Resolved after 4 hours 52 minutes, affecting CAN50 and CS238 and 1 more, on May 21, 2026.

monitoring May 22, 2026, 12:37 AM UTC

Our investigations have highlighted that the impact radius is broader than initially understood. Please refer to https://status.salesforce.com/generalmessages/20000254 for all further communications about this issue. We sincerely apologise for how this issue has impacted you and your business.

Started
May 21, 2026, 10:02 PM UTC
Resolved
May 22, 2026, 02:54 AM UTC
Duration
4h 52m
Detected by Pingoru
May 21, 2026, 10:02 PM UTC

Affected components

CAN50CS238CS240CS244CS245CS249CS254CS257CS259CS260

Update timeline

  1. identified May 21, 2026, 10:02 PM UTC

    Disruption Started: serviceDisruption

  2. monitoring May 21, 2026, 10:02 PM UTC

    We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.

  3. monitoring May 21, 2026, 10:30 PM UTC

    At 20:00 UTC on May 21, 2026, a feature disruption began impacting the Salesforce Core Service in the NA223 instance. As a result, customers may be experiencing intermittent disruptions and degradations due to instability. We are engaged and are actively analyzing the issue to determine a mitigation pathway. We'll provide an update in 30 minutes or sooner if additional information becomes available.

  4. monitoring May 21, 2026, 11:15 PM UTC

    We’ve identified a recent networking patch as the potential trigger. Some customers attempting to log in via login.salesforce.com or test.salesforce.com may be experiencing issues. We’ve initiated a reboot of impacted networking hosts as a possible solution. The team continues to analyze the trigger and explore additional remediation pathways. We'll provide an update in 30 minutes or sooner if additional information becomes available.

  5. monitoring May 21, 2026, 11:16 PM UTC

    Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.

  6. monitoring May 22, 2026, 12:37 AM UTC

    Our investigations have highlighted that the impact radius is broader than initially understood. Please refer to https://status.salesforce.com/generalmessages/20000254 for all further communications about this issue. We sincerely apologise for how this issue has impacted you and your business.

Your product runs on more than Salesforce

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →