Salesforce incident

Further investigation identified the need to engage the vendor. We’re working with the vendor to verify whether the target infrastructure can support the planned capacity expansion and then we can re-

Minor Resolved View vendor source →

Salesforce experienced a minor incident on June 1, 2026 affecting JPN10S and JPN12S and 1 more component, lasting 3h 52m. The incident has been resolved; the full update timeline is below.

Started
Jun 01, 2026, 07:32 AM UTC
Resolved
Jun 01, 2026, 11:24 AM UTC
Duration
3h 52m
Detected by Pingoru
Jun 01, 2026, 07:32 AM UTC

Affected components

JPN10SJPN12SJPN132JPN134JPN136JPN138JPN140JPN142JPN144JPN146

Update timeline

  1. identified Jun 01, 2026, 07:32 AM UTC

    Degradation Started: featureServiceDisruption

  2. monitoring Jun 01, 2026, 08:05 AM UTC

    We’re investigating intermittent failures affecting Einstein Translator through the Einstein Trust Layer that may cause internal server errors when submitting translation requests. We identified a capacity constraint as a contributing factor, and have initiated redeployment actions and refreshed impacted services to help restore service stability. We're actively monitoring service health and error rates as we continue to assess recovery. Our investigations also determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this. We'll provide an update in 30 minutes or sooner if additional information becomes available.

  3. monitoring Jun 01, 2026, 08:53 AM UTC

    Our efforts to increase capacity on the underlying model-serving infrastructure encountered deployment-related issues. We are working on pre-checks before initiating a new deployment. We will share an update once we have additional information on recovery efforts.

  4. monitoring Jun 01, 2026, 10:39 AM UTC

    Further investigation identified the need to engage the vendor. We’re working with the vendor to verify whether the target infrastructure can support the planned capacity expansion and then we can re-initiate the deployment to restore the service. We will provide an update if new information becomes available.